>> On Feb 27, 2015, at 21:28, Mark Tinka <[email protected]> wrote:
>> 
>> On 28/Feb/15 03:08, David Farmer wrote:
>> 
>> If you only look at it through the lens of the current multi-homing
>> requirement for an ASN then you don't need it, it is totally
>> anticipatory and only a future need, but that is self-fulfilling.  I'm
>> suggesting that multi-homing is too narrow of a definition of need for
>> an ASN.  The PI assignment and what every justified that should also
>> equally justify the need for ASN assignment.  The PI assignment was
>> intended to be portable, also assigning an ASN simply is intended to
>> facilitate that portability.  I'm saying that the need for portability
>> is also a need for an ASN, if you look beyond multi-homing.
> 
> True, PI is meant to be portable, which is fine for IPv6 because we have
> a lot of address space.
> 
> But don't you worry that you will blow through 4.2 billion ASN's soon if
> PI allocation policy evolves to become liberal that 4.2 billion PI
> allocations become a reality?
> 
> Mark.

If IPv6 PI allocations gets too liberal, the routing system as we know it will 
implode long before we allocate 4.2 billion ASNs.  Restricting the number of 
ASNs in use in the routing system isn't really going to help that much.  The 
total number of prefixes, PA or PI, has been the primary limiting factor 
historically.  Limiting the portability of PI prefixes by not allocating ASNs 
won't save the routing system.  Only ensuring that the growth in the number of 
prefixes, both PA and PI, is sustainable and doesn't exceed the growth in the 
prefix limit for the typical router in use in the Internet at any point in time 
will keep the current routing system going.

We need a new kind of routing system, we've known that for a while.  But that 
is not a policy issues for the RIRs, that is a technology issues for the IETF 
and the IRTF.  I think things like LISP and ILNP are promising in the long run. 
 We just have to keep the current routing system going until those technologies 
can prove themselves.  We do that by keeping total prefix growth sustainable, 
not by limiting portability of PI prefixes.

-- 
===============================================
David Farmer                          Email: [email protected]
Office of Information Technology
University of Minnesota    
2218 University Ave SE         Phone: +1-612-626-0815
Minneapolis, MN 55414-3029   Cell: +1-612-812-9952
===============================================


*              sig-policy:  APNIC SIG on resource management policy           *
_______________________________________________
sig-policy mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/sig-policy

Reply via email to