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

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19
• 20

ANIMA WG                                               M. Behringer, Ed.
Internet-Draft
Intended status: Standards Track                          T. Eckert, Ed.
Expires: April 15, 2018                                           Huawei
                                                            S. Bjarnason
                                                          Arbor Networks
                                                        October 12, 2017

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

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 OAM (Operations Administration and
   Management) communications over a network that is secure and reliable
   even when the network is not configured, or not 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 April 15, 2018.

Copyright Notice

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

Behringer, et al.        Expires April 15, 2018                 [Page 1]
Internet-Draft      An Autonomic Control Plane (ACP)        October 2017

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Acronyms and Terminology  . . . . . . . . . . . . . . . . . .   6
   3.  Use Cases for an Autonomic Control Plane  . . . . . . . . . .  10
     3.1.  An Infrastructure for Autonomic Functions . . . . . . . .  10
     3.2.  Secure Bootstrap over a not configured Network  . . . . .  10
     3.3.  Data-Plane Independent Permanent Reachability . . . . . .  11
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Self-Creation of an Autonomic Control Plane (ACP) (Normative)  14
     6.1.  ACP Domain, Certificate and Network . . . . . . . . . . .  14
       6.1.1.  Certificate Domain Information Field  . . . . . . . .  15
       6.1.2.  ACP domain membership check . . . . . . . . . . . . .  18
       6.1.3.  Certificate Maintenance . . . . . . . . . . . . . . .  18
     6.2.  ACP Adjacency Table . . . . . . . . . . . . . . . . . . .  20
     6.3.  Neighbor Discovery with DULL GRASP  . . . . . . . . . . .  21
     6.4.  Candidate ACP Neighbor Selection  . . . . . . . . . . . .  23
     6.5.  Channel Selection . . . . . . . . . . . . . . . . . . . .  24
     6.6.  Candidate ACP Neighbor verification . . . . . . . . . . .  26
     6.7.  Security Association protocols  . . . . . . . . . . . . .  26
       6.7.1.  ACP via IKEv2 . . . . . . . . . . . . . . . . . . . .  26
       6.7.2.  ACP via dTLS  . . . . . . . . . . . . . . . . . . . .  27
       6.7.3.  ACP Secure Channel Requirements . . . . . . . . . . .  28
     6.8.  GRASP in the ACP  . . . . . . . . . . . . . . . . . . . .  28
       6.8.1.  GRASP as a core service of the ACP  . . . . . . . . .  28
       6.8.2.  ACP as the Security and Transport substrate for GRASP  29
     6.9.  Context Separation  . . . . . . . . . . . . . . . . . . .  33
     6.10. Addressing inside the ACP . . . . . . . . . . . . . . . .  33
       6.10.1.  Fundamental Concepts of Autonomic Addressing . . . .  33
       6.10.2.  The ACP Addressing Base Scheme . . . . . . . . . . .  35
       6.10.3.  ACP Zone Addressing Sub-Scheme . . . . . . . . . . .  35
       6.10.4.  ACP Manual Addressing Sub-Scheme . . . . . . . . . .  38