Re: Nashville

[Rodney Joffe]

Politico photo seems to have been filtered or dropped. 2nd Attempt:

https://www.politico.com/news/2020/12/25/explosion-downtown-nashville-450448

> On Dec 25, 2020, at 2:42 PM, Rodney Joffe  wrote:
> 
> It seems to be here:
> 
> https://www.google.com/maps/@36.1645601,-86.7768622,3a,60y,145.84h,88.19t/data=!3m6!1e1!3m4!1sqJHVrYi75RWSsuTlBGAg6g!2e0!7i16384!8i8192
> 
> Here’s a link to a photo on Politico that matches:
> 
> Note: Hooters sign on left.
> 
>> On Dec 25, 2020, at 2:33 PM, Andy Ringsmuth  wrote:
>> 
>> Definitely was not at that intersection.
>> 
>> https://www.youtube.com/watch?v=5nygTJeu9fU
>> 
>> That’s security camera footage from about 154 2nd Ave. The AT building is 
>> across the street to the right.
>> 
>> Commerce Street is a block to the left.
>> 
>> 
>> Andy Ringsmuth
>> 5609 Harding Drive
>> Lincoln, NE 68521-5831
>> (402) 304-0083
>> a...@andyring.com
>> 
>> “Better even die free, than to live slaves.” - Frederick Douglas, 1863
>> 
>>> On Dec 25, 2020, at 1:26 PM, cosmo  wrote:
>>> 
>>> The internet is buzzing with speculation about this. According to CNN the 
>>> RV was at 2nd and Commerce st, which puts it 1-block away from the ATT 
>>> building. If it were the target, I'd imagine they would have parked it 
>>> closer.
>>> 
>>> https://www.google.com/maps/search/2nd+and+congress+nashville/@36.1631367,-86.776487,18.42z
>>> 
>>> On Fri, Dec 25, 2020 at 11:20 AM Andy Ringsmuth  wrote:
>>> Certainly thankful no serious injuries or fatalities in this clusterblank.
>>> 
>>> It seems the AT building at 185 2nd Ave N may have been a target, which 
>>> would explain the timing (holiday morning when no one is out, as opposed to 
>>> a holiday evening when there would be mass casualties). A little curious 
>>> what that building has. Is it just a big co-lo place? Regional CLEC/ILEC? 
>>> 
>>> No earth-shattering revelations here. Admittedly just bored on a slow 
>>> Christmas Day when my wife is at work (nurse) and kid is playing with a new 
>>> tablet and I’m just watching the news trying to understand/figure out a 
>>> little what and why.
>>> 
>>> 
>>> Andy Ringsmuth
>>> 5609 Harding Drive
>>> Lincoln, NE 68521-5831
>>> (402) 304-0083
>>> a...@andyring.com
>>> 
>>> “Better even die free, than to live slaves.” - Frederick Douglas, 1863
>>> 
>> 
> 

Re: Nashville

[Rodney Joffe]

It seems to be here:

https://www.google.com/maps/@36.1645601,-86.7768622,3a,60y,145.84h,88.19t/data=!3m6!1e1!3m4!1sqJHVrYi75RWSsuTlBGAg6g!2e0!7i16384!8i8192

Here’s a link to a photo on Politico that matches:

Note: Hooters sign on left.

> On Dec 25, 2020, at 2:33 PM, Andy Ringsmuth  wrote:
> 
> Definitely was not at that intersection.
> 
> https://www.youtube.com/watch?v=5nygTJeu9fU
> 
> That’s security camera footage from about 154 2nd Ave. The AT building is 
> across the street to the right.
> 
> Commerce Street is a block to the left.
> 
> 
> Andy Ringsmuth
> 5609 Harding Drive
> Lincoln, NE 68521-5831
> (402) 304-0083
> a...@andyring.com
> 
> “Better even die free, than to live slaves.” - Frederick Douglas, 1863
> 
>> On Dec 25, 2020, at 1:26 PM, cosmo  wrote:
>> 
>> The internet is buzzing with speculation about this. According to CNN the RV 
>> was at 2nd and Commerce st, which puts it 1-block away from the ATT 
>> building. If it were the target, I'd imagine they would have parked it 
>> closer.
>> 
>> https://www.google.com/maps/search/2nd+and+congress+nashville/@36.1631367,-86.776487,18.42z
>> 
>> On Fri, Dec 25, 2020 at 11:20 AM Andy Ringsmuth  wrote:
>> Certainly thankful no serious injuries or fatalities in this clusterblank.
>> 
>> It seems the AT building at 185 2nd Ave N may have been a target, which 
>> would explain the timing (holiday morning when no one is out, as opposed to 
>> a holiday evening when there would be mass casualties). A little curious 
>> what that building has. Is it just a big co-lo place? Regional CLEC/ILEC? 
>> 
>> No earth-shattering revelations here. Admittedly just bored on a slow 
>> Christmas Day when my wife is at work (nurse) and kid is playing with a new 
>> tablet and I’m just watching the news trying to understand/figure out a 
>> little what and why.
>> 
>> 
>> Andy Ringsmuth
>> 5609 Harding Drive
>> Lincoln, NE 68521-5831
>> (402) 304-0083
>> a...@andyring.com
>> 
>> “Better even die free, than to live slaves.” - Frederick Douglas, 1863
>> 
> 

RFC 2468

[Rodney Joffe]

It is especially fitting whenever the NANOG/ARIN joint meetings occur in the 
same week that we “remember IANA”.

As time has gone on, fewer and fewer of us actually know who J. Postel is - 
that name that appears at the end of so many RFC’s we refer to every day. The 
same person who also guided the management of names and numbers in the “early” 
days of this grand experiment we’re still struggling to get “right”.

