Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
73 changes: 53 additions & 20 deletions draft-ietf-grow-routing-ops-sec-inform.xml
Original file line number Diff line number Diff line change
Expand Up @@ -448,55 +448,64 @@
<t>
A majority of Regional Internet Registries do also operate an IRR and can control whether registered routes conform to the prefixes that are allocated or directly assigned.
However, it should be noted that the list of such prefixes is not necessarily a complete list, and as such the list of routes in an IRR is not the same as the set of RIR-allocated prefixes.
Furthermore, especially IRRs not operated by RIRs regularly list conflicting information, see <xref target="sec-rir-allocated-prefix-filters" format="default"/>.
Furthermore, IRRs not operated by RIRs regularly list conflicting information, see <xref target="sec-prefix-filters-created-from-internet-routing-registries-irrs-hierarchical" format="default"/>.
</t>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-routesets">
<name>ROUTE-SETs</name>
<t>
ROUTE-SETs are used to specify sets of prefixes in import and export RPSL policies, and can be used to generate BGP import and export filters.
ROUTE-SETs are objects that contain prefix ranges <xref target="RFC2622" format="default" section="2"/> and other ROUTE-SETs <xref target="RFC4012" format="default" section="4.2"/>.
</t>
<t>
One flexibility provided by ROUTE-SETs is the ability to use RPSL prefix-range operators, which include exact prefixes (e.g., 192.168.0.0/24), subprefixes (non-inclusive) of a prefix (192.168.0.0/16^-), a prefix and its subprefixes (192.168.0.0/16^+), or any subprefix within a specified prefix length range (e.g., 2001:db8::/32^44-48).
These operators allow for more compact specification of prefix sets in complex configurations.
</t>
<t>
An operator can define ROUTE-SET objects for the routes it plans to announce to neighbors.
Transit providers can define ROUTE-SETs that include ROUTE-SETs defined by their customers.
A network operator can define multiple ROUTE-SETs, each covering different sets of prefixes, to better match different types of peering agreements with neighboring networks.
For example, a transit network may define AS65536:RS-EUROPE for routes learned from customers and announced to peers in Europe, AS65536:RS-NAMERICA for routes learned from customers and announced to peers in North America, and AS65536:RS-ALL for routes announced to its providers.
</t>
</section>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-routeobjects">
<name>Route Objects</name>
<t>
The corner stone of IRR based information are ROUTE (IPv4) and ROUTE6 (IPv6) objects.
These document, for a given prefix, the AS/ASes allowed to originate the prefix.
Note that for a given prefix also more specific objects may exist.
However, technically, the semantic of a ROUTE/ROUTE6 object is that of an exact match.
IRRs store ROUTE (IPv4) and ROUTE6 (IPv6) objects.
Each ROUTE/ROUTE6 object specifies that a given prefix may be announced by a given origin ASN,
and multiple ROUTE/ROUTE6 objects may map one prefix to multiple origin ASNs.
The semantics of a ROUTE/ROUTE6 object are those of an exact prefix match.
ROUTE/ROUTE6 objects may cover other ROUTE/ROUTE6 objects for more specific subprefixes as well as be covered by ROUTE/ROUTE6 objects for less specific superprefixes.
</t>
<t>
Operators <bcp14>SHOULD</bcp14> create ROUTE/ROUTE6 objects for all prefixes they do or do plan to originate.
Operators <bcp14>SHOULD</bcp14> create ROUTE/ROUTE6 objects for all prefixes they originate or plan to originate.
</t>
</section>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-assets">
<name>AS-SETs</name>
<t>
An AS-SET is an object that contains AS numbers or other AS-SETs.
The purpose of AS-SETs is creating a recursively queryable structure documenting the cone, i.e., the set of all prefixes announced by the AS itself, or any of its downstreams, of an AS.
A common use for AS-SETs is creating a recursively queryable structure documenting the cone, i.e., the set of all prefixes announced by the AS itself, or any of its downstreams, of an AS.
An operator may create an AS-SET defining all AS numbers of its customers.
A transit provider might create an AS-SET listing the AS numbers or AS-SETS of those ASes it provides upstream to. In turn, these ASes describe the AS numbers/AS-SETS of their customers, etc.
Using recursion, it is possible to retrieve from an AS-SET the complete list of AS numbers that the neighbor is likely to announce.
For each of these AS numbers, it is also easy to look in the corresponding IRR for all associated prefixes.
</t>
<t>
Please note that different IRR may provide conflicting data, especially on AS-SETs.
Recently, an attack was observed where a malicious party created an empty AS-SET for a large transit provider (see <xref target="NLNOG-22" format="default"/>).
As it was created in an RIR database often taking precedent over other IRR sources, several ASes imported this empty AS-SET, and hence filtered all prefixes advertised by this transit provider.
To mitigate this issue, hierarchical AS-SETs reside in the IRR of the RIR and explicitly list the ASN to which they pertain, e.g., AS65536:AS-EXAMPLE.
Additionally, the IRR source may also be referenced: RIPE::AS65536:AS-EXAMPLE.
</t>
<t>
Operators <bcp14>SHOULD</bcp14> create a hierarchical AS-SET representing their cone.
If AS-SETs are included in another AS-SET, they <bcp14>SHOULD</bcp14> be hierarchical.
</t>
</section>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-creating-filters">
<name>Recursively Computing Filters</name>
<t>
Using AS-SETs and ROUTE/ROUTE6 objects, it is possible to use the IRR information to build, for a given neighbor AS, a list of prefixes the neighbor is authorized to originated or transited.
Using AS-SETs and ROUTE/ROUTE6 objects, it is possible to use the IRR information to build, for a given neighbor AS, a list of prefixes the neighbor is authorized to originate or transit <xref target="RFC2622" format="default" section="5.3"/>.
This can be done relatively easily using scripts and existing tools capable of retrieving this information from the registries.
This approach is exactly the same for both IPv4 and IPv6.
</t>
<t>
The macro-algorithm for the script is as follows.
For the neighbor that is considered, the distant operator has provided the AS and may be able to provide a hierarchically named AS-SET object (aka AS-MACRO).
With these two mechanisms, a script can build, for a given neighbor, that lists allowed prefixes and the AS number from which they should be originated.
With these two mechanisms, a script can build a filter for a given neighbor that lists allowed prefixes and the AS number from which they should be originated.
One could decide not to use the origin information and only build monolithic prefix filters from fetched data combining prefixes a neighbor is authorized to transit and originate.
</t>
<t>
Expand All @@ -507,6 +516,13 @@
When doing requests inside such an IRR, it is possible to specify the source of information in order to have the most reliable data.
One could check a popular IRR containing many sources (such as RADb <xref target="RADb" format="default"/>, the Routing Assets Database) and only select as sources some desired RIRs and trusted major ISPs (Internet Service Providers).
</t>
<t>
ROUTE-SETs may contain AS numbers and AS-SETs, which must be mapped to prefixes using the process above. However, ROUTE-SETs that do not include ASes or AS-SETs are independent of ROUTE/ROUTE6 objects and do not require the mapping described above.
</t>
</section>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-management">
<name>Managing and Updating Filters</name>
<t>
As objects in IRRs may frequently vary over time, it is important that prefix filters computed using this mechanism are refreshed regularly.
Refreshing the filters on a daily basis <bcp14>SHOULD</bcp14> be considered because routing changes must sometimes be done in an emergency and registries may be updated at the very last moment.
Expand All @@ -517,6 +533,22 @@
Please note that large BGP filters will negatively impact performance when ingesting routes, even when operators carefully craft and apply their filters to minimize the performance overhead, see <xref target="sec-prefix-filtering-considerations-order" format="default"/>.
</t>
</section>

