RFC 8995 on Bootstrapping Remote Secure Key Infrastructure (BRSKI)
rfc-editor@rfc-editor.org Sat, 22 May 2021 05:50 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5AA3A164A; Fri, 21 May 2021 22:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8TvjdN0BLSp; Fri, 21 May 2021 22:50:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECCB13A1614; Fri, 21 May 2021 22:50:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F2B3DF40722; Fri, 21 May 2021 22:50:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8995 on Bootstrapping Remote Secure Key Infrastructure (BRSKI)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, anima@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210522055003.F2B3DF40722@rfc-editor.org>
Date: Fri, 21 May 2021 22:50:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/j2UJX6YeXt71Z8hES_716MC9_1s>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 May 2021 05:50:33 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8995
Title: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Author: M. Pritikin,
M. Richardson,
T. Eckert,
M. Behringer,
K. Watsen
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: pritikin@cisco.com,
mcr+ietf@sandelman.ca,
tte+ietf@cs.fau.de,
Michael.H.Behringer@gmail.com,
kent+ietf@watsen.net
Pages: 116
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-anima-bootstrapping-keyinfra-45.txt
URL: https://www.rfc-editor.org/info/rfc8995
DOI: 10.17487/RFC8995
This document specifies automated bootstrapping of an Autonomic
Control Plane. To do this, a Secure Key Infrastructure is
bootstrapped. This is done using manufacturer-installed X.509
certificates, in combination with a manufacturer's authorizing
service, both online and offline. We call this process the
Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol.
Bootstrapping a new device can occur when using a routable address
and a cloud service, only link-local connectivity, or
limited/disconnected networks. Support for deployment models with
less stringent security requirements is included. Bootstrapping is
complete when the cryptographic identity of the new key
infrastructure is successfully deployed to the device. The
established secure connection can be used to deploy a locally issued
certificate to the device as well.
This document is a product of the Autonomic Networking Integrated Model and Approach Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC