Skip to content

Commit 5ca9602

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 264 new elements (2026-05-24)
1 parent ad74fee commit 5ca9602

264 files changed

Lines changed: 2355 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-2576__design-rationale-the-snmp-community-mib-uses-a-transport-tag.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: design-rationale
3+
summary: The SNMP-COMMUNITY-MIB uses a transport tag mechanism (snmpCommunityTransportTag) referencing the snmpTargetAddrTable rather than embedding addresses directly in the community table, allowing community strings to be accepted only from specific subnets without duplicating address configuration.
4+
section: "5.3"
5+
topics:
6+
- snmp
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__design-rationale-two-coexistence-approaches-are-provided-multi-lingual-implementations.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: design-rationale
3+
summary: 'Two coexistence approaches are provided: multi-lingual implementations (a single entity supports multiple SNMP versions and selects the appropriate one per peer) and proxy implementations (a forwarder translates between versions on behalf of mono-lingual entities). The proxy approach is also useful for securing communications over insecure links between locally secure networks.'
4+
section: "4"
5+
topics:
6+
- snmp
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__interoperability-note-counter64-is-the-only-smiv2-syntax-incompatible-with.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2576
2+
kind: interoperability-note
3+
summary: Counter64 is the only SMIv2 syntax incompatible with SMIv1; all other SMIv2 syntaxes are compatible. This incompatibility requires special handling in multi-lingual command responders and proxy forwarders and prevents transmission of Counter64 values over SNMPv1.
4+
section: 4.1.2.1
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__interoperability-note-in-smiv1-the-access-clause-specifies-the-minimum.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2576
2+
kind: interoperability-note
3+
summary: In SMIv1, the ACCESS clause specifies the minimum required access, while in SMIv2, the MAX-ACCESS clause specifies the maximum allowed access — this semantic inversion must be carefully considered during MIB module conversion.
4+
section: 2.1.1
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__interoperability-note-snmpv1-error-codes-should-not-be-forwarded-unchanged.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: interoperability-note
3+
summary: SNMPv1 error codes SHOULD NOT be forwarded unchanged in SNMPv2c or SNMPv3 messages, except in proxy forwarding scenarios where backwards compatibility permits reuse of SNMPv1 error codes without translation.
4+
section: 4.1.2
5+
rfc2119_level: SHOULD NOT
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__interoperability-note-when-a-proxy-forwards-an-snmpv1-trap-as.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2576
2+
kind: interoperability-note
3+
summary: When a proxy forwards an SNMPv1 Trap as an SNMPv2 notification, three additional variable bindings (snmpTrapAddress.0, snmpTrapCommunity.0, snmpTrapEnterprise.0) are appended to preserve the original SNMPv1 agent-addr, community string, and enterprise OID.
4+
section: "3.1"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__normative-requirement-a-command-generator-must-downgrade-getbulkrequest-pdus-to.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: normative-requirement
3+
summary: A command generator MUST downgrade GetBulkRequest PDUs to GetNextRequest PDUs when SNMPv1 is selected as the message version, by changing the operation type to GetNext and ignoring non-repeaters and max-repetitions values.
4+
section: 4.1.1
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__normative-requirement-for-smiv1-to-smiv2-conversion-the-access-clause.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: normative-requirement
3+
summary: For SMIv1-to-SMIv2 conversion, the ACCESS clause MUST be replaced by MAX-ACCESS. A write-only ACCESS value MUST become read-write with a DESCRIPTION noting implementation-specific read results. STATUS values of 'mandatory' or 'optional' MUST be replaced with 'current', 'deprecated', or 'obsolete'.
4+
section: 2.1.1
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__normative-requirement-for-smiv1-to-smiv2-mib-conversion-the-imports.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: normative-requirement
3+
summary: 'For SMIv1-to-SMIv2 MIB conversion: the IMPORTS statement MUST reference SNMPv2-SMI; MODULE-IDENTITY MUST be invoked immediately after IMPORTS; unbounded INTEGER MUST become Integer32; Counter MUST become Counter32; Gauge MUST become Gauge32 or Unsigned32.'
4+
section: 2.1.1
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2576__normative-requirement-if-an-snmpv2-trap-pdu-received-by-a.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2576
2+
kind: normative-requirement
3+
summary: If an SNMPv2-Trap-PDU received by a proxy contains Counter64 objects, the trap cannot be forwarded using SNMPv1. An InformRequest-PDU configuration indicating SNMPv1 forwarding SHALL be ignored; InformRequest-PDUs can only be forwarded using SNMPv2c or SNMPv3.
4+
section: 4.2.2
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)