Extensions to OSPF for Advertising Optional Router Capabilities
draft-acee-ospf-rfc4970bis-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Acee Lindem , Naiming Shen , JP Vasseur , Rahul Aggarwal , Scott Shaffer | ||
Last updated | 2015-02-01 (Latest revision 2014-07-31) | ||
Replaced by | draft-ietf-ospf-rfc4970bis | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ospf-rfc4970bis | |
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 an OSPFv2 or OSPFv3 routing domain to know the capabilities of their neighbors and other routers in the routing domain. This document proposes extensions to OSPFv2 and OSPFv3 for advertising optional router capabilities. A new Router Information (RI) Link State Advertisement (LSA) is proposed for this purpose. In OSPFv2, the RI LSA will be implemented with a new opaque LSA type ID. In OSPFv3, the RI LSA will be implemented with a new LSA type function code. In both protocols, the RI LSA can be advertised at any of the defined flooding scopes (link, area, or autonomous system (AS)). This document obsoletes RFC 4970 by providing a revised specification including support for advertisement of multiple instances of the RI LSA and a TLV for functional capabilities.
Authors
Acee Lindem
Naiming Shen
JP Vasseur
Rahul Aggarwal
Scott Shaffer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)