On Transport of Configuration Information
draft-lear-config-issues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Eliot | ||
| Last updated | 2002-09-26 | ||
| 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
How are network elements configured? What are the different ways in which a device receives configuration, and why do they use those particular mechanisms? How do these mechanisms perform for their given use? This document discusses the problem of device configuration and state exchange. As we do so we will point out some protocol considerations, such as the objects being transported, how transfers are initiated, and what the security requirements are.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)