From 4335766bc5e5ecf46d9615c3cbf2d667dcbcd878 Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 16:36:08 -0300 Subject: [PATCH 1/3] edit: point reference to specific section --- 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 8b0f5f5..eb4114d 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -448,7 +448,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, especially IRRs not operated by RIRs regularly list conflicting information, see . + Furthermore, IRRs not operated by RIRs regularly list conflicting information, see .
Route Objects From 7bc597e89fce01af650d9a6b0740e9e9c25040f0 Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 18:36:19 -0300 Subject: [PATCH 2/3] edit: minor typo or clarity fixes edit: add RFC2622 to references --- draft-ietf-grow-routing-ops-sec-inform.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index eb4114d..3da1d2c 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -459,7 +459,7 @@ However, technically, the semantic of a ROUTE/ROUTE6 object is that of an exact match. - Operators SHOULD create ROUTE/ROUTE6 objects for all prefixes they do or do plan to originate. + Operators SHOULD create ROUTE/ROUTE6 objects for all prefixes they originate or plan to originate.
@@ -489,14 +489,14 @@
Recursively Computing Filters - 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 . 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. 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. @@ -1854,6 +1854,7 @@ + From 0f72bf9ea77669dba6af7bb71709ba3593411461 Mon Sep 17 00:00:00 2001 From: Italo Cunha Date: Sat, 22 Aug 2026 18:38:24 -0300 Subject: [PATCH 3/3] edit: expand discussion of ROUTE/ROUTE6 objects --- draft-ietf-grow-routing-ops-sec-inform.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/draft-ietf-grow-routing-ops-sec-inform.xml b/draft-ietf-grow-routing-ops-sec-inform.xml index 3da1d2c..e056a2d 100644 --- a/draft-ietf-grow-routing-ops-sec-inform.xml +++ b/draft-ietf-grow-routing-ops-sec-inform.xml @@ -454,9 +454,11 @@ Route Objects 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. Operators SHOULD create ROUTE/ROUTE6 objects for all prefixes they originate or plan to originate.