Difference between revisions of "RFC8808"

From RFC-Wiki
(Created page with " Internet Engineering Task Force (IETF) Q. Wu Request for Comments: 8808 Huawei Category: Standards Tr...")
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 

 

−
 
−
 
  
 
Internet Engineering Task Force (IETF)                            Q. Wu
 
Internet Engineering Task Force (IETF)                            Q. Wu
Line 7: Line 5:
 
Category: Standards Track                                    B. Lengyel
 
Category: Standards Track                                    B. Lengyel
 
ISSN: 2070-1721                                        Ericsson Hungary
 
ISSN: 2070-1721                                        Ericsson Hungary
−
                                                                  Y. Niu
+
                                                              Y. Niu
−
                                                                  Huawei
+
                                                              Huawei
−
                                                            August 2020
+
                                                          August 2020
  
 +
          A YANG Data Model for Factory Default Settings
  
−
            A YANG Data Model for Factory Default Settings
+
'''Abstract'''
  
−
Abstract
+
This document defines a YANG data model with the "factory-reset" RPC
 +
to allow clients to reset a server back to its factory default
 +
condition.  It also defines an optional "factory-default" datastore
 +
to allow clients to read the factory default configuration for the
 +
device.
  
−
  This document defines a YANG data model with the "factory-reset" RPC
+
The YANG data model in this document conforms to the Network
−
  to allow clients to reset a server back to its factory default
+
Management Datastore Architecture (NMDA) defined in [[RFC8342|RFC 8342]].
−
  condition.  It also defines an optional "factory-default" datastore
 
−
  to allow clients to read the factory default configuration for the
 
−
  device.
 
  
−
  The YANG data model in this document conforms to the Network
+
'''Status of This Memo'''
−
  Management Datastore Architecture (NMDA) defined in RFC 8342.
 
  
−
Status of This Memo
+
This is an Internet Standards Track document.
  
−
  This is an Internet Standards Track document.
+
This document is a product of the Internet Engineering Task Force
 +
(IETF).  It represents the consensus of the IETF community.  It has
 +
received public review and has been approved for publication by the
 +
Internet Engineering Steering Group (IESG).  Further information on
 +
Internet Standards is available in Section 2 of [[RFC7841|RFC 7841]].
  
−
  This document is a product of the Internet Engineering Task Force
+
Information about the current status of this document, any errata,
−
  (IETF).  It represents the consensus of the IETF community.  It has
+
and how to provide feedback on it may be obtained at
−
  received public review and has been approved for publication by the
+
https://www.rfc-editor.org/info/rfc8808.
−
  Internet Engineering Steering Group (IESG). Further information on
 
−
  Internet Standards is available in Section 2 of RFC 7841.
 
  
−
  Information about the current status of this document, any errata,
+
'''Copyright Notice'''
−
  and how to provide feedback on it may be obtained at
 
−
  https://www.rfc-editor.org/info/rfc8808.
 
  
−
Copyright Notice
+
Copyright (c) 2020 IETF Trust and the persons identified as the
 +
document authors.  All rights reserved.
  
−
  Copyright (c) 2020 IETF Trust and the persons identified as the
+
This document is subject to [[BCP78|BCP 78]] and the IETF Trust's Legal
−
  document authors.  All rights reserved.
+
Provisions Relating to IETF Documents
 +
