OSPF Transport Instance Extensions

Document Type Replaced Internet-Draft (lsr WG)
Authors Acee Lindem  , Yingzhen Qu  , Abhay Roy  , Sina Mirtorabi 
Last updated 2021-05-21 (latest revision 2021-02-21)
Replaces draft-ietf-ospf-transport-instance
Replaced by draft-ietf-lsr-ospf-transport-instance
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized bibtex
Stream WG state Adopted by a WG
Document shepherd Les Ginsberg
IESG IESG state Replaced by draft-ietf-lsr-ospf-transport-instance
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to chopps@chopps.org, ginsberg@cisco.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


OSPFv2 and OSPFv3 include a reliable flooding mechanism to disseminate routing topology and Traffic Engineering (TE) information within a routing domain. Given the effectiveness of these mechanisms, it is convenient to envision using the same mechanism for dissemination of other types of information within the domain. However, burdening OSPF with this additional information will impact intra-domain routing convergence and possibly jeopardize the stability of the OSPF routing domain. This document presents mechanism to relegate this ancillary information to a separate OSPF instance and minimize the impact.


Acee Lindem (acee@cisco.com)
Yingzhen Qu (yingzhen.qu@futurewei.com)
Abhay Roy (abhay@arrcus.com)
Sina Mirtorabi (smirtora@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)