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

Document Type Active Internet-Draft (anima WG)
Last updated 2017-11-15 (latest revision 2017-10-18)
Replaces draft-eckert-anima-stable-connectivity
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Sheng Jiang
Shepherd write-up Show (last changed 2017-10-21)
IESG IESG state In Last Call (ends 2017-11-26)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Terry Manderson
Send notices to "Sheng Jiang" <jiangsheng@huawei.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
ANIMA                                                     T. Eckert, Ed.
Internet-Draft                                                    Huawei
Intended status: Informational                              M. Behringer
Expires: April 21, 2018                                 October 18, 2017

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

Abstract

   OAM (Operations, Administration and Maintenance - as per BCP161,
   (RFC6291) processes for data networks are often subject to the
   problem of circular dependencies when relying on connectivity
   provided by the network to be managed for the OAM purposes.

   Provisioning while bringing up devices and networks tends to be more
   difficult to automate than service provisioning later on, changes in
   core network functions impacting reachability cannot be automated
   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) in order to
   provide stable and secure connectivity for those OAM processes.  This
   connectivity is not subject to aforementioned circular dependencies.

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 21, 2018.

Eckert & Behringer       Expires April 21, 2018                 [Page 1]
Internet-Draft         AN Stable Connectivity OAM           October 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Self dependent OAM Connectivity . . . . . . . . . . . . .   2
     1.2.  Data Communication Networks (DCNs)  . . . . . . . . . . .   3
     1.3.  Leveraging the ACP  . . . . . . . . . . . . . . . . . . .   4
   2.  Solutions . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Stable Connectivity for Centralized OAM . . . . . . . . .   4
       2.1.1.  Simple Connectivity for Non-ACP capable NMS Hosts . .   5
       2.1.2.  Challenges and Limitation of Simple Connectivity  . .   6
       2.1.3.  Simultaneous ACP and Data Plane Connectivity  . . . .   7
       2.1.4.  IPv4-only NMS Hosts . . . . . . . . . . . . . . . . .   8
       2.1.5.  Path Selection Policies . . . . . . . . . . . . . . .  11
       2.1.6.  Autonomic NOC Device/Applications . . . . . . . . . .  12
       2.1.7.  Encryption of data-plane connections  . . . . . . . .  13
       2.1.8.  Long Term Direction of the Solution . . . . . . . . .  14
     2.2.  Stable Connectivity for Distributed Network/OAM . . . . .  15
   3.  Architectural Considerations  . . . . . . . . . . . . . . . .  15
     3.1.  No IPv4 for ACP . . . . . . . . . . . . . . . . . . . . .  15
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   7.  Change log [RFC Editor: Please remove]  . . . . . . . . . . .  18
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

1.1.  Self dependent OAM Connectivity

   OAM (Operations, Administration and Maintenance - as per BCP161,
Show full document text