Extensions to IS-IS and OSPF for Advertising Optinal Router Capabilities
draft-raggarwa-igp-cap-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Acee Lindem | ||
| Last updated | 2002-11-05 | ||
| 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
It is useful for routers in a domain to know of the capabilities of their IGP neighbors, and/or of other routers in the domain. This draft proposes extensions to IS-IS and OSPF for advertising optional router capabilities. We define an optional Router Capability TLV for IS-IS, while for OSPF we define an optional Router Information Opaque LSA.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)