North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
RE: Private ASN suppression
> -----Original Message----- > From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of > Danny McPherson > Sent: Tuesday, May 16, 2000 2:45 PM > To: email@example.com > Subject: Re: Private ASN suppression > > > > > In short, see RFC 2270. ...as well as rfc2260. to be more specific, we have to note that two different options are considered there. if you use the first one (read rfc), then you cannot use private asn until you're ok with generating inconsistencies (and it seems from the previous discussions of this topic that this becomes (illegal? -> no answer...) practice for some smaller isps). with the second option of 2260, you can use private asn since the more specific pa routes are always aggregated (and you cannot use confederations, btw). after all, as was noted, remove-private-as on cisco can be replaced by a simple route map, and the attribute manipulation functionality should definitely exist on versalars... -- dima.