OSPFv3 LSA Extendibility
draft-ietf-ospf-ospfv3-lsa-extend-09
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8362.
Expired & archived
|
|
---|---|---|---|
Authors | Acee Lindem , Sina Mirtorabi , Abhay Roy , Fred Baker | ||
Last updated | 2016-05-22 (Latest revision 2015-11-19) | ||
Replaces | draft-acee-ospfv3-lsa-extend | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. 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.)