draft-ietf-netconf-nmda-netconf-04.txt   draft-ietf-netconf-nmda-netconf-05.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Updates: 6241, 7950 (if approved) J. Schoenwaelder Updates: 6241, 7950 (if approved) J. Schoenwaelder
Intended status: Standards Track Jacobs University Intended status: Standards Track Jacobs University
Expires: September 2, 2018 P. Shafer Expires: October 22, 2018 P. Shafer
K. Watsen K. Watsen
Juniper Networks Juniper Networks
R. Wilton R. Wilton
Cisco Systems Cisco Systems
March 1, 2018 April 20, 2018
NETCONF Extensions to Support the Network Management Datastore NETCONF Extensions to Support the Network Management Datastore
Architecture Architecture
draft-ietf-netconf-nmda-netconf-04 draft-ietf-netconf-nmda-netconf-05
Abstract Abstract
This document extends the NETCONF protocol defined in RFC 6241 in This document extends the NETCONF protocol defined in RFC 6241 in
order to support the Network Management Datastore Architecture order to support the Network Management Datastore Architecture
defined in I-D.ietf-netmod-revised-datastores. defined in RFC 8342.
This document updates both RFC 6241 and RFC 7950. The update to RFC This document updates both RFC 6241 and RFC 7950. The update to RFC
6241 adds new operations <get-data> and <edit-data>, and augments 6241 adds new operations <get-data> and <edit-data>, and augments
existing operations <lock>, <unlock>, and <validate>. The update to existing operations <lock>, <unlock>, and <validate>. The update to
RFC 7950 requires the usage of I-D.ietf-netconf-rfc7895bis by NETCONF RFC 7950 requires the usage of I-D.ietf-netconf-rfc7895bis by NETCONF
servers implementing the Network Management Datastore Architecture. servers implementing the Network Management Datastore Architecture.
REF Editor: please replace "I-D.ietf-netmod-revised-datastores" and RFC Ed.: Please replace "I-D.ietf-netconf-rfc7895bis" above with its
"I-D.ietf-netconf-rfc7895bis" above with their final RFC assignments. final RFC assignment and remove this note.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2018. This Internet-Draft will expire on October 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 43 skipping to change at page 2, line 43
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . 19 7.1. Normative References . . . . . . . . . . . . . . . . . . 19
7.2. Informative References . . . . . . . . . . . . . . . . . 20 7.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document extends the NETCONF protocol defined in [RFC6241] in This document extends the NETCONF protocol defined in [RFC6241] in
order to support the Network Management Datastore Architecture (NMDA) order to support the Network Management Datastore Architecture (NMDA)
defined in [I-D.ietf-netmod-revised-datastores]. defined in [RFC8342].
This document updates [RFC6241] in order to enable NETCONF clients to This document updates [RFC6241] in order to enable NETCONF clients to
interact with all the datastores supported by a server implementing interact with all the datastores supported by a server implementing
the NMDA. The update both adds new operations <get-data> and the NMDA. The update both adds new operations <get-data> and
<edit-data>, and augments existing operations <lock>, <unlock>, and <edit-data>, and augments existing operations <lock>, <unlock>, and
<validate>. <validate>.
This document also updates [RFC7950] in order to enable NETCONF This document also updates [RFC7950] in order to enable NETCONF
clients to both discover which datastores are supported by the clients to both discover which datastores are supported by the
NETCONF server, as well as determine which modules are supported in NETCONF server, as well as determine which modules are supported in
each datastore. The update requires NETCONF servers implementing the each datastore. The update requires NETCONF servers implementing the
NMDA to support [I-D.ietf-netconf-rfc7895bis]. NMDA to support [I-D.ietf-netconf-rfc7895bis].
1.1. Terminology 1.1. Terminology
This document uses the terminology defined by the NMDA This document uses the terminology defined by the NMDA [RFC8342].
[I-D.ietf-netmod-revised-datastores].
The following term is defined in [I-D.ietf-netconf-rfc7895bis]: The following term is defined in [I-D.ietf-netconf-rfc7895bis]:
o YANG library checksum o YANG library checksum
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119] [RFC8174] when, and only when, they appear in all 14, [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.2. Tree Diagrams 1.2. Tree Diagrams
Tree diagrams used in this document follow the notation defined in Tree diagrams used in this document follow the notation defined in
[I-D.ietf-netmod-yang-tree-diagrams]. [RFC8340].
2. Datastore and YANG Library Requirements 2. Datastore and YANG Library Requirements
RFC Ed.: Update 201X-XX-XX below with correct date. RFC Ed.: Update 201X-XX-XX below with correct date.
An NMDA-compliant NETCONF server MUST support the operational state An NMDA-compliant NETCONF server MUST support the operational state
datastore and it MUST implement at least revision 201X-XX-XX of the datastore and it MUST implement at least revision 201X-XX-XX of the
"ietf-yang-library" module defined in [I-D.ietf-netconf-rfc7895bis]. "ietf-yang-library" module defined in [I-D.ietf-netconf-rfc7895bis].
A NETCONF client can discover which datastores and YANG modules the
server supports by reading the YANG library information from the
operational state datastore.
The server MUST advertise the following capability in the <hello> The server MUST advertise the following capability in the <hello>
message (line breaks and whitespaces are used for formatting reasons message (line breaks and whitespaces are used for formatting reasons
only): only):
urn:ietf:params:netconf:capability:yang-library:1.1? urn:ietf:params:netconf:capability:yang-library:1.1?
revision=<date>&checksum=<checksum-value> revision=<date>&checksum=<checksum-value>
The parameter "revision" has the same value as the revision date of The parameter "revision" has the same value as the revision date of
the "ietf-yang-library" module implemented by the server. This the "ietf-yang-library" module implemented by the server. This
parameter MUST be present. parameter MUST be present.
The parameter "checksum" contains the YANG library checksum The parameter "checksum" contains the YANG library checksum
[I-D.ietf-netconf-rfc7895bis]. This parameter MUST be present. [I-D.ietf-netconf-rfc7895bis]. This parameter MUST be present.
With this mechanism, a client can cache the supported modules for a With this mechanism, a client can cache the supported datastores and
server and only update the cache if the "checksum" value in the YANG modules for a server and only update the cache if the "checksum"
<hello> message changes. value in the <hello> message changes.
This document updates [RFC7950], Section 5.6.4, to allow servers to This document updates [RFC7950], Section 5.6.4, to allow servers to
advertise the capability :yang-library:1.1 instead of :yang- advertise the capability :yang-library:1.1 instead of :yang-
library:1.0, and to implement the subtree "/yang-library" library:1.0, and to implement the subtree "/yang-library"
[I-D.ietf-netconf-rfc7895bis] instead of "/modules-state". [I-D.ietf-netconf-rfc7895bis] instead of "/modules-state".
3. NETCONF Extensions 3. NETCONF Extensions
This section describes the NETCONF extensions needed to support the This section describes the NETCONF extensions needed to support the
NMDA. These changes are defined in a new YANG ([RFC7950]) module NMDA. These changes are defined in a new YANG ([RFC7950]) module
"ietf-netconf-nmda". "ietf-netconf-nmda".
These changes include the use of source and target parameters based These changes include the use of source and target parameters based
on the "datastore" identity defined in the "ietf-datastores" module on the "datastore" identity defined in the "ietf-datastores" module
[I-D.ietf-netmod-revised-datastores]. The use of identities allows [RFC8342]. The use of identities allows future expansion in a way
future expansion in a way that the choice-based strategy from the that the choice-based strategy from the original operations (e.g.,
original operations (e.g., <get-config>, <edit-config>) does not. <get-config>, <edit-config>) does not.
3.1. New NETCONF Operations 3.1. New NETCONF Operations
Two new operations <get-data> and <edit-data> are defined in this Two new operations <get-data> and <edit-data> are defined in this
document in order to support the NMDA. These operations are similar document in order to support the NMDA. These operations are similar
to the <get-config> and <edit-config> operations but they can work on to the <get-config> and <edit-config> operations but they can work on
an extensible set of datastores. an extensible set of datastores.
3.1.1. The <get-data> Operation 3.1.1. The <get-data> Operation
The <get-data> operation retrieves data from a specific NMDA The <get-data> operation retrieves data from a specific NMDA
datastore. This operation is similar to NETCONF's <get-config> datastore. This operation is similar to NETCONF's <get-config>
operation defined in [RFC6241], but it adds the flexibility to select operation defined in [RFC6241], but it adds the flexibility to select
the source datastore. the source datastore.
+---x get-data +---x get-data
+---w input +---w input
| +---w datastore ds:datastore-ref | +---w datastore ds:datastore-ref
| +--(filter-spec)? | +---w (filter-spec)?
| | +--:(subtree-filter) | | +--:(subtree-filter)
| | | +---w subtree-filter? <anydata> | | | +---w subtree-filter? <anydata>
| | +--:(xpath-filter) | | +--:(xpath-filter)
| | +---w xpath-filter? yang:xpath1.0 {nc:xpath}? | | +---w xpath-filter? yang:xpath1.0 {nc:xpath}?
| +---w config-filter? boolean | +---w config-filter? boolean
| +--(origin-filters)? {origin}? | +---w (origin-filters)? {origin}?
| | +--:(origin-filter) | | +--:(origin-filter)
| | | +---w origin-filter* or:origin-ref | | | +---w origin-filter* or:origin-ref
| | +--:(negated-origin-filter) | | +--:(negated-origin-filter)
| | +---w negated-origin-filter* or:origin-ref | | +---w negated-origin-filter* or:origin-ref
| +---w max-depth? union | +---w max-depth? union
| +---w with-origin? empty {origin}? | +---w with-origin? empty {origin}?
| +---w with-defaults? with-defaults-mode | +---w with-defaults? with-defaults-mode
+--ro output +--ro output
+--ro data? <anydata> +--ro data? <anydata>
skipping to change at page 6, line 19 skipping to change at page 6, line 19
urn:ietf:params:netconf:capability:with-operational-defaults:1.0 urn:ietf:params:netconf:capability:with-operational-defaults:1.0
If the "with-defaults" parameter is supported for <get-data> If the "with-defaults" parameter is supported for <get-data>
operations on <operational>, then all retrieval modes specified in operations on <operational>, then all retrieval modes specified in
either the 'basic-mode' or 'also-supported' parameters of the either the 'basic-mode' or 'also-supported' parameters of the
"with-defaults" capability are permitted. The behavior of the "with-defaults" capability are permitted. The behavior of the
"with-defaults" parameter for <operational> is defined as below: "with-defaults" parameter for <operational> is defined as below:
o If no "with-defaults" parameter is specified, or if it is set to o If no "with-defaults" parameter is specified, or if it is set to
"explicit", "report-all", or "report-all-tagged", then the "in "explicit", "report-all", or "report-all-tagged", then the "in
use" values, as defined in [I-D.ietf-netmod-revised-datastores] use" values, as defined in [RFC8342] section 5.3, are returned
section 5.3, are returned from the operational state datastore, from the operational state datastore, even if a node happens to
even if a node happens to have a default statement in the YANG have a default statement in the YANG module, and this default
module, and this default value is being used by the server. If value is being used by the server. If the "with-defaults"
the "with-defaults" parameter is set to "report-all-tagged", any parameter is set to "report-all-tagged", any values that match the
values that match the schema default are tagged with additional schema default are tagged with additional metadata, as described
metadata, as described in [RFC6243] section 3.4. in [RFC6243] section 3.4.
o If the "with-defaults" parameter is set to "trim", all "in use" o If the "with-defaults" parameter is set to "trim", all "in use"
values are returned, except that the output is filtered to exclude values are returned, except that the output is filtered to exclude
any values that match the default defined in the YANG schema. any values that match the default defined in the YANG schema.
Support for "with-defaults" in <get-data> operations on any datastore Support for "with-defaults" in <get-data> operations on any datastore
not defined in [I-D.ietf-netmod-revised-datastores] SHOULD be defined not defined in [RFC8342] SHOULD be defined by the specification for
by the specification for the datastore. the datastore.
3.1.1.2. Origin Metadata Attribute 3.1.1.2. Origin Metadata Attribute
The <get-data> operation defines a parameter named "with-origin", The <get-data> operation defines a parameter named "with-origin",
which if present, requests that the server includes "origin" metadata which if present, requests that the server includes "origin" metadata
annotations in its response, as detailed in the NMDA. This parameter annotations in its response, as detailed in the NMDA. This parameter
is only valid for the operational state datastore and any datastores is only valid for the operational state datastore and any datastores
with identities derived from the "operational" identity. Otherwise, with identities derived from the "operational" identity. Otherwise,
if an invalid datastore is specified then an error is returned, as if an invalid datastore is specified then an error is returned, as
specified in "ietf-netconf-nmda" (see Section 4). Note that "origin" specified in "ietf-netconf-nmda" (see Section 4). Note that "origin"
metadata annotations are not included in a response unless a client metadata annotations are not included in a response unless a client
explicitly requests them. explicitly requests them.
Data in the operational state datastore can come from multiple Data in the operational state datastore can come from multiple
sources. The server should return the most accurate value for the sources. The server should return the most accurate value for the
"origin" metadata annotation as possible, indicating the source of "origin" metadata annotation as possible, indicating the source of
the operational value, as specified in Section 5.3.4 of the operational value, as specified in Section 5.3.4 of [RFC8342].
[I-D.ietf-netmod-revised-datastores].
When encoding the origin metadata annotation for a hierarchy of When encoding the origin metadata annotation for a hierarchy of
returned nodes, the annotation may be omitted for a child node when returned nodes, the annotation may be omitted for a child node when
the value matches that of the parent node, as described in the the value matches that of the parent node, as described in the
"ietf-origin" YANG module [I-D.ietf-netmod-revised-datastores]. "ietf-origin" YANG module [RFC8342].
The "with-origin" parameter is optional to support. It is identified The "with-origin" parameter is optional to support. It is identified
with the feature "origin". with the feature "origin".
3.1.1.3. Example: Retrieving an entire subtree from <running> 3.1.1.3. Example: Retrieving an entire subtree from <running>
The following example shows the <get-data> version of the The following example shows the <get-data> version of the
<get-config> example shown in Section 7.1 of [RFC6241]. <get-config> example shown in Section 7.1 of [RFC6241].
<rpc message-id="101" <rpc message-id="101"
skipping to change at page 8, line 18 skipping to change at page 8, line 18
datastore, similar to the <edit-config> operation defined in datastore, similar to the <edit-config> operation defined in
[RFC6241], but with additional flexibility in naming the target [RFC6241], but with additional flexibility in naming the target
datastore. If an <edit-data> operation is invoked on a non-writable datastore. If an <edit-data> operation is invoked on a non-writable
datastore, then an error is returned, as specified in datastore, then an error is returned, as specified in
"ietf-netconf-nmda" (see Section 4). "ietf-netconf-nmda" (see Section 4).
+---x edit-data +---x edit-data
+---w input +---w input
+---w datastore ds:datastore-ref +---w datastore ds:datastore-ref
+---w default-operation? enumeration +---w default-operation? enumeration
+--(edit-content) +---w (edit-content)
+--:(config) +--:(config)
| +---w config? <anydata> | +---w config? <anydata>
+--:(url) +--:(url)
+---w url? inet:uri {nc:url}? +---w url? inet:uri {nc:url}?
The "datastore" parameter is a datastore identity that indicates the The "datastore" parameter is a datastore identity that indicates the
desired target datastore where changes should be made. desired target datastore where changes should be made.
The "default-operation" parameter is a copy of the The "default-operation" parameter is a copy of the
"default-operation" parameter of the <edit-config> operation. "default-operation" parameter of the <edit-config> operation.
skipping to change at page 9, line 49 skipping to change at page 9, line 49
"ietf-netconf" [RFC6241] may be used with new datastores. Hence, the "ietf-netconf" [RFC6241] may be used with new datastores. Hence, the
<lock>, <unlock>, and <validate> operations are augmented with a new <lock>, <unlock>, and <validate> operations are augmented with a new
"datastore" leaf that can select the desired datastore. If a <lock>, "datastore" leaf that can select the desired datastore. If a <lock>,
<unlock>, or <validate> operation is not supported on a particular <unlock>, or <validate> operation is not supported on a particular
datastore then an error is returned, as specified in datastore then an error is returned, as specified in
"ietf-netconf-nmda" (see Section 4). "ietf-netconf-nmda" (see Section 4).
4. NETCONF Datastores YANG Module 4. NETCONF Datastores YANG Module
This module imports definitions from [RFC6991], [RFC6241], [RFC6243], This module imports definitions from [RFC6991], [RFC6241], [RFC6243],
and [I-D.ietf-netmod-revised-datastores]. and [RFC8342].
RFC Ed.: update the date below with the date of RFC publication and RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-netconf-nmda@2018-02-28.yang" <CODE BEGINS> file "ietf-netconf-nmda@2018-04-20"
module ietf-netconf-nmda { module ietf-netconf-nmda {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-nmda"; namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-nmda";
prefix ncds; prefix ncds;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference "RFC 6991: Common YANG Data Types."; reference "RFC 6991: Common YANG Data Types.";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC 6991: Common YANG Data Types."; reference "RFC 6991: Common YANG Data Types.";
} }
import ietf-datastores { import ietf-datastores {
prefix ds; prefix ds;
// RFC Ed.: update the reference below with the actual RFC number reference "RFC 8342: Network Management Datastore Architecture.";
reference "RFC XXXX: Network Management Datastore Architecture.";
} }
import ietf-origin { import ietf-origin {
prefix or; prefix or;
// RFC Ed.: update the reference below with the actual RFC number reference "RFC 8342: Network Management Datastore Architecture.";
reference "RFC XXXX: Network Management Datastore Architecture.";
} }
import ietf-netconf { import ietf-netconf {
prefix nc; prefix nc;
reference "RFC 6241: Network Configuration Protocol (NETCONF)"; reference "RFC 6241: Network Configuration Protocol (NETCONF)";
} }
import ietf-netconf-with-defaults { import ietf-netconf-with-defaults {
prefix ncwd; prefix ncwd;
reference "RFC 6243: With-defaults Capability for NETCONF."; reference "RFC 6243: With-defaults Capability for NETCONF.";
} }
skipping to change at page 11, line 36 skipping to change at page 11, line 35
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://www.rfc-editor.org/info/rfcxxxx); see the RFC itself (http://www.rfc-editor.org/info/rfcxxxx); see the RFC itself
for full legal notices."; for full legal notices.";
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
revision 2018-02-28 { revision 2018-04-20 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: NETCONF Extensions to Support the Network Management "RFC XXXX: NETCONF Extensions to Support the Network Management
Datastore Architecture"; Datastore Architecture";
} }
feature origin { feature origin {
description description
"Indicates that the server supports the 'origin' annotation."; "Indicates that the server supports the 'origin' annotation.";
reference reference
"RFC XXXX: Network Management Datastore Architecture"; "RFC 8342: Network Management Datastore Architecture";
} }
feature with-defaults { feature with-defaults {
description description
"NETCONF :with-defaults capability; If the server advertises "NETCONF :with-defaults capability; If the server advertises
the :with-defaults capability for a session, then this the :with-defaults capability for a session, then this
feature must also be enabled for that session. Otherwise, feature must also be enabled for that session. Otherwise,
this feature must not be enabled."; this feature must not be enabled.";
reference reference
"RFC 6243: With-defaults Capability for NETCONF, section 4; and "RFC 6243: With-defaults Capability for NETCONF, section 4; and
skipping to change at page 18, line 39 skipping to change at page 18, line 39
prefix: ncds prefix: ncds
reference: RFC XXXX reference: RFC XXXX
6. Security Considerations 6. Security Considerations
The YANG module defined in this document extends the base operations The YANG module defined in this document extends the base operations
of the NETCONF [RFC6241] protocol. The lowest NETCONF layer is the of the NETCONF [RFC6241] protocol. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. transport is Secure Shell (SSH) [RFC6242].
The network configuration access control model The network configuration access control model [RFC8341] provides the
[I-D.ietf-netconf-rfc6536bis] provides the means to restrict access means to restrict access for particular NETCONF users to a
for particular NETCONF users to a preconfigured subset of all preconfigured subset of all available NETCONF protocol operations and
available NETCONF protocol operations and content. content.
The security considerations for the base NETCONF protocol operations The security considerations for the base NETCONF protocol operations
(see Section 9 of [RFC6241]) apply to the new NETCONF <get-data> and (see Section 9 of [RFC6241]) apply to the new NETCONF <get-data> and
<edit-data> operations defined in this document. <edit-data> operations defined in this document.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-netconf-rfc6536bis]
Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Module", draft-ietf-netconf-rfc6536bis-09
(work in progress), December 2017.
[I-D.ietf-netconf-rfc7895bis] [I-D.ietf-netconf-rfc7895bis]
Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K.,
and R. Wilton, "YANG Library", draft-ietf-netconf- and R. Wilton, "YANG Library", draft-ietf-netconf-
rfc7895bis-05 (work in progress), February 2018. rfc7895bis-06 (work in progress), April 2018.
[I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), January 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, <https://www.rfc-editor.org/info/ RFC2119, March 1997, <https://www.rfc-editor.org/info/
rfc2119>. rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
skipping to change at page 20, line 13 skipping to change at page 20, line 5
editor.org/info/rfc6991>. editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, DOI 10.17487/
RFC8341, March 2018, <https://www.rfc-editor.org/info/
rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
7.2. Informative References 7.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams] [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
ietf-netmod-yang-tree-diagrams-06 (work in progress), <https://www.rfc-editor.org/info/rfc8340>.
February 2018.
Authors' Addresses Authors' Addresses
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
Email: mbj@tail-f.com Email: mbj@tail-f.com
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Jacobs University
 End of changes. 30 change blocks. 
60 lines changed or deleted 58 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/