Arouteserver

------

- New: add support for `OpenBGPD 7.8 <https://www.mail-archive.com/techopenbsd.org/msg74147.html>`__, also added to the integration testing suite.

------

- Deprecation: support for overly old OpenBGPD versions (< 7.0) is removed.

See `GitHub PR 117 <https://github.com/pierky/arouteserver/pull/117>`__.

- New: add support for `BIRD 2.0.11 <https://bird.network.cz/pipermail/bird-users/2022-December/016431.html>`__, also added to the integration testing suite.

- New: mapping of 32bit ASNs to 16bit private ASNs for announcement control standard BGP communities.

A new feature is added to allow 32bit ASN clients to be mapped to 16bit ASNs in the standard BGP communities used for announcement control. This feature allows clients to use the 16bit mapped ASN as the ``peer_as`` value for standard BGP communities like *do not announce to $PEER*. In those communities, the 32bit ASN will be represented by the 16bit value which is mapped to it.

For details on how to configure this feature, see the documentation, `"BGP Communities" section <https://arouteserver.readthedocs.io/en/latest/CONFIG.html#bgp-communities>`__.

See also `GitHub issue 101 <https://github.com/pierky/arouteserver/issues/101>`__.

- New: add support for `RFC9234 Route Leak Prevention and Detection Using Roles <https://www.rfc-editor.org/rfc/rfc9234>`__.

A new configuration option is available in general.yml to enable RFC9234 roles (supported by BIRD >= 2.0.11 and OpenBGPD >= 7.5, even though `discouraged until 7.8 will be out <https://github.com/openbgpd-portable/openbgpd-portable/issues/51>`__).
When that's set, BGP sessions on the route server are configured to announce the route-server role and routes received from clients and tagged with the OTC (Only To Customer) attribute are dropped.

This option can be enabled in backward compatibility mode in the general.yml file, and can also be tuned on a client-by-client basis via the clients.yml file.

Details can be found in the `documentation page of general.yml <https://arouteserver.readthedocs.io/en/latest/GENERAL.html#rfc9234-roles-roles>`__.

- New: anchors in HTML pages.

The route server policy textual representation HTML files generated via the ``html`` command now have anchors at the various headers and sub-headers, so when referring other parties to the policy they can be pointed directly to the relevant section.

See also `GitHub issue 119 <https://github.com/pierky/arouteserver/issues/119>`__.

- Fix: minor issues with the HTML pages.

Wrong URL in some links and a misleading reference to a wrong mailing list post about private ASNs.

See also `GitHub issue 119 <https://github.com/pierky/arouteserver/issues/119>`__.

Please note: starting with the next release, the default target version used to build BIRD configurations (when the ``--target-version`` argument is not given) will be the latest from the 2.x major version; until now it was 1.6.8. Operators will need to use the ``--target-version 1.6.8`` command line argument to build BIRD 1.x compatible configurations.

------

- Deprecation: the ARIN Whois OriginAS feature (config knob ``use_arin_bulk_whois_data``, documented in `Use ARIN Whois database to accept routes <https://arouteserver.readthedocs.io/en/latest/CONFIG.html#use-arin-whois-database-to-accept-routes>`__) is being deprecated.

Per `Recommended Draft Policy ARIN-2021-8 <https://www.arin.net/participate/policy/drafts/2021_8/>`__, the "Autonomous System Originations" field is going to be removed from the ARIN database. Consequentially, this feature that is based on that is going to be deprecated as well and will be dropped in future releases of ARouteServer.

Operators that will run ARouteServer with ``use_arin_bulk_whois_data.enabled`` set to ``True`` will see a warning message being logged, about the deprecation.

The publicly available intermediate data relay which was running on the NLNOG infrastructure already removed the source file, which was used to fetch those records. So, operators willing to support this feature will need to provide their own version of the file.

See also `GitHub issue 116 <https://github.com/pierky/arouteserver/issues/116>`__.

------

No new functionalities nor bug fixes here, just a change in the releases of Python which are supported and tested.

- Tests are no longer performed for Python 3.6 (EoL).

- Tests for Python 3.10 and 3.11 are introduced: 3.11 is the release used to perform the integration tests.

- Docker images are built on top of Python 3.11 and PyPy 3.9.

------

- New: add support for OpenBGPD 7.6 and 7.7, also added to the integration testing suite (portable edition only).

------

- New: add support for `BIRD 2.0.10 <https://www.mail-archive.com/bird-usersnetwork.cz/msg06819.html>`__, also added to the integration testing suite.

- New: add support for `OpenBGPD 7.5 <https://undeadly.org/cgi?action=article;sid=20220716101930>`__, also added to the integration testing suite (portable edition only).

- New (OpenBGPD): add support for ADD-PATH (on version 7.5 or above).

- Improvement: abort the configuration building process as soon as one *enricher* fails.

This shorten the user feedback in case of errors that unavoidably would make the final configuration broken and not usable.

- Fix: remove ``RGNET`` from the list of default IRR sources.

To remove it from existing deployments, or to add it back, users can edit the arouteserver.yml file, ``bgpq3_sources`` section.

See also `GitHub issue 111 <https://github.com/pierky/arouteserver/issues/111>`__.