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

Author: ietf-corpus-bot

corpus/elements/rfc-8695__design-rationale-several-capabilities-are-modeled-as-optional-yang-features.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: design-rationale
+summary: Several capabilities are modeled as optional YANG features (bfd, explicit-neighbors, global-statistics, interface-statistics) to allow vendors to selectively implement them. The document explicitly states it is each vendor's responsibility to decide whether to support a given feature.
+section: "2.7"
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__design-rationale-the-data-model-conforms-to-nmda-rfc-8342.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: design-rationale
+summary: The data model conforms to NMDA (RFC 8342) by combining operational state data with associated configuration data in the same schema hierarchy, rather than separating them. When queried from the operational state datastore, both 'config true' (rw) and 'config false' (ro) nodes are returned.
+section: "2.4"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__design-rationale-the-model-does-not-define-rip-specific-notifications.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: design-rationale
+summary: The model does not define RIP-specific notifications; instead it relies on the generic YANG notification subscription mechanisms defined in RFC 8639 and RFC 8641, which support per-client subscriptions, subtree/XPath filters, and periodic or on-demand delivery.
+section: "2.6"
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__interoperability-note-the-ietf-rip-module-imports-and-depends-on.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: interoperability-note
+summary: The 'ietf-rip' module imports and depends on ietf-routing (RFC 8349), ietf-interfaces (RFC 8343), ietf-ip (RFC 8344), ietf-key-chain (RFC 8177), ietf-bfd-types, ietf-ospf, and ietf-isis. Implementations must support these modules to use the RIP YANG model.
+section: "1.3"
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__normative-requirement-ospfv2-redistribution-into-rip-is-only-applicable-when.yaml

@@ -0,0 +1,10 @@
+document: rfc-8695
+kind: normative-requirement
+summary: OSPFv2 redistribution into RIP is only applicable when the RIP instance type is 'ripv2', and OSPFv3 redistribution is only applicable when the type is 'ripng'. This is enforced with YANG 'when' statements on the respective lists.
+section: "4"
+rfc2119_level: MUST
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__normative-requirement-ripv2-interfaces-must-have-an-ipv4-address-configured.yaml

@@ -0,0 +1,10 @@
+document: rfc-8695
+kind: normative-requirement
+summary: RIPv2 interfaces must have an IPv4 address configured, and RIPng interfaces must have an IPv6 address configured. This is enforced by a YANG 'must' statement on the interface leaf that checks the corresponding ip:ipv4 or ip:ipv6 presence.
+section: "4"
+rfc2119_level: MUST
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__normative-requirement-the-timers-container-enforces-that-invalid-interval-must.yaml

@@ -0,0 +1,10 @@
+document: rfc-8695
+kind: normative-requirement
+summary: The timers container enforces that invalid-interval must be at least three times the value of update-interval, and flush-interval must be larger than invalid-interval. These constraints are encoded as YANG 'must' statements and will cause an error if violated.
+section: "4"
+rfc2119_level: MUST
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__protocol-element-explicit-neighbor-configuration-feature-explicit-neighbors-is-supported.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: protocol-element
+summary: Explicit neighbor configuration (feature 'explicit-neighbors') is supported per interface, allowing specification of RIP neighbor IP addresses for use on non-broadcast multiple access (NBMA) networks where multicast neighbor discovery is not available.
+section: "4"
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__protocol-element-global-statistics-feature-global-statistics-track-discontinuity-time.yaml

@@ -0,0 +1,9 @@
+document: rfc-8695
+kind: protocol-element
+summary: Global statistics (feature 'global-statistics') track discontinuity-time, requests-rcvd, requests-sent, responses-rcvd, and responses-sent as yang:counter32 values. Per-interface statistics (feature 'interface-statistics') track discontinuity-time, bad-packets-rcvd, bad-routes-rcvd, and updates-sent.
+section: "2.4"
+topics:
+    - yang
+    - routing
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"

corpus/elements/rfc-8695__protocol-element-interface-authentication-is-applicable-only-to-ripv2-not.yaml

@@ -0,0 +1,10 @@
+document: rfc-8695
+kind: protocol-element
+summary: 'Interface authentication is applicable only to RIPv2 (not RIPng) and supports two modes: key-chain reference (using ietf-key-chain) or explicit key string with a crypto-algorithm identity. This is modeled as a YANG choice within the authentication container.'
+section: "4"
+topics:
+    - yang
+    - routing
+    - crypto
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-06"