Skip to content

Commit 607bfb0

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 203 new elements (2026-05-24)
1 parent 844ed12 commit 607bfb0

203 files changed

Lines changed: 1792 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-2266__design-rationale-for-large-octet-counters-readable-unreadable-high-priority.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: design-rationale
3+
summary: For large octet counters (readable, unreadable, high-priority, normal-priority octets), the MIB provides both a 32-bit Counter32 with a paired rollover Counter32 and a 64-bit Counter64. The dual mechanism supports SNMPv1, which lacks 64-bit counters, though retrieval of the two 32-bit counters in the same PDU is not guaranteed to be atomic.
4+
section: "3"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__design-rationale-port-grouping-within-a-repeater-is-recommended-but.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: design-rationale
3+
summary: Port grouping within a repeater is recommended but optional. An implementor may place all ports in a single group or use groups to mirror field-replaceable units. Groups and ports may be sparsely numbered, and the numbering method is implementation-specific.
4+
section: "2.1"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__design-rationale-several-ieee-802-12-managed-objects-were-deliberately.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: design-rationale
3+
summary: 'Several IEEE 802.12 managed objects were deliberately omitted: aGroupMap and aPortMap (derivable via GetNext sweeps), aRepeaterGroupCapacity (ambiguous semantics in chassis/stackable implementations), aRepeaterHealthData/Text (implementation-specific, non-interoperable), and aMediaType (deferred to a future 802.12 PMD MIB).'
4+
section: "2.7"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__design-rationale-the-mib-counters-are-defined-to-be-identical.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: design-rationale
3+
summary: The MIB counters are defined to be identical to those in IEEE Standard 802.12-1995 so that the same hardware instrumentation can satisfy both the IEEE and IETF management standards without duplicating counter logic.
4+
section: "2"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__interoperability-note-ieee-802-12-uses-the-demand-priority-access.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: interoperability-note
3+
summary: IEEE 802.12 uses the Demand Priority Access Method (DPAM), not 802.3 CSMA/CD or 802.5 token ring media access. Although 802.12 can carry 802.3 or 802.5 frame formats, it is incompatible with the 802.3 Repeater MIB's media-access-specific objects; only the topology-mapping OBJECT-GROUP (snmpRptrGrpRptrAddrSearch) from that MIB is encouraged for reuse.
4+
section: 2.6.2
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__interoperability-note-the-mib-ii-interfaces-group-has-no-specific.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: interoperability-note
3+
summary: The MIB-II 'interfaces' group has NO specific relationship to 802.12 repeater ports. The interfaces group applies only to the network interface(s) over which management traffic flows; repeater ports are physical-layer entities and are not represented as MIB-II interfaces.
4+
section: 2.6.1.2
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__interoperability-note-vgrptrportpriorityenable-has-no-effect-on-cascade-ports-or.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2266
2+
kind: interoperability-note
3+
summary: vgRptrPortPriorityEnable has no effect on cascade ports or ports connected to cascaded repeaters; in both cases the port behaves as if the value is always true(1). The object only affects localInternal or localExternal ports connected to end nodes.
4+
section: "3"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__normative-requirement-a-port-that-is-disabled-vgrptrportadminstatus-disabled-when.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2266
2+
kind: normative-requirement
3+
summary: A port that is disabled (vgRptrPortAdminStatus = disabled) when power is lost or a reset is exerted shall remain disabled when normal operation resumes. The value of vgRptrPortAdminStatus should be preserved across repeater resets and power failures.
4+
section: "3"
5+
rfc2119_level: SHOULD
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__normative-requirement-all-mac-address-representations-in-this-mib-are.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2266
2+
kind: normative-requirement
3+
summary: All MAC address representations in this MIB are in canonical (least-significant-bit-first) order as defined by 802.1a, even when the repeater operates in token ring framing mode (which transmits MSB-first on the wire).
4+
section: "2.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2266__normative-requirement-link-training-requires-24-consecutive-error-free-training.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2266
2+
kind: normative-requirement
3+
summary: Link training requires 24 consecutive error-free training frames to be exchanged before vgRptrPortOperStatus transitions to active(1). This requirement, combined with the training frame length (594–675 octets), ensures marginal links will not complete training.
4+
section: "2.4"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)