Today (Friday, October 16) is 22 years since Jon Postel passed away. I won’t 
start to list the rest of the pioneers we’ve lost since then - its obviously 
getting longer and longer. But I think its worth pointing “newcomers" at Vint’s 
RFC2468 (https://tools.ietf.org/rfc/rfc2468.txt) as the starting point for them 
(you) to understand the importance of Jon’s legacy as a moral compass to help 
guide some of the decisions being made or ignored during this week. And 
obviously other weeks and decisions that follow.

Jon was my mentor, colleague, business partner, and friend. And along with his 
other friends still on this list, I miss him a lot. It hasn’t been the same 
without him.

/rlj

Shining a light on ambulance chasers - Noction

[Rodney Joffe]

Under the heading of sales spam from our community that is in even poorer 
taste, and sucks:


Begin forwarded message:

> From: Josh Ankin 
> Subject: BGP Management
> Date: March 25, 2020 at 3:39:02 PM EDT
> To: rjo...@centergate.com
> Reply-To: jan...@noction.com
> 
> Hello Rodney,
>  
> I know things are pretty hectic right now with COVID-19 precautions being 
> taken everywhere. I hope it's not affecting your team too much, and most 
> importantly, I hope everyone is safe.
>  
> In recent months, I've been trying to bring your attention to BGP 
> optimization. However, our solution's other notable features can be of utmost 
> value at these uncertain times as the Internet traffic volumes and patterns 
> change

Etc Etc

Its hard to believe that it has been 21 years...

[Rodney Joffe]

Twenty-one years ago today, Jon Postel passed away in Santa Monica, CA.

Almost all of us get to do what we do today, because of his vision, guidance, 
and leadership. He is one of many giants on whose shoulders we stand today 
(some are still active here in NANOG), but he was the compass that guided most 
of us.

For those of you who are too young to recognize his name, or don’t realize who 
that " J. Postel" is at the end of all of those RFCs you look at and quote:

https://www.ietf.org/rfc/rfc2468.txt

https://en.wikipedia.org/wiki/Jon_Postel

https://www.internetsociety.org/grants-and-awards/postel-service-award/ten-year-tribute-jon-postel/

/rlj

It's been 20 years today (Oct 16, UTC). Hard to believe.

[Rodney Joffe]

At NANOG two weeks ago, we had an interesting discussion at one of the lunch 
tables. One of the subjects we discussed was the original IANA, and RFC Editor, 
Jon Postel.

Seven of the ten people at the table had never heard of him. Maybe these days 
it no longer matters who he was, and what he meant to where we are today.



For those who care about the history of the Internet, and routing and 
addressing. And protocols…

https://tools.ietf.org/html/rfc2468

Oct 16, 1998.

Re: Oct. 3, 2018 EAS Presidential Alert test

[Rodney Joffe]

Weirdly, I received 3. One of them is both French/English.

More weirdly i am in the air, on the way from Nanog Vancouver to Denver. We 
were still in Canada airspace, and my AT phone showed clearly “no service”. 
The phone was NOT on wi-fi.

Screen captures if anyone wants.

> On Oct 3, 2018, at 11:52 AM, Andy Ringsmuth  wrote:
> 
> Did anyone on AT or an iPhone receive the test today? I believe it was 
> supposed to happen at 2:18 EDT, followed by one on broadcast radio at 2:20 
> EDT.
> 
> I’m in CDT, so 1:18 and 1:20 p.m. CDT.
> 
> Message was heard on my desk radio at 1:21:35 p.m. CDT but as of the sending 
> of this at 1:52 p.m. CDT, nothing on phones. I have an office full of AT 
> iPhones and not a single one of them alerted.
> 
> FEMA says https://www.fema.gov/emergency-alert-test
> 
> "Cell towers will broadcast the WEA test for approximately 30 minutes 
> beginning at 2:18 p.m. EDT. During this time, WEA compatible cell phones that 
> are switched on, within range of an active cell tower, and whose wireless 
> provider participates in WEA should be capable of receiving the test message. 
> Some cell phones will not receive the test message, and cell phones should 
> only receive the message once."
> 
> My wife, with a Sprint iPhone, received the test.
> 
> 
> 
> Andy Ringsmuth
> 5609 Harding Drive
> Lincoln, NE 68521-5831
> (402) 304-0083
> a...@andyring.com
> 

Re: What are people using for IPAM these days?

[Rodney Joffe]

> On Jun 12, 2018, at 8:36 PM, Stephen Satchell  wrote:
> 
> On 06/12/2018 08:26 PM, valdis.kletni...@vt.edu wrote:
>>> emacs!
>> vim!
> ed!
 TECO!
>>> cat
>> IBM 029.
> 
> Youngster.  IBM 026.

Infants!  Hollerith (IBM Type 1). I still own it.

Re: ICANN GDPR lawsuit

[Rodney Joffe]

> On Jun 1, 2018, at 10:21 AM, niels=na...@bakker.net wrote:
> 
> * l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
>> How does your shop, Niels, go about making contact with an operator that is 
>> hijacking one of your netblocks, or is doing something weird with routing 
>> that is causing your customers problems, or has broken BGP?
> 
> The same as we do now, by posting on NANOG "Can someone from ASx / 
> largetelco.com contact me offlist?”

Seriously? You’ve been around long enough to know thats a bull$&^% answer. 

Feel free to look through the archives of *this* list and look at how many 
times some $random handle at some $random privacy protected or generic domain 
asks for someone from $bignetwork to contact them about a network problem.

Take you for example. You’ve been around for at least 15-20 years that I 
recall. But I bet you that 80% of the people on NANOG have *no* idea who you 
are or who you work for, and given the “useful" information on your website, an 
op would have to take the time to google you - which is way above the threshold 
of effort most people would take.

And that preassumes that the ops from the tiny little network leaking your 
routes is actually a) subscribed here, and b) monitoring or filtering 
appropriately. And before you talk about the fact you stated “ 
largetelco(dot)com” I would bet that there are large telco’s who don’t have 
op’s like us who waste their time on NANOG.

So, instead of the suggestion you provided, do you have any other suggestions 
that are useful? I’m asking seriously, because I really do see this as a 
problem we all have to be able to solve as operators. I believe this is 
absolutely on-topic for one of the NANOG lists because this is a 100% 
operational problem, that has appears to have as its only GDPR acceptable 
solution alternative, following a manual/email thread from *your* next hop 
network, requesting contacts/intros all the way down to the dumba$$ BGP 
speaking edge network with a part-time routing guy/antenna installer.

/rlj

19 years ago today (Oct 16th, 1998) we lost our guide - Jon Postel - RFC2468

[Rodney Joffe]

To us greaybeards, it feels like just yesterday. And as Randy points out, this 
coming Friday we also remember Abha who passed away 16 years ago, in 2001. 
http://www.neebu.net/~khuon/abha/

Sigh.

Re: Vendors spamming NANOG attendees

[Rodney Joffe]

I guess that explains why so many newcomers are confused about what spam is. 

> On Jun 14, 2017, at 5:33 AM, Ge Dupin <gdu...@taho.fr> wrote:
> 
> It looks like there are more spams coming from these discussions than from 
> the original Scams/Spams..
> Ge
> 
>>> Le 14 juin 2017 à 14:26, Rodney Joffe <rjo...@centergate.com> a écrit :
>>> 
>>> 
>>> 
>>> On Jun 13, 2017, at 10:28 PM, Mel Beckman <m...@beckman.org> wrote:
>>> 
>>> But as I said, harvesting emails is not illegal under can spam. And the 
>>> requirement to not send you UCE to harvested emails is pointless, because 
>>> how do you prove that someone did that?
>>> 
>> Because he said so?
>> 
>>>>>> The spammer had the balls to say, in his email:
>>>>>> 
>>>>>>> 
>>>>>>> We do not know each other. I'm leveraging the attendee list for NANOG 
>>>>>>> to reach out and raise awareness of the value of OCS (Optical Circuit 
>>>>>>> Switching) in the data center and in particular, the Carrier Neutral 
>>>>>>> Hotel where we've been active with next generation MeetMeRoom 
>>>>>>> discussions.
>> 
>> 
> 

