An Autonomic Control Plane (ACP)
draft-ietf-anima-autonomic-control-plane-30
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
Document | Type | Active Internet-Draft (anima WG) | ||
---|---|---|---|---|
Authors | Toerless Eckert , Michael Behringer , Steinthor Bjarnason | |||
Last updated | 2021-01-25 (latest revision 2020-10-30) | |||
Replaces | draft-behringer-anima-autonomic-control-plane | |||
Stream | IETF | |||
Intended RFC status | Proposed Standard | |||
Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication | ||
Document shepherd | Sheng Jiang | |||
Shepherd write-up | Show (last changed 2020-07-30) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Éric Vyncke | |||
Send notices to | "Sheng Jiang" <jiangsheng@huawei.com> | |||
IANA | IANA review state | Version Changed - Review Needed | ||
IANA action state | RFC-Ed-Ack | |||
IANA expert review state | Expert Reviews OK | |||
RFC Editor | RFC Editor state | REF | ||
Details |
ANIMA WG T. Eckert, Ed. Internet-Draft Futurewei USA Intended status: Standards Track M. Behringer, Ed. Expires: 3 May 2021 S. Bjarnason Arbor Networks 30 October 2020 An Autonomic Control Plane (ACP) draft-ietf-anima-autonomic-control-plane-30 Abstract Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing, and as independent as possible of configuration. This document defines such a plane and calls it the "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out-of-band channel" for Operations, Administration and Management (OAM) communications over a network that provides automatically configured hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured, or misconfigured. 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 3 May 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. Eckert, et al. Expires 3 May 2021 [Page 1] Internet-Draft An Autonomic Control Plane (ACP) October 2020 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 (Informative) . . . . . . . . . . . . . . . . . 6 1.1. Applicability and Scope . . . . . . . . . . . . . . . . . 9 2. Acronyms and Terminology (Informative) . . . . . . . . . . . 11 3. Use Cases for an Autonomic Control Plane (Informative) . . . 16 3.1. An Infrastructure for Autonomic Functions . . . . . . . . 17 3.2. Secure Bootstrap over a not configured Network . . . . . 17 3.3. Data-Plane Independent Permanent Reachability . . . . . . 17 4. Requirements (Informative) . . . . . . . . . . . . . . . . . 19 5. Overview (Informative) . . . . . . . . . . . . . . . . . . . 20 6. Self-Creation of an Autonomic Control Plane (ACP) (Normative) . . . . . . . . . . . . . . . . . . . . . . . 21 6.1. Requirements for use of Transport Layer Security (TLS) . 22 6.2. ACP Domain, Certificate and Network . . . . . . . . . . . 23 6.2.1. ACP Certificates . . . . . . . . . . . . . . . . . . 24 6.2.2. ACP Certificate AcpNodeName . . . . . . . . . . . . . 26 6.2.2.1. AcpNodeName ASN.1 Module . . . . . . . . . . . . 29 6.2.3. ACP domain membership check . . . . . . . . . . . . . 30 6.2.3.1. Realtime clock and Time Validation . . . . . . . 33 6.2.4. Trust Anchors (TA) . . . . . . . . . . . . . . . . . 33 6.2.5. Certificate and Trust Anchor Maintenance . . . . . . 34 6.2.5.1. GRASP objective for EST server . . . . . . . . . 35 6.2.5.2. Renewal . . . . . . . . . . . . . . . . . . . . . 37 6.2.5.3. Certificate Revocation Lists (CRLs) . . . . . . . 37 6.2.5.4. Lifetimes . . . . . . . . . . . . . . . . . . . . 38 6.2.5.5. Re-enrollment . . . . . . . . . . . . . . . . . . 38 6.2.5.6. Failing Certificates . . . . . . . . . . . . . . 40 6.3. ACP Adjacency Table . . . . . . . . . . . . . . . . . . . 41 6.4. Neighbor Discovery with DULL GRASP . . . . . . . . . . . 41 6.5. Candidate ACP Neighbor Selection . . . . . . . . . . . . 45Show full document text