draft-ietf-netmod-factory-default-08.txt   draft-ietf-netmod-factory-default-09.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: June 6, 2020 Ericsson Hungary Expires: June 8, 2020 Ericsson Hungary
Y. Niu Y. Niu
Huawei Huawei
December 4, 2019 December 6, 2019
Factory Default Setting Factory Default Setting
draft-ietf-netmod-factory-default-08 draft-ietf-netmod-factory-default-09
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 datastore, all A new factory-reset RPC is defined. When resetting a datastore, all
previous configuration settings will be lost and replaced by the previous configuration settings will be lost and replaced by the
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 June 6, 2020. This Internet-Draft will expire on June 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 4, line 24 skipping to change at page 4, line 24
an appropriate factory-default state. an appropriate factory-default state.
In addition, the "factory-reset" RPC MUST restore storage to factory In addition, the "factory-reset" RPC MUST restore storage to factory
condition, including remove log files, remove temporary files (from condition, including remove log files, remove temporary files (from
datastore or elsewhere). It MUST also remove security credentials datastore or elsewhere). It MUST also remove security credentials
and restoring default security settings including remove and restoring default security settings including remove
certificates, keys, zero passwords, etc. The process invoked by the certificates, keys, zero passwords, etc. The process invoked by the
"factory-reset" RPC SHOULD zero/pattern-write than remove sensitive "factory-reset" RPC SHOULD zero/pattern-write than remove sensitive
files such as the TLS keys, configuration stores, etc. The "factory- files such as the TLS keys, configuration stores, etc. 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, which such as restarting the node or some of the software processes.
are especially needed after having onboard information being
processed or when a specified boot image needs to be Note that operators should be aware that since all read-write
downloaded,verified and installed. datastores are immediately reset to factory default, the device may
become unreachable on the network. It is important to understand how
a given vendor's device will behave after the RPC is executed.
Implementors SHOULD reboot the device or otherwise restart processes
needed to bootstrap it.
3. Factory-Default Datastore 3. Factory-Default Datastore
Following guidelines for defining Datastores in the appendix A of Following 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 only implement the <factory- configuration of a server. A device MAY only implement the <factory-
reset> RPC without implementing the 'factory-default' datastore, reset> RPC without implementing the 'factory-default' datastore,
which make it lose the ability to see what configuration the device which make it lose the ability to see what configuration the device
skipping to change at page 9, line 16 skipping to change at page 9, line 21
[I-D.ietf-netmod-yang-instance-file-format] [I-D.ietf-netmod-yang-instance-file-format]
Lengyel, B. and B. Claise, "YANG Instance Data File Lengyel, B. and B. Claise, "YANG Instance Data File
Format", draft-ietf-netmod-yang-instance-file-format-06 Format", draft-ietf-netmod-yang-instance-file-format-06
(work in progress), December 2019. (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)
v08 - 09
o Provide some guideline for operators and implementor who implement
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;
 End of changes. 6 change blocks. 
8 lines changed or deleted 17 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/