Re: Vendors spamming NANOG attendees

[Rodney Joffe]

> On Jun 13, 2017, at 10:28 PM, Mel Beckman  wrote:
> 
> But as I said, harvesting emails is not illegal under can spam. And the 
> requirement to not send you UCE to harvested emails is pointless, because how 
> do you prove that someone did that?
> 
Because he said so?

 The spammer had the balls to say, in his email:
 
> 
> We do not know each other. I'm leveraging the attendee list for NANOG to 
> reach out and raise awareness of the value of OCS (Optical Circuit 
> Switching) in the data center and in particular, the Carrier Neutral 
> Hotel where we've been active with next generation MeetMeRoom discussions.

Re: Vendors spamming NANOG attendees

[Rodney Joffe]

> On Jun 13, 2017, at 8:31 AM, Mel Beckman <m...@beckman.org> wrote:
> 
> Rodney,
> 
> You said "I see something every couple of months that I can track back to 
> NANOG, or ARIN."
> 
> I would hardly call this a flood. But my point is that most people posting to 
> NANOG, being technical people, respond to notifications that they are 
> spamming. Your example email illustrates this perfectly. Sometimes they're 
> ignorant and don't realize they're spamming. If they're persistent they get 
> removed from the list (I don't think that has had to happen for several 
> years).
> 
> The remaining spammers are easily caught by filters, as you can plainly see.
> 
> I don't see your need for urgency, and you still haven't said what you 
> propose as a better arrangement. I made my suggestion. What's yours?

I'm one of 10,000. I assume others see as many as I do (I have no idea how many 
get caught in my filters).

I don't recall calling this a flood. Did I? And I don't believe he is on the 
list so there's no way to "remove" him.  I think the list does a good job over 
time "training" subscribers. 

But I did say that if others don't respond to spammers to this list from 
vendors, it will become a problem. The list is fertile ground. And I'm not sure 
that Sterns response indicates any awareness. He admitted he used the 1,300 
person attendee list as a prospecting tool. 

So all that I am suggesting is that others take the time to respond to spam 
from vendors (as I did) rather than ignoring it (just hitting delete doesn't 
work out in the long run). I have to assume that after a reasonable number of 
people do complain to his company, they'll learn. And others on the list who 
are tempted, change their minds.  I don't think the list itself per se suffers 
from a spam problem - although my 3 emails probably qualify as too much noise 
already. But it is vendors who use the list to prospect who should be 
discouraged.

Btw I have no doubt that rogue salesmen from my companies over the years have 
tried it once. When I find out about it, I do kick butts.

I'm hoping that this discussion is enough to get Calient to rethink their 
strategy.  For crying out loud, the guy is a VP in their company. What kind of 
example is that?

I'll end my public noise here :-)

Rodney




> 
> -mel 
> 
>> On Jun 13, 2017, at 8:19 AM, Rodney Joffe <rjo...@centergate.com> wrote:
>> 
>> 
>>> On Jun 13, 2017, at 9:02 AM, Mel Beckman <m...@beckman.org> wrote:
>>> 
>>> Rodney,
>>> 
>>> What do you suggest? Shoot them at Dawn? :-) 
>>> 
>>> The standard warning and education has always been adequate in the past. We 
>>> don't have a runaway spamming problem on the list.
>> 
>> What standard warning and education?
>> 
>> We have filters to stop spam making it to the list.
>> 
>> But there is definitely a spamming problem of sorts amongst vendors, to 
>> subscriber addresses. 
>> 
>> I see something every couple of months that I can track back to NANOG, or 
>> ARIN.
>> 
>> What I *know* is that if you open the door, and ignore it with vendors on 
>> NANOG, the list members will end up having a problem. If you want to know 
>> why I consider myself an expert, feel free to ask me offline about what the 
>> attitude that those of us who ran "the backbone" in 1994 had - and how that 
>> worked out.
>> 
>> On the other hand, as a senior citizen, at the end of my tech days, with 
>> enable grudgingly given up, I guess I could turn away and say "not my 
>> problem, really".
>> 
>> YMMV.
>>> 
>>> -mel beckman
>>> 
>>>> On Jun 13, 2017, at 6:00 AM, Rodney Joffe <rjo...@centergate.com> wrote:
>>>> 
>>>> It seems that more than just a few of us were spammed by Glenn Stern 
>>>> (gst...@calient.net), an employee of Calient following NANOG 70.
>>>> 
>>>> The spammer had the balls to say, in his email:
>>>> 
>>>>> 
>>>>> We do not know each other. I'm leveraging the attendee list for NANOG to 
>>>>> reach out and raise awareness of the value of OCS (Optical Circuit 
>>>>> Switching) in the data center and in particular, the Carrier Neutral 
>>>>> Hotel where we've been active with next generation MeetMeRoom discussions.
>>>> 
>>>> He does not show as an attendee at NANOG, but another executive, David 
>>>> Altstaetter, daltstaet...@calient.net did register, and may have even 
>>>> shown up. Hopefully those of you who have traditional community attitudes 
>>>> will show your reaction via your pocketbooks.
>>>> 
>>>> Maybe its time for the NANOG board and staff to step in, and develop some 
>>>> teeth to use in cases like these? Unless the majority of you members are 
>>>> cool with unfettered spamming of member and attendee lists. In which case, 
>>>> have at it!
>>>> 
>>>> Rodney
>> 

Re: Vendors spamming NANOG attendees

[Rodney Joffe]

> On Jun 13, 2017, at 9:02 AM, Mel Beckman <m...@beckman.org> wrote:
> 
> Rodney,
> 
> What do you suggest? Shoot them at Dawn? :-) 
> 
> The standard warning and education has always been adequate in the past. We 
> don't have a runaway spamming problem on the list.

What standard warning and education?

We have filters to stop spam making it to the list.

But there is definitely a spamming problem of sorts amongst vendors, to 
subscriber addresses. 

I see something every couple of months that I can track back to NANOG, or ARIN.

What I *know* is that if you open the door, and ignore it with vendors on 
NANOG, the list members will end up having a problem. If you want to know why I 
consider myself an expert, feel free to ask me offline about what the attitude 
that those of us who ran "the backbone" in 1994 had - and how that worked out.

On the other hand, as a senior citizen, at the end of my tech days, with enable 
grudgingly given up, I guess I could turn away and say "not my problem, really".

