OSPF Transport Instance Extensions
draft-acee-ospf-transport-instance-03

Document Type Replaced Internet-Draft (individual)
Last updated 2012-10-19 (latest revision 2009-02-26)
Replaced by draft-ietf-ospf-transport-instance
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ospf-transport-instance
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-acee-ospf-transport-instance-03.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.)