[78911] in North American Network Operators' Group
RE: ARIN, was Re: 72/8 friendly reminder
daemon@ATHENA.MIT.EDU (Hannigan, Martin)
Fri Mar 25 00:55:43 2005
Date: Fri, 25 Mar 2005 00:55:03 -0500
From: "Hannigan, Martin" <hannigan@verisign.com>
To: "Owen DeLong" <owen@delong.com>,
"Edward Lewis" <Ed.Lewis@neustar.biz>
Cc: "Andrew Dul" <andrew.dul@quark.net>, <nanog@merit.edu>
Errors-To: owner-nanog@merit.edu
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Owen DeLong
> Sent: Friday, March 25, 2005 12:00 AM
> To: Edward Lewis
> Cc: Andrew Dul; nanog@merit.edu
> Subject: Re: ARIN, was Re: 72/8 friendly reminder
>=20
>=20
[ snip ]
=20
> Right... So, things divide into two categories... Major=20
> Undertakings and
> changes to existing policy... Requires policy process. =20
> Easily implemented
> obvious wins for everyone (a pingable address within a new block would
> be an example here) where the first step should be a polite "Hey ARIN
> Staff, can this be done?" If the staff says "Sure...Easy...=20
> look for an
> announcement soon.", then my experience has been they tend to get
> implemented fairly quickly (I believe this is what I just saw from
> Leslie a couple of minutes ago on this very issue). If the staff says
> no, they generally provide reasons and suggestions. In this=20
> case, either
> the policy process or an alternative solution is probably in order.
The problem I see with it not being in policy process is that it means
it's not permanent. Personally, I think that this is a great idea,
but I don't necessarily agree that it's as easy as pinging a host
address in terms of scalability and effectiveness. Outside the policy
process, we lose the framework of discussion and consensus.
The staff is fantastic. Responsive. Intelligent. Good leadership. But
it may not always be that way. These things aren't static.
YMMV
-M<=20