YMMV.
> 
> -mel beckman
> 
>> On Jun 13, 2017, at 6:00 AM, Rodney Joffe <rjo...@centergate.com> wrote:
>> 
>> It seems that more than just a few of us were spammed by Glenn Stern 
>> (gst...@calient.net), an employee of Calient following NANOG 70.
>> 
>> The spammer had the balls to say, in his email:
>> 
>>> 
>>> We do not know each other. I'm leveraging the attendee list for NANOG to 
>>> reach out and raise awareness of the value of OCS (Optical Circuit 
>>> Switching) in the data center and in particular, the Carrier Neutral Hotel 
>>> where we've been active with next generation MeetMeRoom discussions.
>> 
>> He does not show as an attendee at NANOG, but another executive, David 
>> Altstaetter, daltstaet...@calient.net did register, and may have even shown 
>> up. Hopefully those of you who have traditional community attitudes will 
>> show your reaction via your pocketbooks.
>> 
>> Maybe its time for the NANOG board and staff to step in, and develop some 
>> teeth to use in cases like these? Unless the majority of you members are 
>> cool with unfettered spamming of member and attendee lists. In which case, 
>> have at it!
>> 
>> Rodney
>> 

Vendors spamming NANOG attendees

[Rodney Joffe]

It seems that more than just a few of us were spammed by Glenn Stern 
(gst...@calient.net), an employee of Calient following NANOG 70.

The spammer had the balls to say, in his email:

> 
>  We do not know each other. I'm leveraging the attendee list for NANOG to 
> reach out and raise awareness of the value of OCS (Optical Circuit Switching) 
> in the data center and in particular, the Carrier Neutral Hotel where we've 
> been active with next generation MeetMeRoom discussions.

He does not show as an attendee at NANOG, but another executive, David 
Altstaetter, daltstaet...@calient.net did register, and may have even shown up. 
Hopefully those of you who have traditional community attitudes will show your 
reaction via your pocketbooks.

Maybe its time for the NANOG board and staff to step in, and develop some teeth 
to use in cases like these? Unless the majority of you members are cool with 
unfettered spamming of member and attendee lists. In which case, have at it!

Rodney

Re: 18 years ago today - rfc 2468

[Rodney Joffe]

To be clear - Oct 16. Which has just tolled in the APAC region. For most of you 
it will be tomorrow. But no matter. You get the point. 

> On Oct 15, 2016, at 9:08 AM, Rodney Joffe <rjo...@centergate.com> wrote:
> 
> How time flies

18 years ago today - rfc 2468

[Rodney Joffe]

How time flies

Re: i hate october

[Rodney Joffe]

Though fewer and fewer of us remember them and why it sucks. 

Sigh. RFC2468. I can't believe I missed my midnight reminder on the list. 

> On Oct 16, 2015, at 7:57 AM, Randy Bush  wrote:
> 
> jon postel died this day in 1988
> abha ahuja next tuesday
> itojun the 29th
> 
> arrrgh

Re: Looking for ATT (Wireless) to contact me off-list.

[Rodney Joffe]

On Mar 18, 2015, at 9:26 AM, Eric Sieg eric.s...@gmail.com wrote:

 

Speaking as an unaffiliated, irrelevant, old-timer, but hoping to assist you 
and all of those who have preceded you and who will no doubt follow you, I have 
generally found that providing your affiliation and context sometimes helps 
solicit a response, especially when sending a plain email from a gmail account.

And sometimes, of course, it hurts ;-)

Re: Comcast thinks it ok to install public wifi in your house

[Rodney Joffe]

Randy,

You're spot on. I don't understand this griping. The flip side is that as a(n) 
happy xfinity customer I get to roam in lots of places around the US (and maybe 
even abroad),  as do all of the xfinity home customers. This isn't a paid 
service... It's a byproduct of being a cable customer. I'm happy to pay a few 
pennies a day. 

The only challenge I see is the issue around wifi congestion. In my DC condo 
building there are a couple of hundred xfinity cable modem customers, mostly 
with wifi. However, with a little bit of work with the comcast techs, our 
neighborhood is pretty happy. Tip of the hat to Jason and Mike O'. 



 On Dec 11, 2014, at 12:01 PM, Randy Bush ra...@psg.com wrote:
 
 darn.  i shoulda used a comcast cable modem instead of my own so i could
 provide this service to neighbors.  ah well.  i do put up a non-wpa
 ssid, but don't like the non-wpa.
 
 randy

Sigh. 16 years ago today.

[Rodney Joffe]

https://www.ietf.org/rfc/rfc2468.txt

Re: RIPE Database Proxy Service Issues

[Rodney Joffe]

Hell Axel,

On Jan 2, 2013, at 11:00 AM, Axel Pawlik ripencc-managem...@ripe.net wrote:

 [Apologies for duplicate emails]
 
 Dear colleagues,
 
 There has been discussion on various mailing lists regarding the status of 
 the RIPE Database Proxy Service.
 

 We do apologise, however, that the changes regarding the proxy service were 
 not more explicitly communicated to the members and the RIPE community in 
 advance of the final publication of the Activity Plan.


Not being members, we obviously were not privy to these discussions or 
decisions. Not your fault, of course, just a reality.


 
 The RIPE NCC asks that non-RIPE NCC member proxy service users become members 
 but we propose to waive their membership fee until the discussion of the RIPE 
 NCC Charging Scheme 2014 takes place. This will give the membership and 
 community the opportunity to discuss the best way forward for the proxy 
 service in the coming months while ensuring a strong contractual bond between 
 the RIPE NCC and users of this service.
 
 In the meantime, there will be no changes to the proxy service and no loss of 
 functionality for the community.

I appreciate the decision and accommodation… And I am sure the community 
appreciates it. As users have no doubt realized, the proxy data continued to be 
available after Dec 31. We were waiting to see what the DENIED output looked 
like before we implemented our changes, so there was no impact. This too is 
appreciated.

And thank you to the many community and RIPE members who offered and provided 
assistance and support.

Thank you.

Rodney Joffe
CenterGate Research/GeekTools

GeekTools Whois Proxy and RIPE/RIPE-NCC

[Rodney Joffe]

NANOG and ARIN Friends,

14 Years ago, at the suggestion of Jon Postel and some of the early 
participants in NANOG, we developed the GeekTools Whois proxy to make it easier 
for *us* - network security and abuse techs - to deal with the expanding number 
of gtlds and registrars and the varied whois servers that were appearing. The 
service had both a CLI and  web interface.

The service also led directly to the creation of whois-servers.net, which now 
seems to be part of a number of *nix distributions.

The service has been up for 14 years, and over that time we have fulfilled the 
requirements of all of the whois server operators in regards to minimizing and 
stopping abuse of the GT whois proxy by domain scrapers, spammers, etc, while 
enabling the security folks to do their jobs. In some cases we have even 
written code to pass the ip address of the requestor to the whois server 
registry operator when they wanted to manage quota's directly. We think we have 
a really good relationship with all of the whois server operators, and I think 
we provide a useful service to the community, and is widely used. And in 14 
years we have never been tarred as an enabler of abuse of the whois system.