(https://trustee.ietf.org/license-info) in effect on the date of
 +
publication of this document.  Please review these documents
 +
carefully, as they describe your rights and restrictions with respect
 +
to this document.  Code Components extracted from this document must
 +
include Simplified BSD License text as described in Section 4.e of
 +
the Trust Legal Provisions and are provided without warranty as
 +
described in the Simplified BSD License.
  
−
  This document is subject to BCP 78 and the IETF Trust's Legal
+
1.  Introduction
−
  Provisions Relating to IETF Documents
+
  1.1.  Terminology
−
  (https://trustee.ietf.org/license-info) in effect on the date of
+
2. "Factory-Reset" RPC
−
  publication of this document.  Please review these documents
+
3. "Factory-Default" Datastore
−
  carefully, as they describe your rights and restrictions with respect
+
4.  YANG Module
−
  to this document.  Code Components extracted from this document must
+
5.  IANA Considerations
−
  include Simplified BSD License text as described in Section 4.e of
+
6.  Security Considerations
−
  the Trust Legal Provisions and are provided without warranty as
+
7. References
−
  described in the Simplified BSD License.
+
  7.1.  Normative References
 +
  7.2. Informative References
 +
Acknowledgements
 +
Contributors
 +
Authors' Addresses
  
−
Table of Contents
+
== Introduction ==
  
−
  1.  Introduction
+
This document defines a YANG data model and associated mechanism to
−
    1.1.  Terminology
+
reset a server to its factory default contents.  This mechanism may
−
  2.  "Factory-Reset" RPC
+
be used, for example, when the existing configuration has major
−
  3.  "Factory-Default" Datastore
+
errors and so restarting the configuration process from scratch is
−
  4.  YANG Module
+
the best option.
−
  5.  IANA Considerations
 
−
  6.  Security Considerations
 
−
  7.  References
 
−
    7.1.  Normative References
 
−
    7.2. Informative References
 
−
  Acknowledgements
 
−
  Contributors
 
−
  Authors' Addresses
 
  
−
1.  Introduction
+
A "factory-reset" remote procedure call (RPC) is defined within the
 +
YANG data model.  When resetting a device, all previous configuration
 +
settings will be lost and replaced by the factory default contents.
  
−
  This document defines a YANG data model and associated mechanism to
+
In addition, an optional "factory-default" read-only datastore is
−
  reset a server to its factory default contents.  This mechanism may
+
defined within the YANG data model.  This datastore contains the data
−
  be used, for example, when the existing configuration has major
+
to replace the contents of implemented read-write conventional
−
  errors and so restarting the configuration process from scratch is
+
configuration datastores at reset and can also be used in the
−
  the best option.
+
<get-data> operation.
  
−
  A "factory-reset" remote procedure call (RPC) is defined within the
+
The YANG data model in this document conforms to the Network
−
  YANG data model.  When resetting a device, all previous configuration
+
Management Datastore Architecture defined in [[RFC8342]].
−
  settings will be lost and replaced by the factory default contents.
 
  
−
  In addition, an optional "factory-default" read-only datastore is
+
=== Terminology ===
−
  defined within the YANG data model.  This datastore contains the data
 
−
  to replace the contents of implemented read-write conventional
 
−
  configuration datastores at reset and can also be used in the
 
−
  <get-data> operation.
 
  
−
  The YANG data model in this document conforms to the Network
+
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
−
  Management Datastore Architecture defined in [RFC8342].
+
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
 +
"OPTIONAL" in this document are to be interpreted as described in
 +
[[BCP14|BCP 14]] [[RFC2119]] [[RFC8174]] when, and only when, they appear in all
 +
capitals, as shown here.
  
−
1.1.  Terminology
+
The following terms are defined in [[RFC8342]] and [[RFC7950]] and are
 +
not redefined here:
  
−
  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+
*  server
−
  "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
 
−
  "OPTIONAL" in this document are to be interpreted as described in
 
−
  BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
 
−
  capitals, as shown here.
 
  
−
  The following terms are defined in [RFC8342] and [RFC7950] and are
+
*  startup configuration datastore
−
  not redefined here:
 
  
−
  *  server
+
*  candidate configuration datastore
  
−
  *  startup configuration datastore
+
*  running configuration datastore
  
−
  *  candidate configuration datastore
+
*  intended configuration datastore
  
−
  *  running configuration datastore
+
*  operational state datastore
  
−
  *  intended configuration datastore
+
*  conventional configuration datastore
  
−
  *  operational state datastore
+
*  datastore schema
  
−
  *  conventional configuration datastore
+
*  RPC operation
  
−
  *  datastore schema
+
This document defines the following term:
  
−
   * RPC operation
+
"factory-default" datastore:  A read-only configuration datastore
 +
   holding a preset initial configuration that is used to initialize
 +
  the configuration of a server. This datastore is referred to as
 +
  "<factory-default>".
  
−
  This document defines the following term:
+
== "Factory-Reset" RPC ==
  
−
  "factory-default" datastore: A read-only configuration datastore
+
This document introduces a new "factory-reset" RPC. Upon receiving
−
      holding a preset initial configuration that is used to initialize
+
the RPC:
−
      the configuration of a server.  This datastore is referred to as
 
−
      "<factory-default>".
 
  
−
2. "Factory-Reset" RPC
+
*  All supported conventional read-write configuration datastores
 +
  (i.e., <running>, <startup>, and <candidate>) are reset to the
 +
  contents of <factory-default>.
  
−
  This document introduces a new "factory-reset" RPC.  Upon receiving
+
*  Read-only datastores receive their contents from other datastores
−
   the RPC:
+
   (e.g., <intended> gets its contents from <running>).
  
−
  *  All supported conventional read-write configuration datastores
+
*  All data in any dynamic configuration datastores MUST be
−
      (i.e., <running>, <startup>, and <candidate>) are reset to the
+
  discarded.
−
      contents of <factory-default>.
 
  
−
  *  Read-only datastores receive their contents from other datastores
+
*  The contents of the <operational> datastore MUST reflect the
−
      (e.g., <intended> gets its contents from <running>).
+
  operational state of the device after applying the factory default
 +
  configuration.
  
−
  *  All data in any dynamic configuration datastores MUST be
+
In addition, the "factory-reset" RPC MUST restore nonvolatile storage
−
      discarded.
+
to factory condition.  Depending on the system, this may entail
 +
deleting dynamically generated files, such as those containing keys
 +
(e.g., /etc/ssl/private), certificates (e.g., /etc/ssl), logs (e.g.,
 +
/var/log), and temporary files (e.g., /tmp/*). Any other
 +
cryptographic keys that are part of the factory-installed image will
 +
be retained (such as an Initial Device Identifier (IDevID)
 +
certificate [BRSKI]).  When this process includes security-sensitive
 +
data such as cryptographic keys or passwords, it is RECOMMENDED to
 +
perform the deletion in as thorough a manner as possible (e.g.,
 +
overwriting the physical storage medium with zeros and/or random bits
 +
for repurposing or end-of-life (EOL) disposal) to reduce the risk of
 +
the sensitive material being recoverable.  The "factory-reset" RPC
 +
MAY also be used to trigger some other resetting tasks such as
 +
restarting the node or some of the software processes.
  
−
  *  The contents of the <operational> datastore MUST reflect the
+
Note that operators should be aware that since all read-write
−
      operational state of the device after applying the factory default
+
datastores are immediately reset to factory default, the device may
−
      configuration.
+
become unreachable as a host 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 and get it properly
 +
configured or otherwise restart processes needed to bootstrap it.
  
−
  In addition, the "factory-reset" RPC MUST restore nonvolatile storage
+
== "Factory-Default" Datastore ==
−
  to factory condition.  Depending on the system, this may entail
 
−
  deleting dynamically generated files, such as those containing keys
 
−
  (e.g., /etc/ssl/private), certificates (e.g., /etc/ssl), logs (e.g.,
 
−
  /var/log), and temporary files (e.g., /tmp/*).  Any other
 
−
  cryptographic keys that are part of the factory-installed image will
 
−
  be retained (such as an Initial Device Identifier (IDevID)
 
−
  certificate [BRSKI]).  When this process includes security-sensitive
 
−
  data such as cryptographic keys or passwords, it is RECOMMENDED to
 
−
  perform the deletion in as thorough a manner as possible (e.g.,
 
−
  overwriting the physical storage medium with zeros and/or random bits
 
−
  for repurposing or end-of-life (EOL) disposal) to reduce the risk of
 
−
  the sensitive material being recoverable.  The "factory-reset" RPC
 
−
  MAY also be used to trigger some other resetting tasks such as
 
−
  restarting the node or some of the software processes.
 
  
−
  Note that operators should be aware that since all read-write
+
Following the guidelines for defining datastores in Appendix A of
−
  datastores are immediately reset to factory default, the device may
+
[[RFC8342]], this document introduces a new optional datastore resource
−
  become unreachable as a host on the network.  It is important to
+
named "factory-default" that represents a preset initial
−
  understand how a given vendor's device will behave after the RPC is
+
configuration that can be used to initialize the configuration of a
−
  executed.  Implementors SHOULD reboot the device and get it properly
+
server.  A device MAY implement the "factory-reset" RPC without
−
  configured or otherwise restart processes needed to bootstrap it.
+
implementing the "factory-default" datastore, which would only
 +
eliminate the ability to programmatically determine the factory
 +
default configuration.
  
−
3. "Factory-Default" Datastore
+
Name: "factory-default".
  
−
  Following the guidelines for defining datastores in Appendix A of
+
YANG modules:  The "factory-default" datastore schema MUST be either
−
  [RFC8342], this document introduces a new optional datastore resource
+
   (1) the same as the conventional configuration datastores or
−
  named "factory-default" that represents a preset initial
+
   (2) a subset of the datastore schema for the conventional
−
   configuration that can be used to initialize the configuration of a
+
   configuration datastores.
−
   server.  A device MAY implement the "factory-reset" RPC without
 
−
  implementing the "factory-default" datastore, which would only
 
−
  eliminate the ability to programmatically determine the factory
 
−
   default configuration.
 
  
−
  Name:  "factory-default".
+
YANG nodes:  All "config true" data nodes.
  
−
  YANG modules:  The "factory-default" datastore schema MUST be either
+
Management operations:  The contents of the datastore is set by the
−
      (1) the same as the conventional configuration datastores or
+
  server in an implementation-dependent manner.  The contents cannot
−
      (2) a subset of the datastore schema for the conventional
+
  be changed by management operations via the Network Configuration
−
      configuration datastores.
+
  Protocol (NETCONF), RESTCONF, the CLI, etc., unless specialized,
 +
  dedicated operations are provided.  The datastore can be read
 +
  using the standard NETCONF/RESTCONF protocol operations.  The
 +
  "factory-reset" operation copies the factory default contents to
 +
  <running> and, if present, <startup> and/or <candidate>.  The
 +
  contents of these datastores is then propagated automatically to
 +
  any other read-only datastores, e.g., <intended> and
 +
  <operational>.
  
−
  YANG nodes:  All "config true" data nodes.
+
Origin:  This document does not define a new origin identity, as it
 +
  does not interact with the <operational> datastore.
  
−
  Management operations:  The contents of the datastore is set by the
+
Protocols:  RESTCONF, NETCONF, and other management protocols.
−
      server in an implementation-dependent manner.  The contents cannot
 
−
      be changed by management operations via the Network Configuration
 
−
      Protocol (NETCONF), RESTCONF, the CLI, etc., unless specialized,
 
−
      dedicated operations are provided.  The datastore can be read
 
−
      using the standard NETCONF/RESTCONF protocol operations.  The
 
−
      "factory-reset" operation copies the factory default contents to
 
−
      <running> and, if present, <startup> and/or <candidate>.  The
 
−
      contents of these datastores is then propagated automatically to
 
−
      any other read-only datastores, e.g., <intended> and
 
−
      <operational>.
 
  
−
  Origin:  This document does not define a new origin identity, as it
+
Defining YANG module:  "ietf-factory-default".
−
      does not interact with the <operational> datastore.
 
  
−
  Protocols: RESTCONF, NETCONF, and other management protocols.
+
The contents of <factory-default> are defined by the device vendor
 +
and MUST persist across device restarts. If supported, the "factory-
 +
default" datastore MUST be included in the list of datastores in the
 +
YANG library [[RFC8525]].
  
−
  Defining YANG module:  "ietf-factory-default".
+
== YANG Module ==
  
−
  The contents of <factory-default> are defined by the device vendor
+
This module uses the "datastore" identity [[RFC8342]] and the
−
  and MUST persist across device restarts.  If supported, the "factory-
+
"default-deny-all" extension statement from [[RFC8341]].
−
  default" datastore MUST be included in the list of datastores in the
 
−
  YANG library [RFC8525].
 
  
−
4. YANG Module
+
<CODE BEGINS> file "ietf-factory-default@2020-08-31.yang"
 +
  module ietf-factory-default {
 +
    yang-version 1.1;
 +
    namespace "urn:ietf:params:xml:ns:yang:ietf-factory-default";
 +
    prefix fd;
  
−
  This module uses the "datastore" identity [RFC8342] and the
+
    import ietf-datastores {
−
  "default-deny-all" extension statement from [RFC8341].
+
      prefix ds;
 +
      reference
 +
        "[[RFC8342|RFC 8342]]: Network Management Datastore Architecture
 +
          (NMDA)";
 +
    }
 +
    import ietf-netconf-acm {
 +
      prefix nacm;
 +
      reference
 +
        "[[RFC8341|RFC 8341]]: Network Configuration Access Control Model";
 +
    }
  
−
  <CODE BEGINS> file "[email protected]"
+
    organization
−
      module ietf-factory-default {
+
      "IETF Network Modeling (netmod) Working Group";
−
        yang-version 1.1;
+
    contact
−
         namespace "urn:ietf:params:xml:ns:yang:ietf-factory-default";
+
      "WG Web:  <https://datatracker.ietf.org/wg/netmod/>
−
        prefix fd;
+
         WG List: <mailto:netmod@ietf.org>
  
−
         import ietf-datastores {
+
         Editor:   Qin Wu
−
          prefix ds;
+
                  <mailto:[email protected]>
−
          reference
 
−
            "RFC 8342: Network Management Datastore Architecture
 
−
            (NMDA)";
 
−
        }
 
−
        import ietf-netconf-acm {
 
−
          prefix nacm;
 
−
          reference
 
−
            "RFC 8341: Network Configuration Access Control Model";
 
−
        }
 
  
−
         organization
+
         Editor:  Balazs Lengyel
−
          "IETF Network Modeling (netmod) Working Group";
+
                  <mailto:balazs.lengyel@ericsson.com>
−
        contact
 
−
          "WG Web:  <https://datatracker.ietf.org/wg/netmod/>
 
−
          WG List:  <mailto:netmod@ietf.org>
 
  
−
          Editor:  Qin Wu
+
        Editor:  Ye Niu
−
                    <mailto:bill.wu@huawei.com>
+
                  <mailto:niuye@huawei.com>";
 +
    description
 +
      "This module provides functionality to reset a server to its
 +
        factory default configuration and, when supported, to
 +
        discover the factory default configuration contents
 +
        independently of resetting the server.
  
−
          Editor:  Balazs Lengyel
+
        Copyright (c) 2020 IETF Trust and the persons identified as
−
                    <mailto:balazs.lengyel@ericsson.com>
+
        authors of the code. All rights reserved.
  
−
          Editor:  Ye Niu
+
         Redistribution and use in source and binary forms, with or
−
                    <mailto:[email protected]>";
+
        without modification, is permitted pursuant to, and subject
−
         description
+
        to the license terms contained in, the Simplified BSD License
−
          "This module provides functionality to reset a server to its
+
        set forth in Section 4.c of the IETF Trust's Legal Provisions
−
          factory default configuration and, when supported, to
+
        Relating to IETF Documents
−
          discover the factory default configuration contents
+
        (https://trustee.ietf.org/license-info).
−
          independently of resetting the server.
 
  
−
          Copyright (c) 2020 IETF Trust and the persons identified as
+
        This version of this YANG module is part of [[RFC8808|RFC 8808]]; see the
−
          authors of the code.  All rights reserved.
+
        RFC itself for full legal notices.";
  
−
          Redistribution and use in source and binary forms, with or
+
    revision 2020-08-31 {
−
          without modification, is permitted pursuant to, and subject
+
      description
−
          to the license terms contained in, the Simplified BSD License
+
        "Initial revision.";
−
          set forth in Section 4.c of the IETF Trust's Legal Provisions
+
      reference
−
          Relating to IETF Documents
+
        "[[RFC8808|RFC 8808]]: A YANG Data Model for Factory Default Settings";
−
          (https://trustee.ietf.org/license-info).
+
    }
  
−
          This version of this YANG module is part of RFC 8808; see the
+
    feature factory-default-datastore {
−
          RFC itself for full legal notices.";
+
      description
 +
        "Indicates that the factory default configuration is
 +
          available as a datastore.";
 +
    }
  
−
        revision 2020-08-31 {
+
    rpc factory-reset {
−
          description
+
      nacm:default-deny-all;
−
            "Initial revision.";
+
      description
−
           reference
+
        "The server resets all datastores to their factory
−
            "RFC 8808: A YANG Data Model for Factory Default Settings";
+
          default contents and any nonvolatile storage back to
−
        }
+
           factory condition, deleting all dynamically
 +
          generated files, including those containing keys,
 +
          certificates, logs, and other temporary files.
  
−
        feature factory-default-datastore {
+
          Depending on the factory default configuration, after
−
           description
+
           being reset, the device may become unreachable on the
−
            "Indicates that the factory default configuration is
+
          network.";
−
            available as a datastore.";
+
    }
−
        }
 
  
−
        rpc factory-reset {
+
    identity factory-default {
−
          nacm:default-deny-all;
+
      if-feature "factory-default-datastore";
−
          description
+
      base ds:datastore;
−
            "The server resets all datastores to their factory
+
      description
−
            default contents and any nonvolatile storage back to
+
        "This read-only datastore contains the factory default
−
            factory condition, deleting all dynamically
+
          configuration for the device that will be used to replace
−
            generated files, including those containing keys,
+
          the contents of the read-write conventional configuration
−
            certificates, logs, and other temporary files.
+
          datastores during a 'factory-reset' RPC operation.";
 +
    }
 +
  }
 +
<CODE ENDS>
  
−
            Depending on the factory default configuration, after
+
== IANA Considerations ==
−
            being reset, the device may become unreachable on the
 
−
            network.";
 
−
        }
 
  
−
        identity factory-default {
+
IANA has registered the following URI in the "ns" subregistry within
−
          if-feature "factory-default-datastore";
+
the "IETF XML Registry" [[RFC3688]]:
−
          base ds:datastore;
 
−
          description
 
−
            "This read-only datastore contains the factory default
 
−
            configuration for the device that will be used to replace
 
−
            the contents of the read-write conventional configuration
 
−
            datastores during a 'factory-reset' RPC operation.";
 
−
        }
 
−
      }
 
−
  <CODE ENDS>
 
  
−
5.  IANA Considerations
+
URI:  urn:ietf:params:xml:ns:yang:ietf-factory-default
 +
Registrant Contact:  The IESG.
 +
XML: N/A; the requested URI is an XML namespace.
  
−
  IANA has registered the following URI in the "ns" subregistry within
+
IANA has registered the following YANG module in the "YANG Module
−
  the "IETF XML Registry" [RFC3688]:
+
Names" subregistry [[RFC6020]] within the "YANG Parameters" registry:
  
−
  URI:  urn:ietf:params:xml:ns:yang:ietf-factory-default
+
Name:  ietf-factory-default
−
  Registrant Contact:  The IESG.
+
Namespace:  urn:ietf:params:xml:ns:yang:ietf-factory-default
−
  XML:  N/A; the requested URI is an XML namespace.
+
Prefix:  fd
 +
Reference:  8808
  
−
  IANA has registered the following YANG module in the "YANG Module
+
== Security Considerations ==
−
  Names" subregistry [RFC6020] within the "YANG Parameters" registry:
 
  
−
  Name: ietf-factory-default
+
The YANG module specified in this document defines a schema for data
−
  Namespace: urn:ietf:params:xml:ns:yang:ietf-factory-default
+
that is designed to be accessed via network management protocols such
−
  Prefix:  fd
+
as NETCONF [[RFC6241]] or RESTCONF [[RFC8040]]. The lowest NETCONF layer
−
  Reference:  8808
+
is the secure transport layer, and the mandatory-to-implement secure
 +
transport is Secure Shell (SSH) [[RFC6242]]. The lowest RESTCONF layer
 +
is HTTPS, and the mandatory-to-implement secure transport is TLS
 +
[[RFC8446]].
  
−
6. Security Considerations
+
The Network Configuration Access Control Model (NACM) [[RFC8341]]
 +
provides the means to restrict access for particular NETCONF or
 +
RESTCONF users to a preconfigured subset of all available NETCONF or
 +
RESTCONF protocol operations and content.
  
−
  The YANG module specified in this document defines a schema for data
+
Access to the "factory-reset" RPC operation and factory default
−
  that is designed to be accessed via network management protocols such
+
values of all configuration data nodes within the "factory-default"
−
  as NETCONF [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF layer
+
datastore is considered sensitive and therefore has been restricted
−
  is the secure transport layer, and the mandatory-to-implement secure
+
by using the "default-deny-all" access control statement defined in
−
  transport is Secure Shell (SSH) [RFC6242].  The lowest RESTCONF layer
+
[[RFC8341]].
−
  is HTTPS, and the mandatory-to-implement secure transport is TLS
 
−
  [RFC8446].
 
  
−
  The Network Configuration Access Control Model (NACM) [RFC8341]
+
The "factory-reset" RPC can prevent any further management of the
−
  provides the means to restrict access for particular NETCONF or
+
device when the server is reset back to its factory default
−
  RESTCONF users to a preconfigured subset of all available NETCONF or
+
condition, e.g., the session and client configurations are included
−
  RESTCONF protocol operations and content.
+
in the factory default contents or treated as dynamic files in
 +
nonvolatile storage and overwritten by the "factory-reset" RPC.
  
−
  Access to the "factory-reset" RPC operation and factory default
+
The operational disruption caused by setting the configuration to
−
  values of all configuration data nodes within the "factory-default"
+
factory default contents or the lack of appropriate security control
−
  datastore is considered sensitive and therefore has been restricted
+
on the factory default configuration varies greatly, depending on the
−
  by using the "default-deny-all" access control statement defined in
+
implementation and current configuration.
−
  [RFC8341].
 
  
−
  The "factory-reset" RPC can prevent any further management of the
+
The nonvolatile storage is expected to be wiped clean and reset back
−
  device when the server is reset back to its factory default
+
to the factory default state, but there is no guarantee that the data
−
  condition, e.g., the session and client configurations are included
+
is wiped clean according to any particular data-cleansing standard,
−
  in the factory default contents or treated as dynamic files in
+
and the owner of the device MUST NOT rely on any sensitive data
−
  nonvolatile storage and overwritten by the "factory-reset" RPC.
+
(e.g., private keys) being forensically unrecoverable from the
 +
device's nonvolatile storage after a "factory-reset" RPC has been
 +
invoked.
  
−
  The operational disruption caused by setting the configuration to
+
== References ==
−
  factory default contents or the lack of appropriate security control
 
−
  on the factory default configuration varies greatly, depending on the
 
−
  implementation and current configuration.
 
  
−
  The nonvolatile storage is expected to be wiped clean and reset back
+
=== Normative References ===
−
  to the factory default state, but there is no guarantee that the data
 
−
  is wiped clean according to any particular data-cleansing standard,
 
−
  and the owner of the device MUST NOT rely on any sensitive data
 
−
  (e.g., private keys) being forensically unrecoverable from the
 
−
  device's nonvolatile storage after a "factory-reset" RPC has been
 
−
  invoked.
 
  
−
7. References
+
[[RFC2119]]  Bradner, S., "Key words for use in RFCs to Indicate
 +
          Requirement Levels", [[BCP14|BCP 14]], [[RFC2119|RFC 2119]],
 +
          DOI 10.17487/RFC2119, March 1997,
 +
          <https://www.rfc-editor.org/info/rfc2119>.
  
−
7.1. Normative References
+
[[RFC3688]]  Mealling, M., "The IETF XML Registry", [[BCP81|BCP 81]], [[RFC3688|RFC 3688]],
 +
          DOI 10.17487/RFC3688, January 2004,
 +
          <https://www.rfc-editor.org/info/rfc3688>.
  
−
  [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
+
[[RFC6020]]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
−
              Requirement Levels", BCP 14, RFC 2119,
+
          the Network Configuration Protocol (NETCONF)", [[RFC6020|RFC 6020]],
−
              DOI 10.17487/RFC2119, March 1997,
+
          DOI 10.17487/RFC6020, October 2010,
−
              <https://www.rfc-editor.org/info/rfc2119>.
+
          <https://www.rfc-editor.org/info/rfc6020>.
  
−
  [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
+
[[RFC6241]]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
−
              DOI 10.17487/RFC3688, January 2004,
+
          and A. Bierman, Ed., "Network Configuration Protocol
−
              <https://www.rfc-editor.org/info/rfc3688>.
+
          (NETCONF)", [[RFC6241|RFC 6241]], DOI 10.17487/RFC6241, June 2011,
 +
          <https://www.rfc-editor.org/info/rfc6241>.
  
−
  [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
+
[[RFC6242]]  Wasserman, M., "Using the NETCONF Protocol over Secure
−
              the Network Configuration Protocol (NETCONF)", RFC 6020,
+
          Shell (SSH)", [[RFC6242|RFC 6242]], DOI 10.17487/RFC6242, June 2011,
−
              DOI 10.17487/RFC6020, October 2010,
+
          <https://www.rfc-editor.org/info/rfc6242>.
−
              <https://www.rfc-editor.org/info/rfc6020>.
 
  
−
  [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
+
[[RFC7950]]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
−
              and A. Bierman, Ed., "Network Configuration Protocol
+
          [[RFC7950|RFC 7950]], DOI 10.17487/RFC7950, August 2016,
−
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
+
          <https://www.rfc-editor.org/info/rfc7950>.
−
              <https://www.rfc-editor.org/info/rfc6241>.
 
  
−
  [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
+
[[RFC8040]]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
−
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
+
          Protocol", [[RFC8040|RFC 8040]], DOI 10.17487/RFC8040, January 2017,
−
              <https://www.rfc-editor.org/info/rfc6242>.
+
          <https://www.rfc-editor.org/info/rfc8040>.
  
−
  [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
+
[[RFC8174]]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
−
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
+
          2119 Key Words", [[BCP14|BCP 14]], [[RFC8174|RFC 8174]], DOI 10.17487/RFC8174,
−
              <https://www.rfc-editor.org/info/rfc7950>.
+
          May 2017, <https://www.rfc-editor.org/info/rfc8174>.
  
−
  [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
+
[[RFC8341]]  Bierman, A. and M. Bjorklund, "Network Configuration
−
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
+
          Access Control Model", [[STD91|STD 91]], [[RFC8341|RFC 8341]],
−
              <https://www.rfc-editor.org/info/rfc8040>.
+
          DOI 10.17487/RFC8341, March 2018,
 +
          <https://www.rfc-editor.org/info/rfc8341>.
  
−
  [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
+
[[RFC8342]]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
−
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
+
          and R. Wilton, "Network Management Datastore Architecture
−
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.
+
          (NMDA)", [[RFC8342|RFC 8342]], DOI 10.17487/RFC8342, March 2018,
 +
          <https://www.rfc-editor.org/info/rfc8342>.
  
−
  [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
+
[[RFC8446]]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
−
              Access Control Model", STD 91, RFC 8341,
+
          Version 1.3", [[RFC8446|RFC 8446]], DOI 10.17487/RFC8446, August 2018,
−
              DOI 10.17487/RFC8341, March 2018,
+
          <https://www.rfc-editor.org/info/rfc8446>.
−
              <https://www.rfc-editor.org/info/rfc8341>.
 
  
−
  [RFC8342]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
+
[[RFC8525]]  Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K.,
−
              and R. Wilton, "Network Management Datastore Architecture
+
          and R. Wilton, "YANG Library", [[RFC8525|RFC 8525]],
−
              (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
+
          DOI 10.17487/RFC8525, March 2019,
−
              <https://www.rfc-editor.org/info/rfc8342>.
+
          <https://www.rfc-editor.org/info/rfc8525>.
  
−
  [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
+
=== Informative References ===
−
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
 
−
              <https://www.rfc-editor.org/info/rfc8446>.
 
  
−
  [RFC8525]  Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K.,
+
[BRSKI]    Pritikin, M., Richardson, M. C., Eckert, T., Behringer, M.
−
              and R. Wilton, "YANG Library", RFC 8525,
+
          H., and K. Watsen, "Bootstrapping Remote Secure Key
−
              DOI 10.17487/RFC8525, March 2019,
+
          Infrastructures (BRSKI)", Work in Progress, Internet-
−
              <https://www.rfc-editor.org/info/rfc8525>.
+
          Draft, draft-ietf-anima-bootstrapping-keyinfra-43, 7
−
 
+
          August 2020, <https://tools.ietf.org/html/draft-ietf-
−
7.2.  Informative References
+
          anima-bootstrapping-keyinfra-43>.
−
 
 
−
  [BRSKI]    Pritikin, M., Richardson, M. C., Eckert, T., Behringer, M.
 
−
              H., and K. Watsen, "Bootstrapping Remote Secure Key
 
−
              Infrastructures (BRSKI)", Work in Progress, Internet-
 
−
              Draft, draft-ietf-anima-bootstrapping-keyinfra-43, 7
 
−
              August 2020, <https://tools.ietf.org/html/draft-ietf-
 
−
              anima-bootstrapping-keyinfra-43>.
 
  
 
Acknowledgements
 
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, Benjamin Kaduk, Stephen Kent, Stewart Bryant,
+
Bierman, Susan Hares, Benjamin Kaduk, Stephen Kent, Stewart Bryant,
−
  Éric Vyncke, Murray Kucherawy, Roman Danyliw, Tony Przygienda, and
+
Éric Vyncke, Murray Kucherawy, Roman Danyliw, Tony Przygienda, and
−
  John Heasley for reviewing, and providing important input to, this
+
John Heasley for reviewing, and providing important input to, this
−
  document.
+
document.
  
 
Contributors
 
Contributors
  
−
  Rohit R Ranade
+
Rohit R Ranade
−
  Huawei
+
Huawei
−
 
 
− 
  
 +
  
 
Authors' Addresses
 
Authors' Addresses
  
−
  Qin Wu
+
Qin Wu
−
  Huawei
+
Huawei
−
  Yuhua District
+
Yuhua District
−
  101 Software Avenue
+
101 Software Avenue
−
  Nanjing
+
Nanjing
−
  Jiangsu, 210012
+
Jiangsu, 210012
−
  China
+
China
−
 
 
− 
  
 +
  
−
  Balazs Lengyel
+
Balazs Lengyel
−
  Ericsson Hungary
+
Ericsson Hungary
−
  Budapest
+
Budapest
−
  Magyar Tudosok korutja 11
+
Magyar Tudosok korutja 11
−
  1117
+
1117
−
  Hungary
+
Hungary
  
−
  Phone: +36-70-330-7909
+
Phone: +36-70-330-7909
−+
  
 +
Ye Niu
 +
Huawei
  
−
  Ye Niu
+
−
  Huawei
 
  
−+
[[Category:Standards Track]]

Latest revision as of 11:26, 30 October 2020



Internet Engineering Task Force (IETF) Q. Wu Request for Comments: 8808 Huawei Category: Standards Track B. Lengyel ISSN: 2070-1721 Ericsson Hungary 

                                                              Y. Niu
                                                              Huawei
                                                         August 2020

         A YANG Data Model for Factory Default Settings

Abstract

This document defines a YANG data model with the "factory-reset" RPC to allow clients to reset a server back to its factory default condition. It also defines an optional "factory-default" datastore to allow clients to read the factory default configuration for the device.

The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342.

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8808.

Copyright Notice

Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

1. Introduction 

 1.1.  Terminology

2. "Factory-Reset" RPC 3. "Factory-Default" Datastore 4. YANG Module 5. IANA Considerations 6. Security Considerations 7. References 

 7.1.  Normative References
 7.2.  Informative References

Acknowledgements Contributors Authors' Addresses

Introduction

This document defines a YANG data model and associated mechanism to reset a server to its factory default contents. This mechanism may be used, for example, when the existing configuration has major errors and so restarting the configuration process from scratch is the best option.

A "factory-reset" remote procedure call (RPC) is defined within the YANG data model. When resetting a device, all previous configuration settings will be lost and replaced by the factory default contents.

In addition, an optional "factory-default" read-only datastore is defined within the YANG data model. This datastore contains the data to replace the contents of implemented read-write conventional configuration datastores at reset and can also be used in the <get-data> operation.

The YANG data model in this document conforms to the Network Management Datastore Architecture defined in RFC8342.

Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174 when, and only when, they appear in all capitals, as shown here.

The following terms are defined in RFC8342 and RFC7950 and are not redefined here:

  • server
  • startup configuration datastore
  • candidate configuration datastore
  • running configuration datastore
  • intended configuration datastore
  • operational state datastore
  • conventional configuration datastore
  • datastore schema
  • RPC operation

This document defines the following term:

"factory-default" datastore: A read-only configuration datastore 

  holding a preset initial configuration that is used to initialize
  the configuration of a server.  This datastore is referred to as
  "<factory-default>".

"Factory-Reset" RPC

This document introduces a new "factory-reset" RPC. Upon receiving the RPC:

  • All supported conventional read-write configuration datastores
  (i.e., <running>, <startup>, and <candidate>) are reset to the
  contents of <factory-default>.
  • Read-only datastores receive their contents from other datastores
  (e.g., <intended> gets its contents from <running>).
  • All data in any dynamic configuration datastores MUST be
  discarded.
  • The contents of the <operational> datastore MUST reflect the
  operational state of the device after applying the factory default
  configuration.

In addition, the "factory-reset" RPC MUST restore nonvolatile storage to factory condition. Depending on the system, this may entail deleting dynamically generated files, such as those containing keys (e.g., /etc/ssl/private), certificates (e.g., /etc/ssl), logs (e.g., /var/log), and temporary files (e.g., /tmp/*). Any other cryptographic keys that are part of the factory-installed image will be retained (such as an Initial Device Identifier (IDevID) certificate [BRSKI]). When this process includes security-sensitive data such as cryptographic keys or passwords, it is RECOMMENDED to perform the deletion in as thorough a manner as possible (e.g., overwriting the physical storage medium with zeros and/or random bits for repurposing or end-of-life (EOL) disposal) to reduce the risk of the sensitive material being recoverable. The "factory-reset" RPC MAY also be used to trigger some other resetting tasks such as restarting the node or some of the software processes.

Note that operators should be aware that since all read-write datastores are immediately reset to factory default, the device may become unreachable as a host 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 and get it properly configured or otherwise restart processes needed to bootstrap it.

"Factory-Default" Datastore

Following the guidelines for defining datastores in Appendix A of RFC8342, this document introduces a new optional datastore resource named "factory-default" that represents a preset initial configuration that can be used to initialize the configuration of a server. A device MAY implement the "factory-reset" RPC without implementing the "factory-default" datastore, which would only eliminate the ability to programmatically determine the factory default configuration.

Name: "factory-default".

YANG modules: The "factory-default" datastore schema MUST be either 

  (1) the same as the conventional configuration datastores or
  (2) a subset of the datastore schema for the conventional
  configuration datastores.

YANG nodes: All "config true" data nodes.

Management operations: The contents of the datastore is set by the 

  server in an implementation-dependent manner.  The contents cannot
  be changed by management operations via the Network Configuration
  Protocol (NETCONF), RESTCONF, the CLI, etc., unless specialized,
  dedicated operations are provided.  The datastore can be read
  using the standard NETCONF/RESTCONF protocol operations.  The
  "factory-reset" operation copies the factory default contents to
  <running> and, if present, <startup> and/or <candidate>.  The
  contents of these datastores is then propagated automatically to
  any other read-only datastores, e.g., <intended> and
  <operational>.

Origin: This document does not define a new origin identity, as it 

  does not interact with the <operational> datastore.

Protocols: RESTCONF, NETCONF, and other management protocols.

Defining YANG module: "ietf-factory-default".

The contents of <factory-default> are defined by the device vendor and MUST persist across device restarts. If supported, the "factory- default" datastore MUST be included in the list of datastores in the YANG library RFC8525.

YANG Module

This module uses the "datastore" identity RFC8342 and the "default-deny-all" extension statement from RFC8341.

file "[email protected]" 

  module ietf-factory-default {
    yang-version 1.1;
    namespace "urn:ietf:params:xml:ns:yang:ietf-factory-default";
    prefix fd;

    import ietf-datastores {
      prefix ds;
      reference
        "RFC 8342: Network Management Datastore Architecture
         (NMDA)";
    }
    import ietf-netconf-acm {
      prefix nacm;
      reference
        "RFC 8341: Network Configuration Access Control Model";
    }

    organization
      "IETF Network Modeling (netmod) Working Group";
    contact
      "WG Web:   <https://datatracker.ietf.org/wg/netmod/>
       WG List:  <mailto:[email protected]>

       Editor:   Qin Wu
                 <mailto:[email protected]>

       Editor:   Balazs Lengyel
                 <mailto:[email protected]>

       Editor:   Ye Niu
                 <mailto:[email protected]>";
    description
      "This module provides functionality to reset a server to its
       factory default configuration and, when supported, to
       discover the factory default configuration contents
       independently of resetting the server.

       Copyright (c) 2020 IETF Trust and the persons identified as
       authors of the code.  All rights reserved.

       Redistribution and use in source and binary forms, with or
       without modification, is permitted pursuant to, and subject
       to the license terms contained in, the Simplified BSD License
       set forth in Section 4.c of the IETF Trust's Legal Provisions
       Relating to IETF Documents
       (https://trustee.ietf.org/license-info).

       This version of this YANG module is part of RFC 8808; see the
       RFC itself for full legal notices.";

    revision 2020-08-31 {
      description
        "Initial revision.";
      reference
        "RFC 8808: A YANG Data Model for Factory Default Settings";
    }

    feature factory-default-datastore {
      description
        "Indicates that the factory default configuration is
         available as a datastore.";
    }

    rpc factory-reset {
      nacm:default-deny-all;
      description
        "The server resets all datastores to their factory
         default contents and any nonvolatile storage back to
         factory condition, deleting all dynamically
         generated files, including those containing keys,
         certificates, logs, and other temporary files.

         Depending on the factory default configuration, after
         being reset, the device may become unreachable on the
         network.";
    }

    identity factory-default {
      if-feature "factory-default-datastore";
      base ds:datastore;
      description
        "This read-only datastore contains the factory default
         configuration for the device that will be used to replace
         the contents of the read-write conventional configuration
         datastores during a 'factory-reset' RPC operation.";
    }
  }

IANA Considerations

IANA has registered the following URI in the "ns" subregistry within the "IETF XML Registry" RFC3688:

URI: urn:ietf:params:xml:ns:yang:ietf-factory-default Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace.

IANA has registered the following YANG module in the "YANG Module Names" subregistry RFC6020 within the "YANG Parameters" registry:

Name: ietf-factory-default Namespace: urn:ietf:params:xml:ns:yang:ietf-factory-default Prefix: fd Reference: 8808

Security Considerations

The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF RFC6241 or RESTCONF RFC8040. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) RFC6242. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS RFC8446.

The Network Configuration Access Control Model (NACM) RFC8341 provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.

Access to the "factory-reset" RPC operation and factory default values of all configuration data nodes within the "factory-default" datastore is considered sensitive and therefore has been restricted by using the "default-deny-all" access control statement defined in RFC8341.

The "factory-reset" RPC can prevent any further management of the device when the server is reset back to its factory default condition, e.g., the session and client configurations are included in the factory default contents or treated as dynamic files in nonvolatile storage and overwritten by the "factory-reset" RPC.

The operational disruption caused by setting the configuration to factory default contents or the lack of appropriate security control on the factory default configuration varies greatly, depending on the implementation and current configuration.

The nonvolatile storage is expected to be wiped clean and reset back to the factory default state, but there is no guarantee that the data is wiped clean according to any particular data-cleansing standard, and the owner of the device MUST NOT rely on any sensitive data (e.g., private keys) being forensically unrecoverable from the device's nonvolatile storage after a "factory-reset" RPC has been invoked.

References

Normative References

RFC2119 Bradner, S., "Key words for use in RFCs to Indicate 

          Requirement Levels", BCP 14, RFC 2119,
          DOI 10.17487/RFC2119, March 1997,
          <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", 

          RFC 7950, DOI 10.17487/RFC7950, August 2016,
          <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 

          2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
          May 2017, <https://www.rfc-editor.org/info/rfc8174>.

RFC8341 Bierman, A. and M. Bjorklund, "Network Configuration 

          Access Control Model", STD 91, RFC 8341,
          DOI 10.17487/RFC8341, March 2018,
          <https://www.rfc-editor.org/info/rfc8341>.

RFC8342 Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 

          and R. Wilton, "Network Management Datastore Architecture
          (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
          <https://www.rfc-editor.org/info/rfc8342>.

RFC8446 Rescorla, E., "The Transport Layer Security (TLS) Protocol 

          Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
          <https://www.rfc-editor.org/info/rfc8446>.

RFC8525 Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., 

          and R. Wilton, "YANG Library", RFC 8525,
          DOI 10.17487/RFC8525, March 2019,
          <https://www.rfc-editor.org/info/rfc8525>.

Informative References

[BRSKI] Pritikin, M., Richardson, M. C., Eckert, T., Behringer, M. 

          H., and K. Watsen, "Bootstrapping Remote Secure Key
          Infrastructures (BRSKI)", Work in Progress, Internet-
          Draft, draft-ietf-anima-bootstrapping-keyinfra-43, 7
          August 2020, <https://tools.ietf.org/html/draft-ietf-
          anima-bootstrapping-keyinfra-43>.

Acknowledgements

Thanks to Juergen Schoenwaelder, Ladislav Lhotka, Alex Campbell, Joe Clarke, Robert Wilton, Kent Watsen, Joel Jaeggli, Lou Berger, Andy Bierman, Susan Hares, Benjamin Kaduk, Stephen Kent, Stewart Bryant, Éric Vyncke, Murray Kucherawy, Roman Danyliw, Tony Przygienda, and John Heasley for reviewing, and providing important input to, this document.

Contributors

Rohit R Ranade Huawei

Email: [email protected]

Authors' Addresses

Qin Wu Huawei Yuhua District 101 Software Avenue Nanjing Jiangsu, 210012 China

Email: [email protected]

Balazs Lengyel Ericsson Hungary Budapest Magyar Tudosok korutja 11 1117 Hungary

Phone: +36-70-330-7909 Email: [email protected]

Ye Niu Huawei

Email: [email protected]

Retrieved from "https://rfc-wiki.org/index.php?title=RFC8808&oldid=21289"