Arouteserver

------

- Fix: IPv4 prefix length verification when RFC8950 is enabled.

When a peer is configured for RFC8950 support, the prefix length is checked for the IPv6 limits only. This will permit too long IPv4 (up to /48) prefixes and will reject short IPv4 (< /12) prefixes.

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

------

- New: add support of IPv6 NEXT_HOP for IPv4 routes (`RFC8950 <https://tools.ietf.org/html/rfc8950>`__).

Only available for BIRD 2.x.

------

- New: add support for `BIRD 2.15 <https://www.mail-archive.com/bird-usersnetwork.cz/msg07905.html>`__ and `OpenBGPD 8.4 <https://www.undeadly.org/cgi?action=article;sid=20240308064655>`__, also added to the integration testing suite.

------

- Fix: fetching Registro.br dataset via HTTPS.

A *"Can't decode Registro.br Whois DB raw file"* error was raised when trying to fetch the dataset from Registro.br using HTTPS.

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

------

- Fix: ``irr-as-set`` command, the parser considers hierarchical AS-SET names.

Names in the format ``AS<n>:<s>`` were considered as in the format ``source:name``.

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

------

- Fix: ``irr-as-set`` command, omit AS-SETs having a source different from the target registry.

The list of members used to build the IRR object no longer includes client's AS-SETs if their origin does not match the registry for which the object is being created.

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

- Improvement: ``irr-as-set`` command, ``--include-members`` and ``--exclude-members`` options.

Add options to the command that allow the operator to include/exclude AS-SETs from the members list of the object being generated.