An Autonomic Control Plane (ACP)
draft-ietf-anima-autonomic-control-plane-20
| Document | Type | Active Internet-Draft (anima WG) | |
|---|---|---|---|
| Last updated | 2019-07-22 | ||
| Replaces | draft-behringer-anima-autonomic-control-plane | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text xml pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Sheng Jiang | ||
| Shepherd write-up | Show (last changed 2019-03-27) | ||
| IESG | IESG state | IESG Evaluation - Defer::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Needs a YES. Has a DISCUSS. Needs 3 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Terry Manderson | ||
| Send notices to | "Sheng Jiang" <jiangsheng@huawei.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | None | ||
ANIMA WG T. Eckert, Ed.
Internet-Draft Futurewei USA
Intended status: Standards Track M. Behringer, Ed.
Expires: January 23, 2020
S. Bjarnason
Arbor Networks
July 22, 2019
An Autonomic Control Plane (ACP)
draft-ietf-anima-autonomic-control-plane-20
Abstract
Autonomic functions need a control plane to communicate, which
depends on some addressing and routing. This Autonomic Management
and 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 January 23, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Eckert, et al. Expires January 23, 2020 [Page 1]
Internet-Draft An Autonomic Control Plane (ACP) July 2019
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 . . . . . . . . . . . . . . . . . 8
2. Acronyms and Terminology (Informative) . . . . . . . . . . . 10
3. Use Cases for an Autonomic Control Plane (Informative) . . . 16
3.1. An Infrastructure for Autonomic Functions . . . . . . . . 16
3.2. Secure Bootstrap over a not configured Network . . . . . 16
3.3. Data-Plane Independent Permanent Reachability . . . . . . 16
4. Requirements (Informative) . . . . . . . . . . . . . . . . . 18
5. Overview (Informative) . . . . . . . . . . . . . . . . . . . 19
6. Self-Creation of an Autonomic Control Plane (ACP) (Normative) 20
6.1. ACP Domain, Certificate and Network . . . . . . . . . . . 20
6.1.1. ACP Certificates . . . . . . . . . . . . . . . . . . 21
6.1.2. ACP Certificate ACP Domain Information Field . . . . 22
6.1.3. ACP domain membership check . . . . . . . . . . . . . 26
6.1.4. Trust Points and Trust Anchors . . . . . . . . . . . 28
6.1.5. Certificate and Trust Point Maintenance . . . . . . . 29
6.1.5.1. GRASP objective for EST server . . . . . . . . . 30
6.1.5.2. Renewal . . . . . . . . . . . . . . . . . . . . . 31
6.1.5.3. Certificate Revocation Lists (CRLs) . . . . . . . 31
6.1.5.4. Lifetimes . . . . . . . . . . . . . . . . . . . . 32
6.1.5.5. Re-enrollment . . . . . . . . . . . . . . . . . . 32
6.1.5.6. Failing Certificates . . . . . . . . . . . . . . 34
6.2. ACP Adjacency Table . . . . . . . . . . . . . . . . . . . 34
6.3. Neighbor Discovery with DULL GRASP . . . . . . . . . . . 35
6.4. Candidate ACP Neighbor Selection . . . . . . . . . . . . 38
6.5. Channel Selection . . . . . . . . . . . . . . . . . . . . 39
6.6. Candidate ACP Neighbor verification . . . . . . . . . . . 42
6.7. Security Association protocols . . . . . . . . . . . . . 42
6.7.1. ACP via IKEv2 . . . . . . . . . . . . . . . . . . . . 43
Show full document text