Autonomic Networking: Definitions and Design Goals
RFC 7575, “Autonomic Networking: Definitions and Design Goals”, is an Informational document published in June 2015 by M. Behringer, M. Pritikin, S. Bjarnason, A. Clemm, B. Carpenter, S. Jiang, L. Ciavaglia. The canonical text is published by the RFC Editor.
Abstract
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.
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 7575 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7574 Peer-to-Peer Streaming Peer Protocol
- RFC 7576 General Gap Analysis for Autonomic Networking
- RFC 7573 Interworking between the Session Initiation Protocol and the Extensible Messaging and Presence Protocol : One-to-One Text Chat Sessions
- RFC 7577 Definition of Managed Objects for Battery Monitoring
- RFC 7572 Interworking between the Session Initiation Protocol and the Extensible Messaging and Presence Protocol : Instant Messaging
- RFC 7578 Returning Values from Forms: multipart/form-data
- RFC 7571 GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
- RFC 7579 General Network Element Constraint Encoding for GMPLS-Controlled Networks