Skip to content

Commit e60d344

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

178 files changed

Lines changed: 1582 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-3415__design-rationale-a-viewtreefamily-pairs-an-oid-family-name-with.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3415
2+
kind: design-rationale
3+
summary: A ViewTreeFamily pairs an OID (family name) with a bitmask to concisely represent families of view subtrees. This avoids enumerating a very large number of individual subtrees when specifying, for example, all columns in a conceptual row — which appear in separate OID subtrees with similar formats that can be aggregated into one structure.
4+
section: "2.4"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__design-rationale-appendix-a-prescribes-three-installation-security-configurations-initial.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-3415
2+
kind: design-rationale
3+
summary: 'Appendix A prescribes three installation security configurations: initial-minimum-security-configuration (unauthenticated access to all of 1.3.6.1), initial-semi-security-configuration (unauthenticated access restricted to system, snmp, snmpEngine, snmpMPDStats, usmStats subtrees only), and initial-no-access-configuration (no pre-configured access). This graduated bootstrap posture lets operators choose their risk tolerance at deployment.'
4+
section: A
5+
topics:
6+
- snmp
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__design-rationale-instance-level-granularity-in-mib-views-is-optional.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3415
2+
kind: design-rationale
3+
summary: Instance-level granularity in MIB views is optional because it may come at a high performance cost. Managers should avoid requesting instance-level configurations unnecessarily; implementations that do not support it must reject such entries with inconsistentName.
4+
section: "4"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__design-rationale-the-presence-of-entries-in-vacmcontexttable-and-vacmaccesstable.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3415
2+
kind: design-rationale
3+
summary: 'The presence of entries in vacmContextTable and vacmAccessTable are deliberately independent: a context in vacmContextTable need not be referenced by any vacmAccessTable entry, and a context referenced in vacmAccessTable need not currently exist in vacmContextTable. This allows pre-configuration of access rights before contexts are instantiated.'
4+
section: "4"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__interoperability-note-support-for-vacmviewtreefamilymask-values-of-non-zero-length.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3415
2+
kind: interoperability-note
3+
summary: Support for vacmViewTreeFamilyMask values of non-zero length (wildcard masks) is optional. Implementations that do not support wildcard masks may make vacmViewTreeFamilyMask effectively read-only with a WRITE-SYNTAX restricted to OCTET STRING (SIZE 0), as reflected in the vacmMIBCompliance MODULE-COMPLIANCE statement.
4+
section: "4"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__interoperability-note-write-access-to-all-vacmaccesstable-columns-vacmaccesscontextmatch-vacmaccessreadviewname.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3415
2+
kind: interoperability-note
3+
summary: Write access to all vacmAccessTable columns (vacmAccessContextMatch, vacmAccessReadViewName, vacmAccessWriteViewName, vacmAccessNotifyViewName, vacmAccessStorageType, vacmAccessStatus) and all vacmViewTreeFamilyTable columns is not required for compliance — an implementation may treat all of these as read-only.
4+
section: "4"
5+
topics:
6+
- snmp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__normative-requirement-for-an-implementation-of-vacm-to-be-conformant.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-3415
2+
kind: normative-requirement
3+
summary: For an implementation of VACM to be conformant, it MUST implement the SNMP-VIEW-BASED-ACM-MIB according to vacmMIBCompliance (vacmBasicGroup is mandatory) and SHOULD implement the initial configuration described in Appendix A.
4+
section: "7.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-3415__normative-requirement-if-a-create-request-for-a-vacmviewtreefamilyentry-would.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-3415
2+
kind: normative-requirement
3+
summary: If a create request for a vacmViewTreeFamilyEntry would provide instance-level granularity and the implementation does not support instance-level granularity, an inconsistentName error MUST be returned.
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__normative-requirement-implementations-must-not-restrict-the-number-of-families.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-3415
2+
kind: normative-requirement
3+
summary: Implementations MUST NOT restrict the number of families of view subtrees for a given MIB view except as dictated by resource constraints on the overall number of entries in the vacmViewTreeFamilyTable.
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- snmp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-3415__normative-requirement-the-vacmaccesstable-entry-selection-algorithm-narrows-candidates-by.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-3415
2+
kind: normative-requirement
3+
summary: 'The vacmAccessTable entry selection algorithm narrows candidates by groupName, context match (exact or prefix), and securityModel (specific beats ''any''), and requires vacmAccessSecurityLevel to be less than or equal to the requested level. Among remaining ties, preference is: exact securityModel > longest contextPrefix > highest securityLevel.'
4+
section: "4"
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)