<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?rfc toc="yes"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes" ?> <?rfc compact="yes"?> <?rfc subcompact="no"?> <?rfc linkmailto="no" ?> <?rfc editing="no" ?> <?rfc comments="yes" ?> <?rfc inline="yes"?> <?rfc rfcedstyle="yes"?> <?rfc-ext allow-markup-in-artwork="yes" ?> <?rfc-ext include-index="no" ?> <!--<?rfc strict="no"?> --><rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" consensus="true" submissionType="IETF" docName="draft-ietf-netconf-ssh-client-server-40" number="9644" updates="" obsoletes="" ipr="trust200902" tocInclude="true" symRefs="true" sortRefs="true"version="3"> <!-- xml2rfc v2v3 conversion 3.17.4 -->version="3" > <front> <title abbrev="Groupings for SSH Clients and Servers">YANG Groupings for SSH Clients and SSH Servers</title> <seriesInfoname="Internet-Draft" value="draft-ietf-netconf-ssh-client-server-40"/>name="RFC" value="9644"/> <author fullname="Kent Watsen" initials="K." surname="Watsen"> <organization>Watsen Networks</organization> <address> <email>kent+ietf@watsen.net</email> </address> </author><date/> <area>Operations</area> <workgroup>NETCONF Working Group</workgroup><date month="August" year="2024"/> <area>OPS</area> <workgroup>netconf</workgroup> <abstract> <t>This document presentssevenYANG 1.1modules. Threemodules -- three IETFmodules,modules and the script used to create four supporting IANA modules.</t> <t>The three IETF modulesare:are ietf-ssh-common, ietf-ssh-client, and ietf-ssh-server. The "ietf-ssh-client" and "ietf-ssh-server" modules are the primary productions of this work, supporting the configuration and monitoring ofSSHSecure Shell (SSH) clients and servers.</t> <t>The four IANA modulesare:are iana-ssh-encryption-algs, iana-ssh-key-exchange-algs, iana-ssh-mac-algs, and iana-ssh-public-key-algs. These modules each define YANG enumerations providing support for an IANA-maintained algorithm registry.</t> </abstract><note> <name>Editorial Note (To be removed by RFC Editor)</name> <t>This draft contains placeholder values that need to be replaced with finalized values at the time of publication. This note summarizes all of the substitutions that are needed. No other RFC Editor instructions are specified elsewhere in this document.</t> <t>Artwork in this document contains shorthand references to drafts in progress. Please apply the following replacements: </t> <ul spacing="normal"> <li> <tt>AAAA</tt> --> the assigned RFC value for draft-ietf-netconf-crypto-types</li> <li> <tt>BBBB</tt> --> the assigned RFC value for draft-ietf-netconf-trust-anchors</li> <li> <tt>CCCC</tt> --> the assigned RFC value for draft-ietf-netconf-keystore</li> <li> <tt>DDDD</tt> --> the assigned RFC value for draft-ietf-netconf-tcp-client-server</li> <li> <tt>EEEE</tt> --> the assigned RFC value for this draft</li> </ul> <t>Artwork in this document contains placeholder values for the date of publication of this draft. Please apply the following replacement: </t> <ul spacing="normal"> <li> <tt>2024-03-16</tt> --> the publication date of this draft</li> </ul> <t>The "Relation to other RFCs" section <xref target="collective-effort"/> contains the text "one or more YANG modules" and, later, "modules". This text is sourced from a file in a context where it is unknown how many modules a draft defines. The text is not wrong as is, but it may be improved by stating more directly how many modules are defined.</t> <t>The "Relation to other RFCs" section <xref target="collective-effort"/> contains a self-reference to this draft, along with a corresponding reference in the Appendix. Please replace the self-reference in this section with "This RFC" (or similar) and remove the self-reference in the "Normative/Informative References" section, whichever it is in.</t> <t>Tree-diagrams in this draft may use the '\' line-folding mode defined in RFC 8792. However, nicer-to-the-eye is when the '\\' line-folding mode is used. The AD suggested suggested putting a request here for the RFC Editor to help convert "ugly" '\' folded examples to use the '\\' folding mode. "Help convert" may be interpreted as, identify what looks ugly and ask the authors to make the adjustment.</t> <t>The following Appendix sections are to be removed prior to publication: </t> <ul spacing="normal"> <li> <xref target="ssh-enc-algs-model"/>. Initial Module for the "Encryption Algorithm Names" Registry</li> <li> <xref target="ssh-mac-algs-model"/>. Initial Module for the "MAC Algorithm Names" Registry</li> <li> <xref target="ssh-pubkey-algs-model"/>. Initial Module for the "Public Key Algorithm Names" Registry</li> <li> <xref target="ssh-keyex-algs-model"/>. Initial Module for the "Key Exchange Method Names" Registry</li> <li> <xref target="change-log"/>. Change Log</li> </ul> </note></front> <middle> <section> <name>Introduction</name> <t>This document presentssevenYANG 1.1 <xref target="RFC7950"/>modules. Three "IETF"modules -- three IETF modules and the script to create four"IANA"IANA modules.</t> <t>The three IETF modules are ietf-ssh-common (<xref target="ssh-common-model"/>), ietf-ssh-client (<xref target="ssh-client-model"/>), and ietf-ssh-server (<xref target="ssh-server-model"/>). The "ietf-ssh-client" and "ietf-ssh-server" modules are the primary productions of this work, supporting the configuration and monitoring of SSH clients and servers.</t> <t>The groupings defined in this document are expected to be used in conjunction with the groupings defined in an underlying transport-level module, such as the groupings defined in <xreftarget="I-D.ietf-netconf-tcp-client-server"/>.target="RFC9643"/>. The transport-level data model enables the configuration of transport-levelvaluesvalues, such as a remote address, a remote port, a local address, and a local port.</t> <t>The four IANA modules are:iana-ssh-encryption-algs (<xref target="ssh-enc-algs-model"/>), iana-ssh-key-exchange-algs (<xref target="ssh-keyex-algs-model"/>), iana-ssh-mac-algs (<xref target="ssh-mac-algs-model"/>),iana-ssh-encryption-algs, iana-ssh-key-exchange-algs, iana-ssh-mac-algs, andiana-ssh-public-key-algs (<xref target="ssh-pubkey-algs-model"/>).iana-ssh-public-key-algs. These modules each define YANG enumerations providing support for an IANA-maintained algorithm registry.</t> <t>This document assumes that the four IANA modulesexist,exist and presents a script in <xref target="iana-script"/> that IANA may use to generate the YANG modules. This document does not publish the initial versions of these four modules. IANA publishes these modules.</t> <section> <name>Regarding the IETF Modules</name> <t>The three IETF modules define features and groupings to model "generic" SSH clients and SSH servers, where "generic" should be interpreted as "least common denominator" rather than "complete."BasicSupport for the basic SSH protocol(<xref target="RFC4252"/>,<xreftarget="RFC4253"/>, andtarget="RFC4252"/> <xreftarget="RFC4254"/>) supporttarget="RFC4253"/> <xref target="RFC4254"/> is afforded by these modules, leaving configuration ofadvanceadvanced features (e.g., multiple channels) to augmentations made by consuming modules.</t> <t>It is intended that the YANG groupings will be used by applications needing to configure SSH client and server protocol stacks. For instance, these groupings are used to help define the datamodel for NETCONF over SSHmodels in <xreftarget="RFC6242"/> basedtarget="I-D.ietf-netconf-netconf-client-server"/>, for clients and serversinusing the Network Configuration Protocol (NETCONF) over SSH <xreftarget="I-D.ietf-netconf-netconf-client-server"/>.</t>target="RFC6242"/>.</t> <t>Theietf-ssh-client"ietf-ssh-client" andietf-ssh-server"ietf-ssh-server" YANG modules each define one grouping, which is focused on just SSH-specific configuration, and specificallyavoidsavoid any transport-level configuration, such as what ports to listen on or connect to. This affords applications the opportunity to define their own strategy for how the underlying TCP connection is established. For instance, applications supporting NETCONF Call Home <xref target="RFC8071"/> could use the "ssh-server-grouping" grouping for the SSH parts itprovides,provides while adding data nodes for the TCP-level call-home configuration.</t> <t>The modules defined in this document optionally support <xreftarget="RFC6187"/>target="RFC6187"/>, which describes enablingX.509v3 certificate basedhost keys and publickeys.</t>keys based on X.509v3 certificates.</t> </section> <section anchor="collective-effort"> <name>Relation tootherOther RFCs</name> <t>This document presentsone or morethree YANG modules <xref target="RFC7950"/> that are part of a collection of RFCs that work togetherto, ultimately,to ultimately support the configuration of both the clients and servers of both the NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/> protocols.</t> <t> The dependency relationship between the primary YANG groupings defined in the various RFCs is presented in the below diagram. In some cases, adraftdocument may define secondary groupings that introduce dependencies not illustrated in the diagram. The labels in the diagram areashorthandnamenames for the definingRFC.RFCs. The citationreferencereferences for shorthandname isnames are provided below the diagram.</t> <t>Please note that the arrows in the diagram point from referencer to referenced. For example, the "crypto-types" RFC does not have any dependencies, whilst the "keystore" RFC depends on the "crypto-types" RFC.</t> <artwork><![CDATA[ crypto-types ^ ^ / \ / \ truststore keystore ^ ^ ^ ^ | +---------+ | | | | | | | +------------+ | tcp-client-server | / | | ^ ^ ssh-client-server | | | | ^ tls-client-server | | | ^ ^ http-client-server | | | | | ^ | | | +-----+ +---------+ | | | | | | | | +-----------|--------|--------------+ | | | | | | | | +-----------+ | | | | | | | | | | | | | | | | | netconf-client-server restconf-client-server ]]></artwork> <!-- RFC Editor: is there anyway to flush-left the table in PDF/HTML views? --> <table> <name>Label in Diagram to RFC Mapping</name> <tbody> <tr> <th>Label in Diagram</th><th>Originating RFC</th><th>Reference</th> </tr> <tr> <td>crypto-types</td> <td> <xreftarget="I-D.ietf-netconf-crypto-types"/></td>target="RFC9640"/></td> </tr> <tr> <td>truststore</td> <td> <xreftarget="I-D.ietf-netconf-trust-anchors"/></td>target="RFC9641"/></td> </tr> <tr> <td>keystore</td> <td> <xreftarget="I-D.ietf-netconf-keystore"/></td>target="RFC9642"/></td> </tr> <tr> <td>tcp-client-server</td> <td> <xreftarget="I-D.ietf-netconf-tcp-client-server"/></td>target="RFC9643"/></td> </tr> <tr> <td>ssh-client-server</td> <td><xref target="I-D.ietf-netconf-ssh-client-server"/></td>RFC9644</td> </tr> <tr> <td>tls-client-server</td> <td> <xreftarget="I-D.ietf-netconf-tls-client-server"/></td>target="RFC9645"/></td> </tr> <tr> <td>http-client-server</td> <td> <xref target="I-D.ietf-netconf-http-client-server"/></td> </tr> <tr> <td>netconf-client-server</td> <td> <xref target="I-D.ietf-netconf-netconf-client-server"/></td> </tr> <tr> <td>restconf-client-server</td> <td> <xref target="I-D.ietf-netconf-restconf-client-server"/></td> </tr> </tbody> </table> </section> <section> <name>Specification Language</name><t>The<t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> </section> <section> <name>Adherence to the NMDA</name> <t>This document is compliant with the Network Management Datastore Architecture (NMDA) <xref target="RFC8342"/>. For instance, as described in <xreftarget="I-D.ietf-netconf-trust-anchors"/>target="RFC9641"/> and <xreftarget="I-D.ietf-netconf-keystore"/>,target="RFC9642"/>, trust anchors and keys installed during manufacturing are expected to appear in <operational> (<xref section="5.3"target="RFC8342"/>),target="RFC8342"/>) and <system> <xreftarget="I-D.ietf-netmod-system-config"/>,target="I-D.ietf-netmod-system-config"/> if implemented.</t> </section> <section> <name>Conventions</name> <t>Various examples in this document use "BASE64VALUE=" as a placeholder value for binary data that has been base64 encoded (per <xref section="9.8" target="RFC7950"/>). This placeholder value is used because realbase64 encodedbase64-encoded structures are often many lines long and hence distracting to the example being presented.</t> </section> </section> <section anchor="ssh-common-model"> <name>The "ietf-ssh-common" Module</name> <t>The SSH common model presented in this section contains features and groupings common to both SSH clients and SSH servers. The "transport-params-grouping" grouping can be used to configure the list of SSH transport algorithms permitted by the SSH client or SSH server. The lists of permitted algorithms are in decreasing order of usage preference. The algorithm that appears first in the client list that also appears in the server list is the one that is used for the SSH transport layer connection. The ability to restrict the algorithms allowed is provided in this grouping for SSH clients and SSH servers that are capable of doing so and may serve to make SSH clients and SSH servers compliant with security policies.</t> <section> <name>Data Model Overview</name> <t>This section provides an overview of the "ietf-ssh-common" module in terms of its features, identities, and groupings.</t> <section anchor="common-features" toc="exclude"> <name>Features</name> <t>The following diagram lists all the "feature" statements defined in the "ietf-ssh-common" module:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ Features: +-- ssh-x509-certs +-- transport-params +-- asymmetric-key-pair-generation +-- algorithm-discovery]]></artwork>]]></sourcecode> <t>The diagram above uses syntax that is similar to but not defined in <xref target="RFC8340"/>.</t> <t>Please refer to the YANG module for a description of each feature.</t> </section> <section toc="exclude"> <name>Groupings</name> <t>The "ietf-ssh-common" module defines the following "grouping" statement:</t> <ul spacing="compact"> <li>transport-params-grouping</li> </ul> <t>This grouping is presented in the following subsection.</t> <section anchor="transport-params-grouping"> <name>The "transport-params-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "transport-params-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping transport-params-grouping: +-- host-key | +-- host-key-alg* ssh-public-key-algorithm +-- key-exchange | +-- key-exchange-alg* ssh-key-exchange-algorithm +-- encryption | +-- encryption-alg* ssh-encryption-algorithm +-- mac +-- mac-alg* ssh-mac-algorithm]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>This grouping is used by both the "ssh-client-grouping" and the "ssh-server-grouping" groupings defined in Sections <xreftarget="ssh-client-grouping"/>target="ssh-client-grouping" format="counter"/> and <xreftarget="ssh-server-grouping"/>,target="ssh-server-grouping" format="counter"/>, respectively.</li> <li>This grouping enables client and server configurations to specify the algorithms that are to be used when establishing SSH sessions.</li> <li>Each list is "ordered-by user".</li> </ul> </section> </section> <section toc="exclude"><name>Protocol-accessible<name>Protocol-Accessible Nodes</name> <t>The following tree diagram <xref target="RFC8340"/> lists all the protocol-accessible nodes defined in the "ietf-ssh-common"module,module without expanding the "grouping" statements:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ietf-ssh-common +--ro supported-algorithms {algorithm-discovery}? +--ro public-key-algorithms | +--ro supported-algorithm* ssh-public-key-algorithm +--ro encryption-algorithms | +--ro supported-algorithm* ssh-encryption-algorithm +--ro key-exchange-algorithms | +--ro supported-algorithm* ssh-key-exchange-algorithm +--ro mac-algorithms +--ro supported-algorithm* ssh-mac-algorithm rpcs: +---x generate-asymmetric-key-pair {asymmetric-key-pair-generation}? +---w input | +---w algorithm ssh-public-key-algorithm | +---w num-bits? uint16 | +---w private-key-encoding | +---w (private-key-encoding) | +--:(cleartext) {ct:cleartext-private-keys}? | | +---w cleartext? empty | +--:(encrypted) {ct:encrypted-private-keys}? | | +---w encrypted | | +---w ks:encrypted-by-grouping | +--:(hidden) {ct:hidden-private-keys}? | +---w hidden? empty +--ro output +--ro (key-or-hidden)? +--:(key) | +---u ct:asymmetric-key-pair-grouping +--:(hidden) +--ro location? instance-identifier]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>Protocol-accessible nodes are those nodes that are accessible when the module is "implemented", as described in <xref section="5.6.5" target="RFC7950"/>.</li> <li>The protocol-accessible nodes for the "ietf-ssh-common" module are limited to the "supported-algorithms" container, which is constrained by the "algorithm-discovery" feature, and theRPC "generate-asymmetric-key-pair","generate-asymmetric-key-pair" RPC, which is constrained by the "asymmetric-key-pair-generation" feature.</li> <li>The "encrypted-by-grouping" grouping is discussed in <xref section="2.1.3.1"target="I-D.ietf-netconf-keystore"/>.</li>target="RFC9642"/>.</li> <li>The "asymmetric-key-pair-grouping" grouping is discussed in <xref section="2.1.4.6"target="I-D.ietf-netconf-crypto-types"/>.</li>target="RFC9640"/>.</li> </ul> </section> </section> <section> <name>Example Usage</name> <t>The following example illustrates the "transport-params-grouping' grouping when populated with some data.</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <transport-params xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-common"> <host-key> <host-key-alg>x509v3-rsa2048-sha256</host-key-alg> <host-key-alg>ssh-rsa</host-key-alg> <host-key-alg>ssh-rsa@openssh.com</host-key-alg> </host-key> <key-exchange> <key-exchange-alg>diffie-hellman-group-exchange-sha256</key-exch\ ange-alg> </key-exchange> <encryption> <encryption-alg>aes256-ctr</encryption-alg> <encryption-alg>aes192-ctr</encryption-alg> <encryption-alg>aes128-ctr</encryption-alg> <encryption-alg>aes256-gcm@openssh.com</encryption-alg> </encryption> <mac> <mac-alg>hmac-sha2-256</mac-alg> <mac-alg>hmac-sha2-512</mac-alg> </mac> </transport-params>]]></artwork>]]></sourcecode> <t>The following example illustrates operational state data indicating the SSH algorithms supported by the server.</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <supported-algorithms xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-common"> <encryption-algorithms> <supported-algorithm>aes256-ctr</supported-algorithm> <supported-algorithm>arcfour256</supported-algorithm> <supported-algorithm>serpent256-ctr</supported-algorithm> <supported-algorithm>AEAD_AES_128_GCM</supported-algorithm> <supported-algorithm>AEAD_AES_256_GCM</supported-algorithm> <supported-algorithm>aes256-gcm@openssh.com</supported-algorithm> </encryption-algorithms> <key-exchange-algorithms> <supported-algorithm>ecdh-sha2-nistp256</supported-algorithm> <supported-algorithm>rsa2048-sha256</supported-algorithm> <supported-algorithm>gss-group14-sha1-nistp256</supported-algori\ thm> <supported-algorithm>gss-gex-sha1-nistp256</supported-algorithm> <supported-algorithm>gss-group14-sha256-1.2.840.10045.3.1.1</sup\ ported-algorithm> <supported-algorithm>curve25519-sha256</supported-algorithm> </key-exchange-algorithms> <mac-algorithms> <supported-algorithm>hmac-sha2-256</supported-algorithm> <supported-algorithm>hmac-sha2-512</supported-algorithm> <supported-algorithm>AEAD_AES_256_GCM</supported-algorithm> </mac-algorithms> <public-key-algorithms> <supported-algorithm>rsa-sha2-256</supported-algorithm> <supported-algorithm>rsa-sha2-512</supported-algorithm> <supported-algorithm>spki-sign-rsa</supported-algorithm> <supported-algorithm>pgp-sign-dss</supported-algorithm> <supported-algorithm>x509v3-rsa2048-sha256</supported-algorithm> <supported-algorithm>ecdsa-sha2-nistp256</supported-algorithm> <supported-algorithm>ecdsa-sha2-1.3.132.0.37</supported-algorith\ m> <supported-algorithm>ssh-ed25519</supported-algorithm> <supported-algorithm>ssh-rsa@openssh.com</supported-algorithm> </public-key-algorithms> </supported-algorithms>]]></artwork>]]></sourcecode> <t>The following example illustrates the "generate-asymmetric-key-pair" RPC.</t> <t keepWithNext="true">REQUEST</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <generate-asymmetric-key-pair xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-common"> <algorithm>ecdsa-sha2-nistp256</algorithm> <num-bits>521</num-bits> <private-key-encoding> <encrypted> <asymmetric-key-ref>hidden-asymmetric-key</asymmetric-key-re\ f> </encrypted> </private-key-encoding> </generate-asymmetric-key-pair> </rpc>]]></artwork>]]></sourcecode> <t keepWithNext="true">RESPONSE</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types" xmlns:sshcmn="urn:ietf:params:xml:ns:yang:ietf-ssh-common"> <sshcmn:public-key-format>ct:subject-public-key-info-format</sshcm\ n:public-key-format> <sshcmn:public-key>BASE64VALUE=</sshcmn:public-key> <sshcmn:private-key-format>ct:ec-private-key-format</sshcmn:privat\ e-key-format> <sshcmn:cleartext-private-key>BASE64VALUE=</sshcmn:cleartext-priva\ te-key> </rpc-reply>]]></artwork>]]></sourcecode> </section> <section anchor="ssh-common-yang-module"> <name>YANG Module</name> <t>This YANG module has normative references to <xreftarget="RFC4253"/>, <xref target="RFC4344"/>,target="RFC4250"/>, <xreftarget="RFC4419"/>, <xref target="RFC5656"/>,target="RFC4253"/>, <xref target="RFC6187"/>,<xref target="RFC6668"/>,and <xreftarget="FIPS_186-6"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "ietf-ssh-common@2024-03-16.yang"</t> <artwork><![CDATA[target="FIPS_186-5"/>.</t> <sourcecode type="yang" name="ietf-ssh-common@2024-03-16.yang" markers="true"><![CDATA[ module ietf-ssh-common { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ssh-common"; prefix sshcmn; import iana-ssh-encryption-algs { prefix sshea; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } import iana-ssh-key-exchange-algs { prefix sshkea; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } import iana-ssh-mac-algs { prefix sshma; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } import iana-ssh-public-key-algs { prefix sshpka; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } import ietf-crypto-types { prefix ct; reference "RFCAAAA:9640: YANG Data Types and Groupings for Cryptography"; } import ietf-keystore { prefix ks; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: https://datatracker.ietf.org/wg/netconf WG List: NETCONF WG list <mailto:netconf@ietf.org> Author: Kent Watsen <mailto:kent+ietf@watsen.net> Author: Gary Wu <mailto:garywu@cisco.com>"; description "This module definesacommon features and groupings for Secure Shell (SSH). The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCEEEE (https://www.rfc-editor.org/info/rfcEEEE);9644 (https://www.rfc-editor.org/info/rfc9644); see the RFC itself for full legalnotices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here.";notices."; revision 2024-03-16 { description "Initialversion";version."; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } // Features feature ssh-x509-certs { description "X.509v3 certificates are supported for SSH."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } feature transport-params { description "SSH transport layer parameters are configurable."; } feature asymmetric-key-pair-generation { description "Indicates that the server implements the 'generate-asymmetric-key-pair' RPC."; } feature algorithm-discovery { description "Indicates that the server implements the 'supported-algorithms' container."; } // Typedefs typedef ssh-public-key-algorithm { type union { type sshpka:ssh-public-key-algorithm; type string { length "1..64" { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } pattern".*@.*"'.*@.*' { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } } } description "A type that enables the public key algorithm to be either an IANA-maintained public key algorithm in the 'iana-ssh-public-key-algs' YANG module (RFCEEEE),9644) or alocally-definedlocally defined algorithm, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-key-exchange-algorithm { type union { type sshkea:ssh-key-exchange-algorithm; type string { length "1..64" { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } pattern".*@.*"'.*@.*' { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } } } description "A type that enables the key exchange algorithm to be either an IANA-maintained key exchange algorithm in the 'iana-ssh-key-exchange-algs' YANG module (RFCEEEE),9644) or alocally-definedlocally defined algorithm, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-encryption-algorithm { type union { type sshea:ssh-encryption-algorithm; type string { length "1..64" { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } pattern".*@.*"'.*@.*' { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } } } description "A type that enables the encryption algorithm to be either an IANA-maintained encryption algorithm in the 'iana-ssh-encryption-algs' YANG module (RFCEEEE),9644) or alocally-definedlocally defined algorithm, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-mac-algorithm { type union { type sshma:ssh-mac-algorithm; type string { length "1..64" { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } pattern".*@.*"'.*@.*' { description"Non IANA-maintained"Non-IANA-maintained algorithms must include the'at-sign'at sign (@) in them, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers"; } } } description "A type that enables theMACmessage authentication code (MAC) algorithm to be either an IANA-maintained MAC algorithm in the 'iana-ssh-mac-algs' YANG module (RFCEEEE),9644) or alocally-definedlocally defined algorithm, per Section 4.6.1 of RFC 4250."; reference "RFC 4250:SSHThe Secure Shell (SSH) Protocol Assigned Numbers RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } // Groupings grouping transport-params-grouping { description "A reusable grouping for SSH transport parameters."; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; container host-key { description "Parameters regarding host key."; leaf-list host-key-alg { type ssh-public-key-algorithm; ordered-by user; description "Acceptable host key algorithms in order of decreasing preference. If this leaf-list is not configured (has zeroelements)elements), the acceptable host key algorithms areimplementation- defined.";implementation-defined."; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } } container key-exchange { description "Parameters regarding key exchange."; leaf-list key-exchange-alg { type ssh-key-exchange-algorithm; ordered-by user; description "Acceptable key exchange algorithms in order of decreasing preference. If this leaf-list is not configured (has zeroelements)elements), the acceptable key exchange algorithms areimplementation defined.";implementation-defined."; } } container encryption { description "Parameters regarding encryption."; leaf-list encryption-alg { type ssh-encryption-algorithm; ordered-by user; description "Acceptable encryption algorithms in order of decreasing preference. If this leaf-list is not configured (has zeroelements)elements), the acceptable encryption algorithms areimplementation defined.";implementation-defined."; } } container mac { description "Parameters regarding message authentication code (MAC)."; leaf-list mac-alg { type ssh-mac-algorithm; ordered-by user; description "Acceptable MAC algorithms in order of decreasing preference. If this leaf-list is not configured (has zeroelements)elements), the acceptable MAC algorithms areimplementation- defined.";implementation-defined."; } } } // Protocol-accessible Nodes container supported-algorithms { if-feature "algorithm-discovery"; config false; description "Identifies all of the supported algorithms."; container public-key-algorithms { description "A container for a list of public key algorithms supported by the server."; leaf-list supported-algorithm { type ssh-public-key-algorithm; description "A public key algorithm supported by the server."; } } container encryption-algorithms { description "A container for a list of encryption algorithms supported by the server."; leaf-list supported-algorithm { type ssh-encryption-algorithm; description "An encryption algorithm supported by the server."; } } container key-exchange-algorithms { config false; description "A container for a list of key exchange algorithms supported by the server."; leaf-list supported-algorithm { type ssh-key-exchange-algorithm; description "A key exchange algorithm supported by the server."; } } container mac-algorithms { config false; description "A container for a list of MAC algorithms supported by the server."; leaf-list supported-algorithm { type ssh-mac-algorithm; description "A MAC algorithm supported by the server."; } } } rpc generate-asymmetric-key-pair { if-feature "asymmetric-key-pair-generation"; description "Requests the device to generate a public key using the specified key algorithm."; input { leaf algorithm { type ssh-public-key-algorithm; mandatory true; description "The algorithm to be used when generating the key."; } leaf num-bits { type uint16; description "Specifies the number of bits in the key to create. For RSA keys, the minimum size is 1024 bits and the default is 3072 bits. Generally, 3072 bits is considered sufficient. DSA keys must be exactly 1024bitsbits, as specified by FIPS186-6.186-5. ForECDSAElliptic Curve Digital Signature Algorithm (ECDSA) keys, the 'num-bits' value determines the key length by selecting from one of three elliptic curve sizes: 256,384384, or 521 bits. Attempting to use bit lengths other than these three values for ECDSA keys will fail. ECDSA-SK,Ed25519Ed25519, and Ed25519-SK keys have a fixedlengthlength, andthusthus, the 'num-bits' value is not specified."; reference "FIPS186-6:186-5: Digital Signature Standard (DSS)"; } container private-key-encoding { description "Indicates how the private key is to be encoded."; choice private-key-encoding { mandatory true; description "A choice amongst optional private key handling."; case cleartext { if-feature "ct:cleartext-private-keys"; leaf cleartext { type empty; description "Indicates that the private key is to be returned as a cleartext value."; } } case encrypted { if-feature "ct:encrypted-private-keys"; container encrypted { description "Indicates that the private key is to be encrypted using the specified symmetric or asymmetric key."; uses ks:encrypted-by-grouping; } } case hidden { if-feature "ct:hidden-private-keys"; leaf hidden { type empty; description "Indicates that the private key is to be hidden. Unlike the 'cleartext' and 'encrypt' options, the key returned is a placeholder for an internally stored key. See the 'Support for Built-in Keys' section in RFCCCCC9642 for information about hidden keys. It is expected that the server will instantiate the hidden key in the same location where built-in keys are located. Rather thanreturnreturning the key, just the key's location is returned in the output."; } } } } } output { choice key-or-hidden { case key { uses ct:asymmetric-key-pair-grouping; } case hidden { leaf location { type instance-identifier; description "The location to where a hidden key was created."; } } description "The output can be either a key (for cleartext and encrypted keys) or the location to where the key was created (for hidden keys)."; } } } // end generate-asymmetric-key-pair }]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t>]]></sourcecode> </section> </section> <section anchor="ssh-client-model"> <name>The "ietf-ssh-client" Module</name> <t>This section defines a YANG 1.1 <xref target="RFC7950"/> module called "ietf-ssh-client". A high-level overview of the module is provided in <xref target="client-overview"/>. Examples illustrating the module's use are provided in <xreftarget="client-examples">Examples</xref>.target="client-examples"/> ("Example Usage"). The YANG module itself is defined in <xref target="client-yang-module"/>.</t> <section anchor="client-overview"> <name>Data Model Overview</name> <t>This section provides an overview of the "ietf-ssh-client" module in terms of its features and groupings.</t> <section anchor="client-features" toc="exclude"> <name>Features</name> <t>The following diagram lists all the "feature" statements defined in the "ietf-ssh-client" module:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ Features: +-- ssh-client-keepalives +-- client-ident-password +-- client-ident-publickey +-- client-ident-hostbased +-- client-ident-none]]></artwork>]]></sourcecode> <t>The diagram above uses syntax that is similar to but not defined in <xref target="RFC8340"/>.</t> <t>Please refer to the YANG module for a description of each feature.</t> </section> <section toc="exclude"> <name>Groupings</name> <t>The "ietf-ssh-client" module defines the following "grouping" statement:</t> <ul spacing="compact"> <li>ssh-client-grouping</li> </ul> <t>This grouping is presented in the following subsection.</t> <section anchor="ssh-client-grouping"> <name>The "ssh-client-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "ssh-client-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ grouping ssh-client-grouping: +-- client-identity | +-- username? string | +-- public-key! {client-ident-publickey}? | | +---u ks:inline-or-keystore-asymmetric-key-grouping | +-- password! {client-ident-password}? | | +---u ct:password-grouping | +-- hostbased! {client-ident-hostbased}? | | +---u ks:inline-or-keystore-asymmetric-key-grouping | +-- none? empty {client-ident-none}? | +-- certificate! {sshcmn:ssh-x509-certs}? | +---u ks:inline-or-keystore-end-entity-cert-with-key-group\ ing +-- server-authentication | +-- ssh-host-keys! | | +---u ts:inline-or-truststore-public-keys-grouping | +-- ca-certs! {sshcmn:ssh-x509-certs}? | | +---u ts:inline-or-truststore-certs-grouping | +-- ee-certs! {sshcmn:ssh-x509-certs}? | +---u ts:inline-or-truststore-certs-grouping +-- transport-params {sshcmn:transport-params}? | +---u sshcmn:transport-params-grouping +-- keepalives! {ssh-client-keepalives}? +-- max-wait? uint16 +-- max-attempts? uint8]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "client-identity" node configures a "username" and authentication methods, each enabled by a "feature" statement defined in <xref target="client-features"/>.</li> <li>The "server-authentication" node configures trust anchors for authenticating the SSH server, with each option enabled by a "feature" statement.</li> <li>The "transport-params" node, which must be enabled by a feature, configures parameters for the SSH sessions established by this configuration.</li> <li>The "keepalives" node, which must be enabled by a feature, configures a "presence" container for testing the aliveness of the SSH server. The aliveness-test occurs at the SSH protocol layer.</li> <li> <t>For the referenced groupingstatement(s):statements: </t> <ulspacing="compact">spacing="normal"> <li>The "inline-or-keystore-asymmetric-key-grouping" grouping is discussed in <xref section="2.1.3.4"target="I-D.ietf-netconf-keystore"/>.</li>target="RFC9642"/>.</li> <li>The "inline-or-keystore-end-entity-cert-with-key-grouping" grouping is discussed in <xref section="2.1.3.6"target="I-D.ietf-netconf-keystore"/>.</li>target="RFC9642"/>.</li> <li>The "inline-or-truststore-public-keys-grouping" grouping is discussed in <xref section="2.1.3.4"target="I-D.ietf-netconf-trust-anchors"/>.</li>target="RFC9641"/>.</li> <li>The "inline-or-truststore-certs-grouping" grouping is discussed in <xref section="2.1.3.3"target="I-D.ietf-netconf-trust-anchors"/>.</li>target="RFC9641"/>.</li> <li>The "transport-params-grouping" grouping is discussed in <xref target="transport-params-grouping"/> in this document.</li> </ul> </li> </ul> </section> </section> <section toc="exclude"><name>Protocol-accessible<name>Protocol-Accessible Nodes</name> <t>The "ietf-ssh-client" module defines only "grouping" statements that are used by other modules to instantiate protocol-accessible nodes.ThusThus, this module, when implemented, does not itself define any protocol-accessible nodes.</t> </section> </section> <section anchor="client-examples"> <name>Example Usage</name> <t>This section presents two examples showing the "ssh-client-grouping" grouping populated with some data. These examples are effectively thesamesame, except the first configures the client identity usingaan inlinedkeykey, while the second uses a key configured in a keystore. Both examples are consistent with the examples presented in <xref section="2.2.1"target="I-D.ietf-netconf-trust-anchors"/>target="RFC9641"/> and <xref section="2.2.1"target="I-D.ietf-netconf-keystore"/>.</t>target="RFC9642"/>.</t> <t>The following configuration example uses inline-definitions for the client identity and server authentication: </t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <ssh-client xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-client" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> <!-- how this client will authenticate itself to the server --> <client-identity> <username>foobar</username> <public-key> <inline-definition> <private-key-format>ct:rsa-private-key-format</private-key-f\ ormat> <cleartext-private-key>BASE64VALUE=</cleartext-private-key> </inline-definition> </public-key> </client-identity> <!-- which host keys will this client trust --> <server-authentication> <ssh-host-keys> <inline-definition> <public-key> <name>corp-fw1</name> <public-key-format>ct:ssh-public-key-format</public-key-fo\ rmat> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>corp-fw2</name> <public-key-format>ct:ssh-public-key-format</public-key-fo\ rmat> <public-key>BASE64VALUE=</public-key> </public-key> </inline-definition> </ssh-host-keys> <ca-certs> <inline-definition> <certificate> <name>Server Cert Issuer #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Server Cert Issuer #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </inline-definition> </ca-certs> <ee-certs> <inline-definition> <certificate> <name>My Application #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>My Application #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </inline-definition> </ee-certs> </server-authentication> <keepalives> <max-wait>30</max-wait> <max-attempts>3</max-attempts> </keepalives> </ssh-client>]]></artwork>]]></sourcecode> <t>The following configuration example uses central-keystore-references for the client identity and central-truststore-references for serverauthentication:authentication from the keystore: </t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <ssh-client xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-client" xmlns:algs="urn:ietf:params:xml:ns:yang:ietf-ssh-common"> <!-- how this client will authenticate itself to the server --> <client-identity> <username>foobar</username> <public-key> <central-keystore-reference>ssh-rsa-key</central-keystore-refe\ rence> </public-key> <certificate> <central-keystore-reference> <asymmetric-key>ssh-rsa-key-with-cert</asymmetric-key> <certificate>ex-rsa-cert2</certificate> </central-keystore-reference> </certificate> </client-identity> <!-- which host-keys will this client trust --> <server-authentication> <ssh-host-keys> <central-truststore-reference>trusted-ssh-public-keys</central\ -truststore-reference> </ssh-host-keys> <ca-certs> <central-truststore-reference>trusted-server-ca-certs</central\ -truststore-reference> </ca-certs> <ee-certs> <central-truststore-reference>trusted-server-ee-certs</central\ -truststore-reference> </ee-certs> </server-authentication> <keepalives> <max-wait>30</max-wait> <max-attempts>3</max-attempts> </keepalives> </ssh-client>]]></artwork>]]></sourcecode> </section> <section anchor="client-yang-module"> <name>YANG Module</name> <t>This YANG module has normative references to <xref target="RFC4252"/>, <xref target="RFC4254"/>, <xref target="RFC8341"/>, <xreftarget="I-D.ietf-netconf-crypto-types"/>,target="RFC9640"/>, <xreftarget="I-D.ietf-netconf-trust-anchors"/>,target="RFC9641"/>, and <xreftarget="I-D.ietf-netconf-keystore"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "ietf-ssh-client@2024-03-16.yang"</t> <artwork><![CDATA[target="RFC9642"/>.</t> <sourcecode type="yang" markers="true" name="ietf-ssh-client@2024-03-16.yang"><![CDATA[ module ietf-ssh-client { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ssh-client"; prefix sshc; import ietf-netconf-acm { prefix nacm; reference "RFC 8341: Network Configuration Access Control Model"; } import ietf-crypto-types { prefix ct; reference "RFCAAAA:9640: YANG Data Types and Groupings for Cryptography"; } import ietf-truststore { prefix ts; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; } import ietf-keystore { prefix ks; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; } import ietf-ssh-common { prefix sshcmn; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: https://datatracker.ietf.org/wg/netconf WG List: NETCONF WG list <mailto:netconf@ietf.org> Author: Kent Watsen <mailto:kent+ietf@watsen.net>"; description "This module defines a reusable grouping for SSH clients that can be used as a basis for specific SSH client instances. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCEEEE (https://www.rfc-editor.org/info/rfcEEEE);9644 (https://www.rfc-editor.org/info/rfc9644); see the RFC itself for full legalnotices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here.";notices."; revision 2024-03-16 { description "Initialversion";version."; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } // Features feature ssh-client-keepalives { description "Per socket SSHkeepalivekeep-alive parameters are configurable for SSH clients on the server implementing this feature."; } feature client-ident-publickey { description "Indicates that the 'publickey' authentication type, per RFC 4252, is supported for client identification. The 'publickey' authentication type is required by RFC 4252, but common implementations allow it to be disabled."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature client-ident-password { description "Indicates that the 'password' authentication type, per RFC 4252, is supported for client identification."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature client-ident-hostbased { description "Indicates that the 'hostbased' authentication type, per RFC 4252, is supported for client identification."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature client-ident-none { description "Indicates that the 'none' authentication type, per RFC 4252, is supported for client identification. It is NOT RECOMMENDED to enable this feature."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } // Groupings grouping ssh-client-grouping { description "A reusable grouping for configuringaan SSH client without any consideration for how an underlying TCP session is established. Note that this grouping uses fairly typical descendant node names such that a nesting of 'uses' statements will have name conflicts. It is intended that the consuming data model will resolve the issue (e.g., by wrapping the 'uses' statement in a container called 'ssh-client-parameters'). This model purposely does not do this itself so as to provide maximum flexibility to consuming models."; container client-identity { nacm:default-deny-write; description "The username and authentication methods for the client. The authentication methods are unordered. Clients may initially send any configured method or, per Section 5.2 of RFC 4252,Section 5.2,send the 'none' method to prompt the server to provide a list of productive methods. Whenever a choice amongst methods arises, implementations SHOULD use a default ordering that prioritizes automation overhuman-interaction.";human interaction."; leaf username { type string; description "The username of this user. This will be the username used, for instance, to log into an SSH server."; } container public-key { if-feature "client-ident-publickey"; presence "Indicates thatpublickey-basedpublic-key-based authentication has been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "Alocally-definedlocally defined or referenced asymmetric key pair to be used for client identification."; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; uses ks:inline-or-keystore-asymmetric-key-grouping { refine "inline-or-keystore/inline/inline-definition" { must 'not(public-key-format) or derived-from-or-self' + '(public-key-format, "ct:ssh-public-key-format")'; } refine "inline-or-keystore/central-keystore/" + "central-keystore-reference" { must 'not(deref(.)/../ks:public-key-format) or derived-' + 'from-or-self(deref(.)/../ks:public-key-format, ' + '"ct:ssh-public-key-format")'; } } } container password { if-feature "client-ident-password"; presence "Indicates that password-based authentication has been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A password to be used to authenticate the client's identity."; uses ct:password-grouping; } container hostbased { if-feature "client-ident-hostbased"; presence "Indicates thathostbasedhost-based authentication is configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "Alocally-definedlocally defined or referenced asymmetric key pair to be used for host identification."; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; uses ks:inline-or-keystore-asymmetric-key-grouping { refine "inline-or-keystore/inline/inline-definition" { must 'not(public-key-format) or derived-from-or-self(' + 'public-key-format, "ct:ssh-public-key-format")'; } refine "inline-or-keystore/central-keystore/" + "central-keystore-reference" { must 'not(deref(.)/../ks:public-key-format) or derived-' + 'from-or-self(deref(.)/../ks:public-key-format, ' + '"ct:ssh-public-key-format")'; } } } leaf none { if-feature "client-ident-none"; type empty; description "Indicates that the 'none' algorithm is used for client identification."; } container certificate { if-feature "sshcmn:ssh-x509-certs"; presence "Indicates that certificate-based authentication has been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "Alocally-definedlocally defined or referenced certificate to be used for client identification."; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; uses ks:inline-or-keystore-end-entity-cert-with-key-grouping { refine "inline-or-keystore/inline/inline-definition" { must 'not(public-key-format) or derived-from-or-self(' + 'public-key-format, "ct:subject-public-key-info-' + 'format")'; } refine "inline-or-keystore/central-keystore/" + "central-keystore-reference/asymmetric-key" { must 'not(deref(.)/../ks:public-key-format) or derived-' + 'from-or-self(deref(.)/../ks:public-key-format, ' + '"ct:subject-public-key-info-format")'; } } } } // container client-identity container server-authentication { nacm:default-deny-write; must 'ssh-host-keys or ca-certs or ee-certs'; description "Specifies how the SSH client can authenticate SSH servers. Any combination of authentication methods is additive and unordered."; container ssh-host-keys { presence "Indicates that the SSH host key have been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A bag of SSH host keys used by the SSH client to authenticate SSH server host keys. A server host key is authenticated if it is an exact match to a configured SSH host key."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-public-keys-grouping { refine "inline-or-truststore/inline/inline-definition/public" + "-key" { must 'derived-from-or-self(public-key-format,' + ' "ct:ssh-public-key-format")'; } refine "inline-or-truststore/central-truststore/" + "central-truststore-reference" { must 'not(deref(.)/../ts:public-key/ts:public-key-' + 'format[not(derived-from-or-self(., "ct:ssh-' + 'public-key-format"))])'; } } } container ca-certs { if-feature "sshcmn:ssh-x509-certs"; presence "Indicates that the CA certificates have been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A set of certificate authority (CA) certificates used by the SSH client to authenticate SSH servers. A server is authenticated if its certificate has a valid chain of trust to a configured CA certificate."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-certs-grouping; } container ee-certs { if-feature "sshcmn:ssh-x509-certs"; presence "Indicates that the EE certificates have been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A set of end-entity (EE) certificates used by the SSH client to authenticate SSH servers. A server is authenticated if its certificate is an exact match to a configured end-entity certificate."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-certs-grouping; } } // container server-authentication container transport-params { nacm:default-deny-write; if-feature "sshcmn:transport-params"; description "Configurable parameters of the SSH transport layer."; uses sshcmn:transport-params-grouping; } // container transport-parameters container keepalives { nacm:default-deny-write; if-feature "ssh-client-keepalives"; presence "Indicates that the SSH client proactively tests the aliveness of the remote SSH server."; description "Configures the keep-alivepolicy,policy to proactively test the aliveness of the SSH server. An unresponsive SSH server is dropped after approximately max-wait * max-attempts seconds. Per Section 4 of RFC 4254, the SSH client SHOULD send an SSH_MSG_GLOBAL_REQUEST message with a purposely nonexistent 'request name' value (e.g.,keepalive@ietf.org)keepalive@example.com) and the 'want reply' value set to '1'."; reference "RFC 4254: The Secure Shell (SSH) Connection Protocol"; leaf max-wait { type uint16 { range "1..max"; } units "seconds"; default "30"; description "Sets the amount of time in seconds after whichif no data has been received from the SSH server, aan SSH-level message will be sent to test the aliveness of the SSH server if no data has been received from the SSH server."; } leaf max-attempts { type uint8; default "3"; description "Sets the maximum number of sequential keep-alive messages that can fail to obtain a response from the SSH server before assuming the SSH server is no longer alive."; } } // container keepalives } // grouping ssh-client-grouping }]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t>]]></sourcecode> </section> </section> <section anchor="ssh-server-model"> <name>The "ietf-ssh-server" Module</name> <t>This section defines a YANG 1.1 module called "ietf-ssh-server". A high-level overview of the module is provided in <xref target="server-overview"/>. Examples illustrating the module's use are provided in <xreftarget="server-examples">Examples</xref>.target="server-examples"/> ("Example Usage"). The YANG module itself is defined in <xref target="server-yang-module"/>.</t> <section anchor="server-overview"> <name>Data Model Overview</name> <t>This section provides an overview of the "ietf-ssh-server" module in terms of its features and groupings.</t> <section anchor="server-features" toc="exclude"> <name>Features</name> <t>The following diagram lists all the "feature" statements defined in the "ietf-ssh-server" module:</t><artwork><![CDATA[<sourcecode type="yangree"><![CDATA[ Features: +-- ssh-server-keepalives +-- local-users-supported +-- local-user-auth-publickey {local-users-supported}? +-- local-user-auth-password {local-users-supported}? +-- local-user-auth-hostbased {local-users-supported}? +-- local-user-auth-none {local-users-supported}?]]></artwork>]]></sourcecode> <t>The diagram above uses syntax that is similar to but not defined in <xref target="RFC8340"/>.</t> <t>Please refer to the YANG module for a description of each feature.</t> </section> <section toc="exclude"> <name>Groupings</name> <t>The "ietf-ssh-server" module defines the following "grouping" statement:</t> <ul spacing="compact"> <li>ssh-server-grouping</li> </ul> <t>This grouping is presented in the following subsection.</t> <section anchor="ssh-server-grouping"> <name>The "ssh-server-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "ssh-server-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ grouping ssh-server-grouping: +-- server-identity | +-- host-key* [name] | +--name?name string | +-- (host-key-type) | +--:(public-key) | | +-- public-key | | +---u ks:inline-or-keystore-asymmetric-key-groupi\ ng | +--:(certificate) | +-- certificate {sshcmn:ssh-x509-certs}? | +---u ks:inline-or-keystore-end-entity-cert-with-\ key-grouping +-- client-authentication | +-- users {local-users-supported}? | | +-- user* [name] | | +--name?name string | | +-- public-keys! {local-user-auth-publickey}? | | | +---u ts:inline-or-truststore-public-keys-grouping | | +-- password | | | +-- hashed-password? ianach:crypt-hash | | | | {local-user-auth-password}? | | | +--ro last-modified? yang:date-and-time | | +-- hostbased! {local-user-auth-hostbased}? | | | +---u ts:inline-or-truststore-public-keys-grouping | | +-- none? empty {local-user-auth-none}? | +-- ca-certs! {sshcmn:ssh-x509-certs}? | | +---u ts:inline-or-truststore-certs-grouping | +-- ee-certs! {sshcmn:ssh-x509-certs}? | +---u ts:inline-or-truststore-certs-grouping +-- transport-params {sshcmn:transport-params}? | +---u sshcmn:transport-params-grouping +-- keepalives! {ssh-server-keepalives}? +-- max-wait? uint16 +-- max-attempts? uint8]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "server-identity" node configures the authentication methods the server can use to identify itself to clients. The ability to use a certificate is enabled by a "feature".</li> <li>The "client-authentication" node configures trust anchors for authenticating the SSH client, with each option enabled by a "feature" statement.</li> <li>The "transport-params" node, which must be enabled by a feature, configures parameters for the SSH sessions established by this configuration.</li> <li>The "keepalives" node, which must be enabled by a feature, configures a "presence" container for testing the aliveness of the SSH client. The aliveness-test occurs at the SSH protocol layer.</li> <li> <t>For the referenced groupingstatement(s):statements: </t> <ulspacing="compact">spacing="normal"> <li>The "inline-or-keystore-asymmetric-key-grouping" grouping is discussed in <xref section="2.1.3.4"target="I-D.ietf-netconf-keystore"/>.</li>target="RFC9642"/>.</li> <li>The "inline-or-keystore-end-entity-cert-with-key-grouping" grouping is discussed in <xref section="2.1.3.6"target="I-D.ietf-netconf-keystore"/>.</li>target="RFC9642"/>.</li> <li>The "inline-or-truststore-public-keys-grouping" grouping is discussed in <xref section="2.1.3.4"target="I-D.ietf-netconf-trust-anchors"/>.</li>target="RFC9641"/>.</li> <li>The "inline-or-truststore-certs-grouping" grouping is discussed in <xref section="2.1.3.3"target="I-D.ietf-netconf-trust-anchors"/>.</li>target="RFC9641"/>.</li> <li>The "transport-params-grouping" grouping is discussed in <xref target="transport-params-grouping"/> in this document.</li> </ul> </li> </ul> </section> </section> <section toc="exclude"><name>Protocol-accessible<name>Protocol-Accessible Nodes</name> <t>The "ietf-ssh-server" module defines only "grouping" statements that are used by other modules to instantiate protocol-accessible nodes.ThusThus, this module, when implemented, does not itself define any protocol-accessible nodes.</t> </section> </section> <section anchor="server-examples"> <name>Example Usage</name> <t>This section presents two examples showing the "ssh-server-grouping" grouping populated with some data. These examples are effectively thesamesame, except the first configures the server identity usingaan inlinedkeykey, while the second uses a key configured in a keystore. Both examples are consistent with the examples presented in <xref section="2.2.1"target="I-D.ietf-netconf-trust-anchors"/>target="RFC9641"/> and <xref section="2.2.1"target="I-D.ietf-netconf-keystore"/>.</t>target="RFC9642"/>.</t> <t>The following configuration example uses inline-definitions for the server identity and client authentication: </t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <ssh-server xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-server" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> <!-- the host-key this SSH server will present --> <server-identity> <host-key> <name>my-pubkey-based-host-key</name> <public-key> <inline-definition> <private-key-format>ct:rsa-private-key-format</private-key\ -format> <cleartext-private-key>BASE64VALUE=</cleartext-private-key> </inline-definition> </public-key> </host-key> <host-key> <name>my-cert-based-host-key</name> <certificate> <inline-definition> <private-key-format>ct:rsa-private-key-format</private-key\ -format> <cleartext-private-key>BASE64VALUE=</cleartext-private-key> <cert-data>BASE64VALUE=</cert-data> </inline-definition> </certificate> </host-key> </server-identity> <!-- the client credentials this SSH server will trust --> <client-authentication> <users> <user> <name>mary</name> <password> <hashed-password>$0$example-secret</hashed-password> </password> <public-keys> <inline-definition> <public-key> <name>Mary-Key-1</name> <public-key-format>ct:ssh-public-key-format</public-ke\ y-format> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>Mary-Key-2</name> <public-key-format>ct:ssh-public-key-format</public-ke\ y-format> <public-key>BASE64VALUE=</public-key> </public-key> </inline-definition> </public-keys> </user> </users> <ca-certs> <inline-definition> <certificate> <name>Identity Cert Issuer #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Identity Cert Issuer #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </inline-definition> </ca-certs> <ee-certs> <inline-definition> <certificate> <name>Application #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Application #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </inline-definition> </ee-certs> </client-authentication> <keepalives> <max-wait>30</max-wait> <max-attempts>3</max-attempts> </keepalives> </ssh-server>]]></artwork>]]></sourcecode> <t>The following configuration example uses central-keystore-references for the server identity and central-truststore-references for clientauthentication:authentication from the keystore: </t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <ssh-server xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-server"> <!-- the host-key this SSH server will present --> <server-identity> <host-key> <name>my-pubkey-based-host-key</name> <public-key> <central-keystore-reference>ssh-rsa-key</central-keystore-re\ ference> </public-key> </host-key> <host-key> <name>my-cert-based-host-key</name> <certificate> <central-keystore-reference> <asymmetric-key>ssh-rsa-key-with-cert</asymmetric-key> <certificate>ex-rsa-cert2</certificate> </central-keystore-reference> </certificate> </host-key> </server-identity> <!-- the client credentials this SSH server will trust --> <client-authentication> <users> <user> <name>mary</name> <password> <hashed-password>$0$example-secret</hashed-password> </password> <public-keys> <central-truststore-reference>SSH Public Keys for Applicat\ ion A</central-truststore-reference> </public-keys> </user> </users> <ca-certs> <central-truststore-reference>trusted-client-ca-certs</central\ -truststore-reference> </ca-certs> <ee-certs> <central-truststore-reference>trusted-client-ee-certs</central\ -truststore-reference> </ee-certs> </client-authentication> <keepalives> <max-wait>30</max-wait> <max-attempts>3</max-attempts> </keepalives> </ssh-server>]]></artwork>]]></sourcecode> </section> <section anchor="server-yang-module"> <name>YANG Module</name> <t>This YANG module has normative references to <xref target="RFC4251"/>, <xref target="RFC4252"/>, <xref target="RFC4253"/>, <xref target="RFC4254"/>, <xref target="RFC6991"/>, <xref target="RFC7317"/>, <xref target="RFC8341"/>, <xreftarget="I-D.ietf-netconf-crypto-types"/>,target="RFC9640"/>, <xreftarget="I-D.ietf-netconf-trust-anchors"/>,target="RFC9641"/>, and <xreftarget="I-D.ietf-netconf-keystore"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "ietf-ssh-server@2024-03-16.yang"</t> <artwork><![CDATA[target="RFC9642"/>.</t> <sourcecode type="yang" markers="true" name="ietf-ssh-server@2024-03-16.yang"><![CDATA[ module ietf-ssh-server { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ssh-server"; prefix sshs; import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types"; } import iana-crypt-hash { prefix ianach; reference "RFC 7317: A YANG Data Model for System Management"; } import ietf-netconf-acm { prefix nacm; reference "RFC 8341: Network Configuration Access Control Model"; } import ietf-crypto-types { prefix ct; reference "RFCAAAA:9640: YANG Data Types and Groupings for Cryptography"; } import ietf-truststore { prefix ts; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; } import ietf-keystore { prefix ks; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; } import ietf-ssh-common { prefix sshcmn; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: https://datatracker.ietf.org/wg/netconf WG List: NETCONF WG list <mailto:netconf@ietf.org> Author: Kent Watsen <mailto:kent+ietf@watsen.net>"; description "This module defines a reusable grouping for SSH servers that can be used as a basis for specific SSH server instances. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCEEEE (https://www.rfc-editor.org/info/rfcEEEE);9644 (https://www.rfc-editor.org/info/rfc9644); see the RFC itself for full legalnotices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here.";notices."; revision 2024-03-16 { description "Initialversion";version."; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } // Features feature ssh-server-keepalives { description "Per socket SSHkeepalivekeep-alive parameters are configurable for SSH servers on the server implementing this feature."; } feature local-users-supported { description "Indicates that the configuration for users can be configured herein, as opposed to in anapplicationapplication- specific location."; } feature local-user-auth-publickey { if-feature "local-users-supported"; description "Indicates that the 'publickey' authentication type, per RFC 4252, is supported forlocally-definedlocally defined users. The 'publickey' authentication type is required by RFC 4252, but common implementations allow it to be disabled."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature local-user-auth-password { if-feature "local-users-supported"; description "Indicates that the 'password' authentication type, per RFC 4252, is supported forlocally-definedlocally defined users."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature local-user-auth-hostbased { if-feature "local-users-supported"; description "Indicates that the 'hostbased' authentication type, per RFC 4252, is supported forlocally-definedlocally defined users."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } feature local-user-auth-none { if-feature "local-users-supported"; description "Indicates that the 'none' authentication type, per RFC 4252, is supported. It is NOT RECOMMENDED to enable this feature."; reference "RFC 4252: The Secure Shell (SSH) Authentication Protocol"; } // Groupings grouping ssh-server-grouping { description "A reusable grouping for configuringaan SSH server without any consideration for how underlying TCP sessions are established. Note that this grouping uses fairly typical descendant node names such that a nesting of 'uses' statements will have name conflicts. It is intended that the consuming data model will resolve the issue (e.g., by wrapping the 'uses' statement in a container called 'ssh-server-parameters'). This model purposely does not do this itself so as to provide maximum flexibility to consuming models."; container server-identity { nacm:default-deny-write; description "The list of host keys the SSH server will present when establishingaan SSH connection."; list host-key { key "name"; min-elements 1; ordered-by user; description "An ordered list of host keys (see RFC 4251) the SSH server will use to construct its ordered list ofalgorithms,algorithms when sending its SSH_MSG_KEXINIT message, as defined in Section 7.1 of RFC 4253."; reference "RFC 4251: The Secure Shell (SSH) Protocol Architecture RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; leaf name { type string; description "An arbitrary name for this hostkey";key."; } choice host-key-type { mandatory true; description "The type of host key beingspecified";specified."; container public-key { description "Alocally-definedlocally defined or referenced asymmetric key pair to be used for the SSH server's host key."; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; uses ks:inline-or-keystore-asymmetric-key-grouping { refine "inline-or-keystore/inline/inline-definition" { must 'not(public-key-format) or derived-from-or-self' + '(public-key-format, "ct:ssh-public-key-format")'; } refine "inline-or-keystore/central-keystore/" + "central-keystore-reference" { must 'not(deref(.)/../ks:public-key-format) or ' + 'derived-from-or-self(deref(.)/../ks:public-' + 'key-format, "ct:ssh-public-key-format")'; } } } container certificate { if-feature "sshcmn:ssh-x509-certs"; description "Alocally-definedlocally defined or referenced end-entity certificate to be used for the SSH server's host key."; reference "RFCCCCC:9642: A YANG Data Model for aKeystore";Keystore and Keystore Operations"; uses ks:inline-or-keystore-end-entity-cert-with-key-grouping{ refine "inline-or-keystore/inline/inline-definition" { must 'not(public-key-format) or derived-from-or-self' + '(public-key-format, "ct:subject-public-key-' + 'info-format")'; } refine "inline-or-keystore/central-keystore/" + "central-keystore-reference/asymmetric-key" { must 'not(deref(.)/../ks:public-key-format) or ' + 'derived-from-or-self(deref(.)/../ks:public-key' + '-format, "ct:subject-public-key-info-format")'; } } } } } } // container server-identity container client-authentication { nacm:default-deny-write; description "Specifies how the SSH server can be configured to authenticate SSH clients. See RFC 4252 for a general discussion about SSH authentication."; reference "RFC 4252: The Secure Shell (SSH)Transport Layer";Authentication Protocol"; container users { if-feature "local-users-supported"; description "A list of locally configured users."; list user { key "name"; description "A locally configured user. The server SHOULD derive the list of authentication 'method names' returned to the SSH client from the descendant nodes configured herein, per Sections 5.1 and 5.2inof RFC 4252. The authentication methods are unordered. Clients must authenticate to all configured methods. Whenever a choice amongst methods arises, implementations SHOULD use a default ordering that prioritizes automation overhuman-interaction.";human interaction."; leaf name { type string; description "The'user name''username' for the SSH client, as defined in the SSH_MSG_USERAUTH_REQUEST message in RFC 4253."; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } container public-keys { if-feature "local-user-auth-publickey"; presence "Indicates that public keys have been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A set of SSH public keys may be used by the SSH server to authenticate this user. A user is authenticated if its public key is an exact match to a configured public key."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-public-keys-grouping { refine "inline-or-truststore/inline/inline-definition/" + "public-key" { must 'derived-from-or-self(public-key-format,' + ' "ct:ssh-public-key-format")'; } refine "inline-or-truststore/central-truststore/" + "central-truststore-reference" { must 'not(deref(.)/../ts:public-key/ts:public-key-' + 'format[not(derived-from-or-self(., "ct:ssh-' + 'public-key-format"))])'; } } } container password { description "A password the SSH server may use to authenticate this user. A user is authenticated if the hash of the supplied password matches this value."; leaf hashed-password { if-feature "local-user-auth-password"; type ianach:crypt-hash; description "The password for this user."; } leaf last-modified { type yang:date-and-time; config false; description "Identifies when the password was last set."; } } container hostbased { if-feature "local-user-auth-hostbased"; presence "Indicates thathostbased [RFC4252]host-based (RFC 4252) keys have been configured. This statement is present so the mandatory descendant nodes do not imply that this node must be configured."; description "A set of SSH host keys used by the SSH server to authenticate this user's host. A user's host is authenticated if its host key is an exact match to a configured host key."; reference "RFC 4252: The Secure Shell (SSH)Transport LayerAuthentication Protocol RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-public-keys-grouping { refine "inline-or-truststore/inline/inline-definition/" + "public-key" { must 'derived-from-or-self(public-key-format,' + ' "ct:ssh-public-key-format")'; } refine "inline-or-truststore/central-truststore/" + "central-truststore-reference" { must 'not(deref(.)/../ts:public-key/ts:public-key-' + 'format[not(derived-from-or-self(., "ct:ssh-' + 'public-key-format"))])'; } } } leaf none { if-feature "local-user-auth-none"; type empty; description "Indicates that the 'none' method is configured for this user."; reference "RFC 4252: The Secure Shell (SSH) AuthenticationProtocol.";Protocol"; } } } // users container ca-certs { if-feature "sshcmn:ssh-x509-certs"; presence "Indicates that CA certificates have been configured. This statement is present so the mandatory descendant nodes do not imply this node must be configured."; description "A set of certificate authority (CA) certificates used by the SSH server to authenticate SSH client certificates. A client certificate is authenticated if it has a valid chain of trust to a configured CA certificate."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-certs-grouping; } container ee-certs { if-feature "sshcmn:ssh-x509-certs"; presence "Indicates that EE certificates have been configured. This statement is present so the mandatory descendant nodes do not imply this node must be configured."; description "A set of client certificates (i.e.,end entityend-entity certificates) used by the SSH server to authenticate the certificates presented by SSH clients. A client certificate is authenticated if it is an exact match to a configured end-entity certificate."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; uses ts:inline-or-truststore-certs-grouping; } } // container client-authentication container transport-params { nacm:default-deny-write; if-feature "sshcmn:transport-params"; description "Configurable parameters of the SSH transport layer."; uses sshcmn:transport-params-grouping; } // container transport-params container keepalives { nacm:default-deny-write; if-feature "ssh-server-keepalives"; presence "Indicates that the SSH server proactively tests the aliveness of the remote SSH client."; description "Configures the keep-alivepolicy,policy to proactively test the aliveness of the SSH client. An unresponsive SSH client is dropped after approximately max-wait * max-attempts seconds. Per Section 4 of RFC 4254, the SSH server SHOULD send an SSH_MSG_GLOBAL_REQUEST message with a purposely nonexistent 'request name' value (e.g.,keepalive@ietf.org)keepalive@example.com) and the 'want reply' value set to '1'."; reference "RFC 4254: The Secure Shell (SSH) Connection Protocol"; leaf max-wait { type uint16 { range "1..max"; } units "seconds"; default "30"; description "Sets the amount of time in seconds after whichif no data has been received from the SSH client, aan SSH-level message will be sent to test the aliveness of the SSH client if no data has been received from the SSH client."; } leaf max-attempts { type uint8; default "3"; description "Sets the maximum number of sequential keep-alive messages that can fail to obtain a response from the SSH client before assuming the SSH client is no longer alive."; } } } // grouping ssh-server-grouping }]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t>]]></sourcecode> </section> </section> <section> <name>Security Considerations</name> <t>The three IETF YANG modules in this document define groupings and will not be deployed as standalone modules. Their security implications may becontext dependentcontext-dependent based on their use in other modules. The designers of moduleswhichthat import thesegroupinggroupings must conduct their own analysis of the security considerations.</t> <section> <name>Considerations for the "iana-ssh-key-exchange-algs" Module</name> <t>This sectionfollowsis modeled after the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "iana-ssh-key-exchange-algs" YANG module defines a data model that is designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>This YANG module defines YANGenumerations,enumerations for a public IANA-maintained registry.</t> <t>YANG enumerations are not security-sensitive, as they are statically defined in thepublicly-accessiblepublicly accessible YANG module. IANAMAY<bcp14>MAY</bcp14> deprecate and/or obsolete enumerations over time as needed to address security issues found in the algorithms.</t> <t>This module does not define anywritable-nodes,writable nodes, RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "iana-ssh-encryption-algs" Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "iana-ssh-encryption-algs" YANG module defines a data model that is designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>This YANG module defines YANGenumerations,enumerations for a public IANA-maintained registry.</t> <t>YANG enumerations are not security-sensitive, as they are statically defined in thepublicly-accessiblepublicly accessible YANG module.</t> <t>This module does not define anywritable-nodes,writable nodes, RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "iana-ssh-mac-algs" Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "iana-ssh-mac-algs" YANG module defines a data model that is designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>This YANG module defines YANGenumerations,enumerations for a public IANA-maintained registry.</t> <t>YANG enumerations are not security-sensitive, as they are statically defined in thepublicly-accessiblepublicly accessible YANG module.</t> <t>This module does not define anywritable-nodes,writable nodes, RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "iana-ssh-public-key-algs" Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "iana-ssh-public-key-algs" YANG module defines a data model that is designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>This YANG module defines YANGenumerations,enumerations for a public IANA-maintained registry.</t> <t>YANG enumerations are not security-sensitive, as they are statically defined in thepublicly-accessiblepublicly accessible YANG module.</t> <t>This module does not define anywritable-nodes,writable nodes, RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "ietf-ssh-common" YANG Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "ietf-ssh-common" YANG module defines "grouping" statements that are designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>Please be aware that this YANG module uses groupings from other YANG modules that define nodes that may be considered sensitive or vulnerable in network environments. Please review theSecurity Considerationssecurity considerations for dependent YANG modules for information as to which nodes may be considered sensitive or vulnerable in network environments.</t> <t>None of the readable data nodes defined in this YANG module are considered sensitive or vulnerable in network environments. The NACM "default-deny-all" extension has not been set for any data nodes defined in this module.</t> <t>None of the writable data nodes defined in this YANG module are considered sensitive or vulnerable in network environments. The NACM "default-deny-write" extension has not been set for any data nodes defined in this module.</t> <t>This module defines theRPC"generate-asymmetric-key-pair"thatRPC, which may, if the "ct:cleartext-private-keys" feature isenabled,enabled and the client requests it, return the private clear in cleartext form. It isNOT RECOMMENDED<bcp14>NOT RECOMMENDED</bcp14> for private keys to pass the server's security perimeter.</t> <t>This module does not define any actions or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "ietf-ssh-client" YANG Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "ietf-ssh-client" YANG module defines "grouping" statements that are designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>TheNetwork AccessControl Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>Please be aware that this YANG module uses groupings from other YANG modules that define nodes that may be considered sensitive or vulnerable in network environments. Please review theSecurity Considerationssecurity considerations for dependent YANG modules for information as to which nodes may be considered sensitive or vulnerable in network environments.</t> <t>One readable data node defined in this YANG module may be considered sensitive or vulnerable in some network environments. This node is as follows: </t> <ul spacing="normal"> <li> <t>The "client-identity/password" node: </t> <ul empty="true"> <li>The cleartext "password" node defined in the "ssh-client-grouping" grouping is additionally sensitive to read operations such that, in normal use cases, it should never be returned to a client. For this reason, the NACM extension "default-deny-all" has been applied to it.</li> </ul> </li> </ul> <t>All the writable data nodes defined by this module may be considered sensitive or vulnerable in some network environments. For instance, any modification to a key or reference to a key may dramatically alter the implemented security policy. For this reason, the NACM extension "default-deny-write" has been set for all data nodes defined in this module.</t> <t>This module does not define any RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> <section> <name>Considerations for the "ietf-ssh-server" YANG Module</name> <t>This section follows the template defined in <xref section="3.7.1" target="RFC8407"/>.</t> <t>The "ietf-ssh-server" YANG module defines "grouping" statements that are designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. Both of these protocols have mandatory-to-implement secure transport layers (e.g., SSH, TLS) with mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>Please be aware that this YANG module uses groupings from other YANG modules that define nodes that may be considered sensitive or vulnerable in network environments. Please review theSecurity Considerationssecurity considerations for dependent YANG modules for information as to which nodes may be considered sensitive or vulnerable in network environments.</t> <t>None of the readable data nodes defined in this YANG module are considered sensitive or vulnerable in network environments. The NACM "default-deny-all" extension has not been set for any data nodes defined in this module.</t> <t>All the writable data nodes defined by this module may be considered sensitive or vulnerable in some network environments. For instance, the addition or removal of references to keys, certificates, trusted anchors, etc., or even the modification of transport orkeepalivekeep-alive parameters can dramatically alter the implemented security policy. For this reason, the NACM extension "default-deny-write" has been set for all data nodes defined in this module.</t> <t>This module does not define any RPCs, actions, or notifications, andthusthus, the securityconsiderationconsiderations for suchisare not provided here.</t> </section> </section> <section> <name>IANA Considerations</name> <section> <name>The"IETF XML"IETF XML Registry</name><t>This document registers<t>IANA has registered seven URIs in the "ns"subregistryregistry of theIETF"IETF XMLRegistry <xref target="RFC3688"/>. Following the format inRegistry" <xreftarget="RFC3688"/>, the following registrations are requested:</t> <artwork><![CDATA[ URI: urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs Registrant Contact: The IESG XML: N/A,target="RFC3688"/> as follows.</t> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:ietf-ssh-common Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-common</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:ietf-ssh-client Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-client</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:ietf-ssh-server Registrant Contact: The IESG XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-server</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. ]]></artwork>namespace.</dd> </dl> </section> <section> <name>The"YANGYANG ModuleNames"Names Registry</name><t>This document registers<t>IANA has registered seven YANG modules in theYANG"YANG ModuleNamesNames" registry <xreftarget="RFC6020"/>. Following the format in <xref target="RFC6020"/>, the following registrations are requested:</t> <artwork><![CDATA[ name: iana-ssh-key-exchange-algs namespace: urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs prefix: sshkea reference: RFC EEEE name: iana-ssh-encryption-algs namespace: urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs prefix: sshea reference: RFC EEEE name: iana-ssh-mac-algs namespace: urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs prefix: sshma reference: RFC EEEE name: iana-ssh-public-key-algs namespace: urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs prefix: sshpka reference: RFC EEEE name: ietf-ssh-common namespace: urn:ietf:params:xml:ns:yang:ietf-ssh-common prefix: sshcmn reference: RFC EEEE name: ietf-ssh-client namespace: urn:ietf:params:xml:ns:yang:ietf-ssh-client prefix: sshc reference: RFC EEEE name: ietf-ssh-server namespace: urn:ietf:params:xml:ns:yang:ietf-ssh-server prefix: sshs reference: RFC EEEE ]]></artwork>target="RFC6020"/> as follows.</t> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>iana-ssh-key-exchange-algs</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs</dd> <dt>Prefix:</dt> <dd>sshkea</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>iana-ssh-encryption-algs</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs</dd> <dt>Prefix:</dt> <dd>sshea</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>iana-ssh-mac-algs</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs</dd> <dt>Prefix:</dt> <dd>sshma</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>iana-ssh-public-key-algs</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs</dd> <dt>Prefix:</dt> <dd>sshpka</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>ietf-ssh-common</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-common</dd> <dt>Prefix:</dt> <dd>sshcmn</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>ietf-ssh-client</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-client</dd> <dt>Prefix:</dt> <dd>sshc</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>ietf-ssh-server</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-ssh-server</dd> <dt>Prefix:</dt> <dd>sshs</dd> <dt>Reference:</dt> <dd>RFC 9644</dd> </dl> </section> <section> <name>Considerations for the "iana-ssh-encryption-algs" Module</name> <t>This section follows the template defined in <xref section="4.30.3.1" target="I-D.ietf-netmod-rfc8407bis"/>.</t> <t>This document presents a script (see <xref target="iana-script"/>) for IANA to use to generate the IANA-maintained "iana-ssh-encryption-algs" YANG module. The most recent version of the YANG module is availablefromin the "YANG Parameters" registry group <xref target="IANA-YANG-PARAMETERS"/>.</t> <t>IANAis requested to addhas added the following note to the registry:</t> <blockquote>New values must not be directly added to the "iana-ssh-encryption-algs" YANG module. They must instead be added to the "Encryption Algorithm Names"sub-registryregistry of the "Secure Shell (SSH) Protocol Parameters" registry group <xref target="IANA-ENC-ALGS"/>.</blockquote> <t>When a value is added to the "Encryption Algorithm Names"sub-registry,registry, a new "enum" statement must be added to the "iana-ssh-encryption-algs" YANG module. The "enum" statement, andsub-statementssubstatements thereof, should be defined as follows:</t> <dl newline="true"> <dt>enum</dt> <dd>Replicates a name from the registry.</dd> <dt>value</dt> <dd>Contains the decimal value of the IANA-assigned value.</dd> <dt>status</dt> <dd>Include only if a registration has been deprecated or obsoleted. An IANA "Note" containing the word "HISTORIC" maps to YANG status "obsolete". Since the registry is unable to express a"SHOULD NOT""<bcp14>SHOULD NOT</bcp14>" recommendation, there is no mapping to YANG status "deprecated".</dd> <dt>description</dt> <dd>Contains "Enumeration for the 'foo-bar' algorithm.", where "foo-bar" is a placeholder for the algorithm's name (e.g., "3des-cbc").</dd> <dt>reference</dt> <dd>Replicates the reference(s) from the registry with the title of the document(s) added.</dd> </dl> <t>Unassigned or reserved values are not present in the module.</t> <t>When the "iana-ssh-encryption-algs" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. The "revision" must have a "description" statement explaining why thetheupdateoccurred,occurred and must have a "reference" substatement that points to the document defining the registry update that resulted in this change. For instance:</t><artwork><![CDATA[<sourcecode type="yang"><![CDATA[ revision 2024-02-02 { description "This updatereflectreflects the update made to the underlying Foo Bar registry per RFC XXXX."; reference "RFC XXXX: Extend the Foo Bars Registry to Support Something Important";}]]></artwork>}]]></sourcecode> <t>IANAis requested to addhas added the following note to the "Encryption Algorithm Names"sub-registry.</t>registry.</t> <blockquote>When this registry is modified, the YANG module "iana-ssh-encryption-algs" <xref target="IANA-YANG-PARAMETERS"/> must be updated as defined in RFCEEEE.</blockquote>9644.</blockquote> </section> <section> <name>Considerations for the "iana-ssh-mac-algs" Module</name> <t>This section follows the template defined in <xref section="4.30.3.1" target="I-D.ietf-netmod-rfc8407bis"/>.</t> <t>This document presents a script (see <xref target="iana-script"/>) for IANA to use to generate the IANA-maintained "iana-ssh-mac-algs" YANG module. The most recent version of the YANG module is availablefromin the "YANG Parameters" registry group <xref target="IANA-YANG-PARAMETERS"/>.</t> <t>IANAis requested to addhas added the following note to the registry:</t> <blockquote>New values must not be directly added to the "iana-ssh-mac-algs" YANG module. They must instead be added to the "MAC Algorithm Names"sub-registryregistry of the "Secure Shell (SSH) Protocol Parameters" registry group <xref target="IANA-MAC-ALGS"/>.</blockquote> <t>When a value is added to the "MAC Algorithm Names"sub-registry,registry, a new "enum" statement must be added to the "iana-ssh-mac-algs" YANG module. The "enum" statement, andsub-statementssubstatements thereof, should be defined as follows:</t> <dl newline="true"> <dt>enum</dt> <dd>Replicates a name from the registry.</dd> <dt>value</dt> <dd>Contains the decimal value of the IANA-assigned value.</dd> <dt>status</dt> <dd>Include only if a registration has been deprecated or obsoleted.</dd> <dt>description</dt> <dd>Contains "Enumeration for the 'foo-bar' algorithm.", where "foo-bar" is a placeholder for the algorithm's name (e.g., "3des-cbc").</dd> <dt>reference</dt> <dd>Replicates the reference(s) from the registry with the title of the document(s) added.</dd> </dl> <t>Unassigned or reserved values are not present in the module.</t> <t>When the "iana-ssh-mac-algs" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. The "revision" must have a "description" statement explaining why thetheupdateoccurred,occurred and must have a "reference" substatement that points to the document defining the registry update that resulted in this change. For instance:</t><artwork><![CDATA[<sourcecode type="yang"><![CDATA[ revision 2024-02-02 { description "This updatereflectreflects the update made to the underlying Foo Bar registry per RFC XXXX."; reference "RFC XXXX: Extend the Foo Bars Registry to Support Something Important";}]]></artwork>}]]></sourcecode> <t>IANAis requested to addhas added the following note to the "MAC Algorithm Names"sub-registry.</t>registry.</t> <blockquote>When this registry is modified, the YANG module "iana-ssh-mac-algs" <xref target="IANA-YANG-PARAMETERS"/> must be updated as defined in RFCEEEE.</blockquote>9644.</blockquote> </section> <section> <name>Considerations for the "iana-ssh-public-key-algs" Module</name> <t>This section follows the template defined in <xref section="4.30.3.1" target="I-D.ietf-netmod-rfc8407bis"/>.</t> <t>This document presents a script (see <xref target="iana-script"/>) for IANA to use to generate the IANA-maintained "iana-ssh-public-key-algs" YANG module. The most recent version of the YANG module is availablefromin the "YANG Parameters" registry group <xref target="IANA-YANG-PARAMETERS"/>.</t> <t>IANAis requested to addhas added the following note to the registry:</t> <blockquote>New values must not be directly added to the "iana-ssh-public-key-algs" YANG module. They must instead be added to the "Public Key Algorithm Names"sub-registryregistry of the "Secure Shell (SSH) Protocol Parameters" registry group <xref target="IANA-PUBKEY-ALGS"/>.</blockquote> <t>When a value is added to the "Public Key Algorithm Names"sub-registry,registry, a new "enum" statement must be added to the "iana-ssh-public-key-algs" YANG module. The "enum" statement, andsub-statementssubstatements thereof, should be defined as follows:</t> <dl newline="true"> <dt>enum</dt> <dd>Replicates a name from the registry.</dd> <dt>value</dt> <dd>Contains the decimal value of the IANA-assigned value.</dd> <dt>status</dt> <dd>Include only if a registration has been deprecated or obsoleted.</dd> <dt>description</dt> <dd>Contains "Enumeration for the 'foo-bar' algorithm.", where "foo-bar" is a placeholder for the algorithm's name (e.g., "3des-cbc").</dd> <dt>reference</dt> <dd>Replicates the reference(s) from the registry with the title of the document(s) added.</dd> </dl> <t>In the case that the algorithm name ends with "-*", thefamiliyfamily of enumerations must be added. Thefamiliyfamily of enum algorithm names are generated by replacing the'*'"*" character with these strings: "nistp256", "nistp384", "nistp521", "1.3.132.0.1", "1.2.840.10045.3.1.1", "1.3.132.0.33", "1.3.132.0.26", "1.3.132.0.27", "1.3.132.0.16", "1.3.132.0.36", "1.3.132.0.37", and "1.3.132.0.38".</t> <t>Unassigned or reserved values are not present in the module.</t> <t>When the "iana-ssh-public-key-algs" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. The "revision" must have a "description" statement explaining why thetheupdateoccurred,occurred and must have a "reference" substatement that points to the document defining the registry update that resulted in this change. For instance:</t><artwork><![CDATA[<sourcecode type="yang"><![CDATA[ revision 2024-02-02 { description "This updatereflectreflects the update made to the underlying Foo Bar registry per RFC XXXX."; reference "RFC XXXX: Extend the Foo Bars Registry to Support Something Important";}]]></artwork>}]]></sourcecode> <t>IANAis requested to addhas added the following note to the "Public Key Algorithm Names"sub-registry.</t>registry.</t> <blockquote>When this registry is modified, the YANG module "iana-ssh-public-key-algs" <xref target="IANA-YANG-PARAMETERS"/> must be updated as defined in RFCEEEE.</blockquote>9644.</blockquote> </section> <section> <name>Considerations for the "iana-ssh-key-exchange-algs" Module</name> <t>This section follows the template defined in <xref section="4.30.3.1" target="I-D.ietf-netmod-rfc8407bis"/>.</t> <t>This document presents a script (see <xref target="iana-script"/>) for IANA to use to generate the IANA-maintained "iana-ssh-key-exchange-algs" YANG module. The most recent version of the YANG module is availablefromin the "YANG Parameters" registry group <xref target="IANA-YANG-PARAMETERS"/>.</t> <t>IANAis requested to addhas added the following note to the registry:</t> <blockquote>New values must not be directly added to the "iana-ssh-key-exchange-algs" YANG module. They must instead be added to the "Key Exchange Method Names"sub-registryregistry of the "Secure Shell (SSH) Protocol Parameters" registry group <xref target="IANA-KEYEX-ALGS"/>.</blockquote> <t>When a value is added to the "Key Exchange Method Names"sub-registry,registry, a new "enum" statement must be added to the "iana-ssh-key-exchange-algs" YANG module. The "enum" statement, andsub-statementssubstatements thereof, should be defined as follows:</t> <dl newline="true"> <dt>enum</dt> <dd>Replicates a name from the registry.</dd> <dt>value</dt> <dd>Contains the decimal value of the IANA-assigned value.</dd> <dt>status</dt> <dd>Include only if a registration has been deprecated or obsoleted. An IANA "OK to Implement" containing"SHOULD NOT""<bcp14>SHOULD NOT</bcp14>" maps to YANG status "deprecated". An IANA "OK to Implement" containing"MUST NOT""<bcp14>MUST NOT</bcp14>" maps to YANG status "obsolete".</dd> <dt>description</dt> <dd>Contains "Enumeration for the 'foo-bar' algorithm.", where "foo-bar" is a placeholder for the algorithm's name (e.g., "3des-cbc").</dd> <dt>reference</dt> <dd>Replicates the reference(s) from the registry with the title of the document(s) added.</dd> </dl> <t>In the case that the algorithm name ends with "-*", thefamiliyfamily of enumerations must be added. Thefamiliyfamily of enum algorithm names are generated by replacing the'*'"*" character with these strings: "nistp256", "nistp384", "nistp521", "1.3.132.0.1", "1.2.840.10045.3.1.1", "1.3.132.0.33", "1.3.132.0.26", "1.3.132.0.27", "1.3.132.0.16", "1.3.132.0.36", "1.3.132.0.37", and "1.3.132.0.38".</t> <t>Unassigned or reserved values are not present in the module.</t> <t>When the "iana-ssh-key-exchange-algs" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. The "revision" must have a "description" statement explaining why thetheupdate occurred, and must have a "reference" substatement that points to the document defining the registry update that resulted in this change. For instance:</t><artwork><![CDATA[<sourcecode type="yang"><![CDATA[ revision 2024-02-02 { description "This updatereflectreflects the update made to the underlying Foo Bar registry per RFC XXXX."; reference "RFC XXXX: Extend the Foo Bars Registry to Support Something Important";}]]></artwork>}]]></sourcecode> <t>IANAis requested to addhas added the following note to the "Key Exchange Method Names"sub-registry.</t>registry.</t> <blockquote>When this registry is modified, the YANG module "iana-ssh-key-exchange-algs" <xref target="IANA-YANG-PARAMETERS"/> must be updated as defined in RFCEEEE.</blockquote>9644.</blockquote> </section> </section> </middle> <back> <displayreference target="I-D.ietf-netmod-system-config" to="SYSTEM-CONFIG"/> <displayreference target="I-D.ietf-netmod-rfc8407bis" to="YANG-GUIDE"/> <displayreference target="I-D.ietf-netconf-http-client-server" to="HTTP-CLIENT-SERVER"/> <displayreference target="I-D.ietf-netconf-netconf-client-server" to="NETCONF-CLIENT-SERVER"/> <displayreference target="I-D.ietf-netconf-restconf-client-server" to="RESTCONF-CLIENT-SERVER"/> <references> <name>References</name> <references> <name>Normative References</name><reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="March" year="1997"/> <abstract> <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/> </reference> <reference anchor="RFC4251" target="https://www.rfc-editor.org/info/rfc4251" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4251.xml"> <front> <title>The Secure Shell (SSH) Protocol Architecture</title> <author fullname="T. Ylonen" initials="T." surname="Ylonen"/> <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/> <date month="January" year="2006"/> <abstract> <t>The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4251"/> <seriesInfo name="DOI" value="10.17487/RFC4251"/> </reference> <reference anchor="RFC4252" target="https://www.rfc-editor.org/info/rfc4252" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4252.xml"> <front> <title>The Secure Shell (SSH) Authentication Protocol</title> <author fullname="T. Ylonen" initials="T." surname="Ylonen"/> <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/> <date month="January" year="2006"/> <abstract> <t>The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4252"/> <seriesInfo name="DOI" value="10.17487/RFC4252"/> </reference> <reference anchor="RFC4253" target="https://www.rfc-editor.org/info/rfc4253" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4253.xml"> <front> <title>The Secure Shell (SSH) Transport Layer Protocol</title> <author fullname="T. Ylonen" initials="T." surname="Ylonen"/> <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/> <date month="January" year="2006"/> <abstract> <t>The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.</t> <t>This document describes the SSH transport layer protocol, which typically runs on top of TCP/IP. The protocol can be used as a basis for a number of secure network services. It provides strong encryption, server authentication, and integrity protection. It may also provide compression.</t> <t>Key exchange method, public key algorithm, symmetric encryption algorithm, message authentication algorithm, and hash algorithm are all negotiated.</t> <t>This document also describes the Diffie-Hellman key exchange method and the minimal set of algorithms that are needed to implement the SSH transport layer protocol. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4253"/> <seriesInfo name="DOI" value="10.17487/RFC4253"/> </reference> <reference anchor="RFC4254" target="https://www.rfc-editor.org/info/rfc4254" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4254.xml"> <front> <title>The Secure Shell (SSH) Connection Protocol</title> <author fullname="T. Ylonen" initials="T." surname="Ylonen"/> <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/> <date month="January" year="2006"/> <abstract> <t>Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.</t> <t>This document describes the SSH Connection Protocol. It provides interactive login sessions, remote execution of commands, forwarded TCP/IP connections, and forwarded X11 connections. All of these channels are multiplexed into a single encrypted tunnel.</t> <t>The SSH Connection Protocol has been designed to run on top of the SSH transport layer and user authentication protocols. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4254"/> <seriesInfo name="DOI" value="10.17487/RFC4254"/> </reference> <reference anchor="RFC4344" target="https://www.rfc-editor.org/info/rfc4344" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4344.xml"> <front> <title>The Secure Shell (SSH) Transport Layer Encryption Modes</title> <author fullname="M. Bellare" initials="M." surname="Bellare"/> <author fullname="T. Kohno" initials="T." surname="Kohno"/> <author fullname="C. Namprempre" initials="C." surname="Namprempre"/> <date month="January" year="2006"/> <abstract> <t>Researchers have discovered that the authenticated encryption portion of the current SSH Transport Protocol is vulnerable to several attacks.</t> <t>This document describes new symmetric encryption methods for the Secure Shell (SSH) Transport Protocol and gives specific recommendations on how frequently SSH implementations should rekey. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4344"/> <seriesInfo name="DOI" value="10.17487/RFC4344"/> </reference> <reference anchor="RFC4419" target="https://www.rfc-editor.org/info/rfc4419" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4419.xml"> <front> <title>Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol</title> <author fullname="M. Friedl" initials="M." surname="Friedl"/> <author fullname="N. Provos" initials="N." surname="Provos"/> <author fullname="W. Simpson" initials="W." surname="Simpson"/> <date month="March" year="2006"/> <abstract> <t>This memo describes a new key exchange method for the Secure Shell (SSH) protocol. It allows the SSH server to propose new groups on which to perform the Diffie-Hellman key exchange to the client. The proposed groups need not be fixed and can change with time. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4419"/> <seriesInfo name="DOI" value="10.17487/RFC4419"/> </reference> <reference anchor="RFC4432" target="https://www.rfc-editor.org/info/rfc4432" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4432.xml"> <front> <title>RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol</title> <author fullname="B. Harris" initials="B." surname="Harris"/> <date month="March" year="2006"/> <abstract> <t>This memo describes a key-exchange method for the Secure Shell (SSH) protocol based on Rivest-Shamir-Adleman (RSA) public-key encryption. It uses much less client CPU time than the Diffie-Hellman algorithm specified as part of the core protocol, and hence is particularly suitable for slow client systems. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4432"/> <seriesInfo name="DOI" value="10.17487/RFC4432"/> </reference> <reference anchor="RFC4462" target="https://www.rfc-editor.org/info/rfc4462" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4462.xml"> <front> <title>Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol</title> <author fullname="J. Hutzelman" initials="J." surname="Hutzelman"/> <author fullname="J. Salowey" initials="J." surname="Salowey"/> <author fullname="J. Galbraith" initials="J." surname="Galbraith"/> <author fullname="V. Welch" initials="V." surname="Welch"/> <date month="May" year="2006"/> <abstract> <t>The Secure Shell protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network.</t> <t>The Generic Security Service Application Program Interface (GSS-API) provides security services to callers in a mechanism-independent fashion.</t> <t>This memo describes methods for using the GSS-API for authentication and key exchange in SSH. It defines an SSH user authentication method that uses a specified GSS-API mechanism to authenticate a user, and a family of SSH key exchange methods that use GSS-API to authenticate a Diffie-Hellman key exchange.</t> <t>This memo also defines a new host public key algorithm that can be used when no operations are needed using a host's public key, and a new user authentication method that allows an authorization name to be used in conjunction with any authentication that has already occurred<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4250.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4251.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4252.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4253.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4254.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6187.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7317.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <!-- [I-D.ietf-netconf-crypto-types] IESG state: RFC Ed Queue asa side-effect of GSS-API-based key exchange. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4462"/> <seriesInfo name="DOI" value="10.17487/RFC4462"/> </reference> <reference anchor="RFC5647" target="https://www.rfc-editor.org/info/rfc5647" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5647.xml"> <front> <title>AES Galois Counter Mode for the Secure Shell Transport Layer Protocol</title> <author fullname="K. Igoe" initials="K." surname="Igoe"/> <author fullname="J. Solinas" initials="J." surname="Solinas"/> <date month="August" year="2009"/> <abstract> <t>Secure shell (SSH) is a secure remote-login protocol. SSH provides for algorithms that provide authentication, key agreement, confidentiality, and data-integrity services. The purposeofthis document is to show how the AES Galois Counter Mode can be used to provide both confidentiality and data integrity to the SSH Transport Layer Protocol. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="5647"/> <seriesInfo name="DOI" value="10.17487/RFC5647"/> </reference> <reference anchor="RFC5656" target="https://www.rfc-editor.org/info/rfc5656" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5656.xml"> <front> <title>Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer</title> <author fullname="D. Stebila" initials="D." surname="Stebila"/> <author fullname="J. Green" initials="J." surname="Green"/> <date month="December" year="2009"/> <abstract> <t>This03/21/24; companion documentdescribes algorithms based on Elliptic Curve Cryptography (ECC) for use within the Secure Shell (SSH) transport protocol. In particular, it specifies Elliptic Curve Diffie-Hellman (ECDH) key agreement, Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and Elliptic Curve Digital Signature Algorithm (ECDSA) for use in the SSH Transport Layer protocol. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="5656"/> <seriesInfo name="DOI" value="10.17487/RFC5656"/> </reference>RFC 9640 --> <referenceanchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml">anchor="RFC9640" target="https://www.rfc-editor.org/info/rfc9640"> <front> <title>YANG- ADataModeling Language for the Network Configuration Protocol (NETCONF)</title> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <date month="October" year="2010"/> <abstract> <t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls,Types andNETCONF notifications. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6020"/> <seriesInfo name="DOI" value="10.17487/RFC6020"/> </reference> <reference anchor="RFC6187" target="https://www.rfc-editor.org/info/rfc6187" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6187.xml"> <front> <title>X.509v3 CertificatesGroupings forSecure Shell Authentication</title>Cryptography</title> <authorfullname="K. Igoe"initials="K."surname="Igoe"/> <author fullname="D. Stebila" initials="D." surname="Stebila"/>surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <datemonth="March" year="2011"/> <abstract> <t>X.509 public key certificates use a signature by a trusted certification authority to bind a given public key to a given digital identity. This document specifies how to use X.509 version 3 public key certificates in public key algorithms in the Secure Shell protocol. [STANDARDS-TRACK]</t> </abstract>month="August" year="2024"/> </front> <seriesInfo name="RFC"value="6187"/>value="9640"/> <seriesInfo name="DOI"value="10.17487/RFC6187"/>value="10.17487/RFC9640"/> </reference><reference anchor="RFC6668" target="https://www.rfc-editor.org/info/rfc6668" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6668.xml"> <front> <title>SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol</title> <author fullname="D. Bider" initials="D." surname="Bider"/> <author fullname="M. Baushke" initials="M." surname="Baushke"/> <date month="July" year="2012"/> <abstract> <t>This memo defines algorithm names and parameters for use in some of the SHA-2 family<!-- [I-D.ietf-netconf-trust-anchors] IESG state: RFC Ed Queue as ofsecure hash algorithms for data integrity verification in the Secure Shell (SSH) protocol. It also updates03/21/24; companion document RFC4253 by specifying a new RECOMMENDED data integrity algorithm. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6668"/> <seriesInfo name="DOI" value="10.17487/RFC6668"/> </reference>9641--> <referenceanchor="RFC7317" target="https://www.rfc-editor.org/info/rfc7317" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7317.xml">anchor="RFC9641" target="https://www.rfc-editor.org/info/rfc9641"> <front> <title>A YANG Data Model forSystem Management</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <date month="August" year="2014"/> <abstract> <t>This document defines a YANG data model for the configuration and identification of some common system properties withinadevice containing a Network Configuration Protocol (NETCONF) server. This document also includes data node definitions for system identification, time-of-day management, user management, DNS resolver configuration, and some protocol operations for system management.</t> </abstract> </front> <seriesInfo name="RFC" value="7317"/> <seriesInfo name="DOI" value="10.17487/RFC7317"/> </reference> <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"> <front> <title>The YANG 1.1 Data Modeling Language</title>Truststore</title> <authorfullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <date month="August"year="2016"/> <abstract> <t>YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="7950"/> <seriesInfo name="DOI" value="10.17487/RFC7950"/> </reference> <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <author fullname="B. Leiba" initials="B." surname="Leiba"/> <date month="May" year="2017"/> <abstract> <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t> </abstract>year="2024"/> </front> <seriesInfoname="BCP" value="14"/> <seriesInfoname="RFC"value="8174"/>value="9641"/> <seriesInfo name="DOI"value="10.17487/RFC8174"/>value="10.17487/RFC9641"/> </reference><reference anchor="RFC8268" target="https://www.rfc-editor.org/info/rfc8268" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8268.xml"> <front> <title>More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)</title> <author fullname="M. Baushke" initials="M." surname="Baushke"/> <date month="December" year="2017"/> <abstract> <t>This document defines added Modular Exponentiation (MODP) groups for the Secure Shell (SSH) protocol using SHA-2 hashes. This document updates RFC 4250. This document updates<!-- [I-D.ietf-netconf-keystore] IESG state: RFC4253 by correcting an error regarding checking the Peer's DH Public Key.</t> </abstract> </front> <seriesInfo name="RFC" value="8268"/> <seriesInfo name="DOI" value="10.17487/RFC8268"/> </reference> <reference anchor="RFC8308" target="https://www.rfc-editor.org/info/rfc8308" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8308.xml"> <front> <title>Extension Negotiation in the Secure Shell (SSH) Protocol</title> <author fullname="D. Bider" initials="D." surname="Bider"/> <date month="March" year="2018"/> <abstract> <t>This memo updates RFCs 4251, 4252, 4253, and 4254 by defining a mechanism for Secure Shell (SSH) clients and servers to exchange information about supported protocol extensions confidentially after SSH key exchange.</t> </abstract> </front> <seriesInfo name="RFC" value="8308"/> <seriesInfo name="DOI" value="10.17487/RFC8308"/> </reference> <reference anchor="RFC8332" target="https://www.rfc-editor.org/info/rfc8332" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8332.xml"> <front> <title>Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol</title> <author fullname="D. Bider" initials="D." surname="Bider"/> <date month="March" year="2018"/> <abstract> <t>This memo updates RFCs 4252 and 4253 to define new public key algorithms for use of RSA keys with SHA-256 and SHA-512 for server and client authentication in SSH connections.</t> </abstract> </front> <seriesInfo name="RFC" value="8332"/> <seriesInfo name="DOI" value="10.17487/RFC8332"/> </reference> <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"> <front> <title>Network Configuration Access Control Model</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <date month="March" year="2018"/> <abstract> <t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subsetEd Queue as ofall available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t> <t>This document obsoletes RFC 6536.</t> </abstract> </front> <seriesInfo name="STD" value="91"/> <seriesInfo name="RFC" value="8341"/> <seriesInfo name="DOI" value="10.17487/RFC8341"/> </reference> <reference anchor="RFC8709" target="https://www.rfc-editor.org/info/rfc8709" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8709.xml"> <front> <title>Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol</title> <author fullname="B. Harris" initials="B." surname="Harris"/> <author fullname="L. Velvindron" initials="L." surname="Velvindron"/> <date month="February" year="2020"/> <abstract> <t>This03/21/24; companion documentdescribes the use of the Ed25519 and Ed448 digital signature algorithms in the Secure Shell (SSH) protocol. Accordingly, thisRFCupdates RFC 4253.</t> </abstract> </front> <seriesInfo name="RFC" value="8709"/> <seriesInfo name="DOI" value="10.17487/RFC8709"/> </reference>9642--> <referenceanchor="RFC8731" target="https://www.rfc-editor.org/info/rfc8731" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8731.xml">anchor="RFC9642" target="https://www.rfc-editor.org/info/rfc9642"> <front><title>Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448</title> <author fullname="A. Adamantiadis" initials="A." surname="Adamantiadis"/> <author fullname="S. Josefsson" initials="S." surname="Josefsson"/> <author fullname="M. Baushke" initials="M." surname="Baushke"/> <date month="February" year="2020"/> <abstract> <t>This document describes the specification<title>A YANG Data Model forusing Curve25519 and Curve448 key exchange methods in the Secure Shell (SSH) protocol.</t> </abstract> </front> <seriesInfo name="RFC" value="8731"/> <seriesInfo name="DOI" value="10.17487/RFC8731"/> </reference> <reference anchor="RFC8732" target="https://www.rfc-editor.org/info/rfc8732" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8732.xml"> <front> <title>Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2</title> <author fullname="S. Sorce" initials="S." surname="Sorce"/> <author fullname="H. Kario" initials="H." surname="Kario"/> <date month="February" year="2020"/> <abstract> <t>This document specifies additions and amendments to RFC 4462. It definesanew key exchange method that uses SHA-2 for integrityKeystore anddeprecates weak Diffie-Hellman (DH) groups. The purpose of this specification is to modernize the cryptographic primitives used by Generic Security Service (GSS) key exchanges.</t> </abstract> </front> <seriesInfo name="RFC" value="8732"/> <seriesInfo name="DOI" value="10.17487/RFC8732"/> </reference> <reference anchor="RFC8758" target="https://www.rfc-editor.org/info/rfc8758" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8758.xml"> <front> <title>Deprecating RC4 in Secure Shell (SSH)</title>Keystore Operations</title> <authorfullname="L. Velvindron" initials="L." surname="Velvindron"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <datemonth="April" year="2020"/> <abstract> <t>This document deprecates RC4 in Secure Shell (SSH). Therefore, this document formally moves RFC 4345 to Historic status.</t> </abstract>month="August" year="2024"/> </front> <seriesInfoname="BCP" value="227"/> <seriesInfoname="RFC"value="8758"/>value="9642"/> <seriesInfo name="DOI"value="10.17487/RFC8758"/>value="10.17487/RFC9642"/> </reference><xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-crypto-types.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-trust-anchors.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-keystore.xml"/></references> <references> <name>Informative References</name> <!--<reference anchor='FIPS180-4' target="http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf"> <front> <title>Secure Hash Standard (SHS)</title> <author fullname='National Institute of Standards and Technology'/> <date year='2012' month='March'/> </front> <seriesInfo name="FIPS PUB" value="180-4"/> </reference>--><reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"> <front> <title>The IETF XML Registry</title> <author fullname="M. Mealling" initials="M." surname="Mealling"/> <date month="January" year="2004"/> <abstract> <t>This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t> </abstract> </front> <seriesInfo name="BCP" value="81"/> <seriesInfo name="RFC" value="3688"/> <seriesInfo name="DOI" value="10.17487/RFC3688"/> </reference> <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"> <front> <title>Network Configuration Protocol (NETCONF)</title> <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/> <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/> <date month="June" year="2011"/> <abstract> <t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8071.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml"/> <!-- [I-D.ietf-netconf-tcp-client-server] IESG state: RFC4741. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6241"/> <seriesInfo name="DOI" value="10.17487/RFC6241"/> </reference> <reference anchor="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"> <front> <title>Using the NETCONF Protocol over Secure Shell (SSH)</title> <author fullname="M. Wasserman" initials="M." surname="Wasserman"/> <date month="June" year="2011"/> <abstract> <t>This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) sessionEd Queue asan SSH subsystem. Thisof 03/12/24; companion documentobsoletesRFC4742. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6242"/> <seriesInfo name="DOI" value="10.17487/RFC6242"/> </reference>9643--> <referenceanchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml">anchor="RFC9643" target="https://www.rfc-editor.org/info/rfc9643"> <front><title>RESTCONF Protocol</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <date month="January" year="2017"/> <abstract> <t>This document describes an HTTP-based protocol that provides a programmatic interface<title>YANG Groupings foraccessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="8040"/> <seriesInfo name="DOI" value="10.17487/RFC8040"/> </reference> <reference anchor="RFC8071" target="https://www.rfc-editor.org/info/rfc8071" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8071.xml"> <front> <title>NETCONF Call HomeTCP Clients andRESTCONF Call Home</title>TCP Servers</title> <authorfullname="K. Watsen"initials="K."surname="Watsen"/> <date month="February" year="2017"/> <abstract> <t>This RFC presents NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively.</t> </abstract> </front> <seriesInfo name="RFC" value="8071"/> <seriesInfo name="DOI" value="10.17487/RFC8071"/> </reference> <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"> <front> <title>YANG Tree Diagrams</title>surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <authorfullname="M. Bjorklund"initials="M."surname="Bjorklund"/> <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/> <date month="March" year="2018"/> <abstract> <t>This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolutionsurname="Scharf" fullname="Michael Scharf"> <organization>Hochschule Esslingen - University ofthe YANG language.</t> </abstract>Applied Sciences</organization> </author> <date month="August" year="2024"/> </front> <seriesInfoname="BCP" value="215"/> <seriesInfoname="RFC"value="8340"/>value="9643"/> <seriesInfo name="DOI"value="10.17487/RFC8340"/>value="10.17487/RFC9643"/> </reference><reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"> <front> <title>Network Management Datastore Architecture (NMDA)</title> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/> <author fullname="P. Shafer" initials="P." surname="Shafer"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <author fullname="R. Wilton" initials="R." surname="Wilton"/> <date month="March" year="2018"/> <abstract> <t>Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such<!-- [I-D.ietf-netconf-tls-client-server] IESG state: RFC Ed Queue asthe Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. Thisof 03/12/24; companion documentupdatesRFC7950.</t> </abstract> </front> <seriesInfo name="RFC" value="8342"/> <seriesInfo name="DOI" value="10.17487/RFC8342"/> </reference>9645--> <referenceanchor="RFC8407" target="https://www.rfc-editor.org/info/rfc8407" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml">anchor="RFC9645" target="https://www.rfc-editor.org/info/rfc9645"> <front><title>Guidelines<title>YANG Groupings forAuthorsTLS Clients andReviewers of Documents Containing YANG Data Models</title>TLS Servers</title> <authorfullname="A. Bierman" initials="A." surname="Bierman"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <datemonth="October" year="2018"/> <abstract> <t>This memo provides guidelines for authors and reviewers of specifications containing YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 6087.</t> </abstract>month="August" year="2024"/> </front> <seriesInfoname="BCP" value="216"/> <seriesInfoname="RFC"value="8407"/>value="9645"/> <seriesInfo name="DOI"value="10.17487/RFC8407"/>value="10.17487/RFC9645"/> </reference> <!-- [I-D.ietf-netconf-http-client-server] IESG state: IESG Evaluation::AD Followup as of 8/15/24--> <xi:includehref="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-tcp-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-ssh-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-tls-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-http-client-server.xml"/>href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-http-client-server"/> <!-- [I-D.ietf-netconf-netconf-client-server] IESG state: AD Evaluation as of 8/15/24--> <xi:includehref="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-netconf-client-server.xml"/>href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-netconf-client-server"/> <!-- [I-D.ietf-netconf-restconf-client-server] IESG state: AD Evaluation as of 8/15/24--> <xi:includehref="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-restconf-client-server.xml"/>href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-restconf-client-server"/> <!-- [I-D.ietf-netmod-system-config] IESG state: I-D Exists as of 03/12/24--> <xi:includehref="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netmod-system-config.xml"/>href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netmod-system-config.xml"/> <!-- [I-D.ietf-netmod-rfc8407bis] IESG state: I-D Exists as of 03/12/24--> <xi:includehref="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netmod-rfc8407bis.xml"/>href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netmod-rfc8407bis.xml"/> <referenceanchor="FIPS_186-6" target="https://csrc.nist.gov/publications/detail/fips/186/5/draft">anchor="FIPS_186-5" target="https://csrc.nist.gov/pubs/fips/186-5/final"> <front> <title>Digital Signature Standard (DSS)</title><author fullname="The National Institute for Science and Technology (NIST)"/><author> <organization>NIST</organization> </author> <date month="February" year="2023"/> </front> <seriesInfo name="FIPS PUB" value="186-5"/> <seriesInfo name="DOI" value="10.6028/NIST.FIPS.186-5"/> </reference> <!-- <reference anchor="OPENSSH" target="http://www.openssh.com"> <front> <title>OpenSSH</title> <author fullname="The OpenBSD Project"/> </front> </reference> --> <reference anchor="IANA-KEYEX-ALGS"target="https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-16">target="https://www.iana.org/assignments/ssh-parameters"> <front><title>IANA "Key<title>Key Exchange MethodNames" Sub-registry of the "Secure Shell (SSH) Protocol Parameters" Registry</title> <author fullname="Internet Assigned Numbers Authority (IANA)"/>Names</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA-ENC-ALGS"target="https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-17">target="https://www.iana.org/assignments/ssh-parameters/"> <front><title>IANA "Encryption<title>Encryption AlgorithmNames" Sub-registry of the "Secure Shell (SSH) Protocol Parameters" Registry</title> <author fullname="Internet Assigned Numbers Authority (IANA)"/>Names</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA-MAC-ALGS"target="https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-18">target="https://www.iana.org/assignments/ssh-parameters"> <front><title>IANA "MAC<title>MAC AlgorithmNames" Sub-registry of the "Secure Shell (SSH) Protocol Parameters" Registry</title> <author fullname="Internet Assigned Numbers Authority (IANA)"/>Names</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA-PUBKEY-ALGS"target="https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-19">target="https://www.iana.org/assignments/ssh-parameters/"> <front><title>IANA "Public<title>Public Key AlgorithmNames" Sub-registry of the "Secure Shell (SSH) Protocol Parameters" Registry</title> <author fullname="Internet Assigned Numbers Authority (IANA)"/>Names</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA-YANG-PARAMETERS" target="https://www.iana.org/assignments/yang-parameters"> <front> <title>YANG Parameters</title> <author><organization/><organization>IANA</organization> </author><date>n.d.</date></front> </reference> </references> </references> <section anchor="iana-script"> <name>Script to Generate IANA-Maintained YANG Modules</name> <t>This section is notNormative.</t>normative.</t> <t>The Python <ereftarget="https://www.python.org"/>target="https://www.python.org" brackets="angle"/> script contained in this section will create the four IANA-maintained modules that are described (but not contained) in this document.</t> <t>Run the script using the command`python gen-yang-modules.py`,"python gen-yang-modules.py" to produce four YANG module files in the current directory.</t> <t>Be aware that the script does not attempt to copy the "revision" statements from the previous/current YANG module. Copying the revision statements must be done manually.</t> <sourcecode type="python" markers="true"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ import re import csv import textwrap import requests import requests_cache from io import StringIO from datetime import datetime # Metadata for the four YANG modules produced by this script MODULES = [ { "csv_url": "https://www.iana.org/assignments/ssh-parameters/\ ssh-parameters-17.csv", "spaced_name": "encryption", "hypenated_name": "encryption", "prefix": "sshea", "description": """ "This module defines enumerations for \ the encryption algorithms defined in the 'Encryption Algorithm Names'sub-registryregistry of the 'Secure Shell (SSH) Protocol Parameters' registry group maintained by IANA.""", }, { "csv_url": "https://www.iana.org/assignments/ssh-parameters/\ ssh-parameters-19.csv", "spaced_name": "public key", "hypenated_name": "public-key", "prefix": "sshpka", "description": """ "This module defines enumerations for \ the public key algorithms defined in the 'Public Key Algorithm Names'sub-registryregistry of the 'Secure Shell (SSH) Protocol Parameters' registry group maintained by IANA.""" }, { "csv_url": "https://www.iana.org/assignments/ssh-parameters/\ ssh-parameters-18.csv", "spaced_name": "mac", "hypenated_name": "mac", "prefix": "sshma", "description": """ "This module defines enumerations for \ the MAC algorithms defined in the 'MAC Algorithm Names'sub-registryregistry of the 'Secure Shell (SSH) Protocol Parameters' registry group maintained by IANA.""" }, { "csv_url": "https://www.iana.org/assignments/ssh-parameters/\ ssh-parameters-16.csv", "spaced_name": "key exchange", "hypenated_name": "key-exchange", "prefix": "sshkea", "description": """ "This module defines enumerations for \ the key exchange algorithms defined in the 'Key Exchange Method Names'sub-registryregistry of the 'Secure Shell (SSH) Protocol Parameters' registry group maintained by IANA.""" }, ] def create_module_begin(module, f): # Define template for all four modules PREAMBLE_TEMPLATE=""" module iana-ssh-HNAME-algs { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:iana-ssh-HNAME-algs"; prefix PREFIX; organization "Internet Assigned Numbers Authority (IANA)"; contact "Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 Email: iana@iana.org"; description DESCRIPTION Copyright (c) YEAR IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). The initial version of this YANG module is part of RFCEEEE (https://www.rfc-editor.org/info/rfcEEEE);9644 (https://www.rfc-editor.org/info/rfc9644); see the RFC itself for full legal notices. All versions of this module are published by IANA at https://www.iana.org/assignments/yang-parameters."; revision DATE { description "This initial version of the module was created using the script defined in RFCEEEE9644 to reflect the contents of the SNAME algorithms registry maintained by IANA."; reference "RFCEEEE:9644: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-HNAME-algorithm { type enumeration { """ # Replacements rep = { "DATE": datetime.today().strftime('%Y-%m-%d'), "YEAR": datetime.today().strftime('%Y'), "SNAME": module["spaced_name"], "HNAME": module["hypenated_name"], "PREFIX": module["prefix"], "DESCRIPTION": module["description"] } # Do the replacement rep = dict((re.escape(k), v) for k, v in rep.items()) pattern = re.compile("|".join(rep.keys())) text = pattern.sub(lambda m: rep[re.escape(m.group(0))], PREAMBL\ E_TEMPLATE) # Write preamble into the file f.write(text) def create_module_body(module, f): # Fetch the current CSV file from IANA r = requests.get(module["csv_url"]) assert(r.status_code == 200) # Ascertain the first CSV column's name with StringIO(r.text) as csv_file: csv_reader = csv.reader(csv_file) for row in csv_reader: first_colname = row[0] break # Parse each CSV line with StringIO(r.text) as csv_file: csv_reader = csv.DictReader(csv_file) for row in csv_reader: # Extract just the ref refs = row["Reference"][1:-1] # remove the '[' and ']' \ chars refs = refs.split("][") # There may be more than one ref titles = [] for ref in refs: # Ascertain the ref's title if ref.startswith("RFC"): # Fetch the current BIBTEX entry bibtex_url="https://datatracker.ietf.org/doc/"+ \ ref.lower() + "/bibtex/" r = requests.get(bibtex_url) assert r.status_code == 200, "Could not GET " + \ bibtex_url # Append to 'titles' value from the "title" line for item in r.text.split("\n"): if "title =" in item: titles.append(re.sub('.*{{(.*)}}.*', r'\\ g<1>', item)) break else: raise Exception("RFC title not found") # Insert a space: "RFCXXXX" --> "RFC XXXX" index = refs.index(ref) refs[index] = "RFC " + ref[3:] elif ref.startswith("FIPS"): # Special case for FIPS, since no bibtex to fetch if ref == "FIPS 46-3" or ref == "FIPS-46-3": titles.append("Data Encryption Standard (DES\ )") else: raise Exception("FIPS ref not found") else: raise Exception("ref not found") # Function used below def write_enumeration(alg): f.write('\n') f.write(f' enum {alg} {{\n') if "HISTORIC" in row["Note"]: f.write(f' status obsolete;\n') elif "OK to Implement" in row: if "MUST NOT" in row["OK to Implement"]: f.write(f' status obsolete;\n') elif "SHOULD NOT" in row["OK to Implement"]: f.write(f' status deprecated;\n') f.write(f' description\n') description = f' "Enumeration for the \'{al\ g}\' algorithm.' if "Section" in row["Note"]: description += " " + row["Note"] description += '";' description = textwrap.fill(description, width=69, s\ ubsequent_indent=" ") f.write(f'{description}\n') f.write(' reference\n') f.write(' "') if row["Reference"] == "": f.write(' Missing in IANA registry.') else: ref_len = len(refs) for i in range(ref_len): ref = refs[i] f.write(f'{ref}:\n') title = " " + titles[i] if i == ref_len - 1: title += '";' title = textwrap.fill(title, width=67, subse\ quent_indent=" ") f.write(f'{title}') if i != ref_len - 1: f.write('\n ') f.write('\n') f.write(' }\n') # Write one or more "enumeration" statements if not row[first_colname].endswith("-*"): # just one enu\ meration # Avoid duplicate entries caused by the "ecdh-sha2-*\ " family expansion if not row[first_colname].startswith("ecdh-sha2-nist\ p"): write_enumeration(row[first_colname]) else: # a family of enumerations curve_ids = [ "nistp256", "nistp384", "nistp521", "1.3.132.0.1", "1.2.840.10045.3.1.1", "1.3.132.0.33", "1.3.132.0.26", "1.3.132.0.27", "1.3.132.0.16", "1.3.132.0.36", "1.3.132.0.37", "1.3.132.0.38", ] for curve_id in curve_ids: write_enumeration(row[first_colname][:-1] + curv\ e_id) def create_module_end(module, f): # Close out the enumeration, typedef, and module f.write(" }\n") f.write(" description\n") f.write(f' "An enumeration for SSH {module["spaced_name"]} \ algorithms.";\n') f.write(" }\n") f.write('\n') f.write('}\n') def create_module(module): # Install cache for 8x speedup requests_cache.install_cache() #ascertain yangAscertain YANG module's name yang_module_name = "iana-ssh-" + module["hypenated_name"] + "-al\ gs.yang" #create yangCreate YANG module file with open(yang_module_name, "w") as f: create_module_begin(module, f) create_module_body(module, f) create_module_end(module, f) def main(): for module in MODULES: create_module(module) if __name__ == "__main__": main() ]]></sourcecode> </section> <sectionanchor="ssh-enc-algs-model"> <name>Initial Module for the "Encryption Algorithm Names" Registry</name> <t>Following are the complete contentsnumbered="false"> <name>Acknowledgements</name> <t>The authors would like to thank theinitial IANA-maintained YANG module. Please note that the date "2024-03-16" reflects the dayfollowing for lively discussions onwhich the extraction occurred. Applications SHOULD use the IANA-maintained module, not the module defined in this draft.</t> <t>This YANG module has normative references to [FIPS 46-3], <xref target="RFC4253"/>, <xref target="RFC4344"/>, <xref target="RFC5647"/>,list and<xref target="RFC8758"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "iana-ssh-encryption-algs@2024-03-16.yang"</t> <artwork><![CDATA[ module iana-ssh-encryption-algs { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs"; prefix sshea; organization "Internet Assigned Numbers Authority (IANA)"; contact "Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 Email: iana@iana.org"; description "This module defines enumerations for the encryption algorithms definedin the'Encryption Algorithm Names' sub-registry of the 'Secure Shell (SSH) Protocol Parameters' registry maintainedhalls (ordered byIANA. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relatingfirst name): <contact fullname="Alan Luchuk"/>, <contact fullname="Andy Bierman"/>, <contact fullname="Balázs Kovács"/>, <contact fullname="Barry Leiba"/>, <contact fullname="Benoit Claise"/>, <contact fullname="Bert Wijnen"/>, <contact fullname="David Lamparter"/>, <contact fullname="Elwyn Davies"/>, <contact fullname="Gary Wu"/>, <contact fullname="Jürgen Schönwälder"/>, <contact fullname="Ladislav Lhotka"/>, <contact fullname="Liang Xia"/>, <contact fullname="Martin Björklund"/>, <contact fullname="Martin Thomson"/>, <contact fullname="Mehmet Ersue"/>, <contact fullname="Michal Vaško"/>, <contact fullname="Murray Kucherawy"/>, <contact fullname="Paul Wouters"/>, <contact fullname="Per Andersson"/>, <contact fullname="Phil Shafer"/>, <contact fullname="Qin Wun"/>, <contact fullname="Radek Krejci"/>, <contact fullname="Rob Wilton"/>, <contact fullname="Roman Danyliw"/>, <contact fullname="Russ Housley"/>, <contact fullname="Sean Turner"/>, <contact fullname="Thomas Martin"/>, <contact fullname="Tom Petch"/>, and <contact fullname="Warren Kumari"/>.</t> </section> <section numbered="false"> <name>Contributors</name> <t>Special acknowledgement goes toIETF Documents (https://trustee.ietf.org/license-info). The initial version of this YANG module is part of RFC EEEE (https://www.rfc-editor.org/info/rfcEEEE); see the RFC itself<contact fullname="Gary Wu"/> forfull legal notices. All versions of this module are published by IANA at https://www.iana.org/assignments/yang-parameters."; revision 2024-03-16 { description "This initial version of the module was created using the script defined in RFC EEEE to reflect the contents ofhis work on theencryption algorithms registry maintained"ietf-ssh-common" module.</t> </section> <!--[rfced] *ADs - We have removed Appendices A.1 - A.4 per an Editorial Note left byIANA."; reference "RFC EEEE: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-encryption-algorithm { type enumeration { enum 3des-cbc { description "Enumeration for the '3des-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum blowfish-cbc { description "Enumeration for the 'blowfish-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum twofish256-cbc { description "Enumeration for the 'twofish256-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum twofish-cbc { description "Enumeration for the 'twofish-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum twofish192-cbc { description "Enumeration for the 'twofish192-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum twofish128-cbc { description "Enumeration for the 'twofish128-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum aes256-cbc { description "Enumeration for the 'aes256-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum aes192-cbc { description "Enumeration for the 'aes192-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum aes128-cbc { description "Enumeration for the 'aes128-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum serpent256-cbc { description "Enumeration for the 'serpent256-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum serpent192-cbc { description "Enumeration for the 'serpent192-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum serpent128-cbc { description "Enumeration for the 'serpent128-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum arcfour { status obsolete; description "Enumeration for the 'arcfour' algorithm."; reference "RFC 8758: Deprecating RC4 in Secure Shell (SSH)"; } enum idea-cbc { description "Enumeration for the 'idea-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum cast128-cbc { description "Enumeration for the 'cast128-cbc' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum none { description "Enumeration for the 'none' algorithm. Section 6.3"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum des-cbc { status obsolete; description "Enumeration for the 'des-cbc' algorithm."; reference "FIPS-46-3: Data Encryption Standard (DES)"; } enum arcfour128 { status obsolete; description "Enumeration for the 'arcfour128' algorithm."; reference "RFC 8758: Deprecating RC4 in Secure Shell (SSH)"; } enum arcfour256 { status obsolete; description "Enumeration forthe'arcfour256' algorithm."; reference "RFC 8758: Deprecating RC4author inSecure Shell (SSH)"; } enum aes128-ctr { description "Enumeration for the 'aes128-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum aes192-ctr { description "Enumeration for the 'aes192-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum aes256-ctr { description "Enumeration for the 'aes256-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum 3des-ctr { description "Enumeration for the '3des-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum blowfish-ctr { description "Enumeration for the 'blowfish-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum twofish128-ctr { description "Enumeration for the 'twofish128-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum twofish192-ctr { description "Enumeration for the 'twofish192-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum twofish256-ctr { description "Enumeration for the 'twofish256-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum serpent128-ctr { description "Enumeration for the 'serpent128-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum serpent192-ctr { description "Enumeration forthe'serpent192-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum serpent256-ctr { description "Enumeration for the 'serpent256-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum idea-ctr { description "Enumeration for the 'idea-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum cast128-ctr { description "Enumeration for the 'cast128-ctr' algorithm."; reference "RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes"; } enum AEAD_AES_128_GCM { description "Enumeration for the 'AEAD_AES_128_GCM' algorithm. Section 6.1"; reference "RFC 5647: AES Galois Counter Mode for the Secure Shell Transport Layer Protocol"; } enum AEAD_AES_256_GCM { description "Enumeration for the 'AEAD_AES_256_GCM' algorithm. Section 6.2"; reference "RFC 5647: AES Galois Counter Mode for the Secure Shell Transport Layer Protocol"; } } description "An enumeration for SSH encryption algorithms."; } } ]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t> </section> <section anchor="ssh-mac-algs-model"> <name>Initial Module forXML file. Please review the"MAC Algorithm Names" Registry</name> <t>Following arediff file below and approve of thecomplete contents toremoval. Also, please see theinitial IANA-maintained YANG module. Please note that the date "2024-03-16" reflects the day on which the extraction occurred. Applications SHOULD use the IANA-maintained module, not the module defined in this draft.</t> <t>This YANG module has normative references <xref target="RFC4253"/>, <xref target="RFC5647"/>, and <xref target="RFC6668"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "iana-ssh-mac-algs@2024-03-16.yang"</t> <artwork><![CDATA[ module iana-ssh-mac-algs { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs"; prefix sshma; organization "Internet Assigned Numbers Authority (IANA)"; contact "Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 Email: iana@iana.org"; description "This module defines enumerations for the MAC algorithms defined in the 'MAC Algorithm Names' sub-registry of the 'Secure Shell (SSH) Protocol Parameters' registry maintained by IANA. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). The initial version of this YANG module is part of RFC EEEE (https://www.rfc-editor.org/info/rfcEEEE); see the RFC itself for full legal notices. All versions of this module are published by IANA at https://www.iana.org/assignments/yang-parameters."; revision 2024-03-16 { description "This initial version of the module was created using the script defined in RFC EEEE to reflect the contents of the mac algorithms registry maintained by IANA."; reference "RFC EEEE: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-mac-algorithm { type enumeration { enum hmac-sha1 { description "Enumeration for the 'hmac-sha1' algorithm. Section 6.4"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum hmac-sha1-96 { description "Enumeration for the 'hmac-sha1-96' algorithm. Section 6.4"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum hmac-md5 { description "Enumeration for the 'hmac-md5' algorithm. Section 6.4"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum hmac-md5-96 { description "Enumeration for the 'hmac-md5-96' algorithm. Section 6.4"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum none { description "Enumeration for the 'none' algorithm. Section 6.4"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum AEAD_AES_128_GCM { description "Enumeration for the 'AEAD_AES_128_GCM' algorithm. Section 6.1"; reference "RFC 5647: AES Galois Counter Mode for the Secure Shell Transport Layer Protocol"; } enum AEAD_AES_256_GCM { description "Enumeration for the 'AEAD_AES_256_GCM' algorithm. Section 6.2"; reference "RFC 5647: AES Galois Counter Mode for the Secure Shell Transport Layer Protocol"; } enum hmac-sha2-256 { description "Enumeration for the 'hmac-sha2-256' algorithm. Section 2"; reference "RFC 6668: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol"; } enum hmac-sha2-512 { description "Enumeration for the 'hmac-sha2-512' algorithm. Section 2"; reference "RFC 6668: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol"; } } description "An enumeration for SSH mac algorithms."; } } ]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t> </section> <section anchor="ssh-pubkey-algs-model"> <name>Initial Module for the "Public Key Algorithm Names" Registry</name> <t>Following are the complete contents to the initial IANA-maintained YANG module. Please note that the date "2024-03-16" reflects the day on which the extraction occurred. Applications SHOULD use the IANA-maintained module, not the module defined in this draft.</t> <t>This YANG module has normative references <xref target="RFC4253"/>, <xref target="RFC4462"/>, <xref target="RFC5656"/>, <xref target="RFC6187"/>, <xref target="RFC8332"/>, and <xref target="RFC8709"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "iana-ssh-public-key-algs@2024-03-16.yang"</t> <artwork><![CDATA[ module iana-ssh-public-key-algs { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs"; prefix sshpka; organization "Internet Assigned Numbers Authority (IANA)"; contact "Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 Email: iana@iana.org"; description "This module defines enumerations for the public key algorithms defined in the 'Public Key Algorithm Names' sub-registry of the 'Secure Shell (SSH) Protocol Parameters' registry maintained by IANA. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). The initial version of this YANG module is part of RFC EEEE (https://www.rfc-editor.org/info/rfcEEEE); see the RFC itself for full legal notices. All versions of this module are published by IANA at https://www.iana.org/assignments/yang-parameters."; revision 2024-03-16 { description "This initial version of the module was created using the script defined in RFC EEEE to reflect the contents of the public key algorithms registry maintained by IANA."; reference "RFC EEEE: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-public-key-algorithm { type enumeration { enum ssh-dss { description "Enumeration for the 'ssh-dss' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum ssh-rsa { description "Enumeration for the 'ssh-rsa' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum rsa-sha2-256 { description "Enumeration for the 'rsa-sha2-256' algorithm. Section 3"; reference "RFC 8332: Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol"; } enum rsa-sha2-512 { description "Enumeration for the 'rsa-sha2-512' algorithm. Section 3"; reference "RFC 8332: Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol"; } enum spki-sign-rsa { description "Enumeration for the 'spki-sign-rsa' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum spki-sign-dss { description "Enumeration for the 'spki-sign-dss' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum pgp-sign-rsa { description "Enumeration for the 'pgp-sign-rsa' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum pgp-sign-dss { description "Enumeration for the 'pgp-sign-dss' algorithm. Section 6.6"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum null { description "Enumeration for the 'null' algorithm. Section 5"; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol"; } enum ecdsa-sha2-nistp256 { description "Enumeration for the 'ecdsa-sha2-nistp256' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-nistp384 { description "Enumeration for the 'ecdsa-sha2-nistp384' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-nistp521 { description "Enumeration for the 'ecdsa-sha2-nistp521' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.1 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.1' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.2.840.10045.3.1.1 { description "Enumeration for the 'ecdsa-sha2-1.2.840.10045.3.1.1' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.33 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.33' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.26 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.26' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.27 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.27' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.16 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.16' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.36 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.36' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.37 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.37' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdsa-sha2-1.3.132.0.38 { description "Enumeration for the 'ecdsa-sha2-1.3.132.0.38' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum x509v3-ssh-dss { description "Enumeration for the 'x509v3-ssh-dss' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ssh-rsa { description "Enumeration for the 'x509v3-ssh-rsa' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-rsa2048-sha256 { description "Enumeration for the 'x509v3-rsa2048-sha256' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-nistp256 { description "Enumeration for the 'x509v3-ecdsa-sha2-nistp256' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-nistp384 { description "Enumeration for the 'x509v3-ecdsa-sha2-nistp384' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-nistp521 { description "Enumeration for the 'x509v3-ecdsa-sha2-nistp521' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.1 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.1' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.2.840.10045.3.1.1 { description "Enumeration for the 'x509v3-ecdsa- sha2-1.2.840.10045.3.1.1' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.33 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.33' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.26 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.26' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.27 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.27' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.16 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.16' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.36 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.36' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.37 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.37' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum x509v3-ecdsa-sha2-1.3.132.0.38 { description "Enumeration for the 'x509v3-ecdsa-sha2-1.3.132.0.38' algorithm."; reference "RFC 6187: X.509v3 Certificates for Secure Shell Authentication"; } enum ssh-ed25519 { description "Enumeration for the 'ssh-ed25519' algorithm."; reference "RFC 8709: Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol"; } enum ssh-ed448 { description "Enumeration for the 'ssh-ed448' algorithm."; reference "RFC 8709: Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol"; } } description "An enumeration for SSH public key algorithms."; } } ]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t> </section> <section anchor="ssh-keyex-algs-model"> <name>Initial Module for the "Key Exchange Method Names" Registry</name> <t>Following are the complete contents to the initial IANA-maintained YANG module. Please note that the date "2024-03-16" reflects the day on which the extraction occurred. Applications SHOULD use the IANA-maintained module, not the module defined in this draft.</t> <t>This YANG module has normative references to <xref target="RFC4419"/>, <xref target="RFC4432"/>, <xref target="RFC5656"/>, <xref target="RFC8268"/>, <xref target="RFC8308"/>, <xref target="RFC8731"/>, <xref target="RFC8732"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "iana-ssh-key-exchange-algs@2024-03-16.yang"</t> <artwork><![CDATA[ module iana-ssh-key-exchange-algs { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs"; prefix sshkea; organization "Internet Assigned Numbers Authority (IANA)"; contact "Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 Email: iana@iana.org"; description "This module defines enumerations for the key exchange algorithms defined in the 'Key Exchange Method Names' sub-registry of the 'Secure Shell (SSH) Protocol Parameters' registry maintained by IANA. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). The initial version of this YANG module is part of RFC EEEE (https://www.rfc-editor.org/info/rfcEEEE); see the RFC itself for full legal notices. All versions ofquestion above about whether thismodule are published by IANA at https://www.iana.org/assignments/yang-parameters."; revision 2024-03-16 { description "This initial version of the module was created using the script defined in RFC EEEE to reflect the contents of the key exchange algorithms registry maintained by IANA."; reference "RFC EEEE: YANG Groupings for SSH Clients and SSH Servers"; } typedef ssh-key-exchange-algorithm { type enumeration { enum diffie-hellman-group-exchange-sha1 { status deprecated; description "Enumeration for the 'diffie-hellman-group-exchange-sha1' algorithm. Section 4.1"; reference "RFC 4419: Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol RFC 8270: Increase the Secure Shell Minimum Recommended Diffie- Hellman Modulus Size to 2048 Bits"; } enum diffie-hellman-group-exchange-sha256 { description "Enumeration for the 'diffie-hellman-group-exchange-sha256' algorithm. Section 4.2"; reference "RFC 4419: Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol RFC 8270: Increase the Secure Shell Minimum Recommended Diffie- Hellman Modulus Size to 2048 Bits"; } enum diffie-hellman-group1-sha1 { status deprecated; description "Enumeration for the 'diffie-hellman-group1-sha1' algorithm. Section 8.1"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum diffie-hellman-group14-sha1 { description "Enumeration for the 'diffie-hellman-group14-sha1' algorithm. Section 8.2"; reference "RFC 4253: The Secure Shell (SSH) Transport Layer Protocol"; } enum diffie-hellman-group14-sha256 { description "Enumeration for the 'diffie-hellman-group14-sha256' algorithm."; reference "RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)"; } enum diffie-hellman-group15-sha512 { description "Enumeration for the 'diffie-hellman-group15-sha512' algorithm."; reference "RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)"; } enum diffie-hellman-group16-sha512 { description "Enumeration for the 'diffie-hellman-group16-sha512' algorithm."; reference "RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)"; } enum diffie-hellman-group17-sha512 { description "Enumeration for the 'diffie-hellman-group17-sha512' algorithm."; reference "RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)"; } enum diffie-hellman-group18-sha512 { description "Enumeration for the 'diffie-hellman-group18-sha512' algorithm."; reference "RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)"; } enum ecdh-sha2-nistp256 { description "Enumeration for the 'ecdh-sha2-nistp256' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-nistp384 { description "Enumeration for the 'ecdh-sha2-nistp384' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-nistp521 { description "Enumeration for the 'ecdh-sha2-nistp521' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.1 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.1' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.2.840.10045.3.1.1 { description "Enumeration for the 'ecdh-sha2-1.2.840.10045.3.1.1' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.33 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.33' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.26 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.26' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.27 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.27' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.16 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.16' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.36 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.36' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.37 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.37' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecdh-sha2-1.3.132.0.38 { description "Enumeration for the 'ecdh-sha2-1.3.132.0.38' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum ecmqv-sha2 { description "Enumeration for the 'ecmqv-sha2' algorithm."; reference "RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"; } enum gss-group1-sha1-nistp256 { status deprecated; description "Enumeration for the 'gss-group1-sha1-nistp256' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-nistp384 { status deprecated; description "Enumeration for the 'gss-group1-sha1-nistp384' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-nistp521 { status deprecated; description "Enumeration for the 'gss-group1-sha1-nistp521' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.1 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.2.840.10045.3.1.1 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.2.840.10045.3.1.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.33 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.33' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.26 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.26' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.27 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.27' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.16 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.16' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.36 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.36' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.37 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.37' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group1-sha1-1.3.132.0.38 { status deprecated; description "Enumeration for the 'gss-group1-sha1-1.3.132.0.38' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-nistp256 { status deprecated; description "Enumeration for the 'gss-group14-sha1-nistp256' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-nistp384 { status deprecated; description "Enumeration for the 'gss-group14-sha1-nistp384' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-nistp521 { status deprecated; description "Enumeration for the 'gss-group14-sha1-nistp521' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.1 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.2.840.10045.3.1.1 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.2.840.10045.3.1.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.33 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.33' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.26 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.26' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.27 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.27' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.16 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.16' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.36 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.36' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.37 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.37' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha1-1.3.132.0.38 { status deprecated; description "Enumeration for the 'gss-group14-sha1-1.3.132.0.38' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-nistp256 { status deprecated; description "Enumeration for the 'gss-gex-sha1-nistp256' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-nistp384 { status deprecated; description "Enumeration for the 'gss-gex-sha1-nistp384' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-nistp521 { status deprecated; description "Enumeration for the 'gss-gex-sha1-nistp521' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.1 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.2.840.10045.3.1.1 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.2.840.10045.3.1.1' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.33 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.33' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.26 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.26' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.27 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.27' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.16 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.16' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.36 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.36' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.37 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.37' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-gex-sha1-1.3.132.0.38 { status deprecated; description "Enumeration for the 'gss-gex-sha1-1.3.132.0.38' algorithm."; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss- { description "Enumeration for the 'gss-' algorithm. Section 2.6"; reference "RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol"; } enum rsa1024-sha1 { status obsolete; description "Enumeration for the 'rsa1024-sha1' algorithm."; reference "RFC 4432: RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol"; } enum rsa2048-sha256 { description "Enumeration for the 'rsa2048-sha256' algorithm."; reference "RFC 4432: RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol"; } enum ext-info-s { description "Enumeration for the 'ext-info-s' algorithm. Section 2"; reference "RFC 8308: Extension Negotiation in the Secure Shell (SSH) Protocol"; } enum ext-info-c { description "Enumeration for the 'ext-info-c' algorithm. Section 2"; reference "RFC 8308: Extension Negotiation in the Secure Shell (SSH) Protocol"; } enum gss-group14-sha256-nistp256 { description "Enumeration for the 'gss-group14-sha256-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-nistp384 { description "Enumeration for the 'gss-group14-sha256-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-nistp521 { description "Enumeration for the 'gss-group14-sha256-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.1 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- group14-sha256-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.33 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.26 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.27 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.16 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.36 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.37 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group14-sha256-1.3.132.0.38 { description "Enumeration for the 'gss-group14-sha256-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-nistp256 { description "Enumeration for the 'gss-group15-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-nistp384 { description "Enumeration for the 'gss-group15-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-nistp521 { description "Enumeration for the 'gss-group15-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- group15-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group15-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-group15-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-nistp256 { description "Enumeration for the 'gss-group16-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-nistp384 { description "Enumeration for the 'gss-group16-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-nistp521 { description "Enumeration for the 'gss-group16-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- group16-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group16-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-group16-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-nistp256 { description "Enumeration for the 'gss-group17-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-nistp384 { description "Enumeration for the 'gss-group17-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-nistp521 { description "Enumeration for the 'gss-group17-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- group17-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group17-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-group17-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-nistp256 { description "Enumeration for the 'gss-group18-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-nistp384 { description "Enumeration for the 'gss-group18-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-nistp521 { description "Enumeration for the 'gss-group18-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- group18-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-group18-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-group18-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-nistp256 { description "Enumeration for the 'gss-nistp256-sha256-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-nistp384 { description "Enumeration for the 'gss-nistp256-sha256-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-nistp521 { description "Enumeration for the 'gss-nistp256-sha256-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.1 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- nistp256-sha256-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.33 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.26 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.27 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.16 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.36 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.37 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp256-sha256-1.3.132.0.38 { description "Enumeration for the 'gss-nistp256-sha256-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-nistp256 { description "Enumeration for the 'gss-nistp384-sha384-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-nistp384 { description "Enumeration for the 'gss-nistp384-sha384-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-nistp521 { description "Enumeration for the 'gss-nistp384-sha384-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.1 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- nistp384-sha384-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.33 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.26 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.27 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.16 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.36 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.37 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp384-sha384-1.3.132.0.38 { description "Enumeration for the 'gss-nistp384-sha384-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-nistp256 { description "Enumeration for the 'gss-nistp521-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-nistp384 { description "Enumeration for the 'gss-nistp521-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-nistp521 { description "Enumeration for the 'gss-nistp521-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- nistp521-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-nistp521-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-nistp521-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-nistp256 { description "Enumeration for the 'gss-curve25519-sha256-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-nistp384 { description "Enumeration for the 'gss-curve25519-sha256-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-nistp521 { description "Enumeration for the 'gss-curve25519-sha256-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.1 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- curve25519-sha256-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.33 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.26 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.27 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.16 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.36 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.37 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve25519-sha256-1.3.132.0.38 { description "Enumeration for the 'gss-curve25519-sha256-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-nistp256 { description "Enumeration for the 'gss-curve448-sha512-nistp256' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-nistp384 { description "Enumeration for the 'gss-curve448-sha512-nistp384' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-nistp521 { description "Enumeration for the 'gss-curve448-sha512-nistp521' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.1 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.2.840.10045.3.1.1 { description "Enumeration for the 'gss- curve448-sha512-1.2.840.10045.3.1.1' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.33 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.33' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.26 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.26' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.27 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.27' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.16 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.16' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.36 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.36' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.37 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.37' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum gss-curve448-sha512-1.3.132.0.38 { description "Enumeration for the 'gss-curve448-sha512-1.3.132.0.38' algorithm."; reference "RFC 8732: Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2"; } enum curve25519-sha256 { description "Enumeration for the 'curve25519-sha256' algorithm."; reference "RFC 8731: Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448"; } enum curve448-sha512 { description "Enumeration for the 'curve448-sha512' algorithm."; reference "RFC 8731: Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448"; } } description "An enumeration for SSH key exchange algorithms."; } } ]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t> </section> </section> <section anchor="change-log"> <name>Change Log</name> <section> <name>00 to 01</name> <ul spacing="normal"> <li>Noted that '0.0.0.0' and '::' might have special meanings.</li> <li>Renamed "keychain" to "keystore".</li> </ul> </section> <section> <name>01 to 02</name> <ul spacing="normal"> <li>Removed the groupings 'listening-ssh-client-grouping' and 'listening-ssh-server-grouping'. Now modules only contain the transport-independent groupings.</li> <li>Simplified the "client-auth" part in the ietf-ssh-client module. It now inlines what it used to point to keystore for.</li> <li>Added cipher suites for various algorithms into new 'ietf-ssh-common' module.</li> </ul> </section> <section> <name>02 to 03</name> <ul spacing="normal"> <li>Removed 'RESTRICTED' enum from 'password' leaf type.</li> <li>Added a 'must' statement to container 'server-auth' asserting that at least one of the various auth mechanisms must be specified.</li> <li>Fixed description statement for leaf 'trusted-ca-certs'.</li> </ul> </section> <section> <name>03 to 04</name> <ul spacing="normal"> <li>Change title to "YANG Groupings for SSH Clients and SSH Servers"</li> <li>Added reference to RFC 6668</li> <li>Added RFC 8174 to Requirements Language Section.</li> <li>Enhanced description statement for ietf-ssh-server's "trusted-ca-certs" leaf.</li> <li>Added mandatory true to ietf-ssh-client's "client-auth" 'choice' statement.</li> <li>Changed the YANG prefix for module ietf-ssh-common from 'sshcom' to 'sshcmn'.</li> <li>Removed the compression algorithms as they are not commonly configurable in vendors' implementations.</li> <li>Updating descriptions in transport-params-grouping and the servers's usage of it.</li> <li>Now tree diagrams reference ietf-netmod-yang-tree-diagrams</li> <li>Updated YANG to use typedefs around leafrefs to common keystore paths</li> <li>Now inlines key and certificates (no longer a leafref to keystore)</li> </ul> </section> <section> <name>04 to 05</name> <ul spacing="normal"> <li>Merged changes from co-author.</li> </ul> </section> <section> <name>05 to 06</name> <ul spacing="normal"> <li>Updated to use trust anchors from trust-anchors draft (was keystore draft)</li> <li>Now uses new keystore grouping enabling asymmetric key to be either locally defined or a reference to the keystore.</li> </ul> </section> <section> <name>06 to 07</name> <ul spacing="normal"> <li>factored the ssh-[client|server]-groupings into more reusable groupings.</li> <li>added if-feature statements for the new "ssh-host-keys" and "x509-certificates" features defined in draft-ietf-netconf-trust-anchors.</li> </ul> </section> <section> <name>07 to 08</name> <ul spacing="normal"> <li>Added a number of compatibility matrices to Section 5 (thanks Frank!)</li> <li>Clarified that any configured "host-key-alg" values need to be compatible with the configured private key.</li> </ul> </section> <section> <name>08 to 09</name> <ul spacing="normal"> <li>Updated examples to reflect update to groupings defined in the keystore -09 draft.</li> <li>Add SSH keepalives features and groupings.</li> <li>Prefixed top-level SSH grouping nodes with 'ssh-' and support mashups.</li> <li>Updated copyright date, boilerplate template, affiliation, and folding algorithm.</li> </ul> </section> <section> <name>09 to 10</name> <ul spacing="normal"> <li>Reformatted the YANG modules.</li> </ul> </section> <section> <name>10 to 11</name> <ul spacing="normal"> <li>Reformatted lines causing folding to occur.</li> </ul> </section> <section> <name>11 to 12</name> <ul spacing="normal"> <li>Collapsed all the inner groupings into the top-level grouping.</li> <li>Added a top-level "demux container" inside the top-level grouping.</li> <li>Added NACM statements and updated the Security Considerations section.</li> <li>Added "presence" statements on the "keepalive" containers, as was needed to address a validation error that appeared after adding the "must" statements into the NETCONF/RESTCONF client/server modules.</li> <li>Updated the boilerplate text in module-level "description" statement to match copyeditor convention.</li> </ul> </section> <section> <name>12 to 13</name> <ul spacing="normal"> <li>Removed the "demux containers", floating the nacm:default-deny-write to each descendant node, and adding a note to model designers regarding the potential need to add their own demux containers.</li> <li>Fixed a couple references (section 2 --> section 3)</li> <li>In the server model, replaced <client-cert-auth> with <client-authentication> and introduced 'inline-or-external' choice.</li> </ul> </section> <section> <name>13 to 14</name> <ul spacing="normal"> <li>Updated to reflect changes in trust-anchors drafts (e.g., s/trust-anchors/truststore/g + s/pinned.//)</li> </ul> </section> <section> <name>14 to 15</name> <ul spacing="normal"> <li>Updated examples to reflect ietf-crypto-types change (e.g., identities --> enumerations)</li> <li>Updated "server-authentication" and "client-authentication" nodes from being a leaf of type "ts:host-keys-ref" or "ts:certificates-ref" to a container that uses "ts:inline-or-truststore-host-keys-grouping" or "ts:inline-or-truststore-certs-grouping".</li> </ul> </section> <section> <name>15 to 16</name> <ul spacing="normal"> <li>Removed unnecessary if-feature statements in the -client and -server modules.</li> <li>Cleaned up some description statements in the -client and -server modules.</li> <li>Fixed a canonical ordering issue in ietf-ssh-common detected by new pyang.</li> </ul> </section> <section> <name>16 to 17</name> <ul spacing="normal"> <li>Removed choice inline-or-external by removing the 'external' case and flattening the 'local' case and adding a "local-users-supported" feature.</li> <li>Updated examples to include the "*-key-format" nodes.</li> <li>Augmented-in "must" expressions ensuring that locally-defined public-key-format are "ct:ssh-public-key-format" (must expr for ref'ed keys are TBD).</li> </ul> </section> <section> <name>17 to 18</name> <ul spacing="normal"> <li>Removed leaf-list 'other' from ietf-ssh-server.</li> <li>Removed unused 'external-client-auth-supported' feature.</li> <li>Added features client-auth-password, client-auth-hostbased, and client-auth-none.</li> <li>Renamed 'host-key' to 'public-key' for when refering to 'publickey' based auth.</li> <li>Added new feature-protected 'hostbased' and 'none' to the 'user' node's config.</li> <li>Added new feature-protected 'hostbased' and 'none' to the 'client-identity' node's config.</li> <li>Updated examples to reflect new "bag" addition to truststore.</li> <li>Refined truststore/keystore groupings to ensure the key formats "must" be particular values.</li> <li>Switched to using truststore's new "public-key" bag (instead of separate "ssh-public-key" and "raw-public-key" bags.</li> <li>Updated client/server examples to cover ALL cases (local/ref x cert/raw-key/psk).</li> </ul> </section> <section> <name>18 to 19</name> <ul spacing="normal"> <li>Updated the "keepalives" containers to address Michal Vasko's request to align with RFC 8071.</li> <li>Removed algorithm-mapping tables from the "SSH Common Model" section</li> <li>Removed 'algorithm' node from examples.</li> <li>Added feature "userauth-publickey"</li> <li>Removed "choice auth-type", as auth-types are not exclusive.</li> <li>Renamed both "client-certs" and "server-certs" to "ee-certs"</li> <li>Switch "must" to assert the public-key-formatremoval is"subject-public-key-info-format" when certificates are used.</li> <li>Added a "Note to Reviewers" note to first page.</li> </ul> </section> <section> <name>19 to 20</name> <ul spacing="normal"> <li>Added a "must 'public-key or password or hostbased or none or certificate'" statement to the "user" node in ietf-ssh-client</li> <li>Expanded "Data Model Overview section(s) [remove "wall" of tree diagrams].</li> <li>Moved the "ietf-ssh-common" module section to proceed the other two module sections.</li> <li>Updated the Security Considerations section.</li> </ul> </section> <section> <name>20 to 21</name> <ul spacing="normal"> <li>Updated examples to reflect new "cleartext-" prefix in the crypto-types draft.</li> </ul> </section> <section> <name>21 to 22</name> <ul spacing="normal"> <li>Cleaned up the SSH-client examples (i.e., removing FIXMEs)</li> <li>Fixed issues found by the SecDir review of the "keystore" draft.</li> <li>Updated the "ietf-ssh-client" module to use the new "password-grouping" grouping from the "crypto-types" module.</li> </ul> </section> <section> <name>22 to 23</name> <ul spacing="normal"> <li>Addressed comments raised by YANG Doctor in the ct/ts/ks drafts.</li> </ul> </section> <section> <name>23 to 24</name> <ul spacing="normal"> <li>Removed the 'supported-authentication-methods' from {grouping ssh-server-grouping}/client-authentication.</li> <li>Added XML-comment above examples explaining the reason for the unexepected top-most element's presence.</li> <li>Added RFC-references to various 'feature' statements.</li> <li>Renamed "credentials" to "authentication methods"</li> <li>Renamed "client-auth-*" to "userauth-*"</li> <li>Renamed "client-identity-*" to "userauth-*"</li> <li>Fixed nits found by YANG Doctor reviews.</li> <li>Aligned modules with `pyang -f` formatting.</li> <li>Added a 'Contributors' section.</li> </ul> </section> <section> <name>24 to 25</name> <ul spacing="normal"> <li>Moved algorithms in ietf-ssh-common (plus more) to IANA-maintained modules</li> <li>Added "config false" lists for algorithms supported by the server.</li> <li>Renamed "{ietf-ssh-client}userauth-*" to "client-ident-*"</li> <li>Renamed "{ietf-ssh-server}userauth-*" to "local-user-auth-*"</li> <li>Fixed issues found during YANG Doctor review.</li> <li>Fixed issues found during Secdir review.</li> </ul> </section> <section> <name>25 to 26</name> <ul spacing="normal"> <li>Replaced "base64encodedvalue==" with "BASE64VALUE=" in examples.</li> <li>Minor editorial nits</li> </ul> </section> <section> <name>26 to 27</name> <ul spacing="normal"> <li>Fixed up the 'WG Web' and 'WG List' lines in YANG module(s)</li> <li>Fixed up copyright (i.e., s/Simplified/Revised/) in YANG module(s)</li> <li>Created identityref-based typedefs for each of the four IANA alg identity bases.</li> <li>Added ietf-ssh-common:generate-asymmetric-key-pair() RPC for discussion.</li> </ul> </section> <section> <name>27 to 28</name> <ul spacing="normal"> <li>Fixed example to not have line-returns around "identity" values.</li> <li>Fixed examples to not include "xmlns:algs".</li> <li>Added an example for the "generate-asymmetric-key-pair" RPC.</li> </ul> </section> <section> <name>28 to 29</name> <ul spacing="normal"> <li>Updated modules to IANA-maintained modules in Appendix A to 2022-06-16.</li> </ul> </section> <section> <name>29 to 30</name> <ul spacing="normal"> <li>Fixed 'must' expressions.</li> <li>Added missing 'revision' statement.</li> </ul> </section> <section> <name>30 to 31</name> <ul spacing="normal"> <li>Updated per Shepherd reviews impacting the suite of drafts.</li> </ul> </section> <section> <name>31 to 32</name> <ul spacing="normal"> <li>Updated per Shepherd reviews impacting the suite of drafts.</li> </ul> </section> <section> <name>32 to 33</name> <ul spacing="normal"> <li>Updated per Tom Petch review.</li> <li>Updated Intro to clarify what "generic" means.</li> <li>Added RPC-reply for 'generate-asymmetric-key-pair' example.</li> <li>Added references to RFC 4251 and FIPS 186-6.</li> <li>Added "if-feature ct:encrypted-private-keys" for "case cleartext".</li> </ul> </section> <section> <name>33 to 34</name> <ul spacing="normal"> <li>Addresses AD review comments.</li> <li>Added note to Editor to fix line foldings.</li> <li>Introduction now more clearly identifies the "ietf-" and "iana-" modules defined.</li> <li>Clarified that the modules, when implemented, do not define any protocol-accessible nodes.</li> <li>Clarified that IANA may deprecate and/or obsolete identities over time.</li> <li>Added Security Consideration for the "generate-asymmetric-key-pair" RPC.</li> <li>Added Security Considerations text to also look a SC-section from imported modules.</li> <li>Fixed private-key "must" expressions to not require public-key nodes to be present.</li> <li>Renamed leaf from "bits" to "num-bits".</li> <li>Renamed leaf from "hide" to "hidden".</li> <li>Added container "private-key-encoding" to wrap existing choice.</li> <li>Removed "public-key-format" and "public-key" nodes from examples.</li> </ul> </section> <section> <name>34 to 35</name> <ul spacing="normal"> <li>Addresses AD review by Rob Wilton.</li> </ul> </section> <section> <name>35 to 36</name> <ul spacing="normal"> <li>Addresses 1st-round of IESG reviews.</li> </ul> </section> <section> <name>36 to 38</name> <ul spacing="normal"> <li>Addresses issues found in OpsDir review of the ssh-client-server draft.</li> <li>Replaced identities with enums in the IANA modules.</li> <li>Updated per Elwyn Davies' Gen-ART review.</li> <li>Updated Introduction to read more like the Abstract</li> <li>Add refs to where the 'operational' and 'system' datastores are defined.</li> <li>Updated Editor-notes to NOT remove the script (just remove the initial IANA modules)</li> <li>Renamed Security Considerations section s/Template for/Considerations for/</li> <li>s/defines/presents/ in a few places.</li> <li>Renamed script from 'gen-identities.py' to 'gen-yang-modules.py'</li> <li>Removed the removeInRFC="true" attribute in Appendix sections</li> </ul> </section> <section> <name>38 to 39</name> <ul spacing="normal"> <li>Address IESG review comments.</li> </ul> </section> <section> <name>39 to 40</name> <ul spacing="normal"> <li>Updated to reflect comments from Paul Wouters.</li> <li>Fixed the "generate-asymmetric-key-pair" RPC to return the location to where hidden keys are created.</li> </ul> </section> </section> <section numbered="false"> <name>Acknowledgements</name> <t>The authors would like to thank the following for lively discussions on list and in the halls (ordered by first name): Alan Luchuk, Andy Bierman, Balázs Kovács, Barry Leiba, Benoit Claise, Bert Wijnen, David Lamparter, Elwyn Davies, Gary Wu, Jürgen Schönwälder, Ladislav Lhotka, Liang Xia, Martin Björklund, Martin Thomson, Mehmet Ersue, Michal Vaško, Murray Kucherawy, Paul Wouters, Per Andersson, Phil Shafer, Qin Wun, Radek Krejci, Rob Wilton, Roman Danyliw, Russ Housley, Sean Turner, Tom Petch, Thomas Martin, and Warren Kumari.</t> </section> <section numbered="false"> <name>Contributors</name> <t>Special acknowledgement goes to Gary Wu for his work on the "ietf-ssh-common" module.</t> </section>correct. https://www.rfc-editor.org/authors/rfc9644-diff.html --> </back> </rfc>