There has obviously never been any kind of charge or fee for using the proxy, 
or any of the other tools on GeekTools. In about 2002 we started placing a 
banner ad on the web interface page to offset some of the costs for the 
bandwidth that the proxy consumes. An average of about $70 a month for over the 
last 10 years. Actual bandwidth costs are higher than that of course, but it 
was a thought in 2002 that we had frankly forgotten about until recently.

Two weeks ago RIPE-NCC, who provide the whois data for IP addresses in the RIPE 
region, informed us that based on decisions by their members, as of January 1st 
2013, tomorrow, they would no longer provide whois proxy query response 
services to GeekTools unless we ponied up $1,800 a year for RIPE membership.

I don't work very well above layer 7. It is what it is. So I wanted to let you 
know that as of midnight tonight, apparently, you won't be able to use 
GeekTools for RIPE related queries. If you have automated scripts, and you are 
one of the users who has expanded access to GeekTools, you'll need to find an 
alternative for RIPE queries *today*. My guess is that you will be able to 
query RIPE directly, once you have worked out that the address space is within 
RIPE's assignments.

I think its wrong to have to pay for whois data that is part of a community 
resource . So I won't do it.

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: GeekTools Whois Proxy and RIPE/RIPE-NCC

[Rodney Joffe]

Hi David,

On Dec 31, 2012, at 10:55 AM, David Conrad d...@virtualized.org wrote:

 Rodney,
 
 On Dec 31, 2012, at 7:41 AM, Rodney Joffe rjo...@centergate.com wrote:
 Two weeks ago RIPE-NCC, who provide the whois data for IP addresses in the 
 RIPE region, informed us that based on decisions by their members, as of 
 January 1st 2013, tomorrow, they would no longer provide whois proxy query 
 response services to GeekTools unless we ponied up $1,800 a year for RIPE 
 membership.
 ...
 I think its wrong to have to pay for whois data that is part of a community 
 resource . So I won't do it.
 
 I have to assume there is some sort of misunderstanding here as the actions 
 on behalf of RIPE you describe are ... surprising.  However, if there isn't a 
 misunderstanding then I strongly agree with you. 
 
 I'll be interested in seeing RIPE's side of the story…

I am absolutely open to believing that I have misunderstood. The older I've 
gotten, the dumber I've realized I am ;-)

The references I can provide (besides the notice from RIPE which you already 
have) appear to be:

http://www.ripe.net/ripe/docs/ripe-558 , specifically 2.4.7 RIPE Database Proxy 
Service

/rlj

Re: GeekTools Whois Proxy and RIPE/RIPE-NCC

[Rodney Joffe]

Hi Job,

On Dec 31, 2012, at 11:46 AM, Job Snijders job.snijd...@atrato-ip.com wrote:

 Hi Rodney,
 
 From the looks of it, this decision was made by the RIPE NCC Executive Board 
 rather than at the General Meeting.  Inqueries will have to be made why this 
 was decided, and what the consequences are. But, I don't expect a resolution 
 to be reached in the next 6 hours. 


I don't expect it to be resolved in any different way at all, based on my 
experience over the last 20 years. We're not a RIPE member, so we have *zero* 
influence, and relevance for the RIP-NCC board.


 In the meantime you could consider setting up an irrd[1], redirect queries to 
 that instance instead of whois.ripe.net, and keep it kind of fresh by feeding 
 it ftp://ftp.ripe.net/ripe/dbase/ripe.db.gz on a daily basis. 


As far as bulk data, one *really* important aspect of GeekTools from day 1, is 
that we do not provide any actual data, we *only* proxy data. So there is no 
possibility that at any time we have stale data. We are a proxy, not a provider 
of data. Its what Jon told me to do 14 years ago, and its what we have stuck to 
(I think we're the only whois proxy that has done this).

If we give you an answer today, you can count on it being the authoritative 
answer as of this second. If we can't reach a whois server when you query us, 
we do *not* give you a cached answer. We store nothing.  Important when chasing 
miscreants or problems.

I don't want to change this.


 
 Kind regards,
 
 Job
 
 [1] http://www.irrd.net/
 
 On Dec 31, 2012, at 4:41 PM, Rodney Joffe rjo...@centergate.com wrote:
 
 NANOG and ARIN Friends,
 
 14 Years ago, at the suggestion of Jon Postel and some of the early 
 participants in NANOG, we developed the GeekTools Whois proxy to make it 
 easier for *us* - network security and abuse techs - to deal with the 
 expanding number of gtlds and registrars and the varied whois servers that 
 were appearing. The service had both a CLI and  web interface.
 
 The service also led directly to the creation of whois-servers.net, which 
 now seems to be part of a number of *nix distributions.
 
 The service has been up for 14 years, and over that time we have fulfilled 
 the requirements of all of the whois server operators in regards to 
 minimizing and stopping abuse of the GT whois proxy by domain scrapers, 
 spammers, etc, while enabling the security folks to do their jobs. In some 
 cases we have even written code to pass the ip address of the requestor to 
 the whois server registry operator when they wanted to manage quota's 
 directly. We think we have a really good relationship with all of the whois 
 server operators, and I think we provide a useful service to the community, 
 and is widely used. And in 14 years we have never been tarred as an enabler 
 of abuse of the whois system.
 
 There has obviously never been any kind of charge or fee for using the 
 proxy, or any of the other tools on GeekTools. In about 2002 we started 
 placing a banner ad on the web interface page to offset some of the costs 
 for the bandwidth that the proxy consumes. An average of about $70 a month 
 for over the last 10 years. Actual bandwidth costs are higher than that of 
 course, but it was a thought in 2002 that we had frankly forgotten about 
 until recently.
 
 Two weeks ago RIPE-NCC, who provide the whois data for IP addresses in the 
 RIPE region, informed us that based on decisions by their members, as of 
 January 1st 2013, tomorrow, they would no longer provide whois proxy query 
 response services to GeekTools unless we ponied up $1,800 a year for RIPE 
 membership.
 
 I don't work very well above layer 7. It is what it is. So I wanted to let 
 you know that as of midnight tonight, apparently, you won't be able to use 
 GeekTools for RIPE related queries. If you have automated scripts, and you 
 are one of the users who has expanded access to GeekTools, you'll need to 
 find an alternative for RIPE queries *today*. My guess is that you will be 
 able to query RIPE directly, once you have worked out that the address space 
 is within RIPE's assignments.
 
 I think its wrong to have to pay for whois data that is part of a community 
 resource . So I won't do it.
 
 -- 
 AS5580 - Atrato IP Networks
 
 
 
 

Update: Re: GeekTools Whois Proxy and RIPE/RIPE-NCC

[Rodney Joffe]

So we think we're working out the impact, and have a work-around for users.

There seem to be more than a few hundred network operations groups (thats many 
of you on NANOG) that use GeekTools (we can tell by the NAT IP addresses, and 
the rate of queries) that will be affected. It seems that what RIPE is doing is 
removing the ability for us to query their whois server using the special 
format that passes your ip address to RIPE in our queries that go to them. 
This was how they satisfied themselves that if *you* were abusing the query 
limit, and we had not caught it, and were not already preemptively blocking you 
or rate limiting you, they could do it. I guess its their version of trust, 
but verify. No argument from us. 

They are not alone. We do the same thing with AFRINIC and APNIC amongst RIRs, 
nic.br as a TLD operator, and Network Solutions as a registrar.  DENIC and a 
few others have asked us to provide queries in special formats, and we happily 
comply with all of these. We appreciate their efforts to enable us to help the 
community. And I think they've mostly been happy with us for the last 14 years 
or whatever. (BTW there are about 310 of them total at the moment that we're 
able to parse and identify and query for, as well as many more specially 
requested cases, like uk.com, au.com, etc.

RIPE-NCC has decided to limit this to their members only. Not us.

So they are now removing that from us. We will now be subject to their normal 
limits (whatever that is). When we reach our daily limit, we will be blocked. 
When we do that a few times, we will be permanently blacklisted.

The good news is that if you query them yourselves, you'll be able to query 
them up to your daily individual limit before being blocked. So if you have 
been using us, and have never been blocked with RIPE queries, you will likely 
not be blocked when you query then direct (we have already been passing them 
your IP address so they can count and rate limit). The only difference is that 
now you you can make a single query for every TLD, every RWHOIS delegated 
server via the TLD whois server,  and every RIR, and get a answer in one. 
Except if it ends up in RIPE land. Then you're on your own, walking their tree, 
etc. But you can do it manually.

Later today, when we see how RIPE handles rejecting us, we'll write a script, 
and sarcasm without asking you all to become members and pay us $1,800 a year 
/sarcasm, we'll post here, identifying the text we'll pass so that you can 
configure scripts to recognize the rejection, and handle the query in an 
exception routine.

Also, more than 10 years ago, we created a windows program that loaded in the 
systray, and provided desktop capabilities. And we also made available the 
gpl'd unix source for people who wanted to run it locally.  We haven't updated 
it for years, but many of you have it and did update, and that will not be 
affected, beyond the existing limitation you would be seeing - the app queries 
from your own IP address already. If any of you has been maintaining and 
upgrading/updating the app, and feels like sharing it, please do ;-). If you 
want, send it to us and we'll audit it (I know you won't mind in today's 
environment) and then add it to the geektools website.

