[136827] in North American Network Operators' Group
Re: And so it ends...
daemon@ATHENA.MIT.EDU (John Curran)
Sat Feb 5 14:25:50 2011
From: John Curran <jcurran@arin.net>
To: "James P. Ashton" <james@gitflorida.com>
Date: Sat, 5 Feb 2011 19:24:33 +0000
In-Reply-To: <9499604.2426.1296930172108.JavaMail.root@mail.gitflorida.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
James -
ARIN allows legacy holders to update their registration information, in=
fact, we even allow such via ARIN Online. No agreement is required with A=
RIN; we provide this service as well as WHOIS and reverse DNS without charg=
e.
If you no longer want to use your address space, you may return it, or=
transfer according to the community developed policies.
/John
John Curran
President and CEO
ARIN
On Feb 5, 2011, at 1:54 PM, "James P. Ashton" <james@gitflorida.com> wrote:
> John,
> It seams that by stating "Note that ARIN can't allow transfers contrary t=
o the
> community-developed policy" that you intend to say that ARIN, based on yo=
ur current policies and processes, will not actively update whois informati=
on for legacy block holders that either "sub-assign" or "Transfer" segments=
of their legacy space to another entity.
>=20
> Is this the case? If so, as many others seam to be asking, do you and th=
e ARIN legal representatives, feel that you can actually legally follow thi=
s course and do you feel that, as you had nothing to do with the assignment=
of this space that you have any real right to deny these services. The com=
munity expects you to to have a certain quality of information in the datab=
ase and not offering updating services can present operational issues to th=
ose of us using the database as intended.=20
>=20
> James
>=20
>=20
>=20
> ----- Original Message -----
> On Feb 3, 2011, at 6:38 PM, Benson Schliesser wrote:
>=20
>> Having said that, it should be clear that I view ARIN "reclaiming" legac=
y addresses that aren't under contract (i.e. LRSA) as fraud, perhaps even i=
n 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 o=
f 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 r=
eal damage to live networks. This would be bad for the networks that imple=
ment ARIN Whois-based policy, of course. =20
>=20
> Benson -=20
>=20
> ARIN provides legacy holders with WHOIS and IN-ADDR services without char=
ge.
> If a legacy holder simply wishes to make use of their resources and maint=
ains=20
> current directory information, ARIN left them fairly undisturbed since it=
s=20
> formation. =20
>=20
> Via the Legacy RSA, ARIN offers contractual assurances to legacy holders =
of=20
> ARIN providing these services, as well as certain protections from reclam=
ation=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.
>=20
> /John
>=20
> John Curran
> President and CEO
> ARIN
>=20
>=20
