draft-ietf-netmod-factory-default-10.txt   draft-ietf-netmod-factory-default-11.txt 
NETMOD Working Group Q. Wu NETMOD Working Group Q. Wu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track B. Lengyel Intended status: Standards Track B. Lengyel
Expires: August 12, 2020 Ericsson Hungary Expires: August 15, 2020 Ericsson Hungary
Y. Niu Y. Niu
Huawei Huawei
February 9, 2020 February 12, 2020
Factory Default Setting Factory Default Setting
draft-ietf-netmod-factory-default-10 draft-ietf-netmod-factory-default-11
Abstract Abstract
This document defines a method to reset a server to its factory- This document defines a method to reset a server to its factory
default content. The reset operation may be used, e.g., when the default content. The reset operation may be used, e.g., when the
existing configuration has major errors so re-starting the existing configuration has major errors so re-starting the
configuration process from scratch is the best option. configuration process from scratch is the best option.
A new factory-reset RPC is defined. When resetting a device, all A new "factory-reset" RPC is defined. When resetting a device, all
previous configuration settings will be lost and replaced by the previous configuration settings will be lost and replaced by the
factory-default content. factory default content.
A new optional "factory-default" read-only datastore is defined, that A new optional "factory-default" read-only datastore is defined, that
contains the factory default configuration for the device. contains the factory default configuration for the device.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 12, 2020. This Internet-Draft will expire on August 15, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 26 skipping to change at page 2, line 26
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Factory-Reset RPC . . . . . . . . . . . . . . . . . . . . . . 3 2. Factory-Reset RPC . . . . . . . . . . . . . . . . . . . . . . 3
3. Factory-Default Datastore . . . . . . . . . . . . . . . . . . 4 3. Factory-Default Datastore . . . . . . . . . . . . . . . . . . 4
4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Normative References . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8 Appendix A. Changes between revisions . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Changes between revisions . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
This document defines a method to reset a server to its factory- This document defines a method to reset a server to its factory
default content. The reset operation may be used, e.g., when the default content. The reset operation may be used, e.g., when the
existing configuration has major errors so re-starting the existing configuration has major errors so re-starting the
configuration process from scratch is the best option. configuration process from scratch is the best option.
A factory-reset RPC is defined. When resetting a device, all A "factory-reset" RPC is defined. When resetting a device, all
previous configuration settings will be lost and replaced by the previous configuration settings will be lost and replaced by the
factory-default content. factory default content.
A "factory-default" read-only datastore is defined, that contains the A "factory-default" read-only datastore is defined, that contains the
data to replace the contents of implemented read-write conventional data to replace the contents of implemented read-write conventional
configuration datastores at reset. This datastore can also be used configuration datastores at reset. This datastore can also be used
in the <get-data> operation. in the <get-data> operation.
The YANG data model in this document conforms to the Network The YANG data model in this document conforms to the Network
Management Datastore Architecture defined in [RFC8342]. Management Datastore Architecture defined in [RFC8342].
1.1. Terminology 1.1. Terminology
skipping to change at page 3, line 34 skipping to change at page 3, line 34
o intended configuration datastore o intended configuration datastore
o operational state datastore o operational state datastore
o conventional configuration datastore o conventional configuration datastore
o RPC operation o RPC operation
The following terms are defined in this document as follows: The following terms are defined in this document as follows:
o factory-default: a preconfigured initial configuration that is
used to initialize the configuration of a server.
o factory-default datastore: A read-only configuration datastore o factory-default datastore: A read-only configuration datastore
holding a preconfigured initial configuration that is used to holding a preconfigured initial configuration that is used to
initialize the configuration of a server. initialize the configuration of a server.
2. Factory-Reset RPC 2. Factory-Reset RPC
A new "factory-reset" RPC is introduced. Upon receiving the RPC A new "factory-reset" RPC is introduced. Upon receiving the RPC
o All supported conventional read-write configuration datastores o All supported conventional read-write configuration datastores
(i.e. <running>, <startup>, and <candidate>) are all reset to the (i.e. <running>, <startup>, and <candidate>) are all reset to the
skipping to change at page 4, line 12 skipping to change at page 4, line 12
o All data in any ephemeral datastores MUST be discarded. o All data in any ephemeral datastores MUST be discarded.
o The contents of the <operational> datastore MUST reflect the o The contents of the <operational> datastore MUST reflect the
operational state of the device after applying the factory default operational state of the device after applying the factory default
configuration. configuration.
In addition, the "factory-reset" RPC MUST restore non-volatile In addition, the "factory-reset" RPC MUST restore non-volatile
storage to factory condition. Depending on the system, this may storage to factory condition. Depending on the system, this may
entail deleting dynamically generated files, such as those containing entail deleting dynamically generated files, such as those containing
keys (e.g., /etc/ssl/private), certificates (e.g., /etc/ssl), and keys (e.g., /etc/ssl/private), certificates (e.g., /etc/ssl), logs
logs (e.g., /var/log), temporary files (e.g., /tmp/*). All security (e.g., /var/log), and temporary files (e.g., /tmp/*). All security
sensitive data (i.e., private keys, passwords, etc.) SHOULD be sensitive data (i.e., private keys, passwords, etc.) SHOULD be
overwritten with zeros or a pattern before deletion. The "factory- overwritten with zeros or a pattern before deletion. The "factory-
reset" RPC MAY also be used to trigger some other resetting tasks reset" RPC MAY also be used to trigger some other resetting tasks
such as restarting the node or some of the software processes. such as restarting the node or some of the software processes.
Note that operators should be aware that since all read-write Note that operators should be aware that since all read-write
datastores are immediately reset to factory-default, the device may datastores are immediately reset to factory default, the device may
become unreachable on the network. It is important to understand how become unreachable on the network. It is important to understand how
a given vendor's device will behave after the RPC is executed. a given vendor's device will behave after the RPC is executed.
Implementors SHOULD reboot the device or otherwise restart processes Implementors SHOULD reboot the device or otherwise restart processes
needed to bootstrap it. needed to bootstrap it.
3. Factory-Default Datastore 3. Factory-Default Datastore
Following the guidelines for defining Datastores in the appendix A of Following the guidelines for defining Datastores in the appendix A of
[RFC8342], this document introduces a new optional datastore resource [RFC8342], this document introduces a new optional datastore resource
named "factory-default" that represents a preconfigured minimal named "factory-default" that represents a preconfigured minimal
initial configuration that can be used to initialize the initial configuration that can be used to initialize the
configuration of a server. A device MAY implement the <factory- configuration of a server. A device MAY implement the "factory-
reset> RPC without implementing the "factory-default" datastore, reset" RPC without implementing the "factory-default" datastore,
which would only eliminate the ability to programmatically determine which would only eliminate the ability to programmatically determine
the factory-default configuration. the factory default configuration.
o Name: "factory-default" o Name: "factory-default"
o YANG modules: all o YANG modules: all
o YANG nodes: all "config true" data nodes o YANG nodes: all "config true" data nodes
o Management operations: The content of the datastore is set by the o Management operations: The content of the datastore is set by the
server in an implementation dependent manner. The content can not server in an implementation dependent manner. The content can not
be changed by management operations via NETCONF, RESTCONF, the CLI be changed by management operations via NETCONF, RESTCONF, the CLI
etc. unless specialized, dedicated operations are provided. The etc. unless specialized, dedicated operations are provided. The
datastore can be read using the standard NETCONF/RESTCONF protocol datastore can be read using the standard NETCONF/RESTCONF protocol
operations. The <factory-reset> operation copies the factory operations. The "factory-reset" operation copies the factory
default content to <running> and, if present, <startup> default content to <running> and, if present, <startup> and/or
<candidate> and then the content of these datastores is propagated <candidate> and then the content of these datastores is propagated
automatically to any other read only datastores, e.g., <intended> automatically to any other read only datastores, e.g., <intended>
and <operational>. and <operational>.
o Origin: This document does not define a new origin identity as it o Origin: This document does not define a new origin identity as it
does not interact with <operational> datastore. does not interact with <operational> datastore.
o Protocols: RESTCONF, NETCONF and other management protocol. o Protocols: RESTCONF, NETCONF and other management protocol.
o Defining YANG module: "ietf-factory-default". o Defining YANG module: "ietf-factory-default".
The contents of <factory-default> is defined by the device vendor and The contents of <factory-default> is defined by the device vendor and
MUST persist across device restarts. MUST persist across device restarts.
4. YANG Module 4. YANG Module
This module imports typedefs from [RFC8342], and it references This module imports typedefs from [RFC8342], and it references
[RFC6421],[RFC8341]. "default-deny-all" extension statement from [RFC8341].
<CODE BEGINS> file "ietf-factory-default@2019-11-27.yang" <CODE BEGINS> file "ietf-factory-default@2019-11-27.yang"
module ietf-factory-default { module ietf-factory-default {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-factory-default"; namespace "urn:ietf:params:xml:ns:yang:ietf-factory-default";
prefix fd; prefix fd;
import ietf-datastores { import ietf-datastores {
prefix ds; prefix ds;
reference reference
skipping to change at page 5, line 50 skipping to change at page 5, line 50
"WG Web: <https://tools.ietf.org/wg/netconf/> "WG Web: <https://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com> <mailto:bill.wu@huawei.com>
Editor: Balazs Lengyel Editor: Balazs Lengyel
<mailto:balazs.lengyel@ericsson.com> <mailto:balazs.lengyel@ericsson.com>
Editor: Ye Niu Editor: Ye Niu
<mailto:niuye@huawei.com>"; <mailto:niuye@huawei.com>";
description description
"This module defines an RPC called 'factory-reset', a "This module defines an RPC called 'factory-reset', and a
datastore identity called 'factory-default-datastore'. datastore identity called 'factory-default'.
It provides functionality to reset a server to its It provides functionality to reset a server to its factory
factory-default content. default configuration and, when supported, to discover the
factory default configuration contents independent of
resetting the server.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
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).
skipping to change at page 6, line 30 skipping to change at page 6, line 32
revision 2019-11-27 { revision 2019-11-27 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Factory default Setting"; "RFC XXXX: Factory default Setting";
} }
feature factory-default-datastore { feature factory-default-datastore {
description description
"Indicates that the factory-default configuration is "Indicates that the factory default configuration is
available as a datastore."; available as a datastore.";
} }
rpc factory-reset { rpc factory-reset {
nacm:default-deny-all; nacm:default-deny-all;
description description
"The server resets the content of all read-write "The server resets the content of all read-write
configuration datastores (i.e.,<running> , <startup> , configuration datastores (i.e.,<running>, <startup>,
and <candidate>) to their factory-default content."; and <candidate>) to their factory default content.";
} }
identity factory-default { identity factory-default {
if-feature "factory-default-datastore"; if-feature "factory-default-datastore";
base ds:datastore; base ds:datastore;
description description
"This read-only datastore contains the factory-default "This read-only datastore contains the factory default
configuration for the device used to replace the contents configuration for the device used to replace the contents
of the read-write conventional configuration datastores of the read-write conventional configuration datastores
during a factory-reset RPC operation."; during a 'factory-reset' RPC operation.";
} }
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
This document registers one URI in the IETF XML Registry [RFC3688]. This document registers one URI in the IETF XML Registry [RFC3688].
The following registration has been made: The following registration has been made:
URI: urn:ietf:params:xml:ns:yang:ietf-factory-default URI: urn:ietf:params:xml:ns:yang:ietf-factory-default
Registrant Contact: The IESG. Registrant Contact: The IESG.
skipping to change at page 7, line 31 skipping to change at page 7, line 34
6. Security Considerations 6. Security Considerations
The YANG module defined in this document extends the base operations The YANG module defined in this document extends the base operations
for NETCONF [RFC6241] and RESTCONF [RFC8040]. The lowest NETCONF for NETCONF [RFC6241] and RESTCONF [RFC8040]. The lowest NETCONF
layer is the secure transport layer, and the mandatory-to-implement layer is the secure transport layer, and the mandatory-to-implement
secure transport is Secure Shell (SSH) [RFC6242]. The lowest secure transport is Secure Shell (SSH) [RFC6242]. The lowest
RESTCONF layer is HTTPS, and the mandatory-to-implement secure RESTCONF layer is HTTPS, and the mandatory-to-implement secure
transport is TLS [RFC8446]. transport is TLS [RFC8446].
Access to the <factory-reset> RPC operation is considered sensitive Access to the "factory-reset" RPC operation is considered sensitive
in and therefore has been restricted using the "default- deny-all" and therefore has been restricted using the "default-deny-all" access
access control defined in . [RFC8341] control defined in [RFC8341].
The "factory-reset" RPC can prevent any further management of the The "factory-reset" RPC can prevent any further management of the
device if the session and client config is included in the factory- device if the session and client config is included in the factory
reset contents. default contents.
The operational disruption caused by setting the config to factory- The operational disruption caused by setting the config to factory
reset contents varies greatly depending on the implementation and default contents varies greatly depending on the implementation and
current config. current config.
7. Acknowledgements 7. Acknowledgements
Thanks to Juergen Schoenwaelder, Ladislav Lhotka, Alex Campbell, Joe Thanks to Juergen Schoenwaelder, Ladislav Lhotka, Alex Campbell, Joe
Clarke, Robert Wilton, Kent Watsen, Joel Jaeggli, Lou Berger, Andy Clarke, Robert Wilton, Kent Watsen, Joel Jaeggli, Lou Berger, Andy
Bierman, Susan Hares to review this draft and provide important input Bierman, Susan Hares to review this draft and provide important input
to this document. to this document.
8. Contributors 8. Contributors
Rohit R Ranade Rohit R Ranade
Huawei Huawei
Email: rohitrranade@huawei.com Email: rohitrranade@huawei.com
9. References 9. Normative References
9.1. 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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
9.2. Informative References [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
[I-D.ietf-netmod-yang-instance-file-format] <https://www.rfc-editor.org/info/rfc8446>.
Lengyel, B. and B. Claise, "YANG Instance Data File
Format", draft-ietf-netmod-yang-instance-file-format-06
(work in progress), December 2019.
Appendix A. Changes between revisions Appendix A. Changes between revisions
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
v10 - 11
o Incorporate additional Shepherd review's comments.
v09 - 10 v09 - 10
o Incorporate Shepherd review's comments. o Incorporate Shepherd review's comments.
v08 - 09 v08 - 09
o Provide some guideline for operators and implementor who implement o Provide some guideline for operators and implementor who implement
factory defaut method. factory defaut method.
v07 - 08 v07 - 08
o Provide clarification and recommendation on the relationship o Provide clarification and recommendation on the relationship
between factory-reset RPC and reboot. between factory-reset RPC and reboot.
o Nits fixed based on YANG Doctor Review. o Nits fixed based on YANG Doctor Review.
v06 - 07 v06 - 07
o Remove Factory-default content specification; o Remove Factory default content specification;
o Remove reference to YANG instance data file format and zero touch o Remove reference to YANG instance data file format and zero touch
provision [RFC8573]; provision [RFC8573];
o Remove copy-config operation extension on factory-default o Remove copy-config operation extension on factory-default
datastore datastore
v05 - 06 v05 - 06
o Additional text to enhance security section. o Additional text to enhance security section.
o Add nacm:default-deny-all on "factory-reset" RPC. o Add nacm:default-deny-all on "factory-reset" RPC.
o A few clarification on Factory-default content specification. o A few clarification on Factory default content specification.
v03 - 04 v03 - 04
o Additional text to clarify factory-reset RPC usage. o Additional text to clarify factory-reset RPC usage.
v02 - 03 v02 - 03
o Update security consideration section. o Update security consideration section.
v01 - v02 v01 - v02
skipping to change at page 10, line 11 skipping to change at page 10, line 31
o Add an extension to the NETCONF <get-config> operation which o Add an extension to the NETCONF <get-config> operation which
allows it to operate on the factory-default datastore. allows it to operate on the factory-default datastore.
v00 - v01 v00 - v01
o Change YANG server into server defined in NMDA architecture based o Change YANG server into server defined in NMDA architecture based
on discussion. on discussion.
o Allow reset the content of all read-write configuraton datastores o Allow reset the content of all read-write configuraton datastores
to its factory-default content except <candidate>. to its factory default content except <candidate>.
o Add clarification text on factory-reset protocol operation o Add clarification text on factory-reset protocol operation
behavior. behavior.
v03 - v00 v03 - v00
o Change draft name from draft-wu to draft-ietf-netmod-factory- o Change draft name from draft-wu to draft-ietf-netmod-factory-
default-00 without content changes. default-00 without content changes.
v02 - v03 v02 - v03
 End of changes. 36 change blocks. 
54 lines changed or deleted 73 lines changed or added

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