![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
But, with the expanded space, there is an issue of how to transition to the larger numbers. This is a software problem as much as anything. Until all software understands the bigger numbers, people will want to continue using the 16-bit ones.
http://www.potaroo.net/presentations/2006-10-11-asns.pdf
Meanwhile, to encourage the migration to 4-byte ASNs, the RIRs have been developing a globally-coordinated policy for how to transition to 4-byte ASNs (hi Geoff!). The first step of that process, effective January 1, 2007, is to allow requestors to obtain 4-byte ASNs (if they specifically request them). But, in order for the RIRs to be able to offer them, IANA has to give them some. Hence, the IESG action mentioned in the note.
See http://www.arin.net/policy/proposals/2005_9.html for more details.
regards,
Geoff
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.