[136649] in North American Network Operators' Group
Re: And so it ends...
daemon@ATHENA.MIT.EDU (John Curran)
Thu Feb 3 19:01:41 2011
From: John Curran <jcurran@arin.net>
To: Benson Schliesser <bensons@queuefull.net>
Date: Thu, 3 Feb 2011 23:59:32 +0000
In-Reply-To: <3C4B93EE-7629-4612-96FD-514F8720FCEC@queuefull.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Feb 3, 2011, at 6:38 PM, Benson Schliesser wrote:
> Having said that, it should be clear that I view ARIN "reclaiming" legacy=
addresses that aren't under contract (i.e. LRSA) as fraud, perhaps even in=
the legal sense of the word. It might also be considered theft by some. =
But outright reclaiming from ongoing address holders isn't a big concern of=
mine, because I doubt ARIN will go far down that path (if it goes at all).=
My real concern is that ARIN might refuse to recognize legacy transfers, =
fail to update the Whois database, issue RPKI inappropriately, and cause re=
al damage to live networks. This would be bad for the networks that implem=
ent ARIN Whois-based policy, of course. =20
Benson -=20
ARIN provides legacy holders with WHOIS and IN-ADDR services without charge=
.
If a legacy holder simply wishes to make use of their resources and maintai=
ns=20
current directory information, ARIN left them fairly undisturbed since its=
=20
formation. =20
Via the Legacy RSA, ARIN offers contractual assurances to legacy holders of=
=20
ARIN providing these services, as well as certain protections from reclamat=
ion=20
and policy changes. Note that ARIN can't allow transfers contrary to the
community-developed policy, so legacy address holders who wish to do more
then just use their resources (e.g. transfer them) are encouraged to get
involved in the community to create policies that match their needs.
/John
John Curran
President and CEO
ARIN
