Arouteserver

-------

- Fix: minor installation issues.

-------

- New feature: allow to set the source of IRR objects.

AS-SETs can be prepended with an optional source: ``RIPE::AS-FOO``, ``RIPE::AS64496:AS-FOO``.

- New feature: support for RPKI-based Origin Validation added to OpenBGPD configurations.

RPKI ROAs must be loaded from a RIPE RPKI Validator cache file (local or via HTTP).
Mostly inspired by Job Snijders' tool https://github.com/job/rtrsub

- Improvement: RPKI ROAs can be loaded from a local file too.

The file must be in RIPE RPKI Validator cache format.

- Fix (minor): remove internal communities before accepting blackhole routes tagged with a custom blackhole community.

This bug did not affect routes tagged with the BLACKHOLE community; anyway, the internal communities were scrubbed before routes were announced to clients.

-------

- Fix: avoid empty lists of prefixes when a client's ``white_list_pref`` contains only prefixes for an IP version different from the current one.

-------

- Fix: handle the new version of the JSON schema built by `arin-whois-bulk-parser <https://github.com/NLNOG/arin-whois-bulk-parser>`__.

-------

- Improvement: OpenBGPD, more flexibility for inbound communities values.

This allows to use inbound 'peer_as' communities which overlap with other inbound communities whose last *part* is a private ASN.

- New feature: use ARIN Whois database dump to authorize routes.

This feature allows to accept those routes whose origin ASN is authorized by a client AS-SET, whose prefix has not a corresponding route object but is covered by an ARIN Whois record for the same origin ASN.

- Improvement: extend the use of *RPKI ROAs as route objects* and *ARIN Whois database dump* to ``tag_as_set``-only mode.

Before of this, the *RPKI ROAs as route objects* and *ARIN Whois DB dump* features were used only when origin AS and prefix enforcing was set.
Starting with this release they are used even when enforcing is not configured and only the ``tag_as_set`` mode is used.

-------

- New feature: ``configure`` and ``show_config`` *support* commands.

- ``configure``: it can be used to quickly generate a route server policy definition file (``general.yml``) on the basis of best practices and suggestions.

- ``show_config``: to display current configuration settings and also options that have been left to their default values.

- New feature: ``ixf-member-export`` command, to build `IX-F Member Export JSON files <https://github.com/euro-ix/json-schemas>`__ from the list of clients.

- Improvement: cache expiry time values can be set for each external resource type: PeeringDB info, IRR data, ...