Doc: Add ASPA nettype

Edited-By: Ondrej Zajicek <santiago@crfreenet.org>

diff --git a/doc/bird.sgml b/doc/bird.sgml
index 25afe0707f6511d2b39e3bd5381ecb8f4bf2d7dc..22952870e86c156f8d10e8791bbd8df94e16ea95 100644 (file)
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -328,6 +328,18 @@ Their keywords are <cf/roa4/ and <cf/roa6/.
        <item>(PK) AS number
 </itemize>
 
+<sect1>Autonomous System Provider Authorization routes
+<label id="aspa-routes">
+
+<p>These entries can be used to validate <cf/AS_PATH/ attribute of BGP routes.
+An ASPA entry specifies a list of valid providers for specific Autonomous System.
+Configuration keyword is <cf/aspa/.
+
+<itemize>
+       <item>(PK) AS number
+       <item>List of AS numbers of providers
+</itemize>
+
 <sect1>Flowspec for IPv4 and IPv6
 <label id="flow-routes">
 
@@ -1701,6 +1713,9 @@ in the foot).
        prefixes, and also <cf/.maxlen/ which extracts maximal prefix length,
        and <cf/.asn/ which extracts the ASN.
 
+       <cf/NET_ASPA/ prefixes hold an ASN, which can be extracted by <cf/.asn/
+       operator.
+
        <cf/NET_FLOW4/ and <cf/NET_FLOW6/ hold an IP prefix together with a
        flowspec rule. Filters currently do not support much flowspec parsing,
        only <cf/.src/ and <cf/.dst/ operators to get source and destination