draft-ietf-netconf-nmda-netconf-07.txt   draft-ietf-netconf-nmda-netconf-08.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: April 12, 2019 P. Shafer Expires: April 20, 2019 P. Shafer
K. Watsen K. Watsen
Juniper Networks Juniper Networks
R. Wilton R. Wilton
Cisco Systems Cisco Systems
October 9, 2018 October 17, 2018
NETCONF Extensions to Support the Network Management Datastore NETCONF Extensions to Support the Network Management Datastore
Architecture Architecture
draft-ietf-netconf-nmda-netconf-07 draft-ietf-netconf-nmda-netconf-08
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 RFC 8342. 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
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 April 12, 2019. This Internet-Draft will expire on April 20, 2019.
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 3, line 14 skipping to change at page 3, line 14
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 [RFC8342]. This document uses the terminology defined by the NMDA [RFC8342].
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 content identifier
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
skipping to change at page 3, line 46 skipping to change at page 3, line 46
A NETCONF client can discover which datastores and YANG modules the A NETCONF client can discover which datastores and YANG modules the
server supports by reading the YANG library information from the server supports by reading the YANG library information from the
operational state datastore. 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>&content-id=<content-id-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 "content-id" contains the YANG library content
[I-D.ietf-netconf-rfc7895bis]. This parameter MUST be present. identifier [I-D.ietf-netconf-rfc7895bis]. This parameter MUST be
present.
With this mechanism, a client can cache the supported datastores and With this mechanism, a client can cache the supported datastores and
YANG modules for a server and only update the cache if the "checksum" YANG modules for a server and only update the cache if the
value in the <hello> message changes. "content-id" 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
 End of changes. 8 change blocks. 
10 lines changed or deleted 11 lines changed or added

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