One document matched: draft-ietf-netconf-ssh-client-server-01.xml
<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc793 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.793.xml">
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY rfc4252 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4252.xml">
<!ENTITY rfc4253 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4253.xml">
<!ENTITY rfc4254 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4254.xml">
<!ENTITY rfc5246 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5246.xml">
<!ENTITY rfc6020 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml">
<!ENTITY rfc6187 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6187.xml">
<!ENTITY rfc6242 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml">
<!ENTITY rfc6335 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6335.xml">
<!ENTITY rfc6991 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6991.xml">
]>
<?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 category="std"
ipr="trust200902"
docName="draft-ietf-netconf-ssh-client-server-01" >
<front>
<title>SSH Client and Server Models</title>
<author initials="K.W." surname="Watsen" fullname="Kent Watsen">
<organization>Juniper Networks</organization>
<address>
<email>kwatsen@juniper.net</email>
</address>
</author>
<author initials="G.W." surname="Wu" fullname="Gary Wu">
<organization>Cisco Networks</organization>
<address>
<email>garywu@cisco.com</email>
</address>
</author>
<date/>
<area>Operations</area>
<workgroup>NETCONF Working Group</workgroup>
<abstract>
<t>This document defines two YANG modules, one
defines groupings for a generic SSH client and the other defines
groupings for a generic SSH server. It is intended that these
groupings will be used by applications using the SSH protocol.</t>
</abstract>
<note title="Editorial Note (To be removed by RFC Editor)">
<t>This draft contains many 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>This document contains references to other drafts in progress, both in
the Normative References section, as well as in body text throughout.
Please update the following references to reflect their final RFC assignments:
<list style="symbols">
<t>draft-ietf-netconf-keystore</t>
</list>
</t>
<t>Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements:
<list style="symbols">
<t><spanx style="verb">XXXX</spanx> --> the assigned RFC value for this draft</t>
<t><spanx style="verb">YYYY</spanx> --> the assigned RFC value for draft-ietf-netconf-keystore</t>
</list>
</t>
<t>Artwork in this document contains placeholder values for the date of
publication of this draft. Please apply the following replacement:
<list style="symbols">
<t><spanx style="verb">2016-11-02</spanx> --> the publication date of this draft</t>
</list>
</t>
<t>The following two Appendix sections are to be removed prior to publication:
<list style="symbols">
<t>Appendix A. Change Log</t>
<t>Appendix B. Open Issues</t>
</list>
</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>This document defines two YANG <xref target="RFC6020"/> modules,
one defines groupings for a generic SSH client and the other
defines groupings for a generic SSH server (SSH is defined in
<xref target="RFC4252"/>, <xref target="RFC4253"/>, and
<xref target="RFC4254"/>). It is intended that these groupings
will be used by applications using the SSH protocol. For
instance, these groupings could be used to help define the data
model for an OpenSSH <xref target="OPENSSH"/> server or a
NETCONF over SSH <xref target="RFC6242"/> based server.</t>
<t>The two YANG modules in this document each define two groupings. One
grouping defines everything other than what's needed for the TCP
<xref target="RFC793"/> protocol layer. The other grouping uses the
first grouping while adding TCP layer specifics (e.g., addresses to
connect to, ports to listen on, etc.). This separation is done in
order to enable 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="draft-ietf-netconf-call-home"/> could use the first
grouping for the SSH parts it provides, while adding data nodes for
the reversed TCP layer.</t>
<section title="Terminology">
<t>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 <xref target="RFC2119"/>.</t>
</section>
<section title="Tree Diagrams" anchor="tree-diagrams">
<t>A simplified graphical representation of the data models
is used in this document. The meaning of the symbols in
these diagrams is as follows:
<list style="symbols">
<t>Brackets "[" and "]" enclose list keys.</t>
<t>Braces "{" and "}" enclose feature names, and indicate
that the named feature must be present for the subtree
to be present.</t>
<t>Abbreviations before data node names: "rw" means
configuration (read-write) and "ro" state data
(read-only).</t>
<t>Symbols after data node names: "?" means an optional
node, "!" means a presence container, and "*" denotes a
list and leaf-list.</t>
<t>Parentheses enclose choice and case nodes, and case
nodes are also marked with a colon (":").</t>
<t>Ellipsis ("...") stands for contents of subtrees that
are not shown.</t>
</list>
</t>
</section>
</section>
<section title="The SSH Client Model" anchor="ssh-client-model">
<t>The SSH client model presented in this section contains two
YANG groupings, one for a client that initiates the underlying
TCP connection and another for a client that has had the TCP
connection opened for it already (e.g., call home).</t>
<t>Both of these groupings reference data nodes defined by the
Keystore model <xref target="draft-ietf-netconf-keystore"/>. For
instance, a reference to the keystore model is made to indicate
which trusted CA certificate a client should use to authenticate
X.509v3 certificate based host keys <xref target="RFC6187"/>.</t>
<section title="Tree Diagram">
<t>The following tree diagram presents the data model for
the two groupings defined in the ietf-ssh-client module.</t>
<t>
<figure>
<artwork><![CDATA[
module: ietf-ssh-client
groupings:
initiating-ssh-client-grouping
+---- server-auth
| +---- trusted-ssh-host-keys? -> /ks:keystore/trusted-ssh-hos
t-keys/name
| +---- trusted-ca-certs? -> /ks:keystore/trusted-certifi
cates/name {ssh-x509-certs}?
| +---- trusted-server-certs? -> /ks:keystore/trusted-certifi
cates/name
+---- client-auth
+---- matches* [name]
+---- name? string
+---- match* [name]
| +---- name? string
| +---- trusted-ssh-host-keys? -> /ks:keystore/trusted-s
sh-host-keys/name
| +---- trusted-ca-certs? -> /ks:keystore/trusted-c
ertificates/name
| +---- trusted-server-certs? -> /ks:keystore/trusted-c
ertificates/name
+---- user-auth-credentials? -> /ks:keystore/user-auth-cr
edentials/user-auth-credential/username
listening-ssh-client-grouping
+---- address? inet:ip-address
+---- port? inet:port-number
+---- server-auth
| +---- trusted-ssh-host-keys? -> /ks:keystore/trusted-ssh-hos
t-keys/name
| +---- trusted-ca-certs? -> /ks:keystore/trusted-certifi
cates/name {ssh-x509-certs}?
| +---- trusted-server-certs? -> /ks:keystore/trusted-certifi
cates/name
+---- client-auth
+---- matches* [name]
+---- name? string
+---- match* [name]
| +---- name? string
| +---- trusted-ssh-host-keys? -> /ks:keystore/trusted-s
sh-host-keys/name
| +---- trusted-ca-certs? -> /ks:keystore/trusted-c
ertificates/name
| +---- trusted-server-certs? -> /ks:keystore/trusted-c
ertificates/name
+---- user-auth-credentials? -> /ks:keystore/user-auth-cr
edentials/user-auth-credential/username
]]></artwork>
</figure>
</t>
</section>
<section title="Example Usage">
<t>This section shows how it would appear if the
initiating-ssh-client-grouping were populated with some data.
This example is consistent with the examples presented in
Section 2.2 of <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>
<figure>
<artwork><![CDATA[
FIXME (how to do an example for a module that only has groupings?)
]]></artwork>
</figure>
</t>
</section>
<section title="YANG Model" anchor="ssh-client-yang-module">
<t>This YANG module has a normative references to <xref target="RFC6991"/>
and <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<CODE BEGINS> file "ietf-ssh-client@2016-11-02.yang"
module ietf-ssh-client {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ssh-client";
prefix "sshc";
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-keystore {
prefix ks;
reference
"RFC YYYY: Keystore Model";
}
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>
Author: Kent Watsen
<mailto:kwatsen@juniper.net>
Author: Gary Wu
<mailto:garywu@cisco.com>";
description
"This module defines a reusable grouping for a SSH client that
can be used as a basis for specific SSH client instances.
Copyright (c) 2014 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 Simplified BSD
License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision "2016-11-02" {
description
"Initial version";
reference
"RFC XXXX: SSH Client and Server Models";
}
feature ssh-x509-certs {
description
"The ssh-x509-certs feature indicates that the SSH
client supports RFC 6187";
reference
"RFC 6187: X.509v3 Certificates for Secure Shell
Authentication";
}
grouping initiating-ssh-client-grouping {
description
"A reusable grouping for a SSH client that initiates the
underlying TCP transport connection.";
container server-auth {
description
"Trusted server identities.";
leaf trusted-ssh-host-keys {
type leafref {
path "/ks:keystore/ks:trusted-ssh-host-keys/ks:name";
}
description
"A reference to a list of SSH host keys used by the
SSH client to authenticate SSH server host keys.
A server host key is authenticate if it is an exact
match to a configured trusted SSH host key.";
}
leaf trusted-ca-certs {
if-feature ssh-x509-certs;
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of certificate authority (CA)
certificates used by the SSH client to authenticate
SSH server certificates.";
}
leaf trusted-server-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of server certificates used by
the SSH client to authenticate SSH server certificates.
A server certificate is authenticated if it is an
exact match to a configured trusted server certificate.";
}
}
container client-auth {
description
"The credentials used by the client to authenticate to
the SSH server.";
list matches {
key name;
description
"A matches expression, which performs like a firewall
rulebase in that each matches expression is considered
for a match before moving onto the next matches
expression. The first matching expression terminates
the search, and its 'user-auth-credentials' are used
to log into the SSH server.";
leaf name {
type string;
description
"An arbitrary name for this matches expression.";
}
list match {
key name;
description
"A match rule. The presented SSH server's host key
is matched against possible trusted SSH host keys
and certificates. If a match is found, the specified
'user-auth-credentials' is used to log into the
SSH server.";
leaf name {
type string;
description
"An arbitrary name for this match rule.";
}
leaf trusted-ssh-host-keys {
type leafref {
path "/ks:keystore/ks:trusted-ssh-host-keys/ks:name";
}
description
"A test to see if the presented SSH host key
matches any of the host keys in the specified
'trusted-ssh-host-keys' list maintained by the
keystore module.";
}
leaf trusted-ca-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A test to see if the presented SSH host key matches
any of the trusted CA certificates in the specified
'trusted-certificates' list maintained by the
keystore module.";
}
leaf trusted-server-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A test to see if the presented SSH host key matches
any of the trusted server certificates in the specified
'trusted-certificates' list maintained by the
keystore module.";
}
}
leaf user-auth-credentials {
type leafref {
path "/ks:keystore/ks:user-auth-credentials/"
+ "ks:user-auth-credential/ks:username";
}
description
"The specific user authentication credentials to use if
all of the above 'match' expressions match.";
}
}
}
} // end initiating-ssh-client-grouping
grouping listening-ssh-client-grouping {
description
"A reusable grouping for a SSH client that does not
the underlying TCP transport connection have been
established using some other mechanism.";
leaf address {
type inet:ip-address;
description
"The IP address to listen for call-home connections on.";
}
leaf port {
type inet:port-number;
description
"The port number to listen for call-home connections.
When this grouping is used, it is RECOMMENED that
refine statement is used to either set a default port
value or to set mandatory true.";
}
uses initiating-ssh-client-grouping;
}
}
<CODE ENDS>
]]></artwork>
</figure>
</t>
</section>
</section>
<section title="The SSH Server Model" anchor="ssh-server-model">
<t>The SSH server model presented in this section contains two
YANG groupings, one for a server that opens a socket to accept
TCP connections and another for a server that has had the TCP
connection opened for it already (e.g., inetd).</t>
<t>Both of these groupings reference data nodes defined by the
Keystore model <xref target="draft-ietf-netconf-keystore"/>.
For instance, a reference to the keystore model is made to indicate
which host key a server should present.</t>
<section title="Tree Diagram">
<t>The following tree diagram presents the data model for
the two groupings defined in the ietf-ssh-server module.</t>
<t>
<figure>
<artwork><![CDATA[
module: ietf-ssh-server
groupings:
listening-ssh-server-grouping
+---- address? inet:ip-address
+---- port? inet:port-number
+---- host-keys
| +---- host-key* [name]
| +---- name? string
| +---- (host-key-type)
| +--:(public-key)
| | +---- public-key? -> /ks:keystore/private-keys/pri
vate-key/name
| +--:(certificate)
| +---- certificate? -> /ks:keystore/private-keys/pri
vate-key/certificate-chains/certificate-chain/name {ssh-x509-certs}?
+---- client-cert-auth {ssh-x509-certs}?
+---- trusted-ca-certs? -> /ks:keystore/trusted-certific
ates/name
+---- trusted-client-certs? -> /ks:keystore/trusted-certific
ates/name
non-listening-ssh-server-grouping
+---- host-keys
| +---- host-key* [name]
| +---- name? string
| +---- (host-key-type)
| +--:(public-key)
| | +---- public-key? -> /ks:keystore/private-keys/pri
vate-key/name
| +--:(certificate)
| +---- certificate? -> /ks:keystore/private-keys/pri
vate-key/certificate-chains/certificate-chain/name {ssh-x509-certs}?
+---- client-cert-auth {ssh-x509-certs}?
+---- trusted-ca-certs? -> /ks:keystore/trusted-certific
ates/name
+---- trusted-client-certs? -> /ks:keystore/trusted-certific
ates/name
]]></artwork>
</figure>
</t>
</section>
<section title="Example Usage">
<t>This section shows how it would appear if the
listening-ssh-server-grouping were populated with some data.
This example is consistent with the examples presented in
Section 2.2 of <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<listening-ssh-server
xmlns="urn:ietf:params:xml:ns:yang:ietf-ssh-server">
<port>830</port>
<host-keys>
<host-key>
<name>deployment-specific-certificate</name>
<certificate>ex-key-sect571r1-cert</certificate>
</host-key>
</host-keys>
</certificates>
<client-cert-auth>
<trusted-ca-certs>
deployment-specific-ca-certs
</trusted-ca-certs>
<trusted-client-certs>
explicitly-trusted-client-certs
</trusted-client-certs>
</client-cert-auth>
</listening-ssh-server>
]]></artwork>
</figure>
</t>
</section>
<section title="YANG Model" anchor="ssh-server-yang-module">
<t>This YANG module has a normative references to <xref target="RFC4253"/>,
<xref target="RFC6991"/>, and <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<CODE BEGINS> file "ietf-ssh-server@2016-11-02.yang"
module ietf-ssh-server {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ssh-server";
prefix "sshs";
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-keystore {
prefix ks;
reference
"RFC YYYY: Keystore Model";
}
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>
Editor: Kent Watsen
<mailto:kwatsen@juniper.net>";
description
"This module defines a reusable grouping for a SSH server that
can be used as a basis for specific SSH server instances.
Copyright (c) 2014 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 Simplified BSD
License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision "2016-11-02" {
description
"Initial version";
reference
"RFC XXXX: SSH Client and Server Models";
}
// features
feature ssh-x509-certs {
description
"The ssh-x509-certs feature indicates that the NETCONF
server supports RFC 6187";
reference
"RFC 6187: X.509v3 Certificates for Secure Shell
Authentication";
}
// grouping
grouping non-listening-ssh-server-grouping {
description
"A reusable grouping for a SSH server that can be used as a
basis for specific SSH server instances.";
container host-keys {
description
"The list of host-keys the SSH server will present when
establishing a SSH connection.";
list host-key {
key name;
min-elements 1;
ordered-by user;
description
"An ordered list of host keys the SSH server will use to
construct its ordered list of algorithms, when sending
its SSH_MSG_KEXINIT message, as defined in Section 7.1
of RFC 4253.";
reference
"RFC 4253: The Secure Shell (SSH) Transport Layer Protocol";
leaf name {
type string;
description
"An arbitrary name for this host-key";
}
choice host-key-type {
mandatory true;
description
"The type of host key being specified";
leaf public-key {
type leafref {
path "/ks:keystore/ks:private-keys/ks:private-key/"
+ "ks:name";
}
description
"The public key is actually identified by the name of
its cooresponding private-key in the keystore.";
}
leaf certificate {
if-feature ssh-x509-certs;
type leafref {
path "/ks:keystore/ks:private-keys/ks:private-key/"
+ "ks:certificate-chains/ks:certificate-chain/"
+ "ks:name";
}
description
"The name of a certificate in the keystore.";
}
}
}
}
container client-cert-auth {
if-feature ssh-x509-certs;
description
"A reference to a list of trusted certificate authority (CA)
certificates and a reference to a list of trusted client
certificates.";
leaf trusted-ca-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of certificate authority (CA)
certificates used by the SSH server to authenticate
SSH client certificates.";
}
leaf trusted-client-certs {
type leafref {
path "/ks:keystore/ks:trusted-certificates/ks:name";
}
description
"A reference to a list of client certificates used by
the SSH server to authenticate SSH client certificates.
A clients certificate is authenticated if it is an
exact match to a configured trusted client certificate.";
}
}
}
grouping listening-ssh-server-grouping {
description
"A reusable grouping for a SSH server that can be used as a
basis for specific SSH server instances.";
leaf address {
type inet:ip-address;
description
"The IP address of the interface to listen on. The SSH
server will listen on all interfaces if no value is
specified. Please note that some addresses have special
meanings (e.g., '0.0.0.0' and '::').";
}
leaf port {
type inet:port-number;
description
"The local port number on this interface the SSH server
listens on. When this grouping is used, it is RECOMMENED
that refine statement is used to either set a default port
value or to set mandatory true.";
}
uses non-listening-ssh-server-grouping;
}
}
<CODE ENDS>
]]></artwork>
</figure>
</t>
</section>
</section>
<section title="Security Considerations">
<!--
I removed all the NACM statements in the new modules
<t>There are a number of data nodes defined in the
"ietf-netconf-server" and "ietf-restconf-server" YANG
modules which are readable and/or writable that may
be considered sensitive or vulnerable in some
network environments. Write and read operations to
these data nodes can have a negative effect on network
operations. It is thus important to control write
and read access to these data nodes. Below are the
data nodes and their sensitivity/vulnerability.</t>
<t>netconf-server/tls/client-auth/trusted-ca-certs:
<list style="symbols">
<t>This container contains certificates that a NETCONF server
is to use as trust anchors for authenticating X.509-based
client certificates. Write access to this node is
protected using an nacm:default-deny-write statement.</t>
</list>
</t>
<t>netconf-server/tls/client-auth/trusted-client-certs:
<list style="symbols">
<t>This container contains certificates that a NETCONF server
is to trust directly when authenticating X.509-based
client certificates. Write access to this node is
protected using an nacm:default-deny-write statement.</t>
</list>
</t>
<t>restconf-server/tls/client-auth/trusted-ca-certs:
<list style="symbols">
<t>This container contains certificates that a RESTCONF server
is to use as trust anchors for authenticating X.509-based
client certificates. Write access to this node is
protected using an nacm:default-deny-write statement.</t>
</list>
</t>
<t>restconf-server/tls/client-auth/trusted-client-certs:
<list style="symbols">
<t>This container contains certificates that a RESTCONF server
is to trust directly when authenticating X.509-based
client certificates. Write access to this node is
protected using an nacm:default-deny-write statement.</t>
</list>
</t>
-->
</section>
<section title="IANA Considerations">
<section title="The IETF XML Registry">
<t>This document registers two URIs in the IETF XML
registry <xref target="RFC2119"/>. Following the format in
<xref target="RFC3688"/>, the following registrations are
requested:</t>
<t>
<figure>
<artwork><![CDATA[
URI: urn:ietf:params:xml:ns:yang:ietf-ssh-client
Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-ssh-server
Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
]]></artwork>
</figure>
</t>
</section>
<section title="The YANG Module Names Registry">
<t>This document registers two YANG modules in the
YANG Module Names registry <xref target="RFC6020"/>.
Following the format in <xref target="RFC6020"/>, the
the following registrations are requested:</t>
<t>
<figure>
<artwork><![CDATA[
name: ietf-ssh-client
namespace: urn:ietf:params:xml:ns:yang:ietf-ssh-client
prefix: sshc
reference: RFC XXXX
name: ietf-ssh-server
namespace: urn:ietf:params:xml:ns:yang:ietf-ssh-server
prefix: sshs
reference: RFC XXXX
]]></artwork>
</figure>
</t>
</section>
</section>
<section title="Acknowledgements">
<t>The authors would like to thank for following for
lively discussions on list and in the halls (ordered
by last name): Andy Bierman, Martin Bjorklund, Benoit Claise,
Mehmet Ersue, David Lamparter, Alan Luchuk, Ladislav Lhotka,
Radek Krejci, Tom Petch, Juergen Schoenwaelder, Phil Shafer,
Sean Turner, Michal Vaško, and Bert Wijnen.</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc2119;
&rfc6020;
&rfc6187;
&rfc6991;
<reference anchor='draft-ietf-netconf-keystore' target="https://datatracker.ietf.org/html/draft-ieft-netconf-keystore">
<front>
<title>Keystore Model</title>
<author initials='K.W.' surname='Watsen' fullname='Kent Watsen'>
<organization>Juniper Networks</organization>
</author>
<date year='2016' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ieft-netconf-keystore-00'/>
</reference>
</references>
<references title="Informative References">
<reference anchor="RFC793" target="https://www.ietf.org/rfc/rfc793.txt">
<front>
<title>TRANSMISSION CONTROL PROTOCOL</title>
<author initials="J." surname="Postel" fullname="J. Postel">
<organization/>
</author>
<date year="1981" month="September"/>
</front>
<seriesInfo name="STD" value="7"/>
</reference>
&rfc3688;
&rfc4252;
&rfc4253;
&rfc4254;
&rfc6242;
<reference anchor='draft-ietf-netconf-call-home' target="https://datatracker.ietf.org/html/draft-ieft-netconf-call-home-17">
<front>
<title>
NETCONF Call Home and RESTCONF Call Home
</title>
<author initials='K.W.' surname='Watsen' fullname='Kent Watsen'>
<organization>Juniper Networks</organization>
</author>
<date year='2015'/>
</front>
<seriesInfo name='Internet-Draft' value='draft-ieft-netconf-call-home-17' />
</reference>
<reference anchor='OPENSSH' target="http://www.openssh.com">
<front>
<title>OpenSSH</title>
<author fullname='The OpenBSD Project'/>
<date year='2016'/>
</front>
</reference>
</references>
<section title="Change Log">
<section title="server-model-09 to 00">
<t>
<list style="symbols">
<t>This draft was split out from draft-ietf-netconf-server-model-09.</t>
<t>Added in previously missing ietf-ssh-client module.</t>
<t>Noted that '0.0.0.0' and '::' might have special meanings.</t>
</list>
</t>
</section>
</section>
<section title="Open Issues">
<t>Please see: https://github.com/netconf-wg/ssh-client-server/issues.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 05:23:16 |