<section anchor="sec-prefix-filters-created-from-internet-routing-registries-irrs-hierarchical">
<name>Scoping with Hierarchical AS-SETs and ROUTE-SETs</name>
<t>
Please note that different IRRs may provide conflicting data, especially on ROUTE, ROUTE6, AS-SET, and ROUTE-SET objects.
In 2022, an attack was observed where a malicious party created an empty AS-SET for a large transit provider (see <xref target="NLNOG-22" format="default"/>).
As it was created in an RIR database often taking precedence over other IRR sources, several ASes imported this empty AS-SET, and hence filtered all prefixes advertised by this transit provider.
To mitigate this issue, hierarchical AS-SETs and ROUTE-SETs reside in the IRR of the RIR and explicitly list the ASN to which they pertain, e.g., AS65536:AS-EXAMPLE or AS65536:RS-EXAMPLE.
In RIR-operated IRRs, only the maintainer of the ASN (or the corresponding aut-num object) before the colon is authorized to create and modify these objects, preventing unauthorized creation or spoofing.
Additionally, the IRR source may also be referenced: RIPE::AS65536:AS-EXAMPLE or RIPE::AS65536:RS-EXAMPLE.
</t>
<t>
Operators <bcp14>SHOULD</bcp14> create a hierarchical AS-SET representing their cone or hierarchical ROUTE-SETs for prefixes they plan to announce.
If AS-SETs are included in another AS-SET or if ROUTE-SETs are included in another ROUTE-SET, they <bcp14>SHOULD</bcp14> be hierarchical.
</t>
</section>
</section>
<section anchor="sec-sidr-secure-inter-domain-routing">
<name>SIDR - Secure Inter-Domain Routing: RPKI</name>
Expand Down Expand Up @@ -1854,6 +1886,7 @@
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1191.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1918.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1997.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2622.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2827.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3345.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3704.xml"/>
Expand Down