Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance
RFC 8368, “Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance”, is an Informational document published in May 2018 by T. Eckert, M. Behringer. The canonical text is published by the RFC Editor.
Abstract
Operations, Administration, and Maintenance (OAM), as per BCP 161, for data networks is 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 an autonomic control plane in order to provide stable and secure connectivity for those OAM processes. This connectivity is not subject to the aforementioned circular dependencies.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8368 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8367 Wrongful Termination of Internet Protocol Packets
- RFC 8369 Internationalizing IPv6 Using 128-Bit Unicode
- RFC 8366 A Voucher Artifact for Bootstrapping Protocols
- RFC 8370 Techniques to Improve the Scalability of RSVP-TE Deployments
- RFC 8365 A Network Virtualization Overlay Solution Using Ethernet VPN
- RFC 8371 Mobile Node Identifier Types for MIPv6
- RFC 8364 PIM Flooding Mechanism and Source Discovery
- RFC 8372 MPLS Flow Identification Considerations