BRSKI Cloud Registrar
draft-friel-anima-brski-cloud-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-10-23
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
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)
|
Network Working Group O. Friel
Internet-Draft Cisco
Intended status: Standards Track R. Shekh-Yusef
Expires: April 25, 2020 Avaya
M. Richardson
Sandelman Software Works
October 23, 2019
BRSKI Cloud Registrar
draft-friel-anima-brski-cloud-01
Abstract
This document specifies the behaviour of a BRSKI Cloud Registrar, and
how a pledge can interact with a BRSKI Cloud Registrar when
bootstrapping.
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 April 25, 2020.
Copyright Notice
Copyright (c) 2019 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
Friel, et al. Expires April 25, 2020 [Page 1]
Internet-Draft BRSKI-CLOUD October 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Network Connectivity . . . . . . . . . . . . . . . . . . 4
3. Initial Voucher Request . . . . . . . . . . . . . . . . . . . 4
3.1. Cloud Registrar Discovery . . . . . . . . . . . . . . . . 4
3.2. Pledge - Cloud Registrar TLS Establishment Details . . . 4
3.3. Pledge Requests Voucher from the Cloud Registrar . . . . 5
4. Cloud Registrar Voucher Request Operation . . . . . . . . . . 5
4.1. Pledge Ownership Lookup . . . . . . . . . . . . . . . . . 5
5. Voucher Request Redirected to Local Domain Registrar . . . . 6
5.1. Pledge handling of Redirect . . . . . . . . . . . . . . . 6
6. Voucher Request Handled by Cloud Registrar . . . . . . . . . 6
7. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Voucher Request Redirected to Local Domain Registrar . . 7
7.2. Voucher Request Handled by Cloud Registrar . . . . . . . 8
7.2.1. Option 1: EST enroll completed against cloud
registrar . . . . . . . . . . . . . . . . . . . . . . 8
7.2.2. Option 2: EST redirect by cloud registrar . . . . . . 9
7.2.3. Option 3: Voucher includes EST domain . . . . . . . . 10
8. Pledge Certificate Identity Considerations . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. Informative References . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Bootstrapping Remote Secure Key Infrastructures (BRSKI)
[I-D.ietf-anima-bootstrapping-keyinfra] specifies automated
bootstrapping of an Autonomic Control Plane. BRSKI Section 2.7
describes how a pledge "MAY contact a well known URI of a cloud
registrar if a local registrar cannot be discovered or if the
pledge's target use cases do not include a local registrar".
This document further specifies use of a BRSKI cloud registrar and
clarifies operations that are not sufficiently specified in BRSKI.
Two high level deployment models are documented here:
o Local Domain Registrar Discovery: the cloud registrar is used by
the pledge to discover the local domain registrar. The cloud
registrar redirects the pledge to the local domain registrar, and
the pledge completes bootstrap against the local domain registrar.
Show full document text