Repository navigation
Minor clarifications or fixes to IRR-based filtering section #20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
4335766
7bc597e
0f72bf9
5e67e05
f469c1d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -448,18 +448,18 @@ | |
| <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-creating-filters" format="default"/>. | ||
| </t> | ||
| <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 for related prefixes (more-specific subprefixes or less-specific superprefixes) may coexist; each object still applies only to its exact prefix. | ||
| </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> | ||
|
|
||
|
|
@@ -489,14 +489,14 @@ | |
| <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> | ||
|
|
@@ -1854,6 +1854,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"/> | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not see a reference to 2622 being added in this commit; Is there already one that was missing the reference?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added a reference to it in line 494 (previously 492) when describing how to convert an AS-SET into a set of prefixes:
|
||
| <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"/> | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.