Using Autonomic Control Plane for Stable Connectivity of Network OAM
draft-eckert-anima-stable-connectivity-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Toerless Eckert , Michael H. Behringer | ||
| Last updated | 2015-09-07 (Latest revision 2015-03-06) | ||
| Replaced by | draft-ietf-anima-stable-connectivity, draft-ietf-anima-stable-connectivity, RFC 8368 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Toerless Eckert
Michael H. Behringer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)