auto-ingest: ietf-elements backfill — 230 new elements (2026-07-12)

Author: ietf-corpus-bot

corpus/elements/rfc-9644__design-rationale-the-four-iana-algorithm-yang-modules-are-not.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: design-rationale
+summary: The four IANA algorithm YANG modules are not published within this RFC; instead, Appendix A provides a generating script for IANA to produce and maintain these modules directly, keeping YANG enumerations synchronized with IANA registry updates without requiring RFC updates.
+section: "1"
+topics:
+    - yang
+    - registry
+    - process
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__design-rationale-the-groupings-intentionally-avoid-wrapping-uses-statements-in.yaml

@@ -0,0 +1,8 @@
+document: rfc-9644
+kind: design-rationale
+summary: The groupings intentionally avoid wrapping 'uses' statements in a named container to provide maximum flexibility to consuming models; consuming modules are expected to resolve name conflicts by wrapping the 'uses' statement in an appropriately named container (e.g., 'ssh-client-parameters').
+section: "3.3"
+topics:
+    - yang
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__design-rationale-the-ssh-client-grouping-and-ssh-server-grouping.yaml

@@ -0,0 +1,9 @@
+document: rfc-9644
+kind: design-rationale
+summary: The ssh-client-grouping and ssh-server-grouping explicitly exclude all transport-level configuration (ports, addresses) to allow consuming modules to define their own TCP connection strategy, enabling reuse in diverse scenarios such as NETCONF Call Home (RFC 8071) without modification.
+section: "1.1"
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__interoperability-note-optional-support-for-rfc-6187-x-509v3-certificates.yaml

@@ -0,0 +1,11 @@
+document: rfc-9644
+kind: interoperability-note
+summary: Optional support for RFC 6187 (X.509v3 Certificates for SSH Authentication) is gated by the 'ssh-x509-certs' feature in ietf-ssh-common; when enabled, clients may authenticate via certificates and servers may validate client certificates against CA or end-entity trust anchors.
+section: "1.1"
+topics:
+    - yang
+    - pkix
+    - security
+    - crypto
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__interoperability-note-these-ssh-groupings-are-designed-to-be-used.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: interoperability-note
+summary: These SSH groupings are designed to be used in conjunction with transport-level groupings from RFC 9643 (YANG Groupings for TCP Clients and TCP Servers), which provides remote/local address and port configuration. The SSH modules focus exclusively on SSH-layer parameters.
+section: "1"
+topics:
+    - yang
+    - netconf
+    - tcp
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__normative-requirement-enabling-the-client-ident-none-feature-ssh-client.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: normative-requirement
+summary: Enabling the 'client-ident-none' feature (SSH client) or 'local-user-auth-none' feature (SSH server) is NOT RECOMMENDED, as the 'none' authentication method provides no credential-based security.
+section: "3.3"
+rfc2119_level: SHOULD NOT
+topics:
+    - security
+    - yang
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__normative-requirement-the-ssh-client-and-server-should-send-ssh.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: normative-requirement
+summary: The SSH client and server SHOULD send SSH_MSG_GLOBAL_REQUEST with a purposely nonexistent 'request name' value (e.g., keepalive@example.com) and 'want reply' set to '1' to perform keepalive aliveness testing, per Section 4 of RFC 4254.
+section: "3.3"
+rfc2119_level: SHOULD
+topics:
+    - yang
+    - netconf
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__normative-requirement-the-ssh-server-should-derive-the-list-of.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: normative-requirement
+summary: The SSH server SHOULD derive the list of authentication method names returned to the SSH client from the descendant nodes configured in the local user entry, per Sections 5.1 and 5.2 of RFC 4252.
+section: "4.3"
+rfc2119_level: SHOULD
+topics:
+    - yang
+    - security
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__normative-requirement-whenever-a-choice-among-authentication-methods-arises-for.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: normative-requirement
+summary: Whenever a choice among authentication methods arises for either client or server, implementations SHOULD use a default ordering that prioritizes automation over human interaction.
+section: "3.3"
+rfc2119_level: SHOULD
+topics:
+    - yang
+    - security
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"

corpus/elements/rfc-9644__protocol-element-algorithm-typedefs-ssh-public-key-algorithm-ssh-key.yaml

@@ -0,0 +1,10 @@
+document: rfc-9644
+kind: protocol-element
+summary: Algorithm typedefs (ssh-public-key-algorithm, ssh-key-exchange-algorithm, ssh-encryption-algorithm, ssh-mac-algorithm) each accept either an IANA-maintained enumeration value from the corresponding IANA module or a locally defined string of 1-64 characters that MUST contain '@', per RFC 4250 Section 4.6.1.
+section: "2.3"
+topics:
+    - yang
+    - crypto
+    - registry
+extracted_by: claude-sonnet-4-6
+extracted_at: "2026-07-12"