auto-ingest: ietf-elements backfill — 205 new elements (2026-07-06)

Author: ietf-corpus-bot

corpus/elements/rfc-8652__design-rationale-igmp-ipv4-and-mld-ipv6-are-defined-as.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: design-rationale
+summary: IGMP (IPv4) and MLD (IPv6) are defined as separate schema branches rather than a combined address-family branch. This provides independent optionality, consistency with RFC 8344's IPv4/IPv6 separation, and cleaner accommodation of protocol differences including different feature sets and node types.
+section: "2.3"
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__design-rationale-optional-capabilities-are-extensively-declared-as-yang-features.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: design-rationale
+summary: Optional capabilities are extensively declared as YANG features to simplify vendor capability negotiation. Operational state parameters are not widely designated as features because defaulting an operational state parameter is unlikely to harm the system, and implementations can often derive a suitable value.
+section: "2.2"
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__design-rationale-rarely-implemented-protocol-parameters-explicit-tracking-maximum-transmit.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: design-rationale
+summary: Rarely implemented protocol parameters (explicit tracking, maximum transmit rate, last member query count, other querier present time, send router alert, startup query interval/count at global level; disable router alert check, passive mode, promiscuous mode, etc. at interface level) are omitted from the model and left for augmentation to avoid overspecifying optional behavior.
+section: 2.1.1
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__interoperability-note-the-model-covers-igmpv1-igmpv2-igmpv3-mldv1-and.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: interoperability-note
+summary: The model covers IGMPv1, IGMPv2, IGMPv3, MLDv1, and MLDv2 but explicitly excludes IGMP/MLD Proxy (RFC 4605) and IGMP/MLD Snooping (RFC 4541), which are to be specified in separate documents.
+section: "2.1"
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__normative-requirement-an-igmp-interface-name-leafref-must-reference-an.yaml

@@ -0,0 +1,10 @@
+document: rfc-8652
+kind: normative-requirement
+summary: An IGMP interface-name leafref must reference an interface that has IPv4 configured (either enabled or disabled); similarly, an MLD interface-name must reference an interface with IPv6 configured. YANG must constraints enforce these with explicit error messages.
+section: "4"
+rfc2119_level: MUST
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__normative-requirement-source-specific-parameters-max-group-sources-source-policy.yaml

@@ -0,0 +1,10 @@
+document: rfc-8652
+kind: normative-requirement
+summary: Source-specific parameters (max-group-sources, source-policy, explicit-tracking, lite-exclude-filter) require IGMP version 3; YANG must constraints enforce this, returning an error message if configured with a lower version.
+section: "4"
+rfc2119_level: MUST
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__normative-requirement-the-augmentation-to-ietf-routing-allows-multiple-igmp.yaml

@@ -0,0 +1,10 @@
+document: rfc-8652
+kind: normative-requirement
+summary: The augmentation to ietf-routing allows multiple IGMP or MLD instances, but a restriction MAY be added depending on the implementation and the device.
+section: "3.1"
+rfc2119_level: MAY
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__normative-requirement-the-last-member-query-interval-leaf-must-not.yaml

@@ -0,0 +1,10 @@
+document: rfc-8652
+kind: normative-requirement
+summary: The last-member-query-interval leaf must not be configured when IGMP version is 1; a YANG must constraint enforces this with error-message 'IGMPv1 does not support last-member-query-interval.'
+section: "4"
+rfc2119_level: MUST NOT
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__protocol-element-each-of-igmp-and-mld-defines-a-clear.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: protocol-element
+summary: Each of IGMP and MLD defines a clear-groups action (feature action-clear-groups) that takes a mandatory interface choice (by name or all-interfaces), a group-address (IPv4/IPv6 multicast address or '*' for all groups), and a source-address (or '*' for all sources) to clear cache entries.
+section: "3.3"
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8652__protocol-element-each-source-record-under-a-group-contains-source.yaml

@@ -0,0 +1,9 @@
+document: rfc-8652
+kind: protocol-element
+summary: Each source record under a group contains source-address, expire (uint32, mandatory), up-time (uint32, mandatory), optional host-count (requires intf-explicit-tracking feature), last-reporter, and an optional list of host entries (keyed by host-address with host-filter-mode) when explicit tracking is enabled.
+section: "3.1"
+topics:
+    - yang
+    - multicast
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"