One document matched: draft-ietf-ospf-ospfv3-traffic-11.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<rfc category="std" ipr="full3978" docName="draft-ietf-ospf-ospfv3-traffic-11.txt">
<front>
<title abbrev="OSPFv3-Traffic Engineering">
Traffic Engineering Extensions to OSPF version 3</title>
<author initials='K.' surname="Ishiguro" fullname='Kunihiro Ishiguro'>
<organization>IP Infusion, Inc</organization>
<address>
<postal>
<street>125 South Market Street, Suite 900</street>
<city>San Jose</city> <region>CA</region>
<country>USA</country>
<code>95113</code>
</postal>
<email>kunihiro@ipinfusion.com</email>
</address>
</author>
<author initials='V.' surname="Manral" fullname='Vishwas Manral'>
<organization>IP Infusion, Inc</organization>
<address>
<postal>
<street>#41, Ground Floor, 5th Cross Road</street>
<street>8th Main Road</street>
<city>Vasanth Nagar</city> <region>Bangalore</region>
<country>India</country>
<code>560052</code>
</postal>
<email>vishwas@ipinfusion.com</email>
</address>
</author>
<author initials='A.' surname="Davey" fullname='Alan Davey'>
<organization>Data Connection Limited</organization>
<address>
<postal>
<street>100 Church Street</street>
<street>Enfield</street>
<city>EN2 6BQ</city>
<country>UK</country>
</postal>
<email>Alan.Davey@dataconnection.com</email>
</address>
</author>
<author initials='A.' surname="Lindem (Editor)" fullname='Acee Lindem'>
<organization>Redback Networks</organization>
<address>
<postal>
<street>102 Carric Bend Court</street>
<city>Cary</city> <region>NC</region>
<country>USA</country>
<code>27519</code>
</postal>
<email>acee@redback.com</email>
</address>
</author>
<date month="April" year="2008"/>
<abstract><t>This document describes extensions to OSPFv3 to support intra-area
Traffic Engineering (TE). This document extends OSPFv2 TE to handle IPv6 networks.
A new TLV and several new sub-TLVs are defined to support IPv6 networks.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>OSPFv3 has a very flexible mechanism for adding new LS types.
Unknown LS types are flooded properly based on the flooding scope
bits in the LS type <xref target="OSPFV3"/>. This document defines the
Intra-Area-TE LSA to OSPFv3.</t>
<t>For Traffic Engineering, this document uses "Traffic Engineering
Extensions to OSPF" <xref target="TE"/> as a base for TLV definitions. New TLVs and
sub-TLVs are added to <xref target="TE"/> to extend TE capabilities to IPv6 networks. Some
existing TLVs and sub-TLVs require clarification for OSPFv3 applicability.</t>
<t>GMPLS <xref target="GMPLS"/> and the Diff-Serv MPLS Extensions
<xref target="TE-DIFF"/> are based on <xref target="TE"/>.
These functions can also be extended to OSPFv3 by
utilizing the TLVs and sub-TLVs described in this document.</t>
<section title="Requirements notation">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as
described in RFC2119 <xref target="RFC-KEYWORDS"/>.</t>
</section>
</section>
<section title="Intra-Area-TE-LSA">
<t>A new LS type is defined for the Intra-Area-TE LSA. This is different
from OSPFv2 Traffic Engineering <xref target="TE"/> where opaque LSAs are used to
advertise TE information <xref target="OPAQUE"/>. The LSA function
code is 10, the U bit is set, and the scope is set to 01 for area-scoping.
When the U bit is set to 1, an OSPFv3 router must flood the LSA at its
defined flooding scope even if it does not recognize the LS type <xref target="OSPFV3"/>.
<figure title="OSPFv3 Intra-Area-TE-LSA">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS age |0|1|1| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- TLVs -+
| ... |
</artwork>
</figure></t>
<t>The Link State ID of an Intra-Area-TE LSA is an arbitrary value used to
maintain multiple Traffic Engineering LSAs. The LSA ID has no
topological significance.</t>
<t>The format of the TLVs within the body of an Intra-Area-TE LSA
is the same as the format used by the Traffic Engineering
Extensions to OSPF <xref target="TE"/>. The LSA payload consists of one or
more nested Type/Length/Value (TLV) triplets. The format of
each TLV is:
<figure title="TLV Format">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure></t>
<t>The Length field defines the length of the value portion in octets
(thus a TLV with no value portion would have a length of zero). The
TLV is padded to four-octet alignment; padding is not included in
the length field (so a three octet value would have a length of
three, but the total size of the TLV would be eight octets). Nested
TLVs are also 32-bit aligned. For example, a one-byte value
would have the length field set to 1, and three octets of padding
would be added to the end of the value portion of the TLV.
Unrecognized types are ignored.</t>
<section title="Intra-Area-TE-LSA Payload">
<t>An Intra-Area-TE-LSA contains one top-level TLV. There are
two applicable top-level TLVs:
<list style="hanging">
<t>2 - Link TLV</t>
<t>3 - Router IPv6 Address TLV</t>
</list></t>
</section>
</section>
<section title="Router IPv6 Address TLV">
<t>The Router IPv6 Address TLV advertises a reachable IPv6 address.
This is a stable IPv6 address that is always reachable if there is
connectivity to the OSPFv3 router.</t>
<t>The Router IPv6 Address TLV has type 3, length 16, and a value
containing a 16 octet local IPv6 address. It MUST appear in exactly
one Traffic Engineering LSA originated by an OSPFv3 router supporting
the TE extensions. The Router IPv6 Address TLV is a top-level TLV as
defined in Traffic Engineering Extensions to OSPF <xref target="TE"/> and only one
top-level TLV may be contained in an LSA.
<figure title="Router IPv6 Address TLV">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Router IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 3.
Length A 16-bit field that indicates the length of the value
portion in octets. For this TLV it is always 16.
Value A stable and routable IPv6 address.
</artwork>
</figure></t>
</section>
<section title="Link TLV">
<t>The Link TLV describes a single link and consists of a set of
sub-TLVs <xref target="TE"/>. All of the sub-TLVs in <xref target="TE"/>
other than the Link ID sub-TLV
are applicable to OSPFv3. The Link ID sub-TLV can't be used in OSPFv3
since it is defined to use the OSPFv2 identification for the Designated Router (DR)
on multi-access networks. In OSPFv2, neighbors on point-to-point
networks and virtual links are identified by their Router IDs while neighbors
on broadcast, Non-Broadcast Multi-Access (NBMA), and Point-to-Multipoint links
are identified by their IPv4 interface addresses
(Refer to section 8.2 in <xref target="OSPFV2"/>). The IPv4 interface address is
not known to OSPFv3. In contrast to OSPFv2, OSPFv3
always identifies neighboring routers by their Router IDs (Refer to section 2.11
in <xref target="OSPFV3"/>).
</t>
<t>Three new sub-TLVs for the Link TLV are defined:
<list style="hanging">
<t>18 - Neighbor ID (8 octets)</t>
<t>19 - Local Interface IPv6 Address (16N octets, where N is the number
of IPv6 addresses)</t>
<t>20 - Remote Interface IPv6 Address (16N octets, where N is the number
of IPv6 addresses)</t>
</list></t>
<t>The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering
support. It MUST appear exactly once in a Link TLV. All other sub-TLVs
defined in this document MAY occur at most once in a Link TLV.</t>
<section title="Link ID Sub-TLV">
<t>The Link ID sub-TLV is used in OSPFv2 to identify the other end of
the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link
identification. In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent and
MUST be ignored upon receipt.</t>
</section>
<section title="Neighbor ID Sub-TLV">
<t>In OSPFv2, the Link ID is used to identify the other end of a link.
In OSPFv3, the combination of Neighbor Interface ID and Neighbor
Router ID is used for neighbor link identification. Both are advertised
in the Neighbor ID Sub-TLV.</t>
<t>Neighbor Interface ID and Neighbor Router ID values are the same as
described in RFC 2740 <xref target="OSPFV3"/> A.4.3 Router-LSAs.
<figure title="Neighbor ID Sub-TLV">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 18 | 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 18.
Length A 16-bit field that indicates the length of the value
portion in octets. For this sub-TLV it is always 8.
Value The neighbor's interface ID and router ID.
</artwork>
</figure></t>
</section>
<section title="Local Interface IPv6 Address Sub-TLV">
<t>The Local Interface IPv6 Address sub-TLV specifies the IPv6
address(es) of the interface corresponding to this link. If there
are multiple local addresses assigned to the link then they MAY all be
listed in this sub-TLV. Link-local addresses MUST NOT be included
in this sub-TLV.
<figure title="Local Interface IPv6 Address Sub-TLV">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 19 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 19.
Length A 16-bit field that indicates the length of the value
portion in octets. For this sub-TLV, it MUST always be a
multiple of 16 octets dependent on the number of IPv6
global addresses advertised.
Value A list of one or more local IPv6 interface addresses
each consuming 16 octets.
</artwork>
</figure></t>
</section>
<section title="Remote Interface IPv6 Address Sub-TLV">
<t>The Remote Interface IPv6 Address sub-TLV advertises the IPv6
address(es) associated with the neighbor's interface. This Sub-TLV and
the Local Interface IPv6 address Sub-TLV are used to discern amongst
parallel links between OSPFv3 routers. If the Link Type is multi-access,
the Remote Interface IPv6 Address MAY be set to ::. Alternately,
an implementation MAY choose not to send this sub-TLV. Link-local
addresses MUST NOT be advertised in this sub-TLV. Neighbor addresses
advertised in Link-LSAs with a prefix length of 128 and the LA bit
set MAY be advertised.
<figure title="Remote Interface IPv6 Address Sub-TLV">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 20.
Length A 16-bit field that indicates the length of the value
portion in octets. For this sub-TLV, it MUST be a
multiple of 16 octets dependent on the number of IPv6
global addresses advertised.
Value A variable length remote interface IPv6 address list.
</artwork>
</figure></t>
</section>
</section>
<section title="Security Considerations">
<t>The function described in this document does not create any new
security issues for the OSPFv3 protocol. Security considerations for
the base OSPFv3 protocol are covered in <xref target="OSPFV3"/>.</t>
</section>
<section title="IANA Considerations">
<t>The following IANA assignments are to be made from existing
registries:
<list style="numbers">
<t>The OSPFv3 LSA type function code 10 needs to be assigned to
the OSPFv3 Intra-Area-TE-LSA.</t>
<t>The Router IPv6 Address TLV type 3 needs to be assigned from the existing
registry for OSPF TE TLVs.</t>
<t>The Neighbor ID Sub-TLV (18), Local Interface IPv6 Address Sub-TLV (19),
and Remote Interface IPv6 Address Sub-TLV (20), need to be assigned from
the existing registry for OSPF TE Sub-TLVs.</t>
</list></t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC-KEYWORDS">
<front>
<title>Key words for use in RFC's to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="Scott Bradner">
<organization>Harvard University</organization>
</author>
<date month="March" year="1997" />
</front>
<seriesInfo name="RFC" value="2119" />
</reference>
<reference anchor="OSPFV3">
<front>
<title>OSPF for IPv6</title>
<author initials="R." surname="Coltun" fullname="Rob Coltun">
<organization>Siara Systems</organization>
</author>
<author initials="D." surname="Ferguson" fullname="Dennis Ferguson">
<organization>Juniper Network, Inc</organization>
</author>
<author initials="J." surname="Moy" fullname="John Moy">
<organization>Sycamore Systems, Inc</organization>
</author>
<date month="April" year="1998" />
</front>
<seriesInfo name="RFC" value="2740" />
</reference>
<reference anchor="OSPFV2">
<front>
<title>OSPF Version 2</title>
<author initials="J." surname="Moy" fullname="John Moy">
<organization>Ascend Communications, Inc</organization>
</author>
<date month="April" year="1998" />
</front>
<seriesInfo name="RFC" value="2328" />
</reference>
<reference anchor="TE">
<front>
<title>Traffic Engineering Extensions to OSPF</title>
<author initials="D." surname="Katz" fullname="Dave Katz">
<organization>Juniper Networks</organization>
</author>
<author initials="D." surname="Yeung" fullname="Derek Yeung">
<organization>Procket Networks</organization>
</author>
<author initials="K." surname="Kompella" fullname="Kireeti Kompella">
<organization>Juniper Networks</organization>
</author>
<date month="September" year="2003" />
</front>
<seriesInfo name="RFC" value="3630" />
</reference>
</references>
<references title="Informative References">
<reference anchor="OPAQUE">
<front>
<title>The OSPF Opaque LSA Option</title>
<author initials="R." surname="Coltun" fullname="Rob Colton">
<organization>FORE Systems</organization>
</author>
<date month="July" year="1998" />
</front>
<seriesInfo name="RFC" value="2370" />
</reference>
<reference anchor="GMPLS">
<front>
<title>OSPF Extensions in Support of Generalized Multi-Protocol Switching (GMPLS)</title>
<author initials="K." surname="Kompella" fullname="Kiretti Kompella">
<organization>Juniper Networks</organization>
</author>
<author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
<organization>Juniper Networks</organization>
</author>
<date month="October" year="2005"/>
</front>
<seriesInfo name="RFC" value="4203" />
</reference>
<reference anchor="TE-DIFF">
<front>
<title>Multi-Protocol Label Switching (MPLS) Support of Differentiated Services</title>
<author initials="F." surname="Le Faucheur" fullname="Francois Le Faucheur">
<organization>Cisco Systems</organization>
</author>
<author initials="L." surname="Wu" fullname="Liwen Wu">
<organization>Cisco Systems</organization>
</author>
<author initials="B." surname="Davie" fullname="Bruce Davie">
<organization>Cisco Systems</organization>
</author>
<author initials="S." surname="Davari" fullname="Shahram Davari">
<organization>PMC-Sierra Inc</organization>
</author>
<author initials="P." surname="Vaananen" fullname="Pasi Vaananen">
<organization>Nokia</organization>
</author>
<author initials="R." surname="Krishnan" fullname="Ram Krishnan">
<organization>Axiowave Networks</organization>
</author>
<author initials="P." surname="Cheval" fullname="Pierrick Cheval">
<organization>Alcatel</organization>
</author>
<author initials="J." surname="Heinanen" fullname="Juha Heinanen">
<organization>Song Networks, Inc</organization>
</author>
</front>
<seriesInfo name="RFC" value="3270" />
</reference>
</references>
<section title="Acknowledgments">
<t>Thanks to Kireeti Kompella, Alex Zinin,
Adrian Farrell, and Mach Chen for their comments.</t>
<t>The RFC text was produced using Marshall Rose's xml2rfc tool.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 14:50:34 |