An Autonomic Control Plane (ACP)
draft-ietf-anima-autonomic-control-plane-16

Document Type Active Internet-Draft (anima WG)
Last updated 2018-06-08
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 (wg milestones: Mar 2015 - Adoption of initial ..., Sep 2016 - Submit autonomic con... )
Document shepherd Sheng Jiang
Shepherd write-up Show (last changed 2018-01-29)
IESG IESG state IESG Evaluation - Defer
Consensus Boilerplate Yes
Telechat date On agenda of 2018-08-02 IESG telechat
Needs 5 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                                                    Huawei
Intended status: Standards Track                       M. Behringer, Ed.
Expires: December 10, 2018
                                                            S. Bjarnason
                                                          Arbor Networks
                                                            June 8, 2018

                    An Autonomic Control Plane (ACP)
              draft-ietf-anima-autonomic-control-plane-16

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 is secure and reliable 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 December 10, 2018.

Copyright Notice

   Copyright (c) 2018 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

Eckert, et al.          Expires December 10, 2018               [Page 1]
Internet-Draft      An Autonomic Control Plane (ACP)           June 2018

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.1.  Applicability and Scope . . . . . . . . . . . . . . . . .   7
   2.  Acronyms and Terminology  . . . . . . . . . . . . . . . . . .   9
   3.  Use Cases for an Autonomic Control Plane  . . . . . . . . . .  14
     3.1.  An Infrastructure for Autonomic Functions . . . . . . . .  14
     3.2.  Secure Bootstrap over a not configured Network  . . . . .  14
     3.3.  Data-Plane Independent Permanent Reachability . . . . . .  15
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   6.  Self-Creation of an Autonomic Control Plane (ACP) (Normative)  18
     6.1.  ACP Domain, Certificate and Network . . . . . . . . . . .  19
       6.1.1.  Certificate Domain Information Field  . . . . . . . .  20
       6.1.2.  ACP domain membership check . . . . . . . . . . . . .  22
       6.1.3.  Certificate Maintenance . . . . . . . . . . . . . . .  23
         6.1.3.1.  GRASP objective for EST server  . . . . . . . . .  23
         6.1.3.2.  Renewal . . . . . . . . . . . . . . . . . . . . .  25
         6.1.3.3.  Certificate Revocation Lists (CRLs) . . . . . . .  25
         6.1.3.4.  Lifetimes . . . . . . . . . . . . . . . . . . . .  26
         6.1.3.5.  Re-enrollment . . . . . . . . . . . . . . . . . .  26
         6.1.3.6.  Failing Certificates  . . . . . . . . . . . . . .  27
     6.2.  ACP Adjacency Table . . . . . . . . . . . . . . . . . . .  28
     6.3.  Neighbor Discovery with DULL GRASP  . . . . . . . . . . .  29
     6.4.  Candidate ACP Neighbor Selection  . . . . . . . . . . . .  32
     6.5.  Channel Selection . . . . . . . . . . . . . . . . . . . .  32
     6.6.  Candidate ACP Neighbor verification . . . . . . . . . . .  34
     6.7.  Security Association protocols  . . . . . . . . . . . . .  34
       6.7.1.  ACP via IKEv2 . . . . . . . . . . . . . . . . . . . .  34
         6.7.1.1.  Native IPsec  . . . . . . . . . . . . . . . . . .  34
         6.7.1.2.  IPsec with GRE encapsulation  . . . . . . . . . .  35
       6.7.2.  ACP via DTLS  . . . . . . . . . . . . . . . . . . . .  36
       6.7.3.  ACP Secure Channel Requirements . . . . . . . . . . .  36
Show full document text