Skip to content

Commit 8e2ce19

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 183 new elements (2026-07-12)
1 parent 1cf9f89 commit 8e2ce19

183 files changed

Lines changed: 1770 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎corpus/elements/rfc-9625__design-rationale-it-is-recommended-that-the-default-ip-multicast.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9625
2+
kind: design-rationale
3+
summary: It is RECOMMENDED that the default IP multicast tunnels be distinct from the BUM tunnels when P2MP tunnels are used. Using shared BUM tunnels forces PEs interested only in IP multicast to pull all BUM traffic from source BDs to which they have no local ACs, causing unnecessary bandwidth consumption.
4+
section: "2.6"
5+
topics:
6+
- routing
7+
- mpls
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__design-rationale-smet-routes-scoped-to-the-sbd-rather-than.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9625
2+
kind: design-rationale
3+
summary: SMET routes scoped to the SBD rather than individual BDs enable inter-subnet ASM multicast routing without requiring PIM Rendezvous Points, shared trees, or other PIM RP infrastructure, as long as all sources and receivers remain within the Tenant Domain.
4+
section: "2.5"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__design-rationale-the-sbd-concept-allows-a-pe-not-provisioned.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9625
2+
kind: design-rationale
3+
summary: The SBD concept allows a PE not provisioned with a source BD to still forward inter-subnet multicast correctly by treating all such frames as having originated from the SBD. This avoids requiring every PE to be provisioned with every BD in the Tenant Domain.
4+
section: "2.1"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__interoperability-note-interworking-between-evpn-oism-and-mvpn-domains-is.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9625
2+
kind: interoperability-note
3+
summary: Interworking between EVPN OISM and MVPN domains is handled by an MEG (MVPN/EVPN Gateway), which must perform both OISM and MVPN Layer 3 multicast procedures. The solution must support heterogeneous tunneling, e.g., MVPN using MPLS P2MP while EVPN uses IR or VXLAN.
4+
section: 6.1.2
5+
topics:
6+
- routing
7+
- mpls
8+
- vpn
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__interoperability-note-interworking-with-external-pim-domains-is-handled-by.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9625
2+
kind: interoperability-note
3+
summary: Interworking with external PIM domains is handled by a PEG (PIM/EVPN Gateway). The PEG manages First Hop Router / Last Hop Router responsibilities for sources and receivers crossing the EVPN boundary and must handle both ASM and SSM group models.
4+
section: 6.1.4
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__interoperability-note-interworking-with-non-oism-pes-supporting-only-rfc.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9625
2+
kind: interoperability-note
3+
summary: Interworking with non-OISM PEs (supporting only RFC 7432) requires an IP Multicast Gateway (IPMG) that interfaces OISM tunnels with the BUM tunnels of legacy PEs. The IPMG acts as the IPMG Designated Forwarder for the relevant BDs to avoid duplicate delivery when bridging between the two forwarding domains.
4+
section: "5"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__normative-requirement-an-evpn-pe-supporting-oism-must-be-provisioned.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9625
2+
kind: normative-requirement
3+
summary: An EVPN PE supporting OISM MUST be provisioned with the SBD of each Tenant Domain to which it is attached. The SBD-RT MUST NOT be the same as the RT associated with any other BD; this restriction is necessary for the route-to-BD association rules to produce correct results.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__normative-requirement-an-oism-pe-provisioned-with-several-bds-in.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9625
2+
kind: normative-requirement
3+
summary: An OISM PE provisioned with several BDs in the same Tenant Domain MUST originate an IMET route for each such BD. It SHOULD attach the EVPN Multicast Flags Extended Community to each such IMET route but MUST attach it to at least one.
4+
section: 1.5.1
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__normative-requirement-an-oism-pe-should-attach-the-multicast-flags.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9625
2+
kind: normative-requirement
3+
summary: An OISM PE SHOULD attach the Multicast Flags Extended Community with the OISM-supported flag set to all IMET routes it originates. If PE1 imports IMET routes from PE2 and at least one indicates PE2 is an OISM PE, PE1 MUST assume PE2 follows OISM procedures for all BDs in the Tenant Domain.
4+
section: 1.5.1
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9625__normative-requirement-at-an-ingress-pe-an-ip-multicast-frame.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9625
2+
kind: normative-requirement
3+
summary: At an ingress PE, an IP multicast frame received from an AC is (1) tunneled unchanged to interested remote PEs, and (2) sent up the BD's IRB interface for inter-subnet forwarding. IP multicast sent down a non-SBD IRB interface goes ONLY to local ACs of that BD; remote delivery has already occurred via step 1.
4+
section: "2.3"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)