OSPFv3 LSA Extendibility
draft-acee-ospfv3-lsa-extend-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Acee Lindem , Sina Mirtorabi , Abhay Roy , Fred Baker | ||
Last updated | 2013-11-05 (Latest revision 2013-09-10) | ||
Replaces | draft-baker-ipv6-ospf-extensible | ||
Replaced by | draft-ietf-ospf-ospfv3-lsa-extend | ||
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-ospfv3-lsa-extend | |
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
OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSA. This document extends the LSA format by allowing the optional inclusion of Type-Length- Value (TLV) tuples in the LSAs. Backward compatibility mechanisms are also described.
Authors
Acee Lindem
Sina Mirtorabi
Abhay Roy
Fred Baker
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)