draft-ietf-netconf-with-defaults-11.txt   draft-ietf-netconf-with-defaults-12.txt 
NETCONF A. Bierman NETCONF A. Bierman
Internet-Draft Brocade Internet-Draft Brocade
Intended status: Standards Track B. Lengyel Intended status: Standards Track B. Lengyel
Expires: February 14, 2011 Ericsson Expires: April 17, 2011 Ericsson
August 13, 2010 October 14, 2010
With-defaults capability for NETCONF With-defaults capability for NETCONF
draft-ietf-netconf-with-defaults-11 draft-ietf-netconf-with-defaults-12
Abstract Abstract
The NETCONF protocol defines ways to read and edit configuration data The NETCONF protocol defines ways to read and edit configuration data
from a NETCONF server. In some cases, part of this data may not be from a NETCONF server. In some cases, part of this data may not be
set by the NETCONF client, but rather a default value known to the set by the NETCONF client, but rather a default value known to the
server is used instead. In many situations the NETCONF client has a server is used instead. In many situations the NETCONF client has a
priori knowledge about default data, so the NETCONF server does not priori knowledge about default data, so the NETCONF server does not
need to save it in a NETCONF configuration datastore or send it to need to save it in a NETCONF configuration datastore or send it to
the client in a retrieval operation reply. In other situations the the client in a retrieval operation reply. In other situations the
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 February 14, 2011. This Internet-Draft will expire on April 17, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 23 skipping to change at page 2, line 23
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Defaults Handling Behavior . . . . . . . . . . . . . . . . 5 1.2. Defaults Handling Behavior . . . . . . . . . . . . . . . . 5
1.3. Client Controlled Retrieval of Default Data . . . . . . . 5 1.3. Client Controlled Retrieval of Default Data . . . . . . . 5
2. Defaults Handling Basic Modes . . . . . . . . . . . . . . . . 6 2. Defaults Handling Basic Modes . . . . . . . . . . . . . . . . 6
2.1. 'report-all' Basic Mode . . . . . . . . . . . . . . . . . 6 2.1. 'report-all' Basic Mode . . . . . . . . . . . . . . . . . 6
2.1.1. 'report-all' Basic Mode Retrieval . . . . . . . . . . 6 2.1.1. 'report-all' Basic Mode Retrieval . . . . . . . . . . 7
2.1.2. 'report-all' <with-defaults> Retrieval . . . . . . . . 7 2.1.2. 'report-all' <with-defaults> Retrieval . . . . . . . . 7
2.1.3. 'report-all' <edit-config> and <copy-config> 2.1.3. 'report-all' <edit-config> and <copy-config>
Behavior . . . . . . . . . . . . . . . . . . . . . . . 7 Behavior . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. 'trim' Basic Mode . . . . . . . . . . . . . . . . . . . . 7 2.2. 'trim' Basic Mode . . . . . . . . . . . . . . . . . . . . 7
2.2.1. 'trim' Basic Mode Retrieval . . . . . . . . . . . . . 7 2.2.1. 'trim' Basic Mode Retrieval . . . . . . . . . . . . . 7
2.2.2. 'trim' <with-defaults> Retrieval . . . . . . . . . . . 7 2.2.2. 'trim' <with-defaults> Retrieval . . . . . . . . . . . 7
2.2.3. 'trim' <edit-config> and <copy-config> Behavior . . . 7 2.2.3. 'trim' <edit-config> and <copy-config> Behavior . . . 8
2.3. 'explicit' Basic Mode . . . . . . . . . . . . . . . . . . 8 2.3. 'explicit' Basic Mode . . . . . . . . . . . . . . . . . . 8
2.3.1. 'explicit' Basic Mode Retrieval . . . . . . . . . . . 8 2.3.1. 'explicit' Basic Mode Retrieval . . . . . . . . . . . 8
2.3.2. 'explicit' <with-defaults> Retrieval . . . . . . . . . 8 2.3.2. 'explicit' <with-defaults> Retrieval . . . . . . . . . 8
2.3.3. 'explicit' <edit-config> and <copy-config> Behavior . 8 2.3.3. 'explicit' <edit-config> and <copy-config> Behavior . 8
3. Retrieval of Default Data . . . . . . . . . . . . . . . . . . 9 3. Retrieval of Default Data . . . . . . . . . . . . . . . . . . 9
3.1. 'report-all' Retrieval Mode . . . . . . . . . . . . . . . 9 3.1. 'report-all' Retrieval Mode . . . . . . . . . . . . . . . 9
3.2. 'trim' Retrieval Mode . . . . . . . . . . . . . . . . . . 9 3.2. 'trim' Retrieval Mode . . . . . . . . . . . . . . . . . . 9
3.3. 'explicit' Retrieval Mode . . . . . . . . . . . . . . . . 9 3.3. 'explicit' Retrieval Mode . . . . . . . . . . . . . . . . 9
3.4. 'report-all-tagged' Retrieval Mode . . . . . . . . . . . . 9 3.4. 'report-all-tagged' Retrieval Mode . . . . . . . . . . . . 10
4. With-defaults Capability . . . . . . . . . . . . . . . . . . . 10 4. With-defaults Capability . . . . . . . . . . . . . . . . . . . 10
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Dependencies . . . . . . . . . . . . . . . . . . . . . . . 10 4.2. Dependencies . . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Conformance . . . . . . . . . . . . . . . . . . . . . . . 10 4.3. Conformance . . . . . . . . . . . . . . . . . . . . . . . 11
4.4. Capability Identifier . . . . . . . . . . . . . . . . . . 10 4.4. Capability Identifier . . . . . . . . . . . . . . . . . . 11
4.5. New Operations . . . . . . . . . . . . . . . . . . . . . . 11 4.5. New Operations . . . . . . . . . . . . . . . . . . . . . . 11
4.6. Modifications to Existing Operations . . . . . . . . . . . 11 4.6. Modifications to Existing Operations . . . . . . . . . . . 11
4.6.1. <get>, <get-config>, and <copy-config> Operations . . 11 4.6.1. <get>, <get-config>, and <copy-config> Operations . . 11
4.6.2. <edit-config> Operation . . . . . . . . . . . . . . . 12 4.6.2. <edit-config> Operation . . . . . . . . . . . . . . . 13
4.6.3. Other Operations . . . . . . . . . . . . . . . . . . . 13 4.6.3. Other Operations . . . . . . . . . . . . . . . . . . . 13
4.7. Interactions with Other Capabilities . . . . . . . . . . . 13 4.7. Interactions with Other Capabilities . . . . . . . . . . . 14
5. YANG Module for the <with-defaults> Parameter . . . . . . . . 13 5. YANG Module for the <with-defaults> Parameter . . . . . . . . 14
6. XSD for the 'wd:default' Attribute . . . . . . . . . . . . . . 17 6. XSD for the 'wd:default' Attribute . . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
10. Normative References . . . . . . . . . . . . . . . . . . . . . 19 10. Normative References . . . . . . . . . . . . . . . . . . . . . 19
Appendix A. Usage Examples . . . . . . . . . . . . . . . . . . . 20 Appendix A. Usage Examples . . . . . . . . . . . . . . . . . . . 20
A.1. Example YANG Module . . . . . . . . . . . . . . . . . . . 20 A.1. Example YANG Module . . . . . . . . . . . . . . . . . . . 20
A.2. Example Data Set . . . . . . . . . . . . . . . . . . . . . 21 A.2. Example Data Set . . . . . . . . . . . . . . . . . . . . . 22
A.3. Protocol Operation Examples . . . . . . . . . . . . . . . 22 A.3. Protocol Operation Examples . . . . . . . . . . . . . . . 23
A.3.1. <with-defaults> = 'report-all' . . . . . . . . . . . . 23 A.3.1. <with-defaults> = 'report-all' . . . . . . . . . . . . 23
A.3.2. <with-defaults> = 'report-all-tagged' . . . . . . . . 24 A.3.2. <with-defaults> = 'report-all-tagged' . . . . . . . . 24
A.3.3. <with-defaults> = 'trim' . . . . . . . . . . . . . . . 26 A.3.3. <with-defaults> = 'trim' . . . . . . . . . . . . . . . 27
A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 27 A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 28
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 28 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 29
B.1. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.1. 11-12 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.2. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.2. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.3. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.3. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.4. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.4. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.5. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.5. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.6. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.7. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.7. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.8. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.8. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.9. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.9. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.10. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.10. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.11. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.11. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.12. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 B.12. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 B.13. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
The NETCONF protocol [RFC4741] defines ways to read configuration and The NETCONF protocol [RFC4741] defines ways to read configuration and
state data from a NETCONF server. Part of the configuration data may state data from a NETCONF server. Part of the configuration data may
not be set by the NETCONF client, but rather by a default value from not be set by the NETCONF client, but rather by a default value from
the data model. In many situations the NETCONF client has a priori the data model. In many situations the NETCONF client has a priori
knowledge about default data, so the NETCONF server does not need to knowledge about default data, so the NETCONF server does not need to
send it to the client. A priori knowledge can be obtained, e.g., a send it to the client. A priori knowledge can be obtained, e.g., a
document formally describing the data models supported by the NETCONF document formally describing the data models supported by the NETCONF
skipping to change at page 4, line 32 skipping to change at page 4, line 32
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Data model schema: A document or set of documents describing the Data model schema: A document or set of documents describing the
data models supported by the NETCONF server. data models supported by the NETCONF server.
Management Application: A computer program running outside the Management Application: A computer program running outside the
NETCONF server that configures or supervises the NETCONF server. NETCONF server that configures or supervises the NETCONF server.
A management application can reach the device e.g. via NETCONF, A management application can reach the device e.g. via NETCONF,
CLI or SNMP. command line interface (CLI) or Simple Network Management Protocol
(SNMP).
Schema default data: Data specified in the data model schema as Schema default data: Data specified in the data model schema as
default, that is set or used by the device whenever the NETCONF default, that is set or used by the device whenever the NETCONF
client or other management application/user does not provide a client or other management application/user does not provide a
specific value for the relevant data node. Schema default data specific value for the relevant data node. Schema default data
MAY or may not be stored as part of a configuration datastore, may or may not be stored as part of a configuration datastore,
depending on the basic mode used by a particular server. depending on the basic mode used by a particular server.
Default data: Conceptual data containing a default value. Default Default data: Conceptual data containing a default value. Default
data is not kept in a datastore. Not all servers use the same data is not kept in a datastore. Not all servers use the same
criteria to decide if a data node is actually instantiated in a criteria to decide if a data node is actually instantiated in a
datastore. If a data node is not present in a datastore, and a datastore. If a data node is not present in a datastore, and a
schema default definition is in use by the server instead, then it schema default definition is in use by the server instead, then it
is considered to be a default data node. is considered to be a default data node.
Default value: A default value is a value for a data node instance Default value: A default value is a value for a data node instance
that is conceptually in use by the server, when the data node that is conceptually in use by the server, when the data node
instance does not exist. instance does not exist.
skipping to change at page 5, line 17 skipping to change at page 5, line 23
default data. default data.
:with-defaults: The shorthand notation for the with-defaults :with-defaults: The shorthand notation for the with-defaults
capability identifier. capability identifier.
The following terms are defined in [RFC4741]: The following terms are defined in [RFC4741]:
o client o client
o datastore o datastore
o operation o operation
o server o server
The following term is defined in [I-D.ietf-netmod-yang]: The following term is defined in [RFC6020]:
o data node o data node
1.2. Defaults Handling Behavior 1.2. Defaults Handling Behavior
The defaults handling behavior used by a server will impact NETCONF The defaults handling behavior used by a server will impact NETCONF
protocol operations in two ways: protocol operations in two ways:
1. Data retrieval: A server is normally allowed to exclude data 1. Data retrieval: A server is normally allowed to exclude data
nodes which it considers to contain the default value. The nodes which it considers to contain the default value. The
actual nodes omitted depends on the defaults handling behavior actual nodes omitted depends on the defaults handling behavior
skipping to change at page 5, line 40 skipping to change at page 5, line 46
2. Create and delete operations: The <edit-config> 'operation' 2. Create and delete operations: The <edit-config> 'operation'
attribute can be used to create and/or delete specific data attribute can be used to create and/or delete specific data
nodes. These operations depend on whether the target node nodes. These operations depend on whether the target node
currently exists or not. The server's defaults handling behavior currently exists or not. The server's defaults handling behavior
will determine whether the requested node currently exists in the will determine whether the requested node currently exists in the
configuration datastore or not. configuration datastore or not.
1.3. Client Controlled Retrieval of Default Data 1.3. Client Controlled Retrieval of Default Data
A networking device may have a large number of default values. Often A networking device may have a large number of default values. Often
the default values are not interesting or specifically defined with a the default values are specifically defined with a reasonable value,
"reasonable" value, so that the management user does not have to documented and well-known, so that the management user does not need
handle them. For these reasons it is quite common for networking to handle them. For these reasons it is quite common for networking
devices to suppress the output of parameters having the default devices to suppress the output of parameters having the default
value. value.
However, there are use-cases when a NETCONF client will need the However, there are use-cases when a NETCONF client will need the
default data from the server: default data from the server:
o The management application often needs a single, definitive and o The management application often needs a single, definitive and
complete set of configuration values that determine how the a complete set of configuration values that determine how the
networking device works. networking device works.
o Documentation about default values can be unreliable or o Documentation about default values can be unreliable or
unavailable. unavailable.
o Some management applications might not have the capabilities to o Some management applications might not have the capabilities to
correctly parse and interpret formal data models. correctly parse and interpret formal data models.
o Human users might want to understand the received data without o Human users might want to understand the received data without
consultation of the documentation. consultation of the documentation.
In all these cases, the NETCONF client will need a mechanism to In all these cases, the NETCONF client will need a mechanism to
retrieve default data from a NETCONF server. retrieve default data from a NETCONF server.
skipping to change at page 11, line 17 skipping to change at page 11, line 29
parameter indicates which additional default handling modes the parameter indicates which additional default handling modes the
server supports. The value of the parameter is a comma separated server supports. The value of the parameter is a comma separated
list of one or more modes that are supported beside the mode list of one or more modes that are supported beside the mode
indicated in the 'basic-mode' parameter. Possible modes are 'report- indicated in the 'basic-mode' parameter. Possible modes are 'report-
all', 'report-all-tagged', 'trim', and 'explicit', as defined in all', 'report-all-tagged', 'trim', and 'explicit', as defined in
Section 3. Section 3.
Note that this protocol capability URI is separate from the YANG Note that this protocol capability URI is separate from the YANG
module capability URI for the YANG module in Section 5. A server module capability URI for the YANG module in Section 5. A server
which implements this module MUST also advertise a YANG module which implements this module MUST also advertise a YANG module
capability URI according to the rules specified in capability URI according to the rules specified in [RFC6020].
[I-D.ietf-netmod-yang].
Examples: Examples:
urn:ietf:params:netconf:capability:with-defaults:1.0?basic- urn:ietf:params:netconf:capability:with-defaults:1.0?basic-
mode=explicit mode=explicit
urn:ietf:params:netconf:capability:with-defaults:1.0?basic- urn:ietf:params:netconf:capability:with-defaults:1.0?basic-
mode=explicit&also-supported=report-all,report-all-tagged mode=explicit&also-supported=report-all,report-all-tagged
4.5. New Operations 4.5. New Operations
skipping to change at page 13, line 50 skipping to change at page 14, line 13
operations. operations.
4.7. Interactions with Other Capabilities 4.7. Interactions with Other Capabilities
None None
5. YANG Module for the <with-defaults> Parameter 5. YANG Module for the <with-defaults> Parameter
The following YANG module defines the addition of the with-defaults The following YANG module defines the addition of the with-defaults
element to the <get>, <get-config>, and <copy-config> operations. element to the <get>, <get-config>, and <copy-config> operations.
The YANG language is defined in [I-D.ietf-netmod-yang]. The above The YANG language is defined in [RFC6020]. The above operations are
operations are defined in YANG in [I-D.ietf-netconf-4741bis]. Every defined in YANG in [I-D.ietf-netconf-4741bis]. Every NETCONF server
NETCONF server which supports the :with-defaults capability MUST which supports the :with-defaults capability MUST implement this YANG
implement this YANG module. module.
<CODE BEGINS> file="ietf-netconf-with-defaults@2010-06-09.yang" <CODE BEGINS> file="ietf-netconf-with-defaults@2010-06-09.yang"
module ietf-netconf-with-defaults { module ietf-netconf-with-defaults {
namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"; namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults";
prefix ncwd; prefix ncwd;
import ietf-netconf { prefix nc; } import ietf-netconf { prefix nc; }
skipping to change at page 19, line 13 skipping to change at page 19, line 20
registry', following the format defined in [RFC3688]. registry', following the format defined in [RFC3688].
URI: urn:ietf:params:xml:ns:netconf:default:1.0 URI: urn:ietf:params:xml:ns:netconf:default:1.0
URI: urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults URI: urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults
Registrant Contact: The NETCONF WG of the IETF. Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URIs are XML namespaces. XML: N/A, the requested URIs are XML namespaces.
This document registers one module name in the 'YANG Module Names' This document registers one module name in the 'YANG Module Names'
registry, defined in [I-D.ietf-netmod-yang] . registry, defined in [RFC6020] .
name: ietf-netconf-with-defaults name: ietf-netconf-with-defaults
prefix: ncwd prefix: ncwd
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults
RFC: XXXX // RFC Ed.: replace XXXX and remove this comment RFC: XXXX // RFC Ed.: replace XXXX and remove this comment
8. Security Considerations 8. Security Considerations
This document defines an extension to existing NETCONF protocol This document defines an extension to existing NETCONF protocol
operations. It does not introduce any new or increased security operations. It does not introduce any new or increased security
risks into the management system. risks into the management system.
The 'with-defaults' capability gives clients control over the The 'with-defaults' capability gives clients control over the
retrieval of default data from a NETCONF datastore. The security retrieval of default data from a NETCONF datastore. The security
consideration of [I-D.ietf-netconf-4741bis] apply to this document as consideration of [I-D.ietf-netconf-4741bis] apply to this document as
well. well.
9. Acknowledgements 9. Acknowledgements
Thanks to Martin Bjorklund, Sharon Chisholm, Phil Shafer, Juergen Thanks to Martin Bjorklund, Sharon Chisholm, Phil Shafer, Juergen
Schoenwaelder, Washam Fan and many other members of the NETCONF WG Schoenwaelder, Kent Watsen, Washam Fan and many other members of the
for providing important input to this document. NETCONF WG for providing important input to this document.
10. Normative References 10. Normative References
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741, [RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741,
December 2006. December 2006.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[I-D.ietf-netconf-4741bis] [I-D.ietf-netconf-4741bis]
Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", Bierman, "Network Configuration Protocol (NETCONF)",
draft-ietf-netconf-4741bis-03 (work in progress), draft-ietf-netconf-4741bis-04 (work in progress),
July 2010. August 2010.
[I-D.ietf-netmod-yang]
Bjorklund, M., "YANG - A data modeling language for the
Network Configuration Protocol (NETCONF)",
draft-ietf-netmod-yang-13 (work in progress), June 2010.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Paoli, J., Yergeau, F., Sperberg-McQueen, C., Maler, E., Sperberg-McQueen, C., Yergeau, F., Bray, T., Paoli, J.,
and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth and E. Maler, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008, xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
Appendix A. Usage Examples Appendix A. Usage Examples
A.1. Example YANG Module A.1. Example YANG Module
The following YANG module defines an example interfaces table to The following YANG module defines an example interfaces table to
demonstrate how the <with-defaults> parameter behaves for a specific demonstrate how the <with-defaults> parameter behaves for a specific
skipping to change at page 28, line 9 skipping to change at page 29, line 9
<status>waking up</status> <status>waking up</status>
</interface> </interface>
</interfaces> </interfaces>
</data> </data>
</rpc-reply> </rpc-reply>
Appendix B. Change Log Appendix B. Change Log
-- RFC Ed.: remove this section before publication. -- RFC Ed.: remove this section before publication.
B.1. 10-11 B.1. 11-12
Made editorial clarifications based on AD review.
B.2. 10-11
Changed term 'database' to 'configuration datastore' or generic Changed term 'database' to 'configuration datastore' or generic
'datastore'. 'datastore'.
B.2. 09-10 B.3. 09-10
Changed term 'datastore' to 'database'. Changed term 'datastore' to 'database'.
Added term 'default value'. Added term 'default value'.
Clarified verbage for data node containing a default value. Clarified verbage for data node containing a default value.
B.3. 08-09 B.4. 08-09
Removed non-volatile server requirements. Removed non-volatile server requirements.
Moved some text from basic-mode section into the the retrieval modes Moved some text from basic-mode section into the the retrieval modes
section. section.
Added description and reference statements to the YANG module. Added description and reference statements to the YANG module.
Many bugfixes and clarifications, based on WGLC review comments. Many bugfixes and clarifications, based on WGLC review comments.
B.4. 07-08 B.5. 07-08
Added report-all-tagged mode. Added report-all-tagged mode.
Changed conformance so report-all or report-all-tagged mode SHOULD be Changed conformance so report-all or report-all-tagged mode SHOULD be
supported. supported.
Clarified capability requirements for each mode, for edit-config and Clarified capability requirements for each mode, for edit-config and
NV storage requirements. NV storage requirements.
Changed rpc-error details for unsupported with-defaults value. Changed rpc-error details for unsupported with-defaults value.
Added XSD for wd:default attribute Added XSD for wd:default attribute
Expanded example to show report-all-tagged for a basic-mode=trim Expanded example to show report-all-tagged for a basic-mode=trim
server. server.
B.5. 06-07 B.6. 06-07
Removed text in capability identifier section about adding YANG Removed text in capability identifier section about adding YANG
module capability URI parameters. module capability URI parameters.
Changed YANG module namespace to match YANG format, and updated Changed YANG module namespace to match YANG format, and updated
examples to use this new namespace. examples to use this new namespace.
Fixed some typos. Fixed some typos.
B.6. 05-06 B.7. 05-06
Removed ':1.0' from capability URI. Removed ':1.0' from capability URI.
Removed open issues section because all known issues are closed. Removed open issues section because all known issues are closed.
Moved examples to a separate appendix, and expanded them. Moved examples to a separate appendix, and expanded them.
Added example.yang as an appendix to properly explain the examples Added example.yang as an appendix to properly explain the examples
used within the document. used within the document.
skipping to change at page 29, line 38 skipping to change at page 30, line 38
Clarified <with-defaults> behavior for non-configuration data nodes. Clarified <with-defaults> behavior for non-configuration data nodes.
Clarified various sections based on WGLC comments on mailing list. Clarified various sections based on WGLC comments on mailing list.
Removed some unused terms. Removed some unused terms.
Reversed the order of the change log sections so the most recent Reversed the order of the change log sections so the most recent
changes are shown first. changes are shown first.
B.7. 04-05 B.8. 04-05
Updated I-D and YANG module boiler-plate. Updated I-D and YANG module boiler-plate.
Removed redundant 'with-defaults' YANG feature. Removed redundant 'with-defaults' YANG feature.
Changed definition of 'explicit' mode to match the YANG definition Changed definition of 'explicit' mode to match the YANG definition
Removed XSD because the YANG is normative and the XSD is Removed XSD because the YANG is normative and the XSD is
unconstrained, and does not properly extend the 3 affected NETCONF unconstrained, and does not properly extend the 3 affected NETCONF
operations. operations.
skipping to change at page 30, line 18 skipping to change at page 31, line 18
the YANG module imports the ietf-netconf module in order to augment the YANG module imports the ietf-netconf module in order to augment
some operations. some operations.
Updated capability requirements to include YANG module capability Updated capability requirements to include YANG module capability
parameters. parameters.
Added a description statement to the with-defaults leaf definition. Added a description statement to the with-defaults leaf definition.
Update open issues section; ready to close all open issues. Update open issues section; ready to close all open issues.
B.8. 03-04 B.9. 03-04
Clarifications Clarifications
Added non-netconf interfaces to the definition of explicitly set Added non-netconf interfaces to the definition of explicitly set
default data default data
B.9. 02-03 B.10. 02-03
Clarifications Clarifications
YAM added YAM added
Use the same URN for the capability and the XML namespace to Use the same URN for the capability and the XML namespace to
accommodate YANG, and avoid two separate URN/URIs being advertised in accommodate YANG, and avoid two separate URN/URIs being advertised in
the HELLO message, for such a small function. the HELLO message, for such a small function.
B.10. 01-02 B.11. 01-02
report-all made mandatory report-all made mandatory
Placeholder for YAM added, XSD will be removed when 4741 provides the Placeholder for YAM added, XSD will be removed when 4741 provides the
NETCONF YAM NETCONF YAM
with-defaults is valid for state data as well (if state data has a with-defaults is valid for state data as well (if state data has a
defined default which might not be so frequent). The definition of defined default which might not be so frequent). The definition of
explicit was modified for state data. explicit was modified for state data.
B.11. 00-01 B.12. 00-01
Changed value set of with-default capability and element Changed value set of with-default capability and element
Added version to URI Added version to URI
B.12. -00 B.13. -00
Created from draft-bierman-netconf-with-defaults-01.txt Created from draft-bierman-netconf-with-defaults-01.txt
It was decided by the NETCONF mailing list, that with-defaults should It was decided by the NETCONF mailing list, that with-defaults should
be a sub-element of each affected operation. While this violates the be a sub-element of each affected operation. While this violates the
XSD of RFC4741 this is acceptable and follows the ideas behind XSD of RFC4741 this is acceptable and follows the ideas behind
NETCONF and YANG. NETCONF and YANG.
Hopefully it will be clarified in the 4741bis RFC whether such Hopefully it will be clarified in the 4741bis RFC whether such
extensions are allowed. extensions are allowed.
 End of changes. 36 change blocks. 
68 lines changed or deleted 71 lines changed or added

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