[ppml] Policy Proposal 2005-9: 4-Byte AS Number
jeroen at unfix.org
Wed Dec 21 08:07:43 EST 2005
Marshall Eubanks wrote:
> 2.) I think that much of the nomenclature discussion is pretty silly,
> including some of mine. Unless someone comes up with a scheme to
> really burn through them, I would predict that we would not need to
> use more than 6 digits for ASN's a few decades to come (I estimate
> about 20 years).
The 'burn through' is very easy. IANA can allocate a block of 65k ASN's
to each RIR. RIR's won't have to bother IANA then and it makes it easy
for whois-like tools to find the RIR in question.
As for the separator, I am for the use of '.', thus:
* 8298 = 2 byte ASN
* 0.8298 = 4 byte ASN (2 byte space)
* 1.8298 = 4 byte ASN (RIR X space)
* 2.8298 = 4 byte ASN (RIR Y space)
But that also depends on decisions by IANA and if they want to be so
nice in giving out such large blocks. Their IPv6 policy seems to have
changed finally though.
> 3.) 2005-9 says nothing about whether or not people requesting 4 byte
> ASN can request specific 4 byte
> ASN. I think that the current sequential assignment should continue.
> The text
> In accordance with current policy, applications will only be able to
> request AS Numbers that require 4 bytes to express, not specific AS
IMHO This is a very valid point and should really be considered to be
incorporated into the policy.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 238 bytes
Desc: OpenPGP digital signature
More information about the ARIN-PPML