Support of asynchronous Enrollment in BRSKI
draft-fries-anima-brski-async-enroll-03

Document Type Active Internet-Draft (individual)
Last updated 2020-03-06
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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                                                        S. Fries
Internet-Draft                                              H. Brockhaus
Intended status: Standards Track                                 Siemens
Expires: September 7, 2020                                       E. Lear
                                                           Cisco Systems
                                                           March 6, 2020

              Support of asynchronous Enrollment in BRSKI
                draft-fries-anima-brski-async-enroll-03

Abstract

   This document discusses enhancements of bootstrapping of a remote
   secure key infrastructure (BRSKI) to also operate in domains
   featuring no or only timely limited connectivity to backend services
   offering enrollment functionality, specifically a Public Key
   Infrastructure (PKI).  The enhancements proposed to enable this are
   also applied to further set of use cases in which a pledge may not
   have a direct connection to the registrar and is served by for
   instance by a commissioning tool as an agent providing registrar
   connectivity.  In the context of deploying new devices the design of
   BRSKI allows for online (synchronous object exchange) and offline
   interactions (asynchronous object exchange) with a manufacturer's
   authorization service.  For this it utilizes an authenticated self-
   contained voucher to transport the domain credentials as a signed
   object to establish an initial trust between a pledge and the target
   deployment domain.  The currently supported enrollment protocol for
   request and distribution of deployment domain specific device
   certificates provides only limited support for asynchronous PKI
   interactions.  This memo motivates the enhancement of supporting
   authenticated self-contained objects for certificate management by
   using an abstract notation.  The enhancement allows on one hand off-
   site operation of PKI services outside the deployment domain of the
   pledge.  This addresses specifically scenarios, in which the final
   authorization of a certification request of a pledge cannot be made
   in the deployment domain and is therefore delegated to a operator
   backend.  On the other hand, this enhancement also facilitates the
   exchange of certificate management information via a pledge agent.
   The goal is to enable the usage of existing and potentially new PKI
   protocols supporting authenticated self-containment for certificate
   management exchanges.

Status of This Memo

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

Fries, et al.           Expires September 7, 2020               [Page 1]
Internet-Draft                  BRSKI-AE                      March 2020

   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."

   This Internet-Draft will expire on September 7, 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.  History of changes  . . . . . . . . . . . . . . . . . . . . .   6
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Scope of solution . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Supported environment . . . . . . . . . . . . . . . . . .   8
     4.2.  Application Examples  . . . . . . . . . . . . . . . . . .   9
       4.2.1.  Rolling stock . . . . . . . . . . . . . . . . . . . .   9
       4.2.2.  Building automation . . . . . . . . . . . . . . . . .   9
       4.2.3.  Substation automation . . . . . . . . . . . . . . . .  10
       4.2.4.  Electric vehicle charging infrastructure  . . . . . .  10
       4.2.5.  Infrastructure isolation policy . . . . . . . . . . .  11
       4.2.6.  Less operational security in the deployment domain  .  11
Show full document text