Configuration must not be carried by the routing protocol
draft-chroboczek-homenet-configuration-separate-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Juliusz Chroboczek | ||
| Last updated | 2014-01-03 (Latest revision 2013-07-02) | ||
| Replaces | draft-chroboczek-configuration-separate | ||
| 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
Where I argue that configuration information must be carried by a protocol separate from the routing protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)