Any AS numbers used inside an isolated organization are OK as long as they are not used for BGP peering with public networks. To make this more manageable, there is this concept of "private AS" so any peer can easily filter them out if they "escape" by mistake. In our case, for internal peering purposes, the 44net BGP space is NOT public, and private AS can be used as we like.
And as long as no one intentionally peers with another network using the same AS space, there is no possibility for conflicts. BGP neighbors have to be set manually, so unless both sides don't know what they are doing, there is no issue.
Let's not confuse our internal networking work with the internet.
Marius, YO2LOJ
-----Original Message----- From: Pedja YT9TP Sent: Wednesday, December 09, 2015 14:38 To: AMPRNet working group Subject: Re: [44net] Proposal for allocation of AS numbers
(Please trim inclusions from previous messages) _______________________________________________
On 9.12.2015. 11:09, Rob Janssen wrote:
It is customary to use AS numbers from the "private AS ranges" on those radio networks documented in RFC6996: 64512 - 65534 and 4200000000 - 4294967294.
There is one problem. Private AS are not intended for public use, and 44net is de facto public network.
Private AS are used by other private networks and that could lead to conflicts.
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net