One document matched: draft-ietf-netconf-restconf-client-server-01.xml
<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!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 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 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">
<!ENTITY rfc7407 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7407.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-restconf-client-server-01" >
<front>
<title>RESTCONF 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="J.S." surname="Schoenwaelder" fullname="Juergen Schoenwaelder">
<organization>Jacobs University Bremen</organization>
<address>
<email>j.schoenwaelder@jacobs-university.de</email>
</address>
</author>
<date/>
<area>Operations</area>
<workgroup>NETCONF Working Group</workgroup>
<abstract>
<t>This document defines two YANG modules,
one module to configure a RESTCONF client and the other module to
configure a RESTCONF server. Both modules support the TLS transport
protocol with both standard RESTCONF and RESTCONF Call Home connections.</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>
<t>draft-ietf-netconf-tls-client-server</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-restconf</t>
<t><spanx style="verb">ZZZZ</spanx> --> the assigned RFC value for draft-ietf-netconf-tls-client-server</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 module to configure a RESTCONF client and the other module to
configure a RESTCONF server <xref target="draft-ietf-netconf-restconf"/>.
Both modules support the TLS <xref target="RFC5246"/> transport
protocol with both standard RESTCONF and RESTCONF Call Home connections
<xref target="draft-ietf-netconf-call-home"/>.</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 RESTCONF Client Model">
<t>EDITOR NOTE: Please ignore this section, it is incomplete.</t>
<t>The RESTCONF client model presented in this section supports both clients
initiating connections to servers, as well as clients listening
for connections from servers calling home.</t>
<t>This model supports both TLS transport protocols using the TLS client
groupings defined in <xref target="draft-ietf-netconf-tls-client-server"/>.</t>
<t>All private keys and trusted certificates are held in the
keystore model defined in <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>YANG feature statements are used to enable implementations to advertise
which parts of the model the RESTCONF client supports.</t>
<section title="Tree Diagram">
<t>Note: all lines are folded at column 71 with no '\' character.</t>
<t>
<figure>
<artwork><![CDATA[
module: ietf-restconf-client
+--rw restconf-client
+--rw initiate {tls-initiate}?
+--rw listen {tls-listen}?
]]></artwork>
</figure>
</t>
</section>
<section title="Example Usage">
<t>The following example illustrates configuring a RESTCONF
client to initiate connections, as well as listening for call-home
connections.</t>
<t>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
]]></artwork>
</figure>
</t>
</section>
<section title="YANG Model" anchor="ietf-restconf-client-module">
<t>This YANG module imports YANG types from <xref
target="RFC6991"/> and <xref target="RFC7407"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<CODE BEGINS> file "ietf-restconf-client@2016-11-02.yang"
// Editor's Note:
// This module is incomplete at this time. Below is
// just a skeleton so there's something in the draft.
// Please ignore this module for now!
module ietf-restconf-client {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-client";
prefix "rcc";
/*
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
//import ietf-netconf-acm {
// prefix nacm;
// reference
// "RFC 6536: Network Configuration Protocol (NETCONF)
// Access Control Model";
//}
import ietf-x509-cert-to-name {
prefix x509c2n;
reference
"RFC 7407: A YANG Data Model for SNMP Configuration";
}
import ietf-tls-client {
prefix ts;
revision-date 2016-11-02; // stable grouping definitions
reference
"RFC ZZZZ: TLS Client and Server Models";
}
*/
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 contains a collection of YANG definitions for
configuring RESTCONF servers.
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: RESTCONF Client and Server Models";
}
// Features
feature tls-initiate {
description
"The tls-initiate feature indicates that the RESTCONF client
supports initiating TLS connections to RESTCONF servers.";
reference
"RFC YYYY: RESTCONF Protocol";
}
feature tls-listen {
description
"The tls-listen feature indicates that the RESTCONF client
supports opening a port to listen for incoming RESTCONF
server call-home TLS connections.";
reference
"RFC AAAA: NETCONF Call Home and RESTCONF Call Home";
}
container restconf-client {
description
"Top-level container for RESTCONF client configuration.";
container initiate {
if-feature tls-initiate;
description
"Configures client intiating underlying TCP connections.";
}
container listen {
if-feature tls-listen;
description
"Configures client accepting call-home TCP connections.";
}
}
}
<CODE ENDS>
]]></artwork>
</figure>
</t>
</section>
</section>
<section title="The RESTCONF Server Model">
<t>The RESTCONF Server model presented in this section supports servers
both listening for connections as well as initiating call-home
connections.</t>
<t>This model supports the TLS using the TLS server groupings defined in
<xref target="draft-ietf-netconf-tls-client-server"/>.</t>
<t>All private keys and trusted certificates are held in the
keystore model defined in <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>YANG feature statements are used to enable implementations to advertise
which parts of the model the RESTCONF server supports.</t>
<section title="Tree Diagram">
<t>Note: all lines are folded at column 71 with no '\' character.</t>
<t>
<figure>
<artwork><![CDATA[
module: ietf-restconf-server
+--rw restconf-server
+--rw listen {listen}?
| +--rw max-sessions? uint16
| +--rw endpoint* [name]
| +--rw name string
| +--rw (transport)
| +--:(tls) {tls-listen}?
| +--rw tls
| +--rw address? inet:ip-address
| +--rw port? inet:port-number
| +--rw certificates
| | +--rw certificate* [name]
| | +--rw name -> /ks:keystore/private-keys/
private-key/certificate-chains/certificate-chain/name
| +--rw client-auth
| +--rw trusted-ca-certs? -> /ks:keystore/
trusted-certificates/name
| +--rw trusted-client-certs? -> /ks:keystore/
trusted-certificates/name
| +--rw cert-maps
| +--rw cert-to-name* [id]
| +--rw id uint32
| +--rw fingerprint x509c2n:tls-fingerp
rint
| +--rw map-type identityref
| +--rw name string
+--rw call-home {call-home}?
+--rw restconf-client* [name]
+--rw name string
+--rw (transport)
| +--:(tls) {tls-call-home}?
| +--rw tls
| +--rw endpoints
| | +--rw endpoint* [name]
| | +--rw name string
| | +--rw address inet:host
| | +--rw port? inet:port-number
| +--rw certificates
| | +--rw certificate* [name]
| | +--rw name -> /ks:keystore/private-keys/
private-key/certificate-chains/certificate-chain/name
| +--rw client-auth
| +--rw trusted-ca-certs? -> /ks:keystore/
trusted-certificates/name
| +--rw trusted-client-certs? -> /ks:keystore/
trusted-certificates/name
| +--rw cert-maps
| +--rw cert-to-name* [id]
| +--rw id uint32
| +--rw fingerprint x509c2n:tls-fingerp
rint
| +--rw map-type identityref
| +--rw name string
+--rw connection-type
| +--rw (connection-type)?
| +--:(persistent-connection)
| | +--rw persistent!
| | +--rw keep-alives
| | +--rw max-wait? uint16
| | +--rw max-attempts? uint8
| +--:(periodic-connection)
| +--rw periodic!
| +--rw reconnect-timeout? uint16
+--rw reconnect-strategy
+--rw start-with? enumeration
+--rw max-attempts? uint8
]]></artwork>
</figure>
</t>
</section>
<section title="Example Usage">
<t>The following example illustrates configuring a RESTCONF server
to listen for RESTCONF client connections, as well as configuring
call-home to one RESTCONF client.</t>
<t>This example is consistent with the examples presented in
Section 2.2 of <xref target="draft-ietf-netconf-keystore"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<restconf-server
xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-server">
<!-- listening for TLS (HTTPS) connections -->
<listen>
<endpoint>
<name>netconf/tls</name>
<tls>
<address>11.22.33.44</address>
<certificates>
<certificate>ex-key-sect571r1-cert</certificate>
</certificates>
<client-auth>
<trusted-ca-certs>
deployment-specific-ca-certs
</trusted-ca-certs>
<trusted-client-certs>
explicitly-trusted-client-certs
</trusted-client-certs>
<cert-maps>
<cert-to-name>
<id>1</id>
<fingerprint>11:0A:05:11:00</fingerprint>
<map-type>x509c2n:san-any</map-type>
</cert-to-name>
<cert-to-name>
<id>2</id>
<fingerprint>B3:4F:A1:8C:54</fingerprint>
<map-type>x509c2n:specified</map-type>
<name>scooby-doo</name>
</cert-to-name>
</cert-maps>
</client-auth>
</tls>
</endpoint>
</listen>
<!-- calling home to a RESTCONF client -->
<call-home>
<restconf-client>
<name>config-manager</name>
<tls>
<endpoints>
<endpoint>
<name>east-data-center</name>
<address>22.33.44.55</address>
</endpoint>
<endpoint>
<name>west-data-center</name>
<address>33.44.55.66</address>
</endpoint>
</endpoints>
<certificates>
<certificate>ex-key-sect571r1-cert</certificate>
</certificates>
<client-auth>
<trusted-ca-certs>
deployment-specific-ca-certs
</trusted-ca-certs>
<trusted-client-certs>
explicitly-trusted-client-certs
</trusted-client-certs>
<cert-maps>
<cert-to-name>
<id>1</id>
<fingerprint>11:0A:05:11:00</fingerprint>
<map-type>x509c2n:san-any</map-type>
</cert-to-name>
<cert-to-name>
<id>2</id>
<fingerprint>B3:4F:A1:8C:54</fingerprint>
<map-type>x509c2n:specified</map-type>
<name>scooby-doo</name>
</cert-to-name>
</cert-maps>
</client-auth>
</tls>
<connection-type>
<periodic>
<idle-timeout>300</idle-timeout>
<reconnect-timeout>60</reconnect-timeout>
</periodic>
</connection-type>
<reconnect-strategy>
<start-with>last-connected</start-with>
<max-attempts>3</max-attempts>
</reconnect-strategy>
</restconf-client>
</call-home>
</restconf-server>
]]></artwork>
</figure>
</t>
</section>
<section title="YANG Model" anchor="restconf-yang-module">
<t>This YANG module imports YANG types from <xref
target="RFC6991"/> and <xref target="RFC7407"/>.</t>
<t>
<figure>
<artwork><![CDATA[
<CODE BEGINS> file "ietf-restconf-server@2016-11-02.yang"
module ietf-restconf-server {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-server";
prefix "rcs";
//import ietf-netconf-acm {
// prefix nacm;
// reference
// "RFC 6536: Network Configuration Protocol (NETCONF)
// Access Control Model";
//}
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-x509-cert-to-name {
prefix x509c2n;
reference
"RFC 7407: A YANG Data Model for SNMP Configuration";
}
import ietf-tls-server {
prefix ts;
revision-date 2016-11-02; // stable grouping definitions
reference
"RFC ZZZZ: TLS Client and Server Models";
}
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 contains a collection of YANG definitions for
configuring RESTCONF servers.
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: RESTCONF Client and Server Models";
}
// Features
feature listen {
description
"The 'listen' feature indicates that the RESTCONF server
supports opening a port to accept RESTCONF client connections
using at least one transport (e.g., TLS, etc.).";
}
feature tls-listen {
description
"The 'tls-listen' feature indicates that the RESTCONF server
supports opening a port to listen for incoming RESTCONF
client connections.";
reference
"RFC XXXX: RESTCONF Protocol";
}
feature call-home {
description
"The 'call-home' feature indicates that the RESTCONF server
supports initiating RESTCONF call home connections to REETCONF
clients using at least one transport (e.g., TLS, etc.).";
reference
"RFC YYYY: NETCONF Call Home and RESTCONF Call Home";
}
feature tls-call-home {
description
"The 'tls-call-home' feature indicates that the RESTCONF server
supports initiating connections to RESTCONF clients.";
reference
"RFC YYYY: NETCONF Call Home and RESTCONF Call Home";
}
feature client-cert-auth {
description
"The client-cert-auth feature indicates that the RESTCONF
server supports the ClientCertificate authentication scheme.";
reference
"RFC ZZZZ: Client Authentication over New TLS Connection";
}
// top-level container
container restconf-server {
description
"Top-level container for RESTCONF server configuration.";
container listen {
if-feature listen;
description
"Configures listen behavior";
leaf max-sessions {
type uint16;
default 0; // should this be 'max'?
description
"Specifies the maximum number of concurrent sessions
that can be active at one time. The value 0 indicates
that no artificial session limit should be used.";
}
list endpoint {
key name;
description
"List of endpoints to listen for RESTCONF connections on.";
leaf name {
type string;
description
"An arbitrary name for the RESTCONF listen endpoint.";
}
choice transport {
mandatory true;
description
"Selects between available transports.";
case tls {
if-feature tls-listen;
container tls {
description
"TLS-specific listening configuration for inbound
connections.";
uses ts:listening-tls-server-grouping {
refine port {
default 443;
}
augment "client-auth" {
description
"Augments in the cert-to-name structure.";
uses cert-maps-grouping;
}
}
}
}
}
}
}
container call-home {
if-feature call-home;
description
"Configures call-home behavior";
list restconf-client {
key name;
description
"List of RESTCONF clients the RESTCONF server is to
initiate call-home connections to.";
leaf name {
type string;
description
"An arbitrary name for the remote RESTCONF client.";
}
choice transport {
mandatory true;
description
"Selects between TLS and any transports augmented in.";
case tls {
if-feature tls-call-home;
container tls {
description
"Specifies TLS-specific call-home transport
configuration.";
uses endpoints-container {
refine endpoints/endpoint/port {
default 4336;
}
}
uses ts:non-listening-tls-server-grouping {
augment "client-auth" {
description
"Augments in the cert-to-name structure.";
uses cert-maps-grouping;
}
}
}
}
}
container connection-type {
description
"Indicates the RESTCONF client's preference for how the
RESTCONF server's connection is maintained.";
choice connection-type {
description
"Selects between available connection types.";
case persistent-connection {
container persistent {
presence true;
description
"Maintain a persistent connection to the RESTCONF
client. If the connection goes down, immediately
start trying to reconnect to it, using the
reconnection strategy.
This connection type minimizes any RESTCONF client
to RESTCONF server data-transfer delay, albeit at
the expense of holding resources longer.";
container keep-alives {
description
"Configures the keep-alive policy, to proactively
test the aliveness of the TLS client. An
unresponsive TLS client will be dropped after
approximately (max-attempts * max-wait)
seconds.";
reference
"RFC YYYY: NETCONF Call Home and RESTCONF Call
Home, Section 3.1, item S6";
leaf max-wait {
type uint16 {
range "1..max";
}
units seconds;
default 30;
description
"Sets the amount of time in seconds after which
if no data has been received from the TLS
client, a TLS-level message will be sent to
test the aliveness of the TLS 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 TLS client before assuming the TLS client is
no longer alive.";
}
}
}
}
case periodic-connection {
container periodic {
presence true;
description
"Periodically connect to the RESTCONF client, so that
the RESTCONF client may deliver messages pending for
the RESTCONF server. The client must close the
connection when it's ready to release it. Once the
connection has been closed, the server will restart
its timer until the next connection.";
leaf reconnect-timeout {
type uint16 {
range "1..max";
}
units minutes;
default 60;
description
"The maximum amount of unconnected time the
RESTCONF server will wait before re-establishing
a connection to the RESTCONF client. The
RESTCONF server may initiate a connection to
the RESTCONF client before this time if desired
(e.g., to deliver a notification).";
}
}
}
}
}
container reconnect-strategy {
description
"The reconnection strategy directs how a RESTCONF server
reconnects to a RESTCONF client after after discovering
its connection to the client has dropped, even if due to
a reboot. The RESTCONF server starts with the specified
endpoint and tries to connect to it max-attempts times
before trying the next endpoint in the list (round
robin).";
leaf start-with {
type enumeration {
enum first-listed {
description
"Indicates that reconnections should start with
the first endpoint listed.";
}
enum last-connected {
description
"Indicates that reconnections should start with
the endpoint last connected to. If no previous
connection has ever been established, then the
first endpoint configured is used. RESTCONF
servers SHOULD be able to remember the last
endpoint connected to across reboots.";
}
}
default first-listed;
description
"Specifies which of the RESTCONF client's endpoints the
RESTCONF server should start with when trying to connect
to the RESTCONF client.";
}
leaf max-attempts {
type uint8 {
range "1..max";
}
default 3;
description
"Specifies the number times the RESTCONF server tries to
connect to a specific endpoint before moving on to the
next endpoint in the list (round robin).";
}
}
}
}
}
grouping cert-maps-grouping {
description
"A grouping that defines a container around the
cert-to-name structure defined in RFC 7407.";
container cert-maps {
uses x509c2n:cert-to-name;
description
"The cert-maps container is used by a TLS-based RESTCONF
server to map the RESTCONF client's presented X.509
certificate to a RESTCONF username. If no matching and
valid cert-to-name list entry can be found, then the
RESTCONF server MUST close the connection, and MUST NOT
accept RESTCONF messages over it.";
reference
"RFC XXXX: The RESTCONF Protocol";
}
}
grouping endpoints-container {
description
"This grouping is used by tls container for call-home
configurations.";
container endpoints {
description
"Container for the list of endpoints.";
list endpoint {
key name;
min-elements 1;
ordered-by user;
description
"User-ordered list of endpoints for this RESTCONF client.
Defining more than one enables high-availability.";
leaf name {
type string;
description
"An arbitrary name for this endpoint.";
}
leaf address {
type inet:host;
mandatory true;
description
"The IP address or hostname of the endpoint. If a
hostname is configured and the DNS resolution results
in more than one IP address, the RESTCONF server
will process the IP addresses as if they had been
explicitly configured in place of the hostname.";
}
leaf port {
type inet:port-number;
description
"The IP port for this endpoint. The RESTCONF server will
use the IANA-assigned well-known port if no value is
specified.";
}
}
}
}
}
<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>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-restconf-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-restconf-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-restconf-client
namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-client
prefix: ncc
reference: RFC XXXX
name: ietf-restconf-server
namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-server
prefix: ncs
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, Phil Shafer, Sean Turner, and
Bert Wijnen.</t>
<t>
Juergen Schoenwaelder and was partly funded by Flamingo, a
Network of Excellence project (ICT-318488) supported by the
European Commission under its Seventh Framework Programme.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc2119;
&rfc6020;
&rfc6991;
&rfc7407;
<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>
<reference anchor='draft-ietf-netconf-tls-client-server' target="https://datatracker.ietf.org/html/draft-ieft-netconf-tls-client-server">
<front>
<title>TLS Client and Server Models</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-tls-client-server-00'/>
</reference>
<reference anchor='draft-ietf-netconf-restconf' target="https://datatracker.ietf.org/html/draft-ieft-netconf-restconf">
<front>
<title>RESTCONF Protocol</title>
<author initials='A.B.' surname='Bierman' fullname='Andy Bierman'>
<organization>YumaWorks</organization>
</author>
<author initials='M' surname='Bjorklund' fullname='Martin Bjorklund'>
<organization>Tail-f Systems</organization>
</author>
<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-restconf-13' />
</reference>
</references>
<references title="Informative References">
&rfc3688;
&rfc5246;
<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>
</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 new features 'listen' and 'call-home' so future transports
can be augmented in.</t>
</list>
</t>
</section>
</section>
<section title="Open Issues">
<t>Please see: https://github.com/netconf-wg/restconf-client-server/issues.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 19:34:13 |