[arin-ppml] Legacy Space authority (fwd)

Jimmy Hess mysidia at gmail.com
Fri May 2 19:29:21 EDT 2008

Agreed, the same would have a basis for happening, and the block could 
later become assigned
 to another org later...
Just as with domain registrations, there was never as much as a written 
promise that the assignment
is meaningful and permanent forever, and on any network.

There has been some argument that the assignments by the legacy registry 
were "transfers of property"
instead of merely assignment of numbers to go with a named network.

There has been no proof shown that the assignment is a "transfer" of 
property any more than registration
of domain names were.

Just like the registration of  "port 25" to the SMTP protocol or the 
assignment of  "port 201" to Appletalk
is anybody's property;  it doesn't matter whether you created the 
protocol, use it, etc...
Your equipment is your property, but the registration itself is the 
property of whichever organization operates
the registry.

The current maintainer of the online registry _could_  in fact revoke 
that assignment,  but it doesn't necessarily
mean  the community will stop using those port numbers.

Nor does an IP registry de-listing a legacy registration necessarily 
indicate the community will stop routing
those IPs to the same place.

So it may not be a good thing to do:  except in the extroardinary 
circumstance (which may eventually happen)
that previously assigned expired space is the only space
left to assign for new allocations,  as the new registrant  paying for 
maintenance of the registry might now
have an ip block that is difficult or impossible for them to use  
without being disrupted  by legacy
networks still trying to use the space that is no longer assigned by the 
registry to that legacy network.

Pulling domains is much easier...  because the registrar can remove the 
domain's nameservers from the
TLD zone, causing the domain to very quickly be inoperative.

The only immediate thing the IP registries appear to have available to 
pull is  IN-ADDR delegation --
which is a service of the registry.

But that might be good enough, in the respect that it makes legacy space 
hijacking by spammers
(relying on inaccurate org information) less-likely: no good reverse 
zone means the spammer will have
a harder time getting their mail accepted.


Leo Bicknell wrote:
> In a message written on Fri, May 02, 2008 at 05:44:11PM -0400, Dean Anderson wrote:
>> Legacy's got their space from the government. So did the RIRs. Those 
>> blocks are intangible property, just exactly like domain names. 
> There was a time when you could get a domain name by sending off
> an e-mail, much like early legacy assignments.  Somewhere along the
> line a contract was imposed, fees were established, and a UDRP was
> created.  As far as I know unless you agreed and started to pay the
> fees your domain name was dropped from the system.
> If Legacy blocks are "just exactly like domain names" then I would
> assume you feel the same could happen with legacy blocks.  A contract
> could be imposed, fees established, and a dispute procedure created.
> I suppose the only sticking point is who, ARIN, IANA, ICANN, US
> Government?
> ------------------------------------------------------------------------
> _______________________________________________
> You are receiving this message because you are subscribed to the ARIN Public Policy
> Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact the ARIN Member Services Help Desk at info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list