Secure Device Install
draft-ietf-opsawg-sdi-11

Document Type Active Internet-Draft (opsawg WG)
Last updated 2020-05-21 (latest revision 2020-05-20)
Replaces draft-wkumari-opsawg-sdi
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Michael Richardson
Shepherd write-up Show (last changed 2020-05-21)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Robert Wilton
Send notices to Michael Richardson <mcr+ietf@sandelman.ca>
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                          W. Kumari
Internet-Draft                                                    Google
Intended status: Informational                                  C. Doyle
Expires: November 21, 2020                              Juniper Networks
                                                            May 20, 2020

                         Secure Device Install
                        draft-ietf-opsawg-sdi-11

Abstract

   Deploying a new network device in a location where the operator has
   no staff of its own often requires that an employee physically travel
   to the location to perform the initial install and configuration,
   even in shared facilities with "remote-hands" type support.  In many
   cases, this could be avoided if there were a secure way to initially
   provision the device.

   This document extends existing vendor proprietary auto-install to
   make the process more secure.

   [ Ed note: Text inside square brackets ([]) is additional background
   information, answers to frequently asked questions, general musings,
   etc.  They will be removed before publication.  This document is
   being collaborated on in Github at: https://github.com/wkumari/draft-
   wkumari-opsawg-sdi.  The most recent version of the document, open
   issues, etc should all be available here.  The authors (gratefully)
   accept pull requests. ]

   [ Ed note: This document introduces concepts and serves as the basic
   for discussion.  Because of this, it is conversational, and would
   need to be firmed up before being published ]

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 https://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."

Kumari & Doyle          Expires November 21, 2020               [Page 1]
Internet-Draft            Secure Device Install                 May 2020

   This Internet-Draft will expire on November 21, 2020.

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Example Scenario  . . . . . . . . . . . . . . . . . . . .   5
   3.  Vendor Role . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Device key generation . . . . . . . . . . . . . . . . . .   6
     3.2.  Certificate Publication Server  . . . . . . . . . . . . .   6
   4.  Operator Role . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Administrative  . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Technical . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Example Initial Customer Boot . . . . . . . . . . . . . .   8
   5.  Additional Considerations . . . . . . . . . . . . . . . . . .  11
     5.1.  Key storage . . . . . . . . . . . . . . . . . . . . . . .  11
     5.2.  Key replacement . . . . . . . . . . . . . . . . . . . . .  11
     5.3.  Device reinstall  . . . . . . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  13
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . .  14
   Appendix B.  Proof of Concept . . . . . . . . . . . . . . . . . .  16
     B.1.  Step 1: Generating the certificate. . . . . . . . . . . .  16
       B.1.1.  Step 1.1: Generate the private key. . . . . . . . . .  16
       B.1.2.  Step 1.2: Generate the certificate signing request. .  16
       B.1.3.  Step 1.3: Generate the (self signed) certificate
               itself. . . . . . . . . . . . . . . . . . . . . . . .  17
Show full document text