I guess I should also put together a smartphone app that uses the proxy as 
well… 

Anyway, enough noise for now. Apologies. And thanks to all of you who responded 
privately, with offers etc. Fortunately we don't need finance, or resources or 
support. I'm just happy it has helped for so long.

Wishing you everything you want for yourselves in 2013 - the year of IPv6 and 
hundreds of new TLDs.

Rodney and the CenterGate/GeekTools crew (yes, we're still around ;-)).

.  .  .  -  .  -

 
On Dec 31, 2012, at 11:46 AM, Job Snijders job.snijd...@atrato-ip.com wrote:

 Hi Rodney,
 
 From the looks of it, this decision was made by the RIPE NCC Executive Board 
 rather than at the General Meeting.  Inqueries will have to be made why this 
 was decided, and what the consequences are. But, I don't expect a resolution 
 to be reached in the next 6 hours. 
 
 In the meantime you could consider setting up an irrd[1], redirect queries to 
 that instance instead of whois.ripe.net, and keep it kind of fresh by feeding 
 it ftp://ftp.ripe.net/ripe/dbase/ripe.db.gz on a daily basis. 
 
 Kind regards,
 
 Job
 
 [1] http://www.irrd.net/
 
 On Dec 31, 2012, at 4:41 PM, Rodney Joffe rjo...@centergate.com wrote:
 
 NANOG and ARIN Friends,
 
 14 Years ago, at the suggestion of Jon Postel and some of the early 
 participants in NANOG, we developed the GeekTools Whois proxy to make it 
 easier for *us* - network security and abuse techs - to deal with the 
 expanding number of gtlds and registrars and the varied whois servers that 
 were appearing. The service had both a CLI and  web interface.
 
 The service also led directly to the creation of whois-servers.net, which 
 now seems to be part of a number of *nix

Re: GeekTools Whois Proxy and RIPE/RIPE-NCC

[Rodney Joffe]

Hi Erik,

I appreciate the offer (a number of RIPE members have stepped forward). However 
I would not a) want this to in any way threaten your membership status - its 
possible I guess that this might violate the RIPE contract because it is a 
circumvention, and b) would not want special status - its important that the 
problem should be resolved for all the parties who are being affected and don't 
have a voice. GeekTools isn't special. 

I can easily afford RIPE membership. However its the principle, and the small 
folks that matter.

I'm hoping that the good folks on the RIPE board think about the unintended 
detrimental consequences of their decision. I'm sure they didn't mean this to 
happen...

Thanks again.

Rodney

On Dec 31, 2012, at 2:48 PM, Erik Bais eb...@a2b-internet.com wrote:

 Hi Rodney,
 
 Would support from a RIPE LIR be sufficient to keep the service up ? 
 
 I'm pretty sure there isn't a requirement to register for a LIR membership if 
 this is the only usage. 
 
 As a RIPE LIR, we can have a look at what the options are if that would help. 
 
 Have a good new year,
 
 Regards,
 Erik Bais
 A2B Internet 
 
 Verstuurd vanaf mijn iPad
 
 Op 31 dec. 2012 om 16:41 heeft Rodney Joffe rjo...@centergate.com het 
 volgende geschreven:
 
 NANOG and ARIN Friends,
 
 14 Years ago, at the suggestion of Jon Postel and some of the early 
 participants in NANOG, we developed the GeekTools Whois proxy to make it 
 easier for *us* - network security and abuse techs - to deal with the 
 expanding number of gtlds and registrars and the varied whois servers that 
 were appearing. The service had both a CLI and  web interface.
 
 The service also led directly to the creation of whois-servers.net, which 
 now seems to be part of a number of *nix distributions.
 
 The service has been up for 14 years, and over that time we have fulfilled 
 the requirements of all of the whois server operators in regards to 
 minimizing and stopping abuse of the GT whois proxy by domain scrapers, 
 spammers, etc, while enabling the security folks to do their jobs. In some 
 cases we have even written code to pass the ip address of the requestor to 
 the whois server registry operator when they wanted to manage quota's 
 directly. We think we have a really good relationship with all of the whois 
 server operators, and I think we provide a useful service to the community, 
 and is widely used. And in 14 years we have never been tarred as an enabler 
 of abuse of the whois system.
 
 There has obviously never been any kind of charge or fee for using the 
 proxy, or any of the other tools on GeekTools. In about 2002 we started 
 placing a banner ad on the web interface page to offset some of the costs 
 for the bandwidth that the proxy consumes. An average of about $70 a month 
 for over the last 10 years. Actual bandwidth costs are higher than that of 
 course, but it was a thought in 2002 that we had frankly forgotten about 
 until recently.
 
 Two weeks ago RIPE-NCC, who provide the whois data for IP addresses in the 
 RIPE region, informed us that based on decisions by their members, as of 
 January 1st 2013, tomorrow, they would no longer provide whois proxy query 
 response services to GeekTools unless we ponied up $1,800 a year for RIPE 
 membership.
 
 I don't work very well above layer 7. It is what it is. So I wanted to let 
 you know that as of midnight tonight, apparently, you won't be able to use 
 GeekTools for RIPE related queries. If you have automated scripts, and you 
 are one of the users who has expanded access to GeekTools, you'll need to 
 find an alternative for RIPE queries *today*. My guess is that you will be 
 able to query RIPE directly, once you have worked out that the address space 
 is within RIPE's assignments.
 
 I think its wrong to have to pay for whois data that is part of a community 
 resource . So I won't do it.
 

