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

The information below is for an old version of the document
Document Type Active Internet-Draft (anima WG)
Last updated 2016-03-21
Replaces draft-behringer-anima-autonomic-control-plane
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ANIMA WG                                               M. Behringer, Ed.
Internet-Draft                                              S. Bjarnason
Intended status: Standards Track                              Balaji. BL
Expires: September 22, 2016                                    T. Eckert
                                                           Cisco Systems
                                                          March 21, 2016

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

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 22, 2016.

Copyright Notice

   Copyright (c) 2016 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
   carefully, as they describe your rights and restrictions with respect

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

   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 . . . . . .   4
     2.3.  Data Plane Independent Permanent Reachability . . . . . .   5
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Self-Creation of an Autonomic Control Plane . . . . . . . . .   8
     5.1.  Preconditions . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Candidate ACP Neighbor Selection  . . . . . . . . . . . .   8
     5.3.  Capability Negotiation  . . . . . . . . . . . . . . . . .   9
     5.4.  Channel Establishment . . . . . . . . . . . . . . . . . .  10
     5.5.  Context Separation  . . . . . . . . . . . . . . . . . . .  10
     5.6.  Addressing inside the ACP . . . . . . . . . . . . . . . .  11
       5.6.1.  Fundamental Concepts of Autonomic Addressing  . . . .  11
       5.6.2.  The Base Addressing Scheme  . . . . . . . . . . . . .  12
       5.6.3.  Possible Sub-Schemes  . . . . . . . . . . . . . . . .  13
       5.6.4.  Usage of the Zone Field . . . . . . . . . . . . . . .  14
     5.7.  Routing in the ACP  . . . . . . . . . . . . . . . . . . .  15
   6.  Workarounds for Non-Autonomic Nodes . . . . . . . . . . . . .  16
     6.1.  Connecting a Non-Autonomic Controller / NMS system  . . .  16
     6.2.  ACP through Non-Autonomic L3 Clouds . . . . . . . . . . .  16
   7.  Building the ACP  . . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  Neighbor discovery via GRASP  . . . . . . . . . . . . . .  17
     7.2.  Channel Selection . . . . . . . . . . . . . . . . . . . .  17
     7.3.  Security Association protocols  . . . . . . . . . . . . .  18
       7.3.1.  ACP via IPsec . . . . . . . . . . . . . . . . . . . .  18
       7.3.2.  ACP via GRE/IPsec . . . . . . . . . . . . . . . . . .  19
       7.3.3.  ACP via dTLS  . . . . . . . . . . . . . . . . . . . .  19
       7.3.4.  GRASP/TLS negotiation . . . . . . . . . . . . . . . .  19
       7.3.5.  ACP Security Profiles . . . . . . . . . . . . . . . .  20
     7.4.  GRASP instance details  . . . . . . . . . . . . . . . . .  20
   8.  Self-Healing Properties . . . . . . . . . . . . . . . . . . .  21
Show full document text