auto-ingest: ietf-elements backfill — 234 new elements (2026-07-05)

Author: ietf-corpus-bot

corpus/elements/rfc-8532__design-rationale-no-fields-in-path-discovery-data-or-continuity.yaml

@@ -0,0 +1,9 @@
+document: rfc-8532
+kind: design-rationale
+summary: No fields in 'path-discovery-data' or 'continuity-check-data' groupings are made mandatory, so the same generic grouping can serve multiple data retrieval methods (RPC, proactive, on-demand) defined in RFC 8533 without requiring all fields to be populated in every context.
+section: "3.6"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__design-rationale-only-one-measurement-protocol-is-specified-for-delay.yaml

@@ -0,0 +1,9 @@
+document: rfc-8532
+kind: design-rationale
+summary: 'Only one measurement protocol is specified for delay (default: OWAMP, one-way) and one method for jitter (default: IPDV per RFC 3393) for interoperability reasons; if an alternative is used, it is indicated via protocol-id in the RFC 8533 RPC rather than in this base model.'
+section: "5"
+topics:
+    - yang
+    - measurement
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__design-rationale-the-model-is-split-into-two-yang-modules.yaml

@@ -0,0 +1,9 @@
+document: rfc-8532
+kind: design-rationale
+summary: The model is split into two YANG modules—'ietf-lime-time-types' (time/timestamp definitions) and 'ietf-connectionless-oam' (the full model)—so that other LIME data models can import common time types independently without importing the full OAM schema, enabling reuse across the LIME suite.
+section: "3"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__design-rationale-the-tp-address-ni-grouping-separates-the-vrf.yaml

@@ -0,0 +1,10 @@
+document: rfc-8532
+kind: design-rationale
+summary: The 'tp-address-ni' grouping separates the VRF/network-instance reference ('ni' leaf) from 'test-point-location-info' to keep the base grouping addressing-agnostic; the ni leaf is composed separately into each location-type container only where required.
+section: "3"
+topics:
+    - yang
+    - netconf
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__interoperability-note-rfc-7276-classifies-bfd-as-connection-oriented-yet.yaml

@@ -0,0 +1,10 @@
+document: rfc-8532
+kind: interoperability-note
+summary: RFC 7276 classifies BFD as connection-oriented, yet the module's extension examples show BFD managed via the connectionless OAM model as an alternative to the dedicated BFD YANG model, providing a unified OAM management view. Technology-specific groupings from the BFD YANG model can be reused in augmentations to avoid duplication.
+section: "6.1"
+topics:
+    - yang
+    - netconf
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__interoperability-note-two-extension-methods-are-supported-for-adding-technology.yaml

@@ -0,0 +1,9 @@
+document: rfc-8532
+kind: interoperability-note
+summary: 'Two extension methods are supported for adding technology-specific OAM to the base model: (1) YANG augmentation at defined anchor points (technology choice, test-point-locations list, or location-type choice), and (2) schema mount (RFC 8528) via the ''root'' anydata mount point in ''test-point-location-info''. The schema mount method cannot mandate which specific modules must be mounted.'
+section: "6"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__normative-requirement-both-continuity-check-and-path-discovery-boolean-leaves.yaml

@@ -0,0 +1,10 @@
+document: rfc-8532
+kind: normative-requirement
+summary: Both 'continuity-check' and 'path-discovery' boolean leaves in the 'tp-tools' container are declared 'mandatory true', requiring implementations to explicitly declare capability support for both OAM functions at every configured test point.
+section: "5"
+rfc2119_level: REQUIRED
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__normative-requirement-the-tp-location-type-leaf-in-the-tp.yaml

@@ -0,0 +1,10 @@
+document: rfc-8532
+kind: normative-requirement
+summary: The 'tp-location-type' leaf in the 'tp-address' grouping is declared 'mandatory true', requiring every Test Point address entry to explicitly specify its address technology type from the 'tp-address-technology-type' identity hierarchy.
+section: "5"
+rfc2119_level: REQUIRED
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__protocol-element-the-connectionless-oam-tps-grouping-defines-the-oam.yaml

@@ -0,0 +1,9 @@
+document: rfc-8532
+kind: protocol-element
+summary: 'The ''connectionless-oam-tps'' grouping defines the ''oam-neighboring-tps'' list (key: index uint16) with a ''position'' leaf (int8, range -1..1, default 0) encoding the relative stack position of a neighboring test point: -1 means below, 0 means same layer, +1 means above the current test point.'
+section: "3.3"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"

corpus/elements/rfc-8532__protocol-element-the-continuity-check-data-grouping-models-ping-like.yaml

@@ -0,0 +1,10 @@
+document: rfc-8532
+kind: protocol-element
+summary: 'The ''continuity-check-data'' grouping models ping-like output: src-test-point (with egress-intf-name), dest-test-point (with ingress-intf-name), sequence-number (uint64), hop-cnt (uint8), and reused packet/error/delay/jitter statistics groupings.'
+section: "3.7"
+topics:
+    - yang
+    - netconf
+    - measurement
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-05"