draft-ietf-netconf-with-defaults-12.txt   draft-ietf-netconf-with-defaults-13.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: April 17, 2011 Ericsson Expires: May 13, 2011 Ericsson
October 14, 2010 November 9, 2010
With-defaults capability for NETCONF With-defaults capability for NETCONF
draft-ietf-netconf-with-defaults-12 draft-ietf-netconf-with-defaults-13
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 April 17, 2011. This Internet-Draft will expire on May 13, 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 42 skipping to change at page 2, line 42
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 . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . . . . . . 11
4.3. Conformance . . . . . . . . . . . . . . . . . . . . . . . 11 4.3. Capability Identifier . . . . . . . . . . . . . . . . . . 11
4.4. Capability Identifier . . . . . . . . . . . . . . . . . . 11 4.4. New Operations . . . . . . . . . . . . . . . . . . . . . . 11
4.5. New Operations . . . . . . . . . . . . . . . . . . . . . . 11 4.5. Modifications to Existing Operations . . . . . . . . . . . 11
4.6. Modifications to Existing Operations . . . . . . . . . . . 11 4.5.1. <get>, <get-config>, and <copy-config> Operations . . 11
4.6.1. <get>, <get-config>, and <copy-config> Operations . . 11 4.5.2. <edit-config> Operation . . . . . . . . . . . . . . . 13
4.6.2. <edit-config> Operation . . . . . . . . . . . . . . . 13 4.5.3. Other Operations . . . . . . . . . . . . . . . . . . . 13
4.6.3. Other Operations . . . . . . . . . . . . . . . . . . . 13 4.6. Interactions with Other Capabilities . . . . . . . . . . . 14
4.7. Interactions with Other Capabilities . . . . . . . . . . . 14
5. YANG Module for the <with-defaults> Parameter . . . . . . . . 14 5. YANG Module for the <with-defaults> Parameter . . . . . . . . 14
6. XSD for the 'wd:default' Attribute . . . . . . . . . . . . . . 17 6. XSD for the 'default' Attribute . . . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
10. Normative References . . . . . . . . . . . . . . . . . . . . . 19 10. Normative References . . . . . . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . . . . 22 A.2. Example Data Set . . . . . . . . . . . . . . . . . . . . . 22
A.3. Protocol Operation Examples . . . . . . . . . . . . . . . 23 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' . . . . . . . . . . . . . . . 27 A.3.3. <with-defaults> = 'trim' . . . . . . . . . . . . . . . 27
A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 28 A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 28
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 29 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 29
B.1. 11-12 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.1. 12-13 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.2. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.2. 11-12 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.3. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.3. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.4. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.4. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.5. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.5. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.6. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.6. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.7. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.7. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.8. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.8. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.9. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 31 B.9. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.10. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 31 B.10. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.11. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 31 B.11. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 31
B.12. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 31 B.12. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
B.13. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 B.13. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
B.14. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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
skipping to change at page 7, line 13 skipping to change at page 7, line 13
data node to be default data, even schema default data. data node to be default data, even schema default data.
2.1.1. 'report-all' Basic Mode Retrieval 2.1.1. 'report-all' Basic Mode Retrieval
When data is retrieved from a server using the 'report-all' basic When data is retrieved from a server using the 'report-all' basic
mode, and the <with-defaults> parameter is not present, all data mode, and the <with-defaults> parameter is not present, all data
nodes MUST be reported. nodes MUST be reported.
2.1.2. 'report-all' <with-defaults> Retrieval 2.1.2. 'report-all' <with-defaults> Retrieval
The server MUST support the <with-defaults> parameter with a value If the 'report-all' basic mode is used by the server, then the server
equal to 'report-all', as specified in Section 3.1. MUST support the <with-defaults> parameter with a value equal to
'report-all', as specified in Section 3.1.
2.1.3. 'report-all' <edit-config> and <copy-config> Behavior 2.1.3. 'report-all' <edit-config> and <copy-config> Behavior
The server MUST consider every data node to exist, even those The server MUST consider every data node to exist, even those
containing a schema default value. A valid 'create' operation containing a schema default value. A valid 'create' operation
attribute for a data node that contains its schema default value MUST attribute for a data node that contains its schema default value MUST
fail with a 'data-exists' error-tag. A valid 'delete' operation fail with a 'data-exists' error-tag. A valid 'delete' operation
attribute for a data node that contains its schema default value MUST attribute for a data node that contains its schema default value MUST
succeed, even though the data node is immediately replaced by the succeed, even though the data node is immediately replaced by the
server with the default value. server with the default value.
A server which uses the 'report-all' basic-mode has no concept of a A server which uses the 'report-all' basic-mode has no concept of a
default node, so the 'report-all-tagged' <with-defaults> retrieval default node, so the 'report-all-tagged' <with-defaults> retrieval
mode is not relevant. There will never be any tagged nodes, since mode is not relevant. There will never be any tagged nodes, since
there are no nodes which are omitted in a basic-mode retrieval there are no nodes which are omitted in a basic-mode retrieval
operation. If the wd:default attribute is present in any operation. If the 'default' attribute is present in any
configuration data, the server MUST return an <rpc-error> response configuration data, the server MUST return an <rpc-error> response
with an 'unknown-attribute' error-tag. with an 'unknown-attribute' error-tag.
2.2. 'trim' Basic Mode 2.2. 'trim' Basic Mode
A server which uses the 'trim' basic mode MUST consider any data node A server which uses the 'trim' basic mode MUST consider any data node
set to its schema default value to be default data. set to its schema default value to be default data.
2.2.1. 'trim' Basic Mode Retrieval 2.2.1. 'trim' Basic Mode Retrieval
When data is retrieved from a server using the 'trim' basic mode, and When data is retrieved from a server using the 'trim' basic mode, and
the <with-defaults> parameter is not present, data nodes MUST NOT be the <with-defaults> parameter is not present, data nodes MUST NOT be
reported if they contain the schema default value. Non-configuration reported if they contain the schema default value. Non-configuration
data nodes containing the schema default value MUST NOT be reported. data nodes containing the schema default value MUST NOT be reported.
2.2.2. 'trim' <with-defaults> Retrieval 2.2.2. 'trim' <with-defaults> Retrieval
The server MUST support the <with-defaults> parameter with a value If the 'trim' basic mode is used by the server, then the server MUST
equal to 'trim', as specified in Section 3.1. support the <with-defaults> parameter with a value equal to 'trim',
as specified in Section 3.2.
2.2.3. 'trim' <edit-config> and <copy-config> Behavior 2.2.3. 'trim' <edit-config> and <copy-config> Behavior
The server MUST consider any data node that does not contain its The server MUST consider any data node that does not contain its
schema default value to exist. A valid 'create' operation attribute schema default value to exist. A valid 'create' operation attribute
for a data node that has a schema default value defined MUST succeed. for a data node that has a schema default value defined MUST succeed.
A valid 'delete' operation attribute for a missing data node that has A valid 'delete' operation attribute for a missing data node that has
a schema default value MUST fail. The server MUST return an <rpc- a schema default value MUST fail. The server MUST return an <rpc-
error> response with a 'data-missing' error-tag. error> response with a 'data-missing' error-tag.
If a client sets a data node to its schema default value, using any If a client sets a data node to its schema default value, using any
valid operation, it MUST succeed, although the data node MUST NOT be valid operation, it MUST succeed, although the data node MUST NOT be
saved in the NETCONF configuration datastore. This has the same saved in the NETCONF configuration datastore. This has the same
effect as removing the data node and treating it as default data. effect as removing the data node and treating it as default data.
If the server supports the 'report-all-tagged' value for the <with- If the server supports the 'report-all-tagged' value for the <with-
defaults> parameter, then the 'wd:default' attribute MUST be accepted defaults> parameter, then the 'default' attribute MUST be accepted in
in configuration input, as described in Section 4.6.1 and configuration input, as described in Section 4.5.1 and Section 4.5.2.
Section 4.6.2.
2.3. 'explicit' Basic Mode 2.3. 'explicit' Basic Mode
A server which uses the 'explicit' basic mode MUST consider any data A server which uses the 'explicit' basic mode MUST consider any data
node that is not explicitly set data to be default data. node that is not explicitly set data to be default data.
2.3.1. 'explicit' Basic Mode Retrieval 2.3.1. 'explicit' Basic Mode Retrieval
If a client sets a data node to its schema default value, it MUST When data is retrieved from a server using the 'explicit' basic mode,
always be reported. If the server sets a data node to its schema and the <with-defaults> parameter is not present, data nodes MUST be
default value, it MUST NOT be reported. Non-configuration data nodes reported if explicitly set by the client, even if they contain the
containing the schema default value MUST be reported. schema default value. Non-configuration data nodes containing the
schema default value MUST be reported.
2.3.2. 'explicit' <with-defaults> Retrieval 2.3.2. 'explicit' <with-defaults> Retrieval
The server MUST support the <with-defaults> parameter with a value If the 'explicit' basic mode is used by the server, the server MUST
equal to 'explicit', as specified in Section 3.3. support the <with-defaults> parameter with a value equal to
'explicit', as specified in Section 3.3.
2.3.3. 'explicit' <edit-config> and <copy-config> Behavior 2.3.3. 'explicit' <edit-config> and <copy-config> Behavior
The server considers any data node that is explicitly set data to The server considers any data node that is explicitly set data to
exist. A valid 'create' operation attribute for a data node that has exist. A valid 'create' operation attribute for a data node that has
been set by a client to its schema default value MUST fail with a been set by a client to its schema default value MUST fail with a
'data-exists' error-tag. A valid 'create' operation attribute for a 'data-exists' error-tag. A valid 'create' operation attribute for a
data node that has been set by the server to its schema default value data node that has been set by the server to its schema default value
MUST succeed. A valid 'delete' operation attribute for a data node MUST succeed. A valid 'delete' operation attribute for a data node
that has been set by a client to its schema default value MUST that has been set by a client to its schema default value MUST
succeed. A valid 'delete' operation attribute for a data node that succeed. A valid 'delete' operation attribute for a data node that
has been set by the server to its schema default value MUST fail with has been set by the server to its schema default value MUST fail with
a 'data-missing' error-tag. a 'data-missing' error-tag.
If the server supports the 'report-all-tagged' retrieval mode in its If the server supports the 'report-all-tagged' retrieval mode in its
:with-defaults capability, then the 'wd:default' attribute MUST be :with-defaults capability, then the 'default' attribute MUST be
accepted in configuration input. If all NETCONF <edit-config> or accepted in configuration input. If all NETCONF <edit-config> or
<copy-config> parameters are valid, then the server will treat a wd: <copy-config> parameters are valid, then the server will treat a
default="true" tagged data node as a request to return that node to tagged data node (i.e., the 'default' attribute set to 'true' or '1')
default data. If this request is valid within the context of the as a request to return that node to default data. If this request is
requested NETCONF operation, then the data node is removed and valid within the context of the requested NETCONF operation, then the
returned to its default value. The data node within the NETCONF data node is removed and returned to its default value. The data
message MUST contain a value in this case, which MUST be equal to the node within the NETCONF message MUST contain a value in this case,
schema default value. If not, the server MUST return an <rpc-error> which MUST be equal to the schema default value. If not, the server
response with a 'invalid-value' error-tag. MUST return an <rpc-error> response with a 'invalid-value' error-tag.
3. Retrieval of Default Data 3. Retrieval of Default Data
This document defines a new parameter, called <with-defaults>, which This document defines a new parameter, called <with-defaults>, which
can be added to specific NETCONF operation request messages to can be added to specific NETCONF operation request messages to
control how retrieval of default data is treated by the server. control how retrieval of default data is treated by the server.
A server which implements this specification MUST accept the <with- A server which implements this specification MUST accept the <with-
defaults> parameter containing the enumeration for any of the defaults> parameter containing the enumeration for any of the
defaults handling modes it supports. The <with-defaults> parameter defaults handling modes it supports. The <with-defaults> parameter
skipping to change at page 10, line 20 skipping to change at page 10, line 20
:with-defaults capability contains the 'report-all-tagged' option. :with-defaults capability contains the 'report-all-tagged' option.
Refer to Section 4 for encoding details for this capability. Refer to Section 4 for encoding details for this capability.
In this mode the server returns all data nodes, just like the In this mode the server returns all data nodes, just like the
'report-all' mode, except a data node that is considered by the 'report-all' mode, except a data node that is considered by the
server to contain default data will include an XML attribute to server to contain default data will include an XML attribute to
indicate this condition. This is useful for an application to indicate this condition. This is useful for an application to
determine which nodes are considered to contain default data by the determine which nodes are considered to contain default data by the
server, within a single retrieval operation. server, within a single retrieval operation.
A server which supports 'report-all-tagged' MUST also accept the 'wd: A server which supports 'report-all-tagged' MUST also accept the
default' XML attribute within configuration input to the <edit- 'default' XML attribute within configuration input to the <edit-
config> or <copy-config> operations. Refer to Section 6 for XML config> or <copy-config> operations. Refer to Section 6 for XML
encoding details of the 'wd:default' XML attribute. encoding details of the 'default' XML attribute.
4. With-defaults Capability 4. With-defaults Capability
4.1. Overview 4.1. Overview
The :with-defaults capability indicates which defaults handling basic The :with-defaults capability indicates which defaults handling basic
mode is supported by the server. It may also indicate support for mode is supported by the server. It may also indicate support for
additional defaults retrieval modes. These retrieval modes allow a additional defaults retrieval modes. These retrieval modes allow a
NETCONF client to control whether default data is returned by the NETCONF client to control whether default data is returned by the
server. The capability affects both configuration and state data server. The capability affects both configuration and state data
(while acknowledging that the usage of default values for state data (while acknowledging that the usage of default values for state data
is less prevalent). Sending of default data is controlled for each is less prevalent). Sending of default data is controlled for each
individual operation separately. individual operation separately.
A NETCONF server implementing the :with-defaults capability: A NETCONF server implementing the :with-defaults capability:
o MUST indicate its basic mode behavior by including the 'basic- o MUST indicate its basic mode behavior by including the 'basic-
mode' parameter in the capability URI, as defined in Section 4.4. mode' parameter in the capability URI, as defined in Section 4.3.
o MUST support the YANG module defined in Section 5. o MUST support the YANG module defined in Section 5 for the defaults
o SHOULD support the 'report-all' or 'report-all-tagged' defaults handling mode indicated by the 'basic-mode' parameter.
handling mode. o SHOULD support the YANG module in Section 5 for the defaults
o MAY support additional defaults handling modes. handling mode identified by the 'report-all' or 'report-all-
tagged' enumeration value.
o If the 'report-all-tagged' defaults handling mode is supported,
then the 'default' attribute MUST be supported.
o MAY support the YANG module in Section 5 for additional defaults
handling modes.
4.2. Dependencies 4.2. Dependencies
None None
4.3. Conformance 4.3. Capability Identifier
Every NETCONF server SHOULD implement this capability.
4.4. Capability Identifier
urn:ietf:params:netconf:capability:with-defaults:1.0 urn:ietf:params:netconf:capability:with-defaults:1.0
The identifier MUST have a parameter: "basic-mode". This indicates The identifier MUST have a parameter: "basic-mode". This indicates
how the server will treat default data, as defined in Section 2. The how the server will treat default data, as defined in Section 2. The
allowed values of this parameter are 'report-all', 'trim', and allowed values of this parameter are 'report-all', 'trim', and
'explicit', as defined in Section 2. 'explicit', as defined in Section 2.
The identifier MAY have another parameter: "also-supported". This The identifier MAY have another parameter: "also-supported". This
parameter indicates which additional default handling modes the parameter indicates which additional enumeration values (besides the
server supports. The value of the parameter is a comma separated basic-mode enumeration), the server will accept for the <with-
list of one or more modes that are supported beside the mode defaults> parameter in Section 5. The value of the parameter is a
indicated in the 'basic-mode' parameter. Possible modes are 'report- comma separated list of one or more modes that are supported beside
all', 'report-all-tagged', 'trim', and 'explicit', as defined in the mode indicated in the 'basic-mode' parameter. Possible modes are
Section 3. 'report-all', 'report-all-tagged', 'trim', and 'explicit', as defined
in 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 [RFC6020]. capability URI according to the rules specified in [RFC6020].
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.4. New Operations
None None
4.6. Modifications to Existing Operations 4.5. Modifications to Existing Operations
4.6.1. <get>, <get-config>, and <copy-config> Operations 4.5.1. <get>, <get-config>, and <copy-config> Operations
A new <with-defaults> XML element is added to the input for the A new <with-defaults> XML element is added to the input for the
<get>, <get-config> and <copy-config> operations. If the <with- <get>, <get-config> and <copy-config> operations. If the <with-
defaults> element is present, it controls the reporting of default defaults> element is present, it controls the reporting of default
data. The server MUST return default data in the NETCONF <rpc-reply> data. The server MUST return default data in the NETCONF <rpc-reply>
messages according to the value of this element, if the server messages according to the value of this element, if the server
supports the specified retrieval mode. supports the specified retrieval mode.
This parameter only controls these specified retrieval operations, This parameter only controls these specified retrieval operations,
and does not impact any other operations or the non-volatile storage and does not impact any other operations or the non-volatile storage
skipping to change at page 12, line 24 skipping to change at page 12, line 25
defaults-type' typedef in Section 5. The allowed values for a defaults-type' typedef in Section 5. The allowed values for a
particular server are restricted to the values that the server particular server are restricted to the values that the server
indicates it supports within the :with-defaults capability, in the indicates it supports within the :with-defaults capability, in the
'basic-mode' and 'also-supported' parameters. 'basic-mode' and 'also-supported' parameters.
If an unsupported value is used, the NETCONF server MUST return an If an unsupported value is used, the NETCONF server MUST return an
<rpc-error> response with an 'invalid-value' error-tag. <rpc-error> response with an 'invalid-value' error-tag.
If the <with-defaults> element is not present, the server MUST follow If the <with-defaults> element is not present, the server MUST follow
its basic mode behavior as indicated by the :with-defaults capability its basic mode behavior as indicated by the :with-defaults capability
identifier's 'basic-mode' parameter, defined in Section 4.4. identifier's 'basic-mode' parameter, defined in Section 4.3.
The <get> and <get-config> operations support a separate filtering The <get> and <get-config> operations support a separate filtering
mechanism, using the <filter> parameter. The defaults filtering is mechanism, using the <filter> parameter. The defaults filtering is
conceptually done before the <filter> parameter is processed. For conceptually done before the <filter> parameter is processed. For
example, if the <with-defaults> parameter is equal to 'report-all', example, if the <with-defaults> parameter is equal to 'report-all',
then the <filter> parameter is conceptually applied to all data nodes then the <filter> parameter is conceptually applied to all data nodes
and all default data. and all default data.
The <copy-config> operation is only affected by the <with-defaults> The <copy-config> operation is only affected by the <with-defaults>
parameter if the target of the operation is specified with the <url> parameter if the target of the operation is specified with the <url>
parameter. If the target is a NETCONF configuration datastore (i.e., parameter. If the target is a NETCONF configuration datastore (i.e.,
running, candidate or startup), the <with-defaults> parameter has no running, candidate or startup), the <with-defaults> parameter has no
effect. The server MUST use its basic mode when copying data to a effect. The server MUST use its basic mode when copying data to a
NETCONF configuration datastore. If the <with-defaults> parameter is NETCONF configuration datastore. If the <with-defaults> parameter is
present in this case, it MUST be silently ignored by the server. present in this case, it MUST be silently ignored by the server.
If the server supports the 'report-all-tagged' mode, then the 'wd: If the server supports the 'report-all-tagged' mode, then the
default' attribute defined in Section 6 also impacts the <copy- 'default' attribute defined in Section 6 also impacts the <copy-
config> operation. If the wd:default attribute is present and set to config> operation. If the 'default' attribute is present and set to
'true', then the server MUST treat the new data node as a request to 'true' or '1', then the server MUST treat the new data node as a
return that node to its default value (i.e., remove it from the request to return that node to its default value (i.e., remove it
configuration datastore). The data node within the NETCONF message from the configuration datastore). The data node within the NETCONF
MUST contain a value in this case, which MUST be equal to the schema message MUST contain a value in this case, which MUST be equal to the
default value. If not, the server MUST return an <rpc-error> schema default value. If not, the server MUST return an <rpc-error>
response with a 'invalid-value' error-tag. response with a 'invalid-value' error-tag.
4.6.2. <edit-config> Operation 4.5.2. <edit-config> Operation
The <edit-config> operation has several editing modes. The 'create' The <edit-config> operation has several editing modes. The 'create'
and 'delete' editing operations are affected by the defaults handling and 'delete' editing operations are affected by the defaults handling
basic mode. The other enumeration values for the NETCONF operation basic mode. The other enumeration values for the NETCONF operation
attribute are not affected. attribute are not affected.
If the operation attribute contains the value 'create', and the data If the operation attribute contains the value 'create', and the data
node already exists in the target configuration datastore, then the node already exists in the target configuration datastore, then the
server MUST return an <rpc-error> response with a 'invalid-value' server MUST return an <rpc-error> response with a 'invalid-value'
error-tag. error-tag.
If the client sets a data node to its schema default value, the If the client sets a data node to its schema default value, the
server MUST accept the request if it is valid. The server MUST keep server MUST accept the request if it is valid. The server MUST keep
or discard the new value based on its defaults handling basic mode. or discard the new value based on its defaults handling basic mode.
For the 'trim' basic mode, all schema default values are discarded, For the 'trim' basic mode, all schema default values are discarded,
otherwise a client-provided schema default value is saved in a otherwise a client-provided schema default value is saved in a
NETCONF configuration datastore. NETCONF configuration datastore.
If the server supports the 'report-all-tagged' mode, then the 'wd: If the server supports the 'report-all-tagged' mode, then the
default' attribute defined in Section 6 also impacts the <edit- 'default' attribute defined in Section 6 also impacts the <edit-
config> operation. If the wd:default attribute is present and set to config> operation. If the 'default' attribute is present and set to
'true', then the server MUST treat the new data node as a request to 'true' or '1', then the server MUST treat the new data node as a
return that node to its default value (i.e., remove it from the request to return that node to its default value (i.e., remove it
configuration datastore). The data node within the NETCONF message from the configuration datastore). The data node within the NETCONF
MUST contain a value in this case, which MUST be equal to the schema message MUST contain a value in this case, which MUST be equal to the
default value. If not, the server MUST return an <rpc-error> schema default value. If not, the server MUST return an <rpc-error>
response with a 'invalid-value' error-tag. response with a 'invalid-value' error-tag.
If the wd:default attribute is present, then the effective operation If the 'default' attribute is present, then the effective operation
for the target data node MUST be 'create', 'merge' or 'replace'. If for the target data node MUST be 'create', 'merge' or 'replace'. If
not, then the server MUST return an <rpc-error> response with an not, then the server MUST return an <rpc-error> response with an
'invalid-value' error-tag. For example, if 'create' is the effective 'invalid-value' error-tag. For example, if 'create' is the effective
operation, then the create request must be valid on its own (e.g., operation, then the create request must be valid on its own (e.g.,
current data node MUST NOT exist). The procedure for determining the current data node MUST NOT exist). The procedure for determining the
effective operation is defined in [I-D.ietf-netconf-4741bis]. It is effective operation is defined in [I-D.ietf-netconf-4741bis]. It is
derived from the 'default-operation' parameter and/or any operation derived from the 'default-operation' parameter and/or any operation
attributes that are present in the data node or any of its ancestor attributes that are present in the data node or any of its ancestor
nodes, within the <edit-config> request. nodes, within the <edit-config> request.
4.6.3. Other Operations 4.5.3. Other Operations
Other operations that return configuration data SHOULD also handle Other operations that return configuration data SHOULD also handle
default data according to the rules set in this document, and default data according to the rules set in this document, and
explicitly state this in their documentation. If this is not explicitly state this in their documentation. If this is not
specified in the document defining the respective operation, the specified in the document defining the respective operation, the
default handling rules described herein do not affect these default handling rules described herein do not affect these
operations. operations.
4.7. Interactions with Other Capabilities 4.6. 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 [RFC6020]. The above operations are The YANG language is defined in [RFC6020]. The above operations are
defined in YANG in [I-D.ietf-netconf-4741bis]. Every NETCONF server defined in YANG in [I-D.ietf-netconf-4741bis]. Every NETCONF server
which supports the :with-defaults capability MUST implement this YANG which supports the :with-defaults capability MUST implement this YANG
module. module.
<CODE BEGINS> file="ietf-netconf-with-defaults@2010-06-09.yang" <CODE BEGINS> file="ietf-netconf-with-defaults@2010-11-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; }
organization organization
skipping to change at page 15, line 21 skipping to change at page 15, line 21
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this note // RFC Ed.: replace XXXX with actual RFC number and remove this note
// RFC Ed.: remove this note // RFC Ed.: remove this note
// Note: extracted from draft-ietf-netmod-with-defaults-10.txt // Note: extracted from draft-ietf-netmod-with-defaults-13.txt
revision 2010-06-09 { revision 2010-11-09 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXXX: With-defaults capability for NETCONF"; "RFC XXXX: With-defaults capability for NETCONF";
} }
// RFC Ed.: replace XXXX with actual // RFC Ed.: replace XXXX with actual
// RFC number and remove this note // RFC number and remove this note
typedef with-defaults-mode { typedef with-defaults-mode {
description description
skipping to change at page 16, line 6 skipping to change at page 16, line 6
reference reference
"RFC XXXX; section 3.1"; "RFC XXXX; section 3.1";
// RFC Ed.: replace XXXX with actual // RFC Ed.: replace XXXX with actual
// RFC number and remove this note // RFC number and remove this note
} }
enum report-all-tagged { enum report-all-tagged {
description description
"All default data is reported. "All default data is reported.
Any nodes considered to be default data Any nodes considered to be default data
will contain a 'wd:default' XML attribute, will contain a 'default' XML attribute,
set to 'true'."; set to 'true' or '1'.";
reference reference
"RFC XXXX; section 3.4"; "RFC XXXX; section 3.4";
// RFC Ed.: replace XXXX with actual // RFC Ed.: replace XXXX with actual
// RFC number and remove this note // RFC number and remove this note
} }
enum trim { enum trim {
description description
"Values are not reported if they contain the default."; "Values are not reported if they contain the default.";
reference reference
"RFC XXXX; section 3.2"; "RFC XXXX; section 3.2";
skipping to change at page 17, line 46 skipping to change at page 17, line 46
// RFC Ed.: replace XXXX with actual // RFC Ed.: replace XXXX with actual
// RFC number and remove this note // RFC number and remove this note
uses with-defaults-parameters; uses with-defaults-parameters;
} }
} }
<CODE ENDS> <CODE ENDS>
6. XSD for the 'wd:default' Attribute 6. XSD for the 'default' Attribute
The following XML Schema document defines the 'default' attribute, The following XML Schema document [W3C.REC-xml-20081126] defines the
described within this document. This XSD is only relevant if the 'default' attribute, described within this document. This XSD is
server supports the 'report-all-tagged' defaults retrieval mode. only relevant if the server supports the 'report-all-tagged' defaults
retrieval mode.
The 'default' attribute uses the XSD data type 'boolean'. In
accordance with Section 3.2.2.1 of XML Schema Part 2: Datatypes, the
allowable lexical representations for the xs:boolean datatype are the
strings "0" and "false" for the concept of false and the strings "1"
and "true" for the concept of true. Implementations MUST support
both styles of lexical representation.
<CODE BEGINS> file="defaults.xsd" <CODE BEGINS> file="defaults.xsd"
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:netconf:default:1.0" xmlns="urn:ietf:params:xml:ns:netconf:default:1.0"
targetNamespace="urn:ietf:params:xml:ns:netconf:default:1.0" targetNamespace="urn:ietf:params:xml:ns:netconf:default:1.0"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified" attributeFormDefault="unqualified"
xml:lang="en"> xml:lang="en">
skipping to change at page 18, line 31 skipping to change at page 18, line 39
</xs:annotation> </xs:annotation>
<!-- <!--
default attribute default attribute
--> -->
<xs:attribute name="default" type="xs:boolean" default="false"> <xs:attribute name="default" type="xs:boolean" default="false">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
This attribute indicates whether the data node represented This attribute indicates whether the data node represented
by the XML element containing this attribute is considered by the XML element containing this attribute is considered
by the server to be default data. If set to 'true' then by the server to be default data. If set to 'true' or '1' then
the data node is default data. If 'false', then the the data node is default data. If 'false' or '0', then the
data node is not default data. data node is not default data.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:attribute> </xs:attribute>
</xs:schema> </xs:schema>
<CODE ENDS> <CODE ENDS>
7. IANA Considerations 7. IANA Considerations
skipping to change at page 20, line 16 skipping to change at page 20, line 23
[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 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. 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-04 (work in progress), draft-ietf-netconf-4741bis-06 (work in progress),
August 2010. October 2010.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Sperberg-McQueen, C., Yergeau, F., Bray, T., Paoli, J., Yergeau, F., Maler, E., Paoli, J., Sperberg-McQueen, C.,
and E. Maler, "Extensible Markup Language (XML) 1.0 (Fifth and T. Bray, "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>.
[W3C.REC-xmlschema-0-20041028]
Walmsley, P. and D. Fallside, "XML Schema Part 0: Primer
Second Edition", World Wide Web Consortium
Recommendation REC-xmlschema-0-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-0-20041028>.
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
data model. data model.
Note that this is not a real module, and implementation of this Note that this is not a real module, and implementation of this
module is not required for conformance to the :with-defaults module is not required for conformance to the :with-defaults
skipping to change at page 24, line 50 skipping to change at page 24, line 50
<status>waking up</status> <status>waking up</status>
</interface> </interface>
</interfaces> </interfaces>
</data> </data>
</rpc-reply> </rpc-reply>
A.3.2. <with-defaults> = 'report-all-tagged' A.3.2. <with-defaults> = 'report-all-tagged'
The behavior of the <with-defaults> parameter handling for the value The behavior of the <with-defaults> parameter handling for the value
'report-all-tagged' is demonstrated in this example. A 'tagged' data 'report-all-tagged' is demonstrated in this example. A 'tagged' data
node is an element that contains the wd:default XML attribute, set to node is an element that contains the 'default' XML attribute, set to
'true'. 'true' or '1'.
The actual data nodes tagged by the server depends on the defaults The actual data nodes tagged by the server depends on the defaults
handling basic mode used by the server. Only the data nodes that are handling basic mode used by the server. Only the data nodes that are
considered to be default data will be tagged. considered to be default data will be tagged.
In this example, the server's basic mode is equal to 'trim', so all In this example, the server's basic mode is equal to 'trim', so all
data nodes that would contain the schema default value are tagged. data nodes that would contain the schema default value are tagged.
If the server's basic mode is 'explicit', then only data nodes that If the server's basic mode is 'explicit', then only data nodes that
are not explicitly set data are tagged. If the server's basic mode are not explicitly set data are tagged. If the server's basic mode
is 'report-all', then no data nodes are tagged. is 'report-all', then no data nodes are tagged.
skipping to change at page 29, 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. 11-12 B.1. 12-13
Removed with-defaults capability conformance section.
Changed 'wd:default' to 'default'.
Added normative reference to XSD.
Clarified conditional support for with-defaults enumerations, based
on capability parameters.
Clarified that all xs:boolean encoding values must be supported.
Clarified purpose of also-supported parameter in capability URI.
B.2. 11-12
Made editorial clarifications based on AD review. Made editorial clarifications based on AD review.
B.2. 10-11 B.3. 10-11
Changed term 'database' to 'configuration datastore' or generic Changed term 'database' to 'configuration datastore' or generic
'datastore'. 'datastore'.
B.3. 09-10 B.4. 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.4. 08-09 B.5. 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.5. 07-08 B.6. 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.6. 06-07 B.7. 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.7. 05-06 B.8. 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 30, line 38 skipping to change at page 31, line 6
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.8. 04-05 B.9. 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 31, line 18 skipping to change at page 31, line 34
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.9. 03-04 B.10. 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.10. 02-03 B.11. 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.11. 01-02 B.12. 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.12. 00-01 B.13. 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.13. -00 B.14. -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. 54 change blocks. 
125 lines changed or deleted 159 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/