14 years ago today....

[Rodney Joffe]

... we lost Jon.

http://www.ietf.org/rfc/rfc2468.txt

13 years ago today - October 16, 1998...

[Rodney Joffe]

we lost Jon.

It feels like just yesterday.

http://www.apps.ietf.org/rfc/rfc2468.html

Re: 12 years ago today...

[Rodney Joffe]

I'm not sure about a documentary, but a group of us are working on identifying 
all the different independent archives that have records from the early years 
with the idea of creating a Smithsonian/national archive collection at some 
point. We'll probably issue an rfc early next year.  



On Oct 16, 2010, at 2:02 AM, Warren Bailey wbai...@gci.com wrote:

 I bet it was terribly hard for Vint to write that. Was really nice to read 
 though, and to know that he had a good enough friend to express his deep 
 sorrow so publicly. 
 
 While we are on the subject of the godfathers of the Internet, when is a 
 documentary coming out that tells the story? There was a really long 
 documentary done on the BBS, surely someone (myself included) would find it 
 interesting. 
 
 //warren
 
 Sent from a mobile phone with a small keyboard, please excuse my mistakes.
 
 On Oct 16, 2010, at 12:45 AM, Ali S sterbe...@gmail.com wrote:
 
 He should have been better known for his work. The intertubes will miss you
 
 Sent via mobile.
 
 On Oct 15, 2010, at 8:38 PM, Jorge Amodio jmamo...@gmail.com wrote:
 
 On Fri, Oct 15, 2010 at 9:51 PM, Rodney Joffe rjo...@centergate.com wrote:
 On October 16th, we lost a real friend and hero. Sigh
 
 http://www.apps.ietf.org/rfc/rfc2468.html
 
 Amen. Long Live Jon Postel !!
 
 
 
 

12 years ago today...

[Rodney Joffe]

On October 16th, we lost a real friend and hero. Sigh

http://www.apps.ietf.org/rfc/rfc2468.html

Re: Cyber Shockwave on CNN

[Rodney Joffe]

Enough hype. This was an exercise in self promotion by retired  
beaurocrats posturing for private gigs. The US gov publicly  
disassociated themselves from this.


Move along. Nothing to see here.


On Feb 20, 2010, at 3:13 PM, andrew.wallace andrew.wall...@rocketmail.com 
 wrote:



--- On Sat, 20/2/10, Randy Bush ra...@psg.com wrote:


From: Randy Bush ra...@psg.com
Subject: Re: Cyber Shockwave on CNN
To: andrew.wallace andrew.wall...@rocketmail.com
Cc: nanog@nanog.org
Date: Saturday, 20 February, 2010, 21:58

It looks like this demo is


a bunch of sick press and sick ex-gov wishtheycouldbeagains
trying to
get as much mindshare as they can.  and you're helping
them.

randy



I refuse to let you say I am helping them -- I am from UK, I don't  
agree with them wanting to allow The NSA to take over private sector  
networks or citizens smart phones 'in an emergency'.


Andrew

Re: Katrina response, private and public

[Rodney Joffe]

On Jan 19, 2010, at 11:31 AM, Eric Brunner-Williams wrote:

I've no idea. I've just been focused on moving the dry tank moment  
to the right, along with several others. Mind, this was the first  
resupply, its not a stable replenishment schedule yet.


The engineers on site had (as of yesterday) personal food and water  
through Thursday, and dependents in need.


Is there anything that any of us cab do to help, exert influence, etc  
(short of donating which many of us are already doing).

RFC 2468

[Rodney Joffe]

It's been 11 years. Sigh.

ICANN NomCom call for SOIs for Board/Leadership positions

[Rodney Joffe]

Folks,

It's that time again. The 2009 ICANN Nominating Committee is actively  
soliciting applications, nominations, and/or Statements of Interest  
for the Board and other key leadership positions:


# Three members of the ICANN Board of Directors
# Three members of the At Large Advisory Committee (for the African,  
Asia/Australia/Pacific, and Latin American regions)
# Two members of the Council of the Generic Names Supporting  
Organization (GNSO)
# One member of the Council of the Country-Code Names Supporting  
Organization (ccNSO)


This is your opportunity to actually get involved in guiding the  
direction of ICANN, rather than standing on the sidelines and  
complaining.


More info at: http://nomcom.icann.org/

Step up.

Rodney Joffe
ICANN 2009 NomCom Member

Ten years ago today.....

[Rodney Joffe]

Jon Postel left us. A vacuum still unfilled.

http://www.isi.edu/div7/people/postel.home/

Re: The DDOS problem security BOF: Am i mistaken?

[Rodney Joffe]

Scott,

On Oct 14, 2008, at 9:08 AM, Scott Doty wrote:

First, the good news:  so far, the NANOG conference has been very  
valuable and
content-rich, covering a lot of issues that need to be discussed.   
For that, I am grateful.


Thank you. We worked hard to make it valuable.



But now, the bad news(?):  Maybe it's just me  my paranoia, but do  
I detect

an inkling of murk spam going on with some presentations?


Not sure what you mean by murk spam. Thats a term that died years  
ago. And it really related to people claiming that spam was in  
compliance with federal laws. But I think I can guess your intentions  
from the tone of your email, so let me try and respond.





Because there seems to be a fundamental misunderstanding, either on  
my part,
or the part of certain vendors: I'm hear to discuss ideas  freely  
share
them, and they are here to discuss (it would seem) their products.  
Sometimes

both goals coincide, and that is fine...but...

