Zero Touch Provisioning for NETCONF or RESTCONF based Management
draft-ietf-netconf-zerotouch-06

The information below is for an old version of the document
Document Type Active Internet-Draft (netconf WG)
Last updated 2016-03-16
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NETCONF Working Group                                          K. Watsen
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                          M. Abrahamsson
Expires: September 17, 2016                                    T-Systems
                                                          March 16, 2016

    Zero Touch Provisioning for NETCONF or RESTCONF based Management
                    draft-ietf-netconf-zerotouch-06

Abstract

   This draft presents a secure technique for establishing a NETCONF or
   RESTCONF connection between a newly deployed device, configured with
   just its factory default settings, and its deployment specific
   network management system (NMS).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 17, 2016.

Copyright Notice

   Copyright (c) 2016 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
   (http://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.

Watsen & Abrahamsson   Expires September 17, 2016               [Page 1]
Internet-Draft                 Zero Touch                     March 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   6
   2.  Guiding Principles  . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Trust Anchors . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Conveying Trust . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  Ownership . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Information Types . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  Redirect Information  . . . . . . . . . . . . . . . . . .   9
     3.2.  Bootstrap Information . . . . . . . . . . . . . . . . . .   9
   4.  Sources for Bootstrapping Data  . . . . . . . . . . . . . . .  10
     4.1.  Removable Storage . . . . . . . . . . . . . . . . . . . .  11
     4.2.  DNS Server  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.3.  DHCP Server . . . . . . . . . . . . . . . . . . . . . . .  13
     4.4.  Bootstrap Server  . . . . . . . . . . . . . . . . . . . .  14
   5.  Workflow Overview . . . . . . . . . . . . . . . . . . . . . .  14
     5.1.  Onboarding and Ordering Devices . . . . . . . . . . . . .  15
     5.2.  Owner Stages the Network for Bootstrap  . . . . . . . . .  17
     5.3.  Device Powers On  . . . . . . . . . . . . . . . . . . . .  19
   6.  Device Details  . . . . . . . . . . . . . . . . . . . . . . .  22
     6.1.  Factory Default State . . . . . . . . . . . . . . . . . .  23
     6.2.  Boot Sequence . . . . . . . . . . . . . . . . . . . . . .  24
     6.3.  Processing a Source of Boostrapping Data  . . . . . . . .  25
     6.4.  Validating Signed Data  . . . . . . . . . . . . . . . . .  26
     6.5.  Processing Redirect Information . . . . . . . . . . . . .  27
     6.6.  Processing Bootstrap Information  . . . . . . . . . . . .  27
   7.  YANG-defined API and Artifacts  . . . . . . . . . . . . . . .  28
     7.1.  Module Overview . . . . . . . . . . . . . . . . . . . . .  28
     7.2.  API Examples  . . . . . . . . . . . . . . . . . . . . . .  30
       7.2.1.  Unsigned Redirect Information . . . . . . . . . . . .  30
       7.2.2.  Signed Redirect Information . . . . . . . . . . . . .  31
       7.2.3.  Unsigned Bootstrap Information  . . . . . . . . . . .  34
       7.2.4.  Signed Bootstrap Information  . . . . . . . . . . . .  36
       7.2.5.  Progress Notifications  . . . . . . . . . . . . . . .  40
     7.3.  Artifact Examples . . . . . . . . . . . . . . . . . . . .  42
       7.3.1.  Signed Redirect Information . . . . . . . . . . . . .  42
Show full document text