To the degree this draft is actually talking about stable connectivity
for network management (O & M), it seems to make good sense to me.
The term OAM generally is used to refer to the mechanisms to monitor and
diagnose the data plane. These almost always rely on fate-shring with
the actual data behavior. As such, describing this (as the abstract and
other places in the document do) as addressing stable OAM is very confusing.
This distinction is discussed in RFC 6291 / BCP 161.
Yours,
Joel
On 2/7/17 1:00 PM, [email protected] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and
Approach of the IETF.
Title : Using Autonomic Control Plane for Stable Connectivity
of Network OAM
Authors : Toerless Eckert
Michael H. Behringer
Filename : draft-ietf-anima-stable-connectivity-02.txt
Pages : 16
Date : 2017-02-07
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.
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