When a vendor at the security BOF starts showing documents that are  
company
confidential, and trying to whip up a climate of fear, that we  
should all
deploy their product in front of our recursive name servers, i get  
this

funny feeling that I am being murk spammed.


Well, that's interesting. I see your last NANOG was 9, in February of  
1997. So Welcome back!. We're glad to have you here in person.  
Things have changed slightly since then. NSP-SEC never existed in  
1997. It really came about in the early 2000's where it was developed  
as a forum for actual operators to share views and thoughts, generally  
in real time, to help the 'net in general survive disruption,  
malicious or otherwise. It has really worked pretty well, so if you  
qualify, I'd encourage you to get involved. See http://puck.nether.net/mailman/listinfo/nsp-security 
 for info.


The NSP-SEC bof at NANOG is not quite the same environment as the NSP- 
SEC mailing list, but it generally includes the same people, plus  
others from the operations community who take the effort to attend  
NANOG, and so are sort of self-selected as being one of the  
operators with an already working amount of clue about the subjects  
that are being discussed. Additionally,  the concept of a trusted  
environment still sorta applies. You may not have realized it, but  
unlike all other sessions at NANOG, the slides are not published, they  
are not available online, and the session is not broadcast. So  
Confidential was there to remind folks in the BoF that this was a  
non-public (for a skewed version of public) presentation.


Having explained that bit of history which gives you a general  
background, let me deal with some specifics.





Perhaps that is my own perspective ( paranoia?), but I found the CERT
gentleman's call to monitor icmp backscatter on our authoritative
nameservers far more informative -- and open.


I don't think anyone from CERT presented. Perhaps you meant Barry  
Green from Juniper's CERT team? Another vendor? Well, as you'll see  
further on, not really. In this context, like everyone else who  
presented, he was there as an operator, sharing knowledge and  
experience. But I digress...





But I was disappointed with two vendors and their presentations: the  
first
had the tactic of saying DNSSEC is the actual solution when asked  
about
why their product would be necessary...completely ignoring the fact  
that
their proprietary interim solution was by no means the only way to  
prevent
cache poisoning attacks.  Indeed, I would daresay it isn't the best,  
either

by a BCP perspective, or a cost analysis perspective.


While we may disagree on your last claim (and I actually have a few  
years of experience to help me argue my point), I specifically said  
there were a) solutions that solved part of the problem (switching to  
TCP, detecting and blocking cache poisoning attacks) and b) the right  
solutions like DLV and DNSSEC that will take some time to be deployed.  
And I then made sure everyone heard me when I said that we need to  
find an interim solution that can be deployed *now*, until DNSSEC  
exists in a useful footprint. I ignore *nothing*. If you have another  
solution that solves the same problems that has running code now,  
please share it with all of us. Remember, it has to scale, it has to  
solve all of the problems, and it has to be implementable across a  
range of levels of clue.





To put a finer point on this, i should say that i found myself  
discomforted
by a presentation suggesting that I should put their proprietary  
appliances
between my recursive name servers  the Net, and I am grateful that  
Mr.

Vixie stood up and said that there are other ways of dealing with the
problem.


Indeed. Read further.





Fortunately, said vendor had a table at beer and gear, so I was  
able to
talk with one of their representatives -- and learned that they have  
just as
much trouble with automatic detection of attacks designed to look  
like a

Re: remembering Jon Postel: Looking Beyond the Decade

[Rodney Joffe]

On Oct 1, 2008, at 10:49 PM, Scott Francis wrote:


nice writeup by Mr. Cerf:
http://www.circleid.com/posts/ 
20081001_remembering_jon_postel_a_decade/


I was not fortunate enough to have known Mr. Postel, but I have
developed a deep posthumous respect for the work he did from listening
to what others have had to say about him, and from using (and
benefiting from) his legacy on a daily basis. He was not alone among
the pioneers who enabled the Internet to become what it is today, but
there weren't many who made such a significant contribution.


You may want to then consider coming to the next NANOG being held in  
just under two weeks time in Los Angeles (http://www.nanog.org/). This  
NANOG celebrates Jon's contributions on the 10th Anniversary of his  
passing (Oct 16) and includes a rare keynote opening speech by Vint  
Cerf, as well as a 90 minute panel of folks who were there when some  
important decisions were made, and who will share with us the reasons  
some of those decisions were made. Panelists like Paul Mockapetris who  
invented the DNS, Bob Braden who has taken care of much of Jon's role  
as RFC editor since Jon left us, Danny Cohen who Jon worked for, and  
who also worked for Jon ;-) at ISI in the '70s, Bob Hinden who was the  
ietf's first Area Director for routing, Lixia Zhang who was part of a  
small group of 6 including Jon who tackled the issues of addressing  
for the iab/iesg, and Van Jacobson, who you probably know mostly for  
his congestion control work, but who Paul Francis credits for the  
concept of NAT. Of course these folks had many other key contributions  
to the Internets.


Besides these official speakers at NANOG 44 you'll also get to meet in  
person many of Jon's peers and friends from the early days. I hesitate  
to name any, but if you listen carefully in the hallways, and for  
comments from the audience during this NANOG, you'll pick up on them.


If you want to get to know more about some of the people who really  
gave us the opportunity to do the things we do today, this is probably  
the NANOG you want to attend. BTW, it is a joint meeting with ARIN, so  
you get a two'fer.


be conservative in what you do, be liberal in what you accept from  
others - Postel's Law

Re: Silly PUCK/Outages question

[Rodney Joffe]

Perhaps you should report it to outages? ;-)

On Sep 24, 2008, at 11:55 AM, Christopher Morrow wrote:


On Wed, Sep 24, 2008 at 2:48 PM, Laurence F. Sheldon, Jr.
[EMAIL PROTECTED] wrote:

Tuc, stuck on puck  wrote:



  I hate to use NANOG for outages... But can anyone else get to
puck.nether.net or the outages.org list?


outages.org doesn't even resolve here (cox in Omaha).

$ dig NS outages.org @tld2.ultradns.net
;; QUESTION SECTION:
;outages.org.   IN  NS

;; AUTHORITY SECTION:
outages.org.86400   IN  NS  puck.nether.net.
outages.org.86400   IN  NS  anyns.pch.net.

$ dig NS outages.org @204.61.216.4
;; QUESTION SECTION:
;outages.org.   IN  NS

;; AUTHORITY SECTION:
org.172800  IN  NS  D0.ORG.AFILIAS-NST.org.
org.172800  IN  NS  TLD1.ULTRADNS.NET.
org.172800  IN  NS  C0.ORG.AFILIAS-NST.INFO.
org.172800  IN  NS  TLD2.ULTRADNS.NET.
org.172800  IN  NS  B0.ORG.AFILIAS-NST.org.
org.172800  IN  NS  A0.ORG.AFILIAS-NST.INFO.


incorrect NS record setup maybe??

-chris