Bootstrapping Key Infrastructures
draft-ietf-anima-bootstrapping-keyinfra-02

The information below is for an old version of the document
Document Type Active Internet-Draft (anima WG)
Last updated 2016-03-17
Replaces draft-pritikin-anima-bootstrapping-keyinfra
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestones: Mar 2015 - Adoption of initial ..., Jul 2018 - Submit bootstrap a t... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ANIMA WG                                                     M. Pritikin
Internet-Draft                                                     Cisco
Intended status: Informational                             M. Richardson
Expires: September 18, 2016                                          SSW
                                                            M. Behringer
                                                            S. Bjarnason
                                                                   Cisco
                                                          March 17, 2016

                   Bootstrapping Key Infrastructures
               draft-ietf-anima-bootstrapping-keyinfra-02

Abstract

   This document specifies automated bootstrapping of a key
   infrastructure (BSKI) using vendor installed IEEE 802.1AR
   manufacturing installed certificates, in combination with a vendor
   based service on the Internet.  Before being authenticated, a new
   device has only link-local connectivity, and does not require a
   routable address.  When a vendor provides an Internet based service,
   devices can be forced to join only specific domains but in limited/
   disconnected networks or legacy environments we describe a variety of
   options that allow bootstrapping to proceed.

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 18, 2016.

Copyright Notice

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

Pritikin, et al.       Expires September 18, 2016               [Page 1]
Internet-Draft      Bootstrapping Key Infrastructures         March 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Scope of solution . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Trust bootstrap . . . . . . . . . . . . . . . . . . . . .   6
   2.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   6
   3.  Functional Overview . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Behavior of a New Entity  . . . . . . . . . . . . . . . .  10
       3.1.1.  Discovery . . . . . . . . . . . . . . . . . . . . . .  12
       3.1.2.  Identity  . . . . . . . . . . . . . . . . . . . . . .  13
       3.1.3.  Request Join  . . . . . . . . . . . . . . . . . . . .  14
       3.1.4.  Imprint . . . . . . . . . . . . . . . . . . . . . . .  14
       3.1.5.  Enrollment  . . . . . . . . . . . . . . . . . . . . .  15
       3.1.6.  Being Managed . . . . . . . . . . . . . . . . . . . .  16
     3.2.  Behavior of a Proxy . . . . . . . . . . . . . . . . . . .  16
       3.2.1.  CoAP connection to Registrar  . . . . . . . . . . . .  16
       3.2.2.  HTTPS proxy connection to Registrar . . . . . . . . .  17
     3.3.  Behavior of the Registrar (Bootstrap Server)  . . . . . .  18
       3.3.1.  Entity Authentication . . . . . . . . . . . . . . . .  19
       3.3.2.  Entity Authorization  . . . . . . . . . . . . . . . .  19
       3.3.3.  Claiming the New Entity . . . . . . . . . . . . . . .  20
       3.3.4.  Log Verification  . . . . . . . . . . . . . . . . . .  20
       3.3.5.  Forwarding Audit Token plus Configuration . . . . . .  21
     3.4.  Behavior of the MASA Service  . . . . . . . . . . . . . .  21
       3.4.1.  Issue Authorization Token and Log the event . . . . .  21
       3.4.2.  Retrieve Audit Entries from Log . . . . . . . . . . .  22
     3.5.  Leveraging the new key infrastructure / next steps  . . .  22
       3.5.1.  Network boundaries  . . . . . . . . . . . . . . . . .  22
     3.6.  Interactions with Network Access Control  . . . . . . . .  22
   4.  Domain Operator Activities  . . . . . . . . . . . . . . . . .  23
Show full document text