Re: [Idr] new draft - reservation of two already reserved ASNs

[Jon Mitchell <[e-mail]>]

On 20/05/13 14:05 -0500, David Farmer wrote:
> 
> Does anyone know if any implementations disallow the use of one or
> both of these ASNs currently or maybe planed as part of implementing
> draft-ietf-idr-as0?  Either as the Local ASN, a Neighbor ASN, or
> within the AS_PATH (or AS4_PATH as appropriate)?

I don't know of any implementations that don't support these ASN's as
normal ASN's today (assuming they have 4 byte AS Support for the 2nd
one).  I think by any reading of existing standards, having
limitations on these ASN's today would be considered a bug.  I know a
number of networks have used 65535 (it occasionally is leaked as well
by folks who don't properly strip private asns) as if it was a Private
Use ASN and many vendors documentation include it in the Private Use
range regardless of the IANA actual allocation.

I'm open to others thoughts, but forcing a change on existing
implementations (versus just IETF/operator guidance on ASN's usage)
was not my intention. 

Cheers,

Jon