Skip to content

Commit 349e1de

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 224 new elements (2026-07-05)
1 parent 47ec7f9 commit 349e1de

224 files changed

Lines changed: 2089 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-8503__design-rationale-the-mib-separates-generic-mvpn-state-mvpngenerictable-from.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8503
2+
kind: design-rationale
3+
summary: The MIB separates generic MVPN state (mvpnGenericTable) from BGP-MVPN-specific state (mvpnBgpTable) because the two C-multicast signaling methods (PIM-MVPN and BGP-MVPN) share most managed objects but differ in BGP-specific parameters such as extended communities, route advertisement throttles, and inter-site C-tree mode.
4+
section: "3.1"
5+
topics:
6+
- multicast
7+
- mpls
8+
- bgp
9+
- snmp
10+
- vpn
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__design-rationale-two-compliance-levels-are-defined-mvpnmodulefullcompliance-all-groups.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8503
2+
kind: design-rationale
3+
summary: 'Two compliance levels are defined: mvpnModuleFullCompliance (all groups mandatory) and mvpnModuleReadOnlyCompliance (same groups but all read-write objects downgraded to read-only). The read-only compliance allows monitoring-only deployments without configuration capability, while BGP-specific groups are additionally mandatory only on systems supporting BGP-MVPN.'
4+
section: "3.2"
5+
topics:
6+
- multicast
7+
- mpls
8+
- bgp
9+
- snmp
10+
- vpn
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__interoperability-note-bgp-mpls-layer3-vpn-multicast-mib-is-designed.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8503
2+
kind: interoperability-note
3+
summary: BGP-MPLS-LAYER3-VPN-MULTICAST-MIB is designed to be used in conjunction with MPLS-L3VPN-STD-MIB (RFC 4382) and IPMCAST-MIB (RFC 5132). Row pointers and shared index components (mplsL3VpnVrfName) link entries across these three MIB modules.
4+
section: "3"
5+
topics:
6+
- multicast
7+
- mpls
8+
- snmp
9+
- vpn
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__interoperability-note-several-conceptual-rows-use-multi-component-oid-indexes.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8503
2+
kind: interoperability-note
3+
summary: Several conceptual rows use multi-component OID indexes that can exceed 128 sub-identifiers when address strings are long (e.g., mvpnSpmsiEntry warns if mplsL3VpnVrfName + group addr + source addr exceeds 113 octets). Such rows cannot be accessed via SNMPv1, SNMPv2c, or SNMPv3.
4+
section: "3.2"
5+
topics:
6+
- multicast
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__normative-requirement-for-each-entry-in-mvpngenerictable-there-must-be.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8503
2+
kind: normative-requirement
3+
summary: For each entry in mvpnGenericTable, there MUST be a corresponding VRF entry in MPLS-L3VPN-STD-MIB (RFC 4382). This coupling ensures that every MVPN management entry is anchored to an existing VRF.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- mpls
9+
- snmp
10+
- vpn
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__normative-requirement-for-mvpnmroutecmcastsourceaddrtype-and-mvpnmroutenexthopsourceaddrtype-if-the-value-is.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8503
2+
kind: normative-requirement
3+
summary: For mvpnMrouteCmcastSourceAddrType and mvpnMrouteNextHopSourceAddrType, if the value is not unknown(0), it MUST be the same as the corresponding group address type. A value of unknown(0) indicates a non-source-specific (*,G) entry.
4+
section: "3.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- snmp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__normative-requirement-in-mvpnmroutecmcastgroupaddr-and-mvpnmroutecmcastsourceaddrs-address-bits-beyond-the.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8503
2+
kind: normative-requirement
3+
summary: In mvpnMrouteCmcastGroupAddr and mvpnMrouteCmcastSourceAddrs, address bits beyond the corresponding prefix length MUST be set to zero. This requirement also applies to the equivalent objects in mvpnMrouteNextHopTable.
4+
section: "3.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- multicast
8+
- snmp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__normative-requirement-mvpnsptunnellimit-unsigned32-range-1-4294967295-sets-the-maximum.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8503
2+
kind: normative-requirement
3+
summary: mvpnSPTunnelLimit (Unsigned32, range 1..4294967295) sets the maximum number of selective provider tunnels allowed for a particular MVPN on the PE, per RFC 6513 Section 13. This is a read-write scalar, configurable by the operator.
4+
section: "3.2"
5+
rfc2119_level: SHOULD
6+
topics:
7+
- multicast
8+
- mpls
9+
- snmp
10+
- vpn
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__protocol-element-bgp-mpls-layer3-vpn-multicast-mib-defines-seven.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8503
2+
kind: protocol-element
3+
summary: 'BGP-MPLS-LAYER3-VPN-MULTICAST-MIB defines seven conceptual tables: mvpnGenericTable, mvpnBgpTable, mvpnPmsiTable, mvpnSpmsiTable, mvpnAdvtStatsTable, mvpnMrouteTable, and mvpnMrouteNextHopTable. Together they support monitoring and configuration of MVPN instances on a Provider Edge (PE) router for both PIM-MVPN and BGP-MVPN deployments.'
4+
section: "3.1"
5+
topics:
6+
- multicast
7+
- mpls
8+
- bgp
9+
- snmp
10+
- vpn
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-05"

‎corpus/elements/rfc-8503__protocol-element-mvpnadvtstatstable-tracks-per-mvpn-per-peer-pe-advertisement.yaml‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
document: rfc-8503
2+
kind: protocol-element
3+
summary: mvpnAdvtStatsTable tracks per-MVPN, per-peer-PE advertisement statistics indexed by VRF name, advertisement type (intraAsIpmsi, interAsIpmsi, sPmsi), peer address type, and peer address. Counters include sent, received, received-with-error, malformed tunnel type, and malformed tunnel identifier, with a discontinuity timestamp.
4+
section: "3.2"
5+
topics:
6+
- multicast
7+
- mpls
8+
- bgp
9+
- snmp
10+
- vpn
11+
- measurement
12+
extracted_by: claude-sonnet-4-6
13+
extracted_at: "2026-07-05"

0 commit comments

Comments
 (0)