[ppml] alternative realities (was PIv6 for legacy holders (/wRSA + efficient use))

> -----Original Message-----
> From: ppml-bounces at arin.net [mailto:ppml-bounces at arin.net] On 
> Behalf Of David Conrad
> Sent: Wednesday, August 01, 2007 1:35 PM
> To: Paul Vixie
> Cc: ppml at arin.net
> Subject: Re: [ppml] alternative realities (was PIv6 for 
> legacy holders (/wRSA + efficient use))
> 
> > i didn't make that rule -- david conrad did, or at least, 
> david conrad 
> > participated in writing down the rule which had predated 
> his work in 
> > founding APNIC.  see RFC 2052.
> 
> I suspect you mean RFC 2050 (and I was involved in writing it 
> while I was at APNIC, not before).  You might look at the 
> date of publication, read the IESG preamble, and ponder 
> whether the circumstances in which that document were 
> published are still applicable today.

I could guess at whether you would co-author such an RFC today,
or I could ask you what you think, though you might have trouble
doffing your hat.

Are the goals enumerated in RFC2050 still supported by the
ARIN community?

   1) Conservation: Fair distribution of globally unique Internet
address
   space according to the operational needs of the end-users and
Internet
   Service Providers operating networks using this address space.
   Prevention of stockpiling in order to maximize the lifetime of the
   Internet address space.

   2) Routability: Distribution of globally unique Internet addresses
   in a hierarchical manner, permitting the routing scalability of
   the addresses. This scalability is necessary to ensure proper
   operation of Internet routing, although it must be stressed that
   routability is in no way guaranteed with the allocation or
   assignment of IPv4 addresses.

   3) Registration: Provision of a public registry documenting address
   space allocation and assignment.  This is necessary to ensure
   uniqueness and to provide information for Internet trouble shooting
   at all levels. 



Lee