On 11/09/2008, at 12:11 PM, Amante Alvaran wrote:
I think we are dealing with two things here the admin side which is more of the concerns for the ASDOT and the routing side that makes ASDOT complicated for the regular expression.
I would have thought the admin side would be far easier dealing with a 32bit integer rather than the structured ASDOT notation.
Just a simple suggestion, again just a suggestion :) can we think in a way that maybe can we keep the readability in place (with the ASDOT for admin purpose) so that IANA and the RIR's life would be easy when it comes to assigning 4 byte ASN. But still in the routing side we'll keep the PLAIN format (maybe a simple conversion from the ASDOT to PLAIN is needed).
Some vendors are having problems delivering /any/ four byte ASN capability in a suitable timeframe, irrespective of notation. The last thing we want is for those vendors to direct their engineering time towards the ASDOT notation that does not work well in an operational environment. Which they are. Because the wider community is unintentionally telling the that ASDOT should be used.
Do people really feel that the presentation of 32bit ASNs is more important than their operational usability? Or that we should wait for some other entity to make that call for us, and hope it happens soon enough to be useful?
Cheers, Jonny.