v0.16.0

CHANGES.rst

@@ -3,8 +3,8 @@ Change log
 
 .. note:: **Upgrade notes**: after upgrading, run the ``arouteserver setup-templates`` command to sync the local templates with those distributed with the new version. More details on the `Upgrading <https://arouteserver.readthedocs.io/en/latest/INSTALLATION.html#upgrading>`__ section of the documentation.
 
-next release
-------------
+v0.16.0
+-------
 
 - Improvement: OpenBGPD, more flexibility for inbound communities values.
 

docs/_static/tests_real_general.html

@@ -89,6 +89,9 @@ <h3>IRRDBs prefix/origin ASN enforcement</h3>
 
 <li><p>RPKI ROAs are fetched from the RIPE RPKI Validator cache file at <a href="http://localcert.ripe.net:8088/export.json" rel="noopener">http://localcert.ripe.net:8088/export.json</a>. The following Trust Anchors are used: APNIC from AFRINIC RPKI Root, APNIC from ARIN RPKI Root, APNIC from IANA RPKI Root, APNIC from LACNIC RPKI Root, APNIC from RIPE RPKI Root, AfriNIC RPKI Root, LACNIC RPKI Root, RIPE NCC RPKI Root</p></li>
 
+<li><p>Use <strong>ARIN Whois DB dump</strong> to validate routes whose origin ASN is authorized by the client's AS-SET but whose prefix is not.</p></li>
+
+<li><p>Database is fetched from <a href="http://irrexplorer.nlnog.net/static/dumps/arin-whois-originas.json.bz2" rel="noopener">http://irrexplorer.nlnog.net/static/dumps/arin-whois-originas.json.bz2</a>.</p></li>
 
 <li><p>
 Route <strong>validity state</strong> is signalled to route server clients using the following <strong>BGP communities</strong>: