On Thu, 6 May 2010, James Hess wrote:
Now that AS numbers have been extended to 4 bytes in length, and RIRs
are even about to stop differentiating between them when allocating
AS numbers, or allowing anyone to request and be sure of getting a new
16-bit ASN.
Then you may be interested to see this Last Call:
http://www.ietf.org/mail-archive/web/mboned/current/msg01021.html
(draft-ietf-mboned-ipv4-uni-based-mcast)
It seems that it will be impossible for the scheme to be followed in IPv4.
A more sensible BCP at this point would be to designate the entire
223/8 to IRRs, like was suggested by the BCP for 64512 -- 65535,
since most ASNs are not using GLOP addressing.
Uhh. Take away the numbers from those who have already started using
them? Are you serious?
There were multiple attempts to the private etc. ASN parts of 233/8 to
RIRs but these have failed (lack of interest?). The current situation
(RFC5771) is that this has been designated as "AD-HOC Block III" and
is assignable from IANA.
The curious minds may also want to take a look at:
http://tools.ietf.org/html/draft-ietf-mboned-addrarch-06
(Comments welcome, this has been waiting the completion of
abovementioned draft.)
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
