draft-ietf-netconf-with-defaults-10.txt   draft-ietf-netconf-with-defaults-11.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 12, 2011 Ericsson Expires: February 14, 2011 Ericsson
August 11, 2010 August 13, 2010
With-defaults capability for NETCONF With-defaults capability for NETCONF
draft-ietf-netconf-with-defaults-10 draft-ietf-netconf-with-defaults-11
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 database or send it to the client in a need to save it in a NETCONF configuration datastore or send it to
retrieval operation reply. In other situations the NETCONF client the client in a retrieval operation reply. In other situations the
will need this data from the server. Not all server implementations NETCONF client will need this data from the server. Not all server
treat this default data the same way. This document defines a implementations treat this default data the same way. This document
capability-based extension to the NETCONF protocol that allows the defines a capability-based extension to the NETCONF protocol that
NETCONF client to identify how defaults are processed by the server, allows the NETCONF client to identify how defaults are processed by
and also defines new mechanisms for client control of server the server, and also defines new mechanisms for client control of
processing of default data. server processing of default data.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 12, 2011. This Internet-Draft will expire on February 14, 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 3, line 18 skipping to change at page 3, line 18
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 . . . . . . . . . . . . . . . . . . . . . 21
A.3. Protocol Operation Examples . . . . . . . . . . . . . . . 22 A.3. Protocol Operation Examples . . . . . . . . . . . . . . . 22
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' . . . . . . . . . . . . . . . 26
A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 27 A.3.4. <with-defaults> = 'explicit' . . . . . . . . . . . . . 27
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 28 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 28
B.1. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.1. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
B.2. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.2. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
B.3. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.3. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
B.4. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B.4. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 28
B.5. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.5. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.6. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29 B.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.7. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.7. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.8. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.8. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.9. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.9. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.10. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.10. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.11. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.11. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.12. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
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 4, line 37 skipping to change at page 4, line 37
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. CLI or 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 database, 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 configuration database. Not all servers use data is not kept in a datastore. Not all servers use the same
the same criteria to decide if a data node is actually criteria to decide if a data node is actually instantiated in a
instantiated in a database. If a data node is not present in a datastore. If a data node is not present in a datastore, and a
database, and a schema default definition is in use by the server schema default definition is in use by the server instead, then it
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.
Explicitly set data: Data that is set to any value by a NETCONF Explicitly set data: Data that is set to any value by a NETCONF
client or other management application by the way of an explicit client or other management application by the way of an explicit
management operation, including any data model schema default management operation, including any data model schema default
value. Any value set by the NETCONF server which is not the value. Any value set by the NETCONF server which is not the
schema defined default value is also considered explicitly set schema defined default value is also considered explicitly set
data. data.
<with-defaults> retrieval: Refers to a protocol operation which <with-defaults> retrieval: Refers to a protocol operation which
includes the <with-default> parameter to control the handling of includes the <with-default> parameter to control the handling of
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 database 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 [I-D.ietf-netmod-yang]:
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:
skipping to change at page 5, line 35 skipping to change at page 5, line 35
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
used by the server. used by the server.
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
database 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 not interesting or specifically defined with a
"reasonable" value, so that the management user does not have to "reasonable" value, so that the management user does not have to
handle them. For these reasons it is quite common for networking 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.
skipping to change at page 8, line 7 skipping to change at page 8, line 7
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 database. This has the same effect as removing saved in the NETCONF configuration datastore. This has the same
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 'wd:default' attribute MUST be accepted
in configuration input, as described in Section 4.6.1 and in configuration input, as described in Section 4.6.1 and
Section 4.6.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.
skipping to change at page 12, line 25 skipping to change at page 12, line 25
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 database (i.e., running, parameter. If the target is a NETCONF configuration datastore (i.e.,
candidate or startup), the <with-defaults> parameter has no effect. running, candidate or startup), the <with-defaults> parameter has no
The server MUST use its basic mode when copying data to a NETCONF effect. The server MUST use its basic mode when copying data to a
database. If the <with-defaults> parameter is present in this case, NETCONF configuration datastore. If the <with-defaults> parameter is
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 'wd:
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 wd:default attribute is present and set to
'true', then the server MUST treat the new data node as a request to 'true', then the server MUST treat the new data node as a request to
return that node to its default value (i.e., remove it from the return that node to its default value (i.e., remove it from the
database). The data node within the NETCONF message MUST contain a configuration datastore). The data node within the NETCONF message
value in this case, which MUST be equal to the schema default value. MUST contain a value in this case, which MUST be equal to the schema
If not, the server MUST return an <rpc-error> response with a default value. If not, the server MUST return an <rpc-error>
'invalid-value' error-tag. response with a 'invalid-value' error-tag.
4.6.2. <edit-config> Operation 4.6.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 database, then the server MUST node already exists in the target configuration datastore, then the
return an <rpc-error> response with a 'invalid-value' error-tag. server MUST return an <rpc-error> response with a 'invalid-value'
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 database. 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 'wd:
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 wd:default attribute is present and set to
'true', then the server MUST treat the new data node as a request to 'true', then the server MUST treat the new data node as a request to
return that node to its default value (i.e., remove it from the return that node to its default value (i.e., remove it from the
database). The data node within the NETCONF message MUST contain a configuration datastore). The data node within the NETCONF message
value in this case, which MUST be equal to the schema default value. MUST contain a value in this case, which MUST be equal to the schema
If not, the server MUST return an <rpc-error> response with a default value. If not, the server MUST return an <rpc-error>
'invalid-value' error-tag. response with a 'invalid-value' error-tag.
If the wd:default attribute is present, then the effective operation If the wd: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
skipping to change at page 19, line 27 skipping to change at page 19, line 27
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 configuration database. The retrieval of default data from a NETCONF datastore. The security
security consideration of [I-D.ietf-netconf-4741bis] apply to this consideration of [I-D.ietf-netconf-4741bis] apply to this document as
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, Washam Fan and many other members of the NETCONF WG
for providing important input to this document. 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
skipping to change at page 20, line 15 skipping to change at page 20, line 15
Bierman, "Network Configuration Protocol (NETCONF)", Bierman, "Network Configuration Protocol (NETCONF)",
draft-ietf-netconf-4741bis-03 (work in progress), draft-ietf-netconf-4741bis-03 (work in progress),
July 2010. July 2010.
[I-D.ietf-netmod-yang] [I-D.ietf-netmod-yang]
Bjorklund, M., "YANG - A data modeling language for the Bjorklund, M., "YANG - A data modeling language for the
Network Configuration Protocol (NETCONF)", Network Configuration Protocol (NETCONF)",
draft-ietf-netmod-yang-13 (work in progress), June 2010. draft-ietf-netmod-yang-13 (work in progress), June 2010.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Paoli, J., Yergeau, F., Maler, E., Sperberg-McQueen, C., Paoli, J., Yergeau, F., Sperberg-McQueen, C., Maler, E.,
and T. Bray, "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>.
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
skipping to change at page 28, line 9 skipping to change at page 28, 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. 09-10 B.1. 10-11
Changed term 'database' to 'configuration datastore' or generic
'datastore'.
B.2. 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.2. 08-09 B.3. 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.3. 07-08 B.4. 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.4. 06-07 B.5. 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.5. 05-06 B.6. 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 30 skipping to change at page 29, 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.6. 04-05 B.7. 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 9 skipping to change at page 30, 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.7. 03-04 B.8. 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.8. 02-03 B.9. 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.9. 01-02 B.10. 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.10. 00-01 B.11. 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.11. -00 B.12. -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. 28 change blocks. 
64 lines changed or deleted 71 lines changed or added

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