Bootstrapping Key Infrastructures
draft-pritikin-anima-bootstrapping-keyinfra-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-02-13
Replaces draft-pritikin-bootstrapping-keyinfrastructures
Replaced by draft-ietf-anima-bootstrapping-keyinfra
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ANIMA WG                                                     M. Pritikin
Internet-Draft                                              M. Behringer
Intended status: Informational                              S. Bjarnason
Expires: August 17, 2015                                           Cisco
                                                       February 13, 2015

                   Bootstrapping Key Infrastructures
             draft-pritikin-anima-bootstrapping-keyinfra-01

Abstract

   This document specifies automated bootstrapping of an key
   infrastructure 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 for constrained 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 August 17, 2015.

Copyright Notice

   Copyright (c) 2015 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

Pritikin, et al.         Expires August 17, 2015                [Page 1]
Internet-Draft      Bootstrapping Key Infrastructures      February 2015

   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
   2.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   4
   3.  Operational Overview  . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Instantiating the Domain Certification Authority  . . . .   7
     3.2.  Instantiating the Registrar . . . . . . . . . . . . . . .   7
     3.3.  Accepting New Entities  . . . . . . . . . . . . . . . . .   8
     3.4.  Automatic Enrolment of Devices  . . . . . . . . . . . . .   9
     3.5.  Operating the Network . . . . . . . . . . . . . . . . . .   9
   4.  Functional Overview . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Behavior of a new entity  . . . . . . . . . . . . . . . .  10
       4.1.1.  Proxy Discovery . . . . . . . . . . . . . . . . . . .  11
       4.1.2.  Receiving and accepting the Domain Identity . . . . .  12
       4.1.3.  Enrollment  . . . . . . . . . . . . . . . . . . . . .  13
       4.1.4.  After Enrollment  . . . . . . . . . . . . . . . . . .  13
     4.2.  Behavior of a proxy . . . . . . . . . . . . . . . . . . .  13
     4.3.  Behavior of the Registrar . . . . . . . . . . . . . . . .  14
       4.3.1.  Authenticating the Device . . . . . . . . . . . . . .  14
       4.3.2.  Accepting the Entity  . . . . . . . . . . . . . . . .  14
       4.3.3.  Claiming the new entity . . . . . . . . . . . . . . .  15
     4.4.  Behavior of the MASA Service  . . . . . . . . . . . . . .  15
       4.4.1.  Issue Authorization Token and Log the event . . . . .  16
       4.4.2.  Retrieve Audit Entries from Log . . . . . . . . . . .  16
     4.5.  Leveraging the new key infrastructure / next steps  . . .  16
       4.5.1.  Network boundaries  . . . . . . . . . . . . . . . . .  16
   5.  Protocol Details  . . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  EAP-EST . . . . . . . . . . . . . . . . . . . . . . . . .  18
     5.2.  Request bootstrap token . . . . . . . . . . . . . . . . .  18
     5.3.  Request MASA authorization token  . . . . . . . . . . . .  18
     5.4.  Request MASA authorization log  . . . . . . . . . . . . .  19
   6.  Reduced security operational modes  . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
     7.1.  Trust Model . . . . . . . . . . . . . . . . . . . . . . .  22
Show full document text