The OSPF Opaque LSA Option
RFC 5250
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document defines enhancements to the OSPF protocol to support a new class of link state … Received changes through RFC Editor sync (changed abstract to 'This document defines enhancements to the OSPF protocol to support a new class of link state advertisements (LSAs) called Opaque LSAs. Opaque LSAs provide a generalized mechanism to allow for the future extensibility of OSPF. Opaque LSAs consist of a standard LSA header followed by application-specific information. The information field may be used directly by OSPF or by other applications. Standard OSPF link-state database flooding mechanisms are used to distribute Opaque LSAs to all or some limited portion of the OSPF topology. This document replaces RFC 2370 and adds to it a mechanism to enable an OSPF router to validate Autonomous System (AS)-scope Opaque LSAs originated outside of the router's OSPF area. [STANDARDS-TRACK]') |
2017-05-16
|
(System) | Changed document authors from "Alex Zinin, Igor Bryskin, Lou Berger" to "Alex Zinin, Igor Bryskin, Lou Berger, Rob Coltun" |
2015-10-14
|
(System) | Notify list changed from ospf-chairs@ietf.org, draft-ietf-ospf-rfc2370bis@ietf.org to (None) |
2008-07-07
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
2008-07-07
|
Cindy Morgan | [Note]: 'RFC 5250' added by Cindy Morgan |
2008-07-03
|
(System) | RFC published |