Public bug reported:
Currently there is a limit hardcoded in Neutron that will only allow
16bit ASN being used in the configuration of BGP speakers and peers,
i.e. a range of [1..65535]. But with https://tools.ietf.org/html/rfc6793
it is possible for BGP implementations to allow 32bit numbers to be used
and in fact some RIRs have already run out of 16bit ASNs and are only
handing out new ASNs that are above 65536.
So although the ryu-based reference implementation does not support
this, there may be other agents e.g. based on ExaBGP that will support
32bit ASNs being used, and it doesn't seem sensible that Neutron should
prevent this upfront.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1573092
Title:
neutron and python-neutronclient should allow for 32bit ASN
Status in neutron:
New
Bug description:
Currently there is a limit hardcoded in Neutron that will only allow
16bit ASN being used in the configuration of BGP speakers and peers,
i.e. a range of [1..65535]. But with
https://tools.ietf.org/html/rfc6793 it is possible for BGP
implementations to allow 32bit numbers to be used and in fact some
RIRs have already run out of 16bit ASNs and are only handing out new
ASNs that are above 65536.
So although the ryu-based reference implementation does not support
this, there may be other agents e.g. based on ExaBGP that will support
32bit ASNs being used, and it doesn't seem sensible that Neutron
should prevent this upfront.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1573092/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
