Using Autonomic Control Plane for Stable Connectivity of Network OAM
draft-ietf-anima-stable-connectivity-02

Document Type Active Internet-Draft (anima WG)
Last updated 2017-02-08 (latest revision 2017-02-07)
Replaces draft-eckert-anima-stable-connectivity
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Sheng Jiang
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Sheng Jiang" <jiangsheng@huawei.com>
ANIMA                                                          T. Eckert
Internet-Draft                                                    Huawei
Intended status: Informational                              M. Behringer
Expires: August 11, 2017                                           Cisco
                                                        February 7, 2017

  Using Autonomic Control Plane for Stable Connectivity of Network OAM
                draft-ietf-anima-stable-connectivity-02

Abstract

   OAM (Operations, Administration and Management) processes for data
   networks are often subject to the problem of circular dependencies
   when relying on network connectivity of the network to be managed for
   the OAM operations itself.  Provisioning during device/network bring
   up tends to be far less easy to automate than service provisioning
   later on, changes in core network functions impacting reachability
   can not be automated either because of ongoing connectivity
   requirements for the OAM equipment itself, and widely used OAM
   protocols are not secure enough to be carried across the network
   without security concerns.

   This document describes how to integrate OAM processes with the
   autonomic control plane (ACP) in Autonomic Networks (AN). to provide
   stable and secure connectivity for those OAM processes.

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 August 11, 2017.

Eckert & Behringer       Expires August 11, 2017                [Page 1]
Internet-Draft         AN Stable Connectivity OAM          February 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Self dependent OAM connectivity . . . . . . . . . . . . .   3
     1.2.  Data Communication Networks (DCNs)  . . . . . . . . . . .   3
     1.3.  Leveraging the ACP  . . . . . . . . . . . . . . . . . . .   4
   2.  Solutions . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Stable connectivity for centralized OAM operations  . . .   4
       2.1.1.  Simple connectivity for non-autonomic NOC application
               devices . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.2.  Limitations and enhancement overview  . . . . . . . .   5
       2.1.3.  Simultaneous ACP and data plane connectivity  . . . .   6
       2.1.4.  IPv4 only NOC application devices . . . . . . . . . .   7
       2.1.5.  Path selection policies . . . . . . . . . . . . . . .   8
       2.1.6.  Autonomic NOC device/applications . . . . . . . . . .  10
       2.1.7.  Encryption of data-plane connections  . . . . . . . .  10
       2.1.8.  Long term direction of the solution . . . . . . . . .  11
     2.2.  Stable connectivity for distributed network/OAM functions  12
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   4.  No IPv4 for ACP . . . . . . . . . . . . . . . . . . . . . . .  14
   5.  Further considerations  . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   8.  Change log [RFC Editor: Please remove]  . . . . . . . . . . .  15
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

Eckert & Behringer       Expires August 11, 2017                [Page 2]
Show full document text