[ppml] Proposed Policy: 4-Byte AS Number Policy Proposal
owen at delong.com
Tue Dec 13 01:07:48 EST 2005
In general, I like the policy, however, I think the nomenclature is a bad
idea as specified below:
> It is proposed to identify 4-byte AS Numbers using a syntax of
> <high order 16 bit value in decimal>:<low order 16 bit value
> in decimal>. Accordingly, a 4-byte AS number of value 65546
> (decimal) would be identified as "1:10".
That fits really well with the current ASN:Comm syntax used for
communities... NOT! This will create no end of confusion by
using this nomenclature. Is 45:1234 AS45 community 1234 or
is it AS45:1234? What about communities within 16 bit ASNs?
Will it then become AS45:1234:5678?
Perhaps using dot as a separator as in 45.1234 instead would be a better
idea. Perhaps hyphen, perhaps something else. I really don't care, but,
I'd hate to see : used as it will do nothing but create confusion.
If this message was not signed with gpg key 0FE2AA3D, it's probably
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 186 bytes
Desc: not available
More information about the ARIN-PPML