An Autonomic Control Plane
draft-ietf-anima-autonomic-control-plane-06

Document Type Active Internet-Draft (anima WG)
Last updated 2017-03-27
Replaces draft-behringer-anima-autonomic-control-plane
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Sheng Jiang
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Sheng Jiang" <jiangsheng@huawei.com>
ANIMA WG                                               M. Behringer, Ed.
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                               T. Eckert
Expires: September 28, 2017                                       Huawei
                                                            S. Bjarnason
                                                          Arbor Networks
                                                          March 27, 2017

                       An Autonomic Control Plane
              draft-ietf-anima-autonomic-control-plane-06

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 an "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 communications
   over a network that is not configured, or mis-configured.

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 http://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 September 28, 2017.

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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Behringer, et al.      Expires September 28, 2017               [Page 1]
Internet-Draft         An Autonomic Control Plane             March 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases for an Autonomic Control Plane  . . . . . . . . . .   4
     2.1.  An Infrastructure for Autonomic Functions . . . . . . . .   4
     2.2.  Secure Bootstrap over an Unconfigured Network . . . . . .   5
     2.3.  Data Plane Independent Permanent Reachability . . . . . .   5
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Self-Creation of an Autonomic Control Plane . . . . . . . . .   8
     5.1.  Preconditions . . . . . . . . . . . . . . . . . . . . . .   8
       5.1.1.  Domain Certificate with ANIMA information . . . . . .   8
       5.1.2.  AN Adjacency Table  . . . . . . . . . . . . . . . . .  10
     5.2.  Neighbor discovery  . . . . . . . . . . . . . . . . . . .  11
       5.2.1.  L2 topology considerations  . . . . . . . . . . . . .  11
       5.2.2.  CDP/LLDP/mDNS considerations  . . . . . . . . . . . .  12
       5.2.3.  Discovery with GRASP  . . . . . . . . . . . . . . . .  12
       5.2.4.  Discovery and BRSKY . . . . . . . . . . . . . . . . .  13
     5.3.  Candidate ACP Neighbor Selection  . . . . . . . . . . . .  13
     5.4.  Channel Selection . . . . . . . . . . . . . . . . . . . .  14
     5.5.  Security Association protocols  . . . . . . . . . . . . .  15
       5.5.1.  ACP via IPsec . . . . . . . . . . . . . . . . . . . .  15
       5.5.2.  ACP via GRE/IPsec . . . . . . . . . . . . . . . . . .  16
       5.5.3.  ACP via dTLS  . . . . . . . . . . . . . . . . . . . .  16
       5.5.4.  GRASP/TLS negotiation . . . . . . . . . . . . . . . .  16
       5.5.5.  ACP Security Profiles . . . . . . . . . . . . . . . .  17
     5.6.  GRASP instance details  . . . . . . . . . . . . . . . . .  17
     5.7.  Context Separation  . . . . . . . . . . . . . . . . . . .  18
     5.8.  Addressing inside the ACP . . . . . . . . . . . . . . . .  18
       5.8.1.  Fundamental Concepts of Autonomic Addressing  . . . .  18
       5.8.2.  The ACP Addressing Base Scheme  . . . . . . . . . . .  19
Show full document text