Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8368
Discuss this RFC: Send questions or comments to the mailing listanima@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8368
Operations, Administration, and Maintenance (OAM), as per BCP 161,for data networks is often subject to the problem of circulardependencies when relying on connectivity provided by the network tobe managed for the OAM purposes.
Provisioning while bringing up devices and networks tends to be moredifficult to automate than service provisioning later on. Changes incore network functions impacting reachability cannot be automatedbecause of ongoing connectivity requirements for the OAM equipmentitself, and widely used OAM protocols are not secure enough to becarried across the network without security concerns.
This document describes how to integrate OAM processes with anautonomic control plane in order to provide stable and secureconnectivity for those OAM processes. This connectivity is notsubject to the aforementioned circular dependencies.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.