An Autonomic Control Plane
draft-behringer-anima-autonomic-control-plane-03
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-06-30 | ||
| Replaces | draft-behringer-autonomic-control-plane | ||
| Replaced by | draft-ietf-anima-autonomic-control-plane | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-anima-autonomic-control-plane | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-behringer-anima-autonomic-control-plane-03.txt
Abstract
Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing, and as independent as possible of configuration. One application is a "virtual out of band channel" for communications over a network that is not configured or mis- configured. This document describes requirements and implementation options for an "Autonomic Control Plane".
Authors
Michael Behringer
(mbehring@cisco.com)
Steinthor Bjarnason
(sbjarnas@cisco.com)
Balaji BL
(blbalaji@cisco.com)
Toerless Eckert
(eckert@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)