Requirements for Automated (Configuration) Management
draft-boucadair-network-automation-requirements-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Christian Jacquenet , Luis M. Contreras | ||
| Last updated | 2015-08-17 (Latest revision 2015-02-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Given the ever-increasing complexity of the configuration tasks required for the dynamic provisioning of IP networks and services, this document aims at listing the requirements for an automated configuration management framework.
Authors
Mohamed Boucadair
Christian Jacquenet
Luis M. Contreras
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)