Support of asynchronous Enrollment in BRSKI (BRSKI-AE)
draft-ietf-anima-brski-async-enroll-01
ANIMA WG S. Fries
Internet-Draft H. Brockhaus
Intended status: Standards Track Siemens
Expires: July 11, 2021 E. Lear
Cisco Systems
T. Werner
Siemens
January 7, 2021
Support of asynchronous Enrollment in BRSKI (BRSKI-AE)
draft-ietf-anima-brski-async-enroll-01
Abstract
This document describes enhancements of bootstrapping a remote secure
key infrastructure (BRSKI) to also operate in domains featuring no or
only timely limited connectivity between involved components.
Moreover, newly introduced are methods to perform the BRSKI approach
in environments, in which the role of the pledge changes to a server
instead of the client. This changes the interaction model as the
pledge is pushed to interact with the registrar instead of pulling
information from the registrar. To support both, BRSKI-AE relies on
the exchange of it authenticated self-contained objects (signature-
wrapped objects) also for requesting and distributing of domain
specific device certificates. The defined approach is agnostic
regarding the utilized enrollment protocol allowing the application
of existing and potentially new certificate management protocols.
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."
This Internet-Draft will expire on July 11, 2021.
Fries, et al. Expires July 11, 2021 [Page 1]
Internet-Draft BRSKI-AE January 2021
Copyright Notice
Copyright (c) 2021 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Scope of solution . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Supported environment . . . . . . . . . . . . . . . . . . 7
3.2. Application Examples . . . . . . . . . . . . . . . . . . 7
3.2.1. Rolling stock . . . . . . . . . . . . . . . . . . . . 7
3.2.2. Building automation . . . . . . . . . . . . . . . . . 8
3.2.3. Substation automation . . . . . . . . . . . . . . . . 8
3.2.4. Electric vehicle charging infrastructure . . . . . . 9
3.2.5. Infrastructure isolation policy . . . . . . . . . . . 9
3.2.6. Less operational security in the target domain . . . 9
4. Requirement discussion and mapping to solution elements . . . 9
5. Architectural Overview and Communication Exchanges . . . . . 12
5.1. Use Case 1 (PULL): Support of off-site PKI service . . . 12
5.1.1. Behavior of a pledge . . . . . . . . . . . . . . . . 15
5.1.2. Pledge - Registrar discovery and voucher exchange . . 16
5.1.3. Registrar - MASA voucher exchange . . . . . . . . . . 16
5.1.4. Pledge - Registrar - RA/CA certificate enrollment . . 16
5.1.5. Addressing Scheme Enhancements . . . . . . . . . . . 19
5.2. Use Case 2 (PUSH): pledge-agent . . . . . . . . . . . . . 19
5.2.1. Behavior of a pledge . . . . . . . . . . . . . . . . 23
5.2.2. Behavior of a pledge-agent . . . . . . . . . . . . . 24
5.2.3. Protocol Details (Pledge-Agent - Pledge) . . . . . . 25
5.2.4. Protocol flow . . . . . . . . . . . . . . . . . . . . 29
5.3. Domain registrar support of different enrollment options 31
Show full document text