Reviewed: https://review.openstack.org/499915 Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=972756f603f72a0026713d98a0d485eb0026094a Submitter: Zuul Branch: master
commit 972756f603f72a0026713d98a0d485eb0026094a Author: Hirofumi Ichihara <ichihara.hirof...@lab.ntt.co.jp> Date: Fri Sep 1 15:33:01 2017 +0900 Support 4-Byte AS Numbers Now neutron_dynamic_routing supports 2 byte AS numbers only. This patch expands AS numbers constraint so that it supports 4 byte AS numbers. It expects that operators use asplain notation to set AS numbers[1]. That's backward compatible with existing 2 byte AS numbers. [1]: https://tools.ietf.org/html/rfc5396 Change-Id: I06ae0c42d983e88e1f38c501d5c85a7956f195ad Closes-Bug: #1573092 ** Changed in: neutron Status: In Progress => Fix Released -- 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: [RFE] BGP neutron should allow for 32bit ASN Status in neutron: Fix Released 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