From b6699ebf919a454a12bb5aeb25163253e71a368d Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 17:13:22 -0300 Subject: [PATCH 1/4] edit: rephrase purpose of AS-SETs Toning down "purpose" of AS-SETs into "common use case", and dropping ROUTE/ROUTE6 objects as "the cornerstone" of IRR-based filtering. Extended reasoning: My operational practice managing IRR objects for the PEERING Research Testbed (AS47065) is that ROUTE-SETs are significantly more flexible and easier to manage than the AS-SETs and ROUTE/ROUTE6 combo widely employed by operators today. This RFC is an opportunity to steer operators towards ROUTE-SETs and possibly improve operational practice. ROUTE-SETs allow precise specification of prefixes via RPSL prefix-range operators, and an AS can define multiple ROUTE-SETs for different peering relationships. ROUTE/ROUTE6 objects are not hierarchical, have few contraints on who can create them, and do not support range operators. As AS added as a member of an AS-SET contributes the exact same of routes to a prefix, which implies that AS-SETs cannot define different sets of prefixes better suited to different peering relationships. RPSL allows operators to specify import and export rules using the following syntax (in aut-num objects): mp-import: from import mp-export: to export I would argue that AS-SETs are better fit for specifying the part of import/export rules (which is usually just an ASN), and that ROUTE-SETs are a better fit for the part of import/export rule. The only limitation I can think of ROUTE-SETs relative to the AS-SET plus ROUTE combo is that ROUTE-SETs alone do not allow AS-path-based filters that check that the originator of an announcement is within a given AS-SET. This does not seem like a significant loss: (1) I would guess that few operators configure AS-path-based filters, and (2) the RFC should recommend that operators deploy ROV for origin validation instead of ROUTE/ROUTE6 objects. --- draft-ietf-grow-routing-ops-sec-inform.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index f2e9766..eafb8ac 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -477,7 +477,7 @@ AS-SETs 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. From d58ebab1b47de4c3f071c548c2deae3c9b049b26 Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 18:42:28 -0300 Subject: [PATCH 2/4] edit: add discussion around ROUTE-SETs --- draft-ietf-grow-routing-ops-sec-inform.xml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index eafb8ac..c59cc34 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -460,6 +460,25 @@ 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, IRRs not operated by RIRs regularly list conflicting information, see . + +
+ ROUTE-SETs + + 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 and other ROUTE-SETs . + + + 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. + + + 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. + +
+
Route Objects From 1297503e3b1cd3199b54c76729e9e6bc231c75ad Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 18:43:27 -0300 Subject: [PATCH 3/4] edit: move discussion of hierarchical names to separate section --- draft-ietf-grow-routing-ops-sec-inform.xml | 29 +++++++++++++--------- 1 file changed, 17 insertions(+), 12 deletions(-) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index c59cc34..2e9da62 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -458,7 +458,7 @@ 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, IRRs not operated by RIRs regularly list conflicting information, see . + Furthermore, IRRs not operated by RIRs regularly list conflicting information, see .
@@ -502,17 +502,6 @@ 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. - - 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 ). - 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. - - - Operators SHOULD create a hierarchical AS-SET representing their cone. - If AS-SETs are included in another AS-SET, they SHOULD be hierarchical. -
@@ -546,6 +535,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 .
+ +
+ Scoping with Hierarchical AS-SETs and ROUTE-SETs + + 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 ). + 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. + + + Operators SHOULD 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 SHOULD be hierarchical. + +
SIDR - Secure Inter-Domain Routing: RPKI From 9f1dd4f622b3db5819412b21b9798f18e7e7108f Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 18:43:52 -0300 Subject: [PATCH 4/4] edit: move management of filters to separate section --- draft-ietf-grow-routing-ops-sec-inform.xml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index 2e9da62..b5af904 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -525,6 +525,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 , the Routing Assets Database) and only select as sources some desired RIRs and trusted major ISPs (Internet Service Providers). + + 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. + +
+ +
+ Managing and Updating Filters 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 SHOULD be considered because routing changes must sometimes be done in an emergency and registries may be updated at the very last moment.