Skip to content

Commit ffcbd74

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 213 new elements (2026-05-22)
1 parent 89c1ed8 commit ffcbd74

213 files changed

Lines changed: 1867 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-2579__design-rationale-changes-to-a-textual-convention-that-could-cause.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2579
2+
kind: design-rationale
3+
summary: Changes to a textual convention that could cause interoperability problems between old and new implementations are not allowed; such changes require defining a new textual convention with a new name. Allowed revisions include adding enumerations, adding/updating DISPLAY-HINT and REFERENCE, deprecating status, and editorial clarifications.
4+
section: "5"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__design-rationale-for-large-tables-a-mib-defined-helper-object.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2579
2+
kind: design-rationale
3+
summary: For large tables, a MIB-defined helper object returning an acceptable index is recommended for row creation; for small tables, pseudo-random index selection with retry on inconsistentValue is preferred. This distinction is made because scanning all existing rows to find a free index is highly sub-optimal at scale.
4+
section: "2"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__design-rationale-the-rowstatus-description-clause-not-the-convention-itself.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2579
2+
kind: design-rationale
3+
summary: The RowStatus DESCRIPTION clause (not the convention itself) is responsible for specifying whether the status must be non-active in order to modify other columns. This keeps the textual convention general and allows table-specific policies to be expressed in the MIB object description.
4+
section: "2"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__interoperability-note-macaddress-is-always-stored-in-canonical-lsb-first.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2579
2+
kind: interoperability-note
3+
summary: MacAddress is always stored in canonical (LSB-first) order regardless of the underlying 802 technology. This contrasts with 802.5 (Token Ring), which transmits MAC addresses MSB-first; implementors must convert when reading from 802.5 hardware.
4+
section: "2"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__interoperability-note-timestamp-values-are-reset-to-zero-when-sysuptime.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2579
2+
kind: interoperability-note
3+
summary: TimeStamp values are reset to zero when sysUpTime is reset. However, after approximately 497 days sysUpTime wraps back to zero without a re-initialization; in this case TimeStamp values do not change, creating potential ambiguity between old and new timestamps.
4+
section: "2"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__normative-requirement-the-agent-must-detect-conceptual-rows-that-have.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2579
2+
kind: normative-requirement
3+
summary: The agent must detect conceptual rows that have been in notInService or notReady state for an abnormally long period and remove them. In the absence of a DESCRIPTION-specified timeout, approximately 5 minutes is suggested.
4+
section: "2"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__normative-requirement-the-display-hint-clause-must-not-be-present.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2579
2+
kind: normative-requirement
3+
summary: The DISPLAY-HINT clause must not be present when the Textual Convention syntax is OBJECT IDENTIFIER, IpAddress, Counter32, Counter64, or any enumerated syntax (BITS or INTEGER).
4+
section: "3.1"
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__normative-requirement-the-name-of-a-textual-convention-must-begin.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2579
2+
kind: normative-requirement
3+
summary: The name of a textual convention must begin with an upper-case letter, must not conflict with SMIv2 reserved words, shall not exceed 64 characters in length, and must not contain hyphens (except for SMIv1 conversions). All names in standard information modules shall be unique.
4+
section: "3"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__normative-requirement-the-syntax-clause-of-a-textual-convention-macro.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2579
2+
kind: normative-requirement
3+
summary: The SYNTAX clause of a TEXTUAL-CONVENTION macro must refer to a base SMIv2 type or the BITS construct; it cannot reference a previously defined Textual Convention.
4+
section: "3.5"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2579__normative-requirement-when-a-createandgo-set-succeeds-the-agent-must.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2579
2+
kind: normative-requirement
3+
summary: When a createAndGo set succeeds, the agent must immediately set the status column to active and return noError; if the agent lacks sufficient information, it must not create the row and must return inconsistentValue.
4+
section: "2"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

0 commit comments

Comments
 (0)