[arin-ppml] A compromise on legacy space?

Kevin Kargel kkargel at polartel.com
Wed Sep 10 12:59:51 EDT 2008

Actually it defines pretty well what happens.  If Arin assigns the database
slot for a.b.c.0/20 to Fred then everyone who uses the ARIN database will by
default route that network to Fred.  If Joe Legacy wants everyone to route
it to him then he needs to cooperate with ARIN to make sure that his network
is assigned the slot in the database and his records are updated.  

That sounds pretty straightforward to me.

> -----Original Message-----
> From: John Santos [mailto:JOHN at egh.com] 
> Sent: Wednesday, September 10, 2008 10:10 AM
> To: Kevin Kargel
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] A compromise on legacy space?
> This argument totally ignores what happens if ARIN allocates 
> a "slot in the database" to someone when the number 
> corresponding to that slot was allocated by a predecessor to 
> a legacy holder.
> You can't make the issue of legacy assignments go away by 
> sophistry.  It still has to be dealt with.
> --
> John Santos
> Evans Griffiths & Hart, Inc.
> 781-861-0670 ext 539
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3107 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20080910/7826d3c7/attachment.bin>

More information about the ARIN-PPML mailing list