| | | | | | | | |
|
|
|
You're here: Home |
On 20/08/2008, at 2:08 PM, Philip Smith wrote:
Only because they started using it without consulting the industry. ;-)
Because you and Gaurab have both decided to propagate this rather silly notion in the last day or two, and because the "they" you refer to appears to include myself in my day job, I should respond to correct it.
The original policy proposal regarding the 4 byte AS numbers put to the RIRs had a section called "Nomenclature" and proposed a colon separator, which, as far as I recall, I picked up from original notes by Enke Chen in the context of the IDR working group of the IETF when they were developing the work.
Noone from any region make a single comment on the nomenclature section of the proposal at the time, with the exception of the ARIN community, where the general response after some considered discussion on the matter was the view that a colon would make parsing BGP communities tricky, so why not use a period in place of a colon as a delimiter of the low and high bytes of the AS value. Subsequent review of the policy proposal in ARIN generated the comment that nomenclature on the dot notation was out of scope for policy, so why not drop this section completely. So it was dropped from the policy proposal not only in ARIN, but, as this was a coordinated policy across all the RIRs, it was dropped from the proposal for all the other RIRs as well.
So as far as I can see where we are with AS notation largely as a result of consulting with, and listening to, the community.
Geoff Disclaimer:I guess that most folk would've figured it out by now, but for the one or two who evidently feel some pressing need to see this stuff every time, the above is a personal comment, and in no way is intended to reflect
any position of the APNIC Secretariat, now or in the future.
