RFC 7575: Autonomic Networking: Definitions and Design Goals
In plain English — editorial summary, not part of the RFC
Autonomic systems were first described in 2001. The fundamental goal is self-management, including self-configuration, self-optimization, self-healing, and self-protection. This is achieved by an autonomic function having minimal dependencies on human administrators or centralized management systems. It usually implies distribution across network elements. This document defines common language and outlines design goals (and what are not design goals) for autonomic functions. A high-level reference model illustrates how functional elements in an Autonomic Network interact. This document is a product of the IRTF's Network Management Research Group.
Document record
- Document ID
- RFC7575
- Published
- June 2015
- Authors
- M. Behringer; M. Pritikin; S. Bjarnason; A. Clemm; B. Carpenter; S. Jiang; L. Ciavaglia
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7149Software-Defined Networking: A Perspective from within a Service Provider EnvironmentCurrent
March 2014
- RFC 8366A Voucher Artifact for Bootstrapping ProtocolsCurrent
May 2018
- RFC 8368Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)Current
May 2018
- RFC 8990GeneRic Autonomic Signaling Protocol (GRASP)Current
May 2021
- RFC 8991GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)Current
May 2021
- RFC 8993A Reference Model for Autonomic NetworkingCurrent
May 2021
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 8995Bootstrapping Remote Secure Key Infrastructure (BRSKI)Current
May 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?