OSPF Transport Instance Extensions
draft-ietf-ospf-transport-instance-11

 
Document
Type Expired Internet-Draft (ospf WG)
Last updated 2014-12-27 (latest revision 2014-06-25)
Replaces draft-acee-ospf-transport-instance
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
WG state WG Document
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-ietf-ospf-transport-instance-11.txt

Abstract

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.

Authors

Acee Lindem (acee.lindem@ericsson.com)
Abhay Roy (akr@cisco.com)
Sina Mirtorabi (sina@cisco.com)

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