On Fri, Mar 24, 2017 at 02:32:35AM +0100, Kai 'wusel' Siering wrote:
Sorry, but as a public ASN is to serve public inter-AS-uses,
Can you cite the policy requiring that?
why even think about private usage of a public resource? If you use a public AS internally only, you should switch to a private AS.
Private ASN are non-unique, and as such pretty much a non-starter in extranet situations.
Care to list at least a few? https://www.ripe.net/publications/docs/ripe-679 looks rather straightforward ??? and against hidden usage of assigned ASNs?
I cannot see any language in this document requiring any kind of "visibility" in any part of whatever network, especially the "Internet". Can you point us to the specific regulation?
So, you need a "new" *external* routing policy to receive a (public) ASN.
Yes. You seem to mistake "external" with "on the public Internet". "External" in BGP context is "with other ASN", that's it - not more, not less.
If your ASN does not show up in the global routing anymore, you obviously lost the need for that '"new" *external* routing policy', no?
No. Best regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0