<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.acee-ospf-transport-instance'>
<front>
<title>OSPF Transport Instance Extensions</title>

<author initials='A' surname='Lindem' fullname='Acee Lindem'>
    <organization />
</author>

<author initials='A' surname='Roy' fullname='Abhay Roy'>
    <organization />
</author>

<author initials='S' surname='Mirtorabi' fullname='Sina Mirtorabi'>
    <organization />
</author>

<date month='February' day='26' year='2009' />

<abstract><t>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.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-acee-ospf-transport-instance-03' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-acee-ospf-transport-instance-03.txt' />
</reference>

