< draft-srisuresh-ospf-te-06.txt   draft-srisuresh-ospf-te-07.txt >
Network Working Group P. Srisuresh Network Working Group P. Srisuresh
INTERNET-DRAFT Caymas Systems, Inc. INTERNET-DRAFT Caymas Systems
Expires as of September 3, 2004 P. Joseph Expires as of June 31, 2005 P. Joseph
Force10 Networks Symbol Technologies
March 3, 2004 December 31, 2004
OSPF-xTE: An experimental extension to OSPF for Traffic Engineering OSPF-xTE: An experimental extension to OSPF for Traffic Engineering
<draft-srisuresh-ospf-te-06.txt> <draft-srisuresh-ospf-te-07.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet- Drafts as time. It is inappropriate to use Internet-Drafts as reference
reference material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html"
Abstract Abstract
This document defines OSPF-xTE, an experimental traffic engineering This document defines OSPF-xTE, an experimental traffic engineering
(TE) extension to the link-state routing protocol OSPF. OSPF-xTE (TE) extension to the link-state routing protocol OSPF. OSPF-xTE
defines new TE LSAs to disseminate TE metrics within an autonomous defines new TE LSAs to disseminate TE metrics within an autonomous
System (AS), which may consist of multiple areas. Further, When an System (AS), which may consist of multiple areas. Further, When an
AS consists of TE and non-TE nodes, OSPF-xTE ensures that Non-TE AS consists of TE and non-TE nodes, OSPF-xTE ensures that Non-TE
nodes in the AS are uneffected by the TE LSAs. OSPF-xTE generates nodes in the AS are uneffected by the TE LSAs. OSPF-xTE generates
a stand-alone TE Link State Database (TE-LSDB), distinct from the a stand-alone TE Link State Database (TE-LSDB), distinct from the
skipping to change at page 2, line 4 skipping to change at page 2, line 6
defines new TE LSAs to disseminate TE metrics within an autonomous defines new TE LSAs to disseminate TE metrics within an autonomous
System (AS), which may consist of multiple areas. Further, When an System (AS), which may consist of multiple areas. Further, When an
AS consists of TE and non-TE nodes, OSPF-xTE ensures that Non-TE AS consists of TE and non-TE nodes, OSPF-xTE ensures that Non-TE
nodes in the AS are uneffected by the TE LSAs. OSPF-xTE generates nodes in the AS are uneffected by the TE LSAs. OSPF-xTE generates
a stand-alone TE Link State Database (TE-LSDB), distinct from the a stand-alone TE Link State Database (TE-LSDB), distinct from the
native OSPF LSDB, for computation of TE circuit paths. OSPF-xTE is native OSPF LSDB, for computation of TE circuit paths. OSPF-xTE is
versatile and extendible to non-packet networks such as SONET/TDM versatile and extendible to non-packet networks such as SONET/TDM
and optical networks. and optical networks.
Table of Contents Table of Contents
1. Introduction ................................................3 1. Introduction ................................................3
2. Principles of traffic engineering ...........................3 2. Principles of traffic engineering ...........................3
3. Terminology .................................................4 3. Terminology .................................................4
3.1. Native OSPF terms ......................................4 3.1. Native OSPF terms ......................................5
3.2. OSPF-xTE terms .........................................5 3.2. OSPF-xTE terms .........................................5
4. Motivations behind the design of OSPF-xTE ...................8 4. Motivations behind the design of OSPF-xTE ...................8
4.1. Scalable design ........................................8 4.1. Scalable design ........................................9
4.2. Operable in mixed and peer networks ....................9 4.2. Operable in mixed and peer networks ....................9
4.3. Efficient in flooding reach ............................9 4.3. Efficient in flooding reach ............................9
4.4. Ability to reserve TE-exclusive links ..................9 4.4. Ability to reserve TE-exclusive links .................10
4.5. Extendible design .....................................10 4.5. Extendible design .....................................10
4.6. Unified for packet and non-packet networks ............10 4.6. Unified for packet and non-packet networks ............10
4.7. Networks benefiting from the OSPF-xTE design ..........10 4.7. Networks benefiting from the OSPF-xTE design ..........11
5. OSPF-xTE solution overview .................................11 5. OSPF-xTE solution overview .................................12
5.1. OSPF-xTE Solution .....................................11 5.1. OSPF-xTE Solution .....................................12
5.2. Assumptions ...........................................13 5.2. Assumptions ...........................................13
6. Opaque LSAs to OSPF-xTE transition strategy ................14 6. Opaque LSAs to OSPF-xTE transition strategy ................14
7. OSPF-xTE router adjacency - TE topology discovery ..........14 7. OSPF-xTE router adjacency - TE topology discovery ..........14
7.1. The OSPF Options field ................................15 7.1. The OSPF-xTE router adjacency .........................14
7.2. The Hello Protocol ....................................15 7.2. The Hello Protocol ....................................15
7.3. Flooding and the Synchronization of Databases .........16 7.3. The Designated Router .................................15
7.4. The Designated Router .................................16 7.4. The Backup Designated Router ..........................15
7.5. The Backup Designated Router ..........................16 7.5. Flooding and the Synchronization of Databases .........16
7.6. The graph of adjacencies ..............................17 7.6. The graph of adjacencies ..............................16
8. TE LSAs for packet network .................................18 8. TE LSAs for packet network .................................18
8.1. TE-Router LSA (0x81) ..................................19 8.1. TE-Router LSA (0x81) ..................................19
8.2. TE-incremental-link-Update LSA (0x8d) .................28 8.2. TE-incremental-link-Update LSA (0x8d) .................27
8.3. TE-Circuit-paths LSA (0x8C) ...........................30 8.3. TE-Circuit-paths LSA (0x8C) ...........................29
8.4. TE-Summary LSAs .......................................32 8.4. TE-Summary LSAs .......................................32
8.5. TE-AS-external LSAs (0x85) ............................35 8.5. TE-AS-external LSAs (0x85) ............................34
9. TE LSAs for non-packet network .............................37 9. TE LSAs for non-packet network .............................36
9.1. TE-Router LSA (0x81) ..................................37 9.1. TE-Router LSA (0x81) ..................................36
9.2. TE-Positional-ring-network LSA (0x82) .................39 9.2. TE-Positional-ring-network LSA (0x82) .................38
9.3. TE-Router-Proxy LSA (0x8e) ............................41 9.3. TE-Router-Proxy LSA (0x8e) ............................40
10. Abstract topology representation with TE support ...........42 10. Abstract topology representation with TE support ...........41
11. Changes to Data structures in OSPF-xTE routers .............44 11. Changes to Data structures in OSPF-xTE routers .............43
11.1. Changes to Router data structure .....................44 11.1. Changes to Router data structure .....................43
11.2. Two set of Neighbors .................................44 11.2. Two set of Neighbors .................................43
11.3. Changes to Interface data structure ..................44 11.3. Changes to Interface data structure ..................43
12. IANA Considerations ........................................45 12. IANA Considerations ........................................44
12.1. TE LSA type values ...................................45 12.1. TE LSA type values ...................................44
12.2. TE TLV tag values ....................................46 12.2. TE TLV tag values ....................................45
13. Acknowledgements ...........................................46 13. Acknowledgements ...........................................45
14. Security Considerations ....................................47 14. Security Considerations ....................................46
15. Normative References .......................................48 15. Normative References .......................................47
16. Informative References .....................................48 16. Informative References .....................................47
17. Authors' Addresses .........................................48
18. Full Copyright Statement ...................................48
1. Introduction 1. Introduction
This document defines OSPF-xTE, an experimental traffic This document defines OSPF-xTE, an experimental traffic
engineering (TE) extension to the link-state routing protocol engineering (TE) extension to the link-state routing protocol
OSPF. The objective of OSPF-xTE is to discover TE network OSPF. The objective of OSPF-xTE is to discover TE network
topology and disseminate TE metrics within an autonomous system topology and disseminate TE metrics within an autonomous system
(AS). A stand-alone TE Link State Database (TE-LSDB), different (AS). A stand-alone TE Link State Database (TE-LSDB), different
from the native OSPF LSDB, is created to facilitate computation from the native OSPF LSDB, is created to facilitate computation
of TE circuit paths. Devising algorithms to compute TE circuit of TE circuit paths. Devising algorithms to compute TE circuit
paths is not an objective of this document. paths is not an objective of this document.
OSPF-xTE is different from the Opaque-LSA-based design outlined OSPF-xTE is different from the Opaque-LSA-based approach
in [OPQLSA-TE]. Section 4 describes the motivations behind the outlined in [OPQLSA-TE]. Section 4 describes the motivations
design of OSPF-xTE. Section 6 outlines a transition path for behind the design of OSPF-xTE. Section 6 outlines a transition
those currently using [OPQLSA-TE] and wish to experiment with path for those currently using [OPQLSA-TE] for intra-area and
OSPF-xTE. wish to extend this using OSPF-xTE across the AS.
Readers interested in TE extensions for the packet networks Readers interested in TE extensions for the packet networks
alone may skip section 9.0. alone may skip section 9.0.
2. Principles of traffic engineering 2. Principles of traffic engineering
The objective of traffic engineering (TE) is to set up circuit The objective of traffic engineering (TE) is to set up circuit
path(s) between a pair of nodes or links and to forward traffic path(s) between a pair of nodes or links and to forward traffic
of a certain forwarding equivalency class (FEC) through the of a certain forwarding equivalency class (FEC) through the
circuit path. Only the unicast circuit paths are considered circuit path. Only the unicast circuit paths are considered
skipping to change at page 8, line 20 skipping to change at page 8, line 24
A TLV stands for an object in the form of Tag-Length-Value. All A TLV stands for an object in the form of Tag-Length-Value. All
TLVs are assumed to be of the following format, unless specified TLVs are assumed to be of the following format, unless specified
otherwise. The Tag and length are 16 bits wide each. The length otherwise. The Tag and length are 16 bits wide each. The length
includes the 4 octets required for Tag and Length specification. includes the 4 octets required for Tag and Length specification.
All TLVs described in this document are padded to 32-bit All TLVs described in this document are padded to 32-bit
alignment. Any padding required for alignment will not be a part alignment. Any padding required for alignment will not be a part
of the length field, however. TLVs are used to describe traffic of the length field, however. TLVs are used to describe traffic
engineering characteristics of the TE nodes, TE links and TE circuit engineering characteristics of the TE nodes, TE links and TE circuit
paths. paths.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag | Length (4 or more) | | Tag | Length (4 or more) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value .... | | Value .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .... | | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2.13. Router-TE TLVs (Router TLVs) 3.2.13. Router-TE TLVs (Router TLVs)
skipping to change at page 9, line 4 skipping to change at page 9, line 9
There are several motivations that led to the design of OSPF-xTE. There are several motivations that led to the design of OSPF-xTE.
OSPF-xTE is scalable, efficient and usable across a variety of OSPF-xTE is scalable, efficient and usable across a variety of
network topologies. These motivations are explained in detail in network topologies. These motivations are explained in detail in
the following subsections. The last subsection lists real-world the following subsections. The last subsection lists real-world
network scenarios that benefit from the OSPF-xTE. network scenarios that benefit from the OSPF-xTE.
4.1. Scalable design 4.1. Scalable design
OSPF-xTE area level abstraction provides the scaling required OSPF-xTE area level abstraction provides the scaling required
for the TE topology in a large autonomous system (AS). for the TE topology in a large autonomous system (AS).
An OSPF-xTE area border router will advertise summary LSAs for An OSPF-xTE area border router will advertise summary LSAs for
TE and non-TE topologies independent of each other. Readers TE and non-TE topologies independent of each other. Readers
may refer to section 10 for a topological view of the AS from may refer to section 10 for a topological view of the AS from
the perspective of a OSPF-xTE node in an area. the perspective of a OSPF-xTE node in an area.
[OPQLSA-TE], on the other hand, is designed for intra-area and
is not scalable to AS-wide scope.
4.2. Operable in mixed and peer networks 4.2. Operable in mixed and peer networks
OSPF-xTE assumes that an AS may be constituted of coexisting OSPF-xTE assumes that an AS may be constituted of coexisting
TE and non-TE networks. OSPF-xTE dynamically discovers TE TE and non-TE networks. OSPF-xTE dynamically discovers TE
topology and the associated TE metrics of the nodes and links topology and the associated TE metrics of the nodes and links
that form the TE network. As such, OSPF-xTE generates a that form the TE network. As such, OSPF-xTE generates a
stand-alone TE-LSDB that is fully representative of the TE stand-alone TE-LSDB that is fully representative of the TE
network. Stand-alone TE-LSDB allows for speedy TE computations. network. Stand-alone TE-LSDB allows for speedy TE computations.
In [OPQLSA-TE], the TE-LSDB is derived from the combination of [OPQLSA-TE] is designed for packet networks and is not suitable
opaque LSAs and native LSDB. Further, the TE-LSDB thus derived has for mixes and peer networks. TE-LSDB in [OPQLSA-TE] is derived
no knowledge of the TE capabilities of the routers in the network. from the combination of opaque LSAs and native LSDB. Further,
the TE-LSDB thus derived has no knowledge of the TE
capabilities of the routers in the network.
4.3. Efficient in flooding reach 4.3. Efficient in flooding reach
OSPF-xTE is able to identify the TE topology in a mixed network OSPF-xTE is able to identify the TE topology in a mixed network
and will limit the flooding of TE LSAs to just the TE-nodes. and will limit the flooding of TE LSAs to just the TE-nodes.
Non-TE nodes are not bombarded with TE LSAs. Non-TE nodes are not bombarded with TE LSAs.
In a TE network, a subset of the TE metrics may be prone to rapid In a TE network, a subset of the TE metrics may be prone to rapid
change, while others remain largely unchanged. Changes in TE change, while others remain largely unchanged. Changes in TE
metrics must be communicated at the earliest throughout the metrics must be communicated at the earliest throughout the
skipping to change at page 11, line 40 skipping to change at page 11, line 50
reachability knowledge. This in turn will make TE circuit reachability knowledge. This in turn will make TE circuit
setup predictable and computationally bounded. setup predictable and computationally bounded.
4.7.4. Non-packet networks and Peer networks 4.7.4. Non-packet networks and Peer networks
Vendors may also use OSPF-xTE for their non-packet TE networks. Vendors may also use OSPF-xTE for their non-packet TE networks.
OSPF-xTE defines the following functions in support of OSPF-xTE defines the following functions in support of
non-packet TE networks. non-packet TE networks.
(a) "Positional-Ring" type network LSA and (a) "Positional-Ring" type network LSA and
(b) Router Proxying - allowing a router to advertise on behalf (b) Router Proxying - allowing a router to advertise on behalf
of other nodes (that are not Packet/OSPF capable). of other nodes (that are not Packet/OSPF capable).
5. OSPF-xTE solution overview 5. OSPF-xTE solution overview
5.1. OSPF-xTE Solution 5.1. OSPF-xTE Solution
A new TE flag is introduced within the OSPF options field to Locally scoped opaque LSA (type 9) is used to discovery the TE
enable discovery of TE topology. Section 8.0 describes the topology within a network. Section 7.1 describes in detail the
semantics of the TE flag. TE LSAs are designed for use by the use of type 9 Opaque LSA for TE topology discovery. TE LSAs are
OSPF-xTE nodes. Section 9.0 describes the TE LSAs in detail. designed for use by the OSPF-xTE nodes. Section 8.0 describes
the TE LSAs in detail. Changes required of the OSPF data
Changes required of the OSPF data structures to support structures to support OSPF-xTE are described in section 11.0.
OSPF-xTE are described in section 11.0. A new TE-neighbors data A new TE-neighbors data structure will be used to advertise
structure will be used to flood TE LSAs along TE-topology. TE LSAs along TE-topology.
An OSPF-xTE node will have the native LSDB and the TE-LSDB, An OSPF-xTE node will have the native LSDB and the TE-LSDB,
A native OSPF node will have just the native LSDB. A native OSPF node will have just the native LSDB.
Consider the following OSPF area constituted of OSPF-xTE and Consider the following OSPF area constituted of OSPF-xTE and
native OSPF routers. Nodes RT1, RT2, RT3 and RT6 are OSPF-xTE native OSPF routers. Nodes RT1, RT2, RT3 and RT6 are OSPF-xTE
routers with TE and non-TE link attachments. Nodes RT4 and RT5 routers with TE and non-TE link attachments. Nodes RT4 and RT5
are native OSPF routers with no TE links. When the LSA database are native OSPF routers with no TE links. When the LSA database
is synchronized, all nodes will share the same native LSDB is synchronized, all nodes will share the same native LSDB.
OSPF-xTE nodes alone will have the additional TE-LSDB. OSPF-xTE nodes alone will have the additional TE-LSDB.
+---+ +---+
| |--------------------------------------+ | |--------------------------------------+
|RT6|\\ | |RT6|\\ |
+---+ \\ | +---+ \\ |
|| \\ | || \\ |
|| \\ | || \\ |
|| \\ | || \\ |
|| +---+ | || +---+ |
skipping to change at page 14, line 26 skipping to change at page 14, line 26
the link capacity is set aside for TE traffic. the link capacity is set aside for TE traffic.
4. Non-packet TE sub-topologies must have a minimum of one node 4. Non-packet TE sub-topologies must have a minimum of one node
running OSPF-xTE protocol. For example, a SONET/SDH TDM ring running OSPF-xTE protocol. For example, a SONET/SDH TDM ring
must have a minimum of one Gateway Network Element(GNE) must have a minimum of one Gateway Network Element(GNE)
running OSPF-xTE. The OSPF-xTE node will advertise on behalf running OSPF-xTE. The OSPF-xTE node will advertise on behalf
of all the TE nodes in the ring. of all the TE nodes in the ring.
6. Opaque LSAs to OSPF-xTE transition strategy 6. Opaque LSAs to OSPF-xTE transition strategy
Below is a strategy to transition implementations using opaque Below is a strategy to transition implementations currently using
LSAs ([OPQLSA-TE]) to adapt OSPF-xTE in a gradual fashion. opaque LSAs ([OPQLSA-TE]) within an area to adapt OSPF-xTE in
a gradual fashion across the AS.
1. Restrict the use of Opaque-LSAs to within an area.
2. Use the TE option flag to construct the TE topologies 1. Use [OPQLSA-TE] within an area. Derive TE topology within the
area-wise. By doing this, the TE topology for the AS will area from the combination of opaque LSAs and native LSDB.
be available at area level abstraction.
3. Use TE-Summary LSAs and TE-AS-external-LSAs for inter-area 2. Use TE-Summary LSAs and TE-AS-external-LSAs for inter-area
Communication. Make use of the TE-topology within an area to Communication. Make use of the TE-topology within an area to
summarize the TE networks in the area and advertise the same summarize the TE networks in the area and advertise the same
to all TE-nodes in the backbone. The TE-ABRs on the backbone to all TE-nodes in the backbone. The TE-ABRs on the backbone
area will in-turn advertise these summaries within their area will in-turn advertise these summaries within their
connected areas. connected areas.
7. OSPF-xTE router adjacency - TE topology discovery 7. OSPF-xTE router adjacency - TE topology discovery
OSPF creates adjacencies between neighboring routers for the purpose OSPF creates adjacencies between neighboring routers for the purpose
of exchanging routing information. In the following subsections, we of exchanging routing information. In the following subsections, we
describe modifications to the OSPF options field and the use of describe the use of locally scoped Opaque LSA to discover OSPF-xTE
Hello protocol to establish TE capability compliance between neighboring routers. The capability is used as the basis to build
neighboring routers in an area. The capability is used as the basis TE topology.
to build TE topology.
7.1. The OSPF Options field
A new TE flag is introduced within the options field to identify TE
extensions to the OSPF. This bit will be used to distinguish routers
that support OSPF-xTE. The OSPF options field is present in OSPF
Hello packets, Database Description packets, and all link state
advertisements. The TE bit, however, is a requirement only for the
Hello packets. Use of TE-bit is optional in Database Description
packets and LSAs.
Below is a description of the TE-Bit. Refer [OSPF-V2], [OSPF-NSSA]
and [OPAQUE] for a description of the remaining bits in the
options field.
-------------------------------------- 7.1. The OSPF-xTE router adjacency
|TE | O | DC | EA | N/P | MC | E | * |
--------------------------------------
The OSPF options field - TE support
TE-Bit: This bit is set to indicate support for traffic engineering OSPF uses the options field in the hello packet to advertise optional
extensions to the OSPF. The Hello protocol which is used for router capabilities [OSPF]. However, all the bits in this field have
establishing router adjacency will use the TE-bit to been allocated and there is no way to advertise OSPF-xTE capability
establish OSPF-xTE adjacency. Two routers will not become using the options field at this time. This document proposes using
TE-neighbors unless they agree on the state of the TE-bit. local scope opaque lsa (OPAQUE-9 LSA) to advertise support for
TE-compliant OSPF extensions are advertised only to the OSPF-xTE and establish OSPF-xTE adjacency. In order to exchange
TE-compliant routers. All other routers may simply ignore Opaque LSAs, the neighboring routers must have the O-bit (Opaque
the advertisements. option bit) set in the options field as a prerequisite.
There is however a caveat with the above use of the last remaining [OSPF-CAP] proposes a format for exchanging router capabilities
reserved bit in the options field. OSPF v2 will have no more via OPAQUE-9 LSA. Routers supporting OSPF-xTE will be required to
reserved bits left for future option extensions. If deemed set the "OSPF Experimental TE" bit within the "router
necessary to leave this bit as is, the OPAQUE-9 LSA (local scope) capabilities" field. Two routers will not become TE-neighbors
can be used on each interface to communicate the support for unless they share a common network link on which both routers
OSPF-xTE. For the reminder of the document, we will assume the advertise support for OSPF-xTE. Routers that donot support
above defined TE-bit in options filed is permissible. OSPF-xTE may simply ignore the advertisement.
7.2. The Hello Protocol 7.2. The Hello Protocol
The Hello Protocol is primarily responsible for dynamically The Hello Protocol is primarily responsible for dynamically
establishing and maintaining neighbor adjacencies. In a TE network, establishing and maintaining neighbor adjacencies. In a TE network,
it is not required for all links and neighbors to establish it is not required for all links and neighbors to establish
adjacency using this protocol. The Hello protocol will use the adjacency using this protocol. OSPF-xTE router adjacency between
TE-bit to establish traffic engineering capability between two two routers is established using the method described in the
OSPF routers. previous section.
For NBMA and broadcast networks, this protocol is responsible for
electing the Designated Router and the Backup Designated Router.
Routers supporting the TE option shall be given a higher For NBMA and broadcast networks, the HELLO protocol is responsible
for electing the Designated Router and the Backup Designated
Router. Routers supporting the TE option shall be given a higher
precedence for becoming a designated router over those that do precedence for becoming a designated router over those that do
not support TE. not support TE.
7.3. The Designated Router 7.3. The Designated Router
When a router's non-TE link first becomes functional, it checks to When a router's non-TE link first becomes functional, it checks to
see whether there is currently a Designated Router for the network. see whether there is currently a Designated Router for the network.
If there is one, it accepts that Designated Router, regardless of If there is one, it accepts that Designated Router, regardless of
its Router Priority, so long as the current designated router is its Router Priority, so long as the current designated router is
TE compliant. Otherwise, the router itself becomes Designated TE compliant. Otherwise, the router itself becomes Designated
skipping to change at page 18, line 11 skipping to change at page 18, line 11
have TE-compliant adjacency with the designated and backup have TE-compliant adjacency with the designated and backup
routers. RT5 and RT6 will only have native adjacency with the routers. RT5 and RT6 will only have native adjacency with the
designated and backup routers. designated and backup routers.
Network Adjacency Network Adjacency
+---+ +---+ +---+ +---+
|RT1|------------|RT2| o--------------------o |RT1|------------|RT2| o--------------------o
+---+ N1 +---+ RT1 RT2 +---+ N1 +---+ RT1 RT2
RT7 RT7
o::::: o:::::
+---+ +---+ +---+ /| : +---+ +---+ +---+ /| :
|RT7| |RT3| |RT4| / | : |RT7| |RT3| |RT4| / | :
+---+ +---+ +---+ / | : +---+ +---+ +---+ / | :
| | | / | : | | | / | :
+-----------------------+ RT5o RT6o oRT4 +-----------------------+ RT5o RT6o oRT4
| | N2 * * : | | N2 * * :
+---+ +---+ * * : +---+ +---+ * * :
|RT5| |RT6| * * : |RT5| |RT6| * * :
+---+ +---+ ** : +---+ +---+ ** :
o::::: o:::::
RT3 RT3
Adjacency Legend: Adjacency Legend:
----- Native adjacency (primary) ----- Native adjacency (primary)
***** Native adjacency (Backup) ***** Native adjacency (Backup)
::::: TE-compliant adjacency (primary) ::::: TE-compliant adjacency (primary)
;;;;; TE-compliant adjacency (Backup) ;;;;; TE-compliant adjacency (Backup)
Figure 6: The graph of adjacencies with TE-compliant routers. Figure 6: The graph of adjacencies with TE-compliant routers.
8. TE LSAs for packet network 8. TE LSAs for packet network
skipping to change at page 19, line 42 skipping to change at page 19, line 42
The TE-router LSA (0x81) is modeled after the router LSA and has the The TE-router LSA (0x81) is modeled after the router LSA and has the
same flooding scope as the router-LSA. However, the scope is same flooding scope as the router-LSA. However, the scope is
restricted to only the OSPF-xTE nodes within the area. The TE-router restricted to only the OSPF-xTE nodes within the area. The TE-router
LSA describes the TE metrics of the router as well as the TE-links LSA describes the TE metrics of the router as well as the TE-links
attached to the router. Below is the format of the TE-router LSA. attached to the router. Below is the format of the TE-router LSA.
Unless specified explicitly otherwise, the fields carry the same Unless specified explicitly otherwise, the fields carry the same
meaning as they do in a router LSA. Only the differences are meaning as they do in a router LSA. Only the differences are
explained below. Router-TE flags, Router-TE TLVs, Link-TE options, explained below. Router-TE flags, Router-TE TLVs, Link-TE options,
and Link-TE TLVs are each described in the following sub-sections. and Link-TE TLVs are each described in the following sub-sections.
0 1 2 3 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 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 | Options | 0x81 | | LS age | Options | 0x81 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 20, line 29 skipping to change at page 20, line 29
| Type | 0 | Link-TE flags | | Type | 0 | Link-TE flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link-TE flags (contd.) | Zero or more Link-TE TLVs | | Link-TE flags (contd.) | Zero or more Link-TE TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link ID | | Link ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Data | | Link Data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
Option
In TE-capable router nodes, the TE-bit may be set to 1.
8.1.1. Router-TE flags - TE capabilities of the router 8.1.1. Router-TE flags - TE capabilities of the router
The following flags are used to describe the TE capabilities of an The following flags are used to describe the TE capabilities of an
OSPF-xTE router. The remaining bits of the 32-bit word are reserved OSPF-xTE router. The remaining bits of the 32-bit word are reserved
for future use. for future use.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L|L|P| | | | |L|S|C| |L|L|P| | | | |L|S|C|
|S|E|S| | | | |S|I|S| |S|E|S| | | | |S|I|S|
|R|R|C| | | | |P|G|P| |R|R|C| | | | |P|G|P|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->| |<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->|
Bit LSR Bit LSR
When set, the router is considered to have LSR capability. When set, the router is considered to have LSR capability.
Bit LER Bit LER
When set, the router is considered to have LER capability. When set, the router is considered to have LER capability.
All MPLS border routers will be required to have the LER All MPLS border routers will be required to have the LER
capability. When the E bit is also set, that indicates an capability. When the E bit is also set, that indicates an
AS Boundary router with LER capability. When the B bit is AS Boundary router with LER capability. When the B bit is
also set, that indicates an area border router with LER also set, that indicates an area border router with LER
capability. capability.
Bit PSC Bit PSC
Indicates the node is Packet Switch Capable. Indicates the node is Packet Switch Capable.
Bit LSP Bit LSP
MPLS Label switch TLV TE-NODE-TLV-MPLS-SWITCHING follows. MPLS Label switch TLV TE-NODE-TLV-MPLS-SWITCHING follows.
This is applicable only when the PSC flag is set. This is applicable only when the PSC flag is set.
Bit SIG Bit SIG
MPLS Signaling protocol support TLV MPLS Signaling protocol support TLV
TE-NODE-TLV-MPLS-SIG-PROTOCOLS follows. TE-NODE-TLV-MPLS-SIG-PROTOCOLS follows.
BIT CSPF BIT CSPF
CSPF algorithm support TLV TE-NODE-TLV-CSPF-ALG follows. CSPF algorithm support TLV TE-NODE-TLV-CSPF-ALG follows.
8.1.2. Router-TE TLVs 8.1.2. Router-TE TLVs
The following Router-TE TLVs are defined. The following Router-TE TLVs are defined.
8.1.2.4. TE-NODE-TLV-MPLS-SWITCHING 8.1.2.4. TE-NODE-TLV-MPLS-SWITCHING
MPLS switching TLV is applicable only for packet switched nodes. The MPLS switching TLV is applicable only for packet switched nodes. The
TLV specifies the MPLS packet switching capabilities of the TE TLV specifies the MPLS packet switching capabilities of the TE
node. node.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8001 | Length = 6 | | Tag = 0x8001 | Length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label depth | QOS | | | Label depth | QOS | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
'Label depth' is the depth of label stack the node is capable of 'Label depth' is the depth of label stack the node is capable of
processing on its ingress interfaces. An octet is used to represent processing on its ingress interfaces. An octet is used to represent
label depth. A default value of 1 is assumed when the TLV is not label depth. A default value of 1 is assumed when the TLV is not
listed. Label depth is relevant when an LER has to pop off multiple listed. Label depth is relevant when an LER has to pop off multiple
skipping to change at page 23, line 11 skipping to change at page 22, line 11
'QOS' is a single octet field that may be assigned '1' or '0'. Nodes 'QOS' is a single octet field that may be assigned '1' or '0'. Nodes
supporting QOS are able to interpret the EXP bits in the MPLS header supporting QOS are able to interpret the EXP bits in the MPLS header
to prioritize multiple classes of traffic through the same LSP. to prioritize multiple classes of traffic through the same LSP.
8.1.2.2. TE-NODE-TLV-MPLS-SIG-PROTOCOLS 8.1.2.2. TE-NODE-TLV-MPLS-SIG-PROTOCOLS
MPLS signaling protocols TLV lists all the signaling protocol MPLS signaling protocols TLV lists all the signaling protocol
supported by the node. An octet is used to list each signaling supported by the node. An octet is used to list each signaling
protocol supported. protocol supported.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8002 | Length = 5, 6 or 7 | | Tag = 0x8002 | Length = 5, 6 or 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol-1 | ... | .... | | Protocol-1 | ... | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RSVP-TE protocol is represented as 1, CR-LDP as 2 and LDP as 3. RSVP-TE protocol is represented as 1, CR-LDP as 2 and LDP as 3.
These are the only permitted signaling protocols at this time. These are the only permitted signaling protocols at this time.
8.1.2.3. TE-NODE-TLV-CSPF-ALGORITHMS 8.1.2.3. TE-NODE-TLV-CSPF-ALGORITHMS
skipping to change at page 23, line 36 skipping to change at page 22, line 36
compute complete or partial circuit paths. Support for CSPF compute complete or partial circuit paths. Support for CSPF
algorithms can also be beneficial in knowing whether or not a node algorithms can also be beneficial in knowing whether or not a node
is capable of expanding loose routes (in an MPLS signaling request) is capable of expanding loose routes (in an MPLS signaling request)
into a detailed circuit path. into a detailed circuit path.
Two octets are used to list each CSPF algorithm code. The algorithm Two octets are used to list each CSPF algorithm code. The algorithm
codes may be vendor defined and unique within an Autonomous System. codes may be vendor defined and unique within an Autonomous System.
If the node supports 'n' CSPF algorithms, the Length would be If the node supports 'n' CSPF algorithms, the Length would be
(4 + 4 * ((n+1)/2)) octets. (4 + 4 * ((n+1)/2)) octets.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length = 4(1 + (n+1)/2) | | Tag = 0x8003 | Length = 4(1 + (n+1)/2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CSPF-1 | .... | | CSPF-1 | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CSPF-n | | | CSPF-n | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.1.2.4. TE-NODE-TLV-NULL 8.1.2.4. TE-NODE-TLV-NULL
When a TE-Router or a TE-link has multiple TLVs to describe the When a TE-Router or a TE-link has multiple TLVs to describe the
metrics, the NULL TLV is used to terminate the TLV list. metrics, the NULL TLV is used to terminate the TLV list.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8888 | Length = 4 | | Tag = 0x8888 | Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.1.3. Link-TE flags - TE capabilities of a link 8.1.3. Link-TE flags - TE capabilities of a link
The following flags are used to describe the TE capabilities of a The following flags are used to describe the TE capabilities of a
link. The remaining bits of the 32-bit word are reserved for link. The remaining bits of the 32-bit word are reserved for
future use. future use.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|N|P| | | |D| |S|L|B|C| |T|N|P| | | |D| |S|L|B|C|
|E|T|K| | | |B| |R|U|W|O| |E|T|K| | | |B| |R|U|W|O|
| |E|T| | | |S| |L|G| |L| | |E|T| | | |S| |L|G| |L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->| |<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->|
TE - Indicates whether TE is permitted on the link. A link TE - Indicates whether TE is permitted on the link. A link
can be denied for TE use by setting the flag to 0. can be denied for TE use by setting the flag to 0.
NTE - Indicates whether non-TE traffic is permitted on the NTE - Indicates whether non-TE traffic is permitted on the
TE link. This flag is relevant only when the TE TE link. This flag is relevant only when the TE
flag is set. flag is set.
PKT - Indicates whether or not the link is capable of IP PKT - Indicates whether or not the link is capable of IP
packet processing. packet processing.
DBS - Indicates whether or not Database synchronization DBS - Indicates whether or not Database synchronization
is permitted on this link. is permitted on this link.
SRLG Bit - Shared Risk Link Group TLV TE-LINK-TLV-SRLG follows. SRLG Bit - Shared Risk Link Group TLV TE-LINK-TLV-SRLG follows.
LUG bit - Link usage cost metric TLV TE-LINK-TLV-LUG follows. LUG bit - Link usage cost metric TLV TE-LINK-TLV-LUG follows.
BW bit - One or more Link bandwidth TLVs follow BW bit - One or more Link bandwidth TLVs follow
COL bit - Link Color TLV TE-LINK-TLV-COLOR follows. COL bit - Link Color TLV TE-LINK-TLV-COLOR follows.
8.1.4. Link-TE TLVs 8.1.4. Link-TE TLVs
8.1.4.1. TE-LINK-TLV-SRLG 8.1.4.1. TE-LINK-TLV-SRLG
The SRLG describes the list of Shared Risk Link Groups (SRLG) the The SRLG describes the list of Shared Risk Link Groups (SRLG) the
link belongs to. Two octets are used to list each SRLG. If the link link belongs to. Two octets are used to list each SRLG. If the link
belongs to 'n' SRLGs, the Length would be (4 + 4 * ((n+1)/2)) octets. belongs to 'n' SRLGs, the Length would be (4 + 4 * ((n+1)/2)) octets.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length = 4(1 + (n+1)/2) | | Tag = 0x0001 | Length = 4(1 + (n+1)/2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SRLG-1 | .... | | SRLG-1 | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SRLG-n | | | SRLG-n | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.1.4.2. TE-LINK-TLV-BANDWIDTH-MAX 8.1.4.2. TE-LINK-TLV-BANDWIDTH-MAX
The bandwidth TLV specifies maximum bandwidth of the link as follows. The bandwidth TLV specifies maximum bandwidth of the link as follows.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0002 | Length = 8 | | Tag = 0x0002 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Bandwidth | | Maximum Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec). Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec).
A 32-bit field for bandwidth would permit specification not exceeding A 32-bit field for bandwidth would permit specification not exceeding
1 tera-bits/sec. 1 tera-bits/sec.
'Maximum bandwidth' is be the maximum link capacity expressed in 'Maximum bandwidth' is be the maximum link capacity expressed in
bandwidth units. Portions or all of this bandwidth may be used for bandwidth units. Portions or all of this bandwidth may be used for
TE use. TE use.
8.1.4.3. TE-LINK-TLV-BANDWIDTH-MAX-FOR-TE 8.1.4.3. TE-LINK-TLV-BANDWIDTH-MAX-FOR-TE
The bandwidth TLV specifies maximum bandwidth available for TE use The bandwidth TLV specifies maximum bandwidth available for TE use
as follows. as follows.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0003 | Length = 8 | | Tag = 0x0003 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Bandwidth available for TE use | | Maximum Bandwidth available for TE use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec). Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec).
A 32-bit field for bandwidth would permit specification not exceeding A 32-bit field for bandwidth would permit specification not exceeding
1 tera-bits/sec. 1 tera-bits/sec.
skipping to change at page 27, line 10 skipping to change at page 26, line 10
the link. The link is oversubscribed when this field is more than the link. The link is oversubscribed when this field is more than
the 'Maximum Bandwidth'. When the field is less than the the 'Maximum Bandwidth'. When the field is less than the
'Maximum Bandwidth', the remaining bandwidth on the link may 'Maximum Bandwidth', the remaining bandwidth on the link may
be used for non-TE traffic in a mixed network. be used for non-TE traffic in a mixed network.
8.1.4.4. TE-LINK-TLV-BANDWIDTH-TE 8.1.4.4. TE-LINK-TLV-BANDWIDTH-TE
The bandwidth TLV specifies the bandwidth reserved for TE as follows. The bandwidth TLV specifies the bandwidth reserved for TE as follows.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length = 8 | | Tag = 0x0004 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TE Bandwidth subscribed | | TE Bandwidth subscribed |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec). Bandwidth is expressed in units of 32 bytes/sec (256 bits/sec).
A 32-bit field for bandwidth would permit specification not exceeding A 32-bit field for bandwidth would permit specification not exceeding
1 tera-bits/sec. 1 tera-bits/sec.
skipping to change at page 27, line 34 skipping to change at page 26, line 34
paths are able to claim no more than the difference between the paths are able to claim no more than the difference between the
two bandwidths for reservation. two bandwidths for reservation.
8.1.4.5. TE-LINK-TLV-LUG 8.1.4.5. TE-LINK-TLV-LUG
The link usage cost TLV specifies Bandwidth unit usage cost, The link usage cost TLV specifies Bandwidth unit usage cost,
TE circuit set-up cost, and any time constraints for setup and TE circuit set-up cost, and any time constraints for setup and
teardown of TE circuits on the link. teardown of TE circuits on the link.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0005 | Length = 28 | | Tag = 0x0005 | Length = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth unit usage cost | | Bandwidth unit usage cost |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TE circuit set-up cost | | TE circuit set-up cost |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TE circuit set-up time constraint | | TE circuit set-up time constraint |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 28, line 26 skipping to change at page 27, line 26
8.1.4.6. TE-LINK-TLV-COLOR 8.1.4.6. TE-LINK-TLV-COLOR
The color TLV is similar to the SRLG TLV, in that an Autonomous The color TLV is similar to the SRLG TLV, in that an Autonomous
System may choose to issue colors to a TE-link meeting certain System may choose to issue colors to a TE-link meeting certain
criteria. The color TLV can be used to specify one or more colors criteria. The color TLV can be used to specify one or more colors
assigned to the link as follows. Two octets are used to list each assigned to the link as follows. Two octets are used to list each
color. If the link belongs to 'n' number of colors, the Length color. If the link belongs to 'n' number of colors, the Length
would be (4 + 4 * ((n+1)/2)) octets. would be (4 + 4 * ((n+1)/2)) octets.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 4(1 + (n+1)/2) | | Tag = 0x0006 | Length = 4(1 + (n+1)/2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Color-1 | .... | | Color-1 | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Color-n | | | Color-n | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.1.4.7. TE-LINK-TLV-NULL 8.1.4.7. TE-LINK-TLV-NULL
skipping to change at page 29, line 19 skipping to change at page 28, line 19
MinLSInterval seconds). The TE-link sequence is largely the MinLSInterval seconds). The TE-link sequence is largely the
advertisement of a sub-portion of router LSA. The sequence number on advertisement of a sub-portion of router LSA. The sequence number on
this will be incremented with the TE-router LSA's sequence as the this will be incremented with the TE-router LSA's sequence as the
basis. When an updated TE-router LSA is advertised within 30 minutes basis. When an updated TE-router LSA is advertised within 30 minutes
of the previous advertisement, the updated TE-router LSA will assume of the previous advertisement, the updated TE-router LSA will assume
a sequence no. that is larger than the most frequently updated of a sequence no. that is larger than the most frequently updated of
its links. its links.
Below is the format of the TE-incremental-link-update LSA. Below is the format of the TE-incremental-link-update LSA.
0 1 2 3 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 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 | Options | 0x8d | | LS age | Options | 0x8d |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID (same as Link ID) | | Link State ID (same as Link ID) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 30, line 29 skipping to change at page 29, line 29
sequence number of the TE-router LSA it belongs to. Further, when a sequence number of the TE-router LSA it belongs to. Further, when a
new TE-router LSA update with a larger sequence number is advertised, new TE-router LSA update with a larger sequence number is advertised,
the newer sequence number is assumed by al the link LSAs. the newer sequence number is assumed by al the link LSAs.
8.3. TE-Circuit-path LSA (0x8C) 8.3. TE-Circuit-path LSA (0x8C)
TE-Circuit-path LSA may be used to advertise the availability of TE-Circuit-path LSA may be used to advertise the availability of
pre-engineered TE circuit path(s) originating from any router pre-engineered TE circuit path(s) originating from any router
in the network. The flooding scope may be Area wide or AS wide. in the network. The flooding scope may be Area wide or AS wide.
0 1 2 3 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 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 | Options | 0x84 | | LS age | Options | 0x84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 31, line 29 skipping to change at page 30, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
Link State ID Link State ID
The ID of the far-end router or the far-end Link-ID to which the The ID of the far-end router or the far-end Link-ID to which the
TE circuit path(s) is being advertised. TE circuit path(s) is being advertised.
TE-circuit-path(s) flags TE-circuit-path(s) flags
Bit G - When set, the flooding scope is set to be AS wide. Bit G - When set, the flooding scope is set to be AS wide.
Otherwise, the flooding scope is set to be area wide. Otherwise, the flooding scope is set to be area wide.
Bit E - When set, the advertised Link-State ID is an AS boundary Bit E - When set, the advertised Link-State ID is an AS boundary
router (E is for external). The advertising router and router (E is for external). The advertising router and
the Link State ID belong to the same area. the Link State ID belong to the same area.
Bit B - When set, the advertised Link state ID is an Area border Bit B - When set, the advertised Link state ID is an Area border
router (B is for Border) router (B is for Border)
Bit D - When set, this indicates that the duration of circuit Bit D - When set, this indicates that the duration of circuit
path validity follows. path validity follows.
Bit S - When set, this indicates that Setup-time of the circuit Bit S - When set, this indicates that Setup-time of the circuit
path follows. path follows.
Bit T - When set, this indicates that teardown-time of the Bit T - When set, this indicates that teardown-time of the
circuit path follows. circuit path follows.
CktType CktType
This 4-bit field specifies the Circuit type of the Forward This 4-bit field specifies the Circuit type of the Forward
Equivalency Class (FC). Equivalency Class (FC).
0x01 - Origin is Router, Destination is Router. 0x01 - Origin is Router, Destination is Router.
0x02 - Origin is Link, Destination is Link. 0x02 - Origin is Link, Destination is Link.
0x04 - Origin is Router, Destination is Link. 0x04 - Origin is Router, Destination is Link.
0x08 - Origin is Link, Destination is Router. 0x08 - Origin is Link, Destination is Router.
Circuit Duration (Optional) Circuit Duration (Optional)
This 64-bit number specifies the seconds from the time of the This 64-bit number specifies the seconds from the time of the
LSA advertisement for which the pre-engineered circuit path LSA advertisement for which the pre-engineered circuit path
will be valid. This field is specified only when the D-bit is will be valid. This field is specified only when the D-bit is
set in the TE-circuit-path flags. set in the TE-circuit-path flags.
Circuit Setup time (Optional) Circuit Setup time (Optional)
This 64-bit number specifies the time at which the TE-circuit This 64-bit number specifies the time at which the TE-circuit
path may be set up. This field is specified only when the path may be set up. This field is specified only when the
skipping to change at page 32, line 49 skipping to change at page 31, line 49
Circuit-TE Data Circuit-TE Data
This is the virtual link identifier on the near-end router for This is the virtual link identifier on the near-end router for
a given TE-circuit path segment. This can be a private a given TE-circuit path segment. This can be a private
interface or handle the near-end router uses to identify the interface or handle the near-end router uses to identify the
virtual link. virtual link.
The sequence of (circuit-TE ID, Circuit-TE Data) list the The sequence of (circuit-TE ID, Circuit-TE Data) list the
end-point nodes and links in the LSA as a series. end-point nodes and links in the LSA as a series.
Circuit-TE flags Circuit-TE flags
This lists the Zero or more TE-link TLVs that all member This lists the Zero or more TE-link TLVs that all member
elements of the LSP meet. elements of the LSP meet.
8.4. TE-Summary LSAs 8.4. TE-Summary LSAs
TE-Summary-LSAs are the Type 0x83 and 0x84 LSAs. These LSAs are TE-Summary-LSAs are the Type 0x83 and 0x84 LSAs. These LSAs are
originated by area border routers. TE-Summary-network-LSA (0x83) originated by area border routers. TE-Summary-network-LSA (0x83)
describes the reachability of TE networks in a non-backbone describes the reachability of TE networks in a non-backbone
area, advertised by the Area Border Router. Type 0x84 area, advertised by the Area Border Router. Type 0x84
summary-LSA describes the reachability of Area Border Routers summary-LSA describes the reachability of Area Border Routers
and AS border routers and their TE capabilities. and AS border routers and their TE capabilities.
skipping to change at page 33, line 43 skipping to change at page 32, line 43
not advertise summary costs to reach networks within an area. not advertise summary costs to reach networks within an area.
This is because TE parameters are not necessarily additive or This is because TE parameters are not necessarily additive or
comparative. The parameters can be varied in their expression. comparative. The parameters can be varied in their expression.
For example, a TE-summary network LSA will not summarize a For example, a TE-summary network LSA will not summarize a
network whose links do not fall under an SRLG (Shared-Risk Link network whose links do not fall under an SRLG (Shared-Risk Link
Group). This way, the TE-summary LSA merely advertises the Group). This way, the TE-summary LSA merely advertises the
reachability of TE networks within an area. The specific circuit reachability of TE networks within an area. The specific circuit
paths can be computed by the BDRs. Pre-engineered circuit paths paths can be computed by the BDRs. Pre-engineered circuit paths
are advertised using TE-Circuit-path LSA (refer section 8.3). are advertised using TE-Circuit-path LSA (refer section 8.3).
0 1 2 3 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 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 | Options | 0x83 | | LS age | Options | 0x83 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID (IP Network Number) | | Link State ID (IP Network Number) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router (Area Border Router) | | Advertising Router (Area Border Router) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 34, line 21 skipping to change at page 33, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.4.2. TE-Summary router LSA (0x84) 8.4.2. TE-Summary router LSA (0x84)
TE-summary router LSA may be used to advertise the availability of TE-summary router LSA may be used to advertise the availability of
Area Border Routers (ABRs) and AS Border Routers (ASBRs) that are Area Border Routers (ABRs) and AS Border Routers (ASBRs) that are
TE capable. The TE-summary router LSAs are originated by the Area TE capable. The TE-summary router LSAs are originated by the Area
Border Routers. The scope of flooding for the TE-summary router LSA Border Routers. The scope of flooding for the TE-summary router LSA
is the non-backbone area the advertising ABR belongs to. is the non-backbone area the advertising ABR belongs to.
0 1 2 3 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 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 | Options | 0x84 | | LS age | Options | 0x84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router (ABR) | | Advertising Router (ABR) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 35, line 24 skipping to change at page 34, line 24
Specifies the OSPF area(s) the link state ID belongs to. When Specifies the OSPF area(s) the link state ID belongs to. When
the link state ID is same as the advertising router ID, the the link state ID is same as the advertising router ID, the
Area-ID lists all the areas the ABR belongs to. In the case Area-ID lists all the areas the ABR belongs to. In the case
the link state ID is an ASBR, the Area-ID simply lists the the link state ID is an ASBR, the Area-ID simply lists the
area the ASBR belongs to. The advertising router is assumed to area the ASBR belongs to. The advertising router is assumed to
be the ABR from the same area the ASBR is located in. be the ABR from the same area the ASBR is located in.
Summary-router-TE flags Summary-router-TE flags
Bit E - When set, the advertised Link-State ID is an AS boundary Bit E - When set, the advertised Link-State ID is an AS boundary
router (E is for external). The advertising router and router (E is for external). The advertising router and
the Link State ID belong to the same area. the Link State ID belong to the same area.
Bit B - When set, the advertised Link state ID is an Area Bit B - When set, the advertised Link state ID is an Area
border router (B is for Border) border router (B is for Border)
Router-TE flags, Router-TE flags,
Router-TE TLVs (TE capabilities of the link-state-ID router) Router-TE TLVs (TE capabilities of the link-state-ID router)
TE Flags and TE TLVs are as applicable to the ABR/ASBR TE Flags and TE TLVs are as applicable to the ABR/ASBR
specified in the link state ID. The semantics is same as specified in the link state ID. The semantics is same as
specified in the Router-TE LSA. specified in the Router-TE LSA.
8.5. TE-AS-external LSAs (0x85) 8.5. TE-AS-external LSAs (0x85)
TE-AS-external-LSAs are the Type 0x85 LSAs. This is modeled after TE-AS-external-LSAs are the Type 0x85 LSAs. This is modeled after
AS-external LSA format and flooding scope. TE-AS-external LSAs are AS-external LSA format and flooding scope. TE-AS-external LSAs are
originated by AS boundary routers with TE extensions, and describe originated by AS boundary routers with TE extensions, and describe
the TE networks and pre-engineered circuit paths external to the the TE networks and pre-engineered circuit paths external to the
AS. As with AS-external LSA, the flooding scope of the AS. As with AS-external LSA, the flooding scope of the
TE-AS-external LSA is AS wide, with the exception of stub areas. TE-AS-external LSA is AS wide, with the exception of stub areas.
0 1 2 3 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 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 | Options | 0x85 | | LS age | Options | 0x85 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 36, line 33 skipping to change at page 35, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TE-Forwarding address | | TE-Forwarding address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| External Route TE Tag | | External Route TE Tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
Network Mask Network Mask
The IP address mask for the advertised TE destination. For The IP address mask for the advertised TE destination. For
example, this can be used to specify access to a specific example, this can be used to specify access to a specific
TE-node or TE-link with an mask of 0xffffffff. This can also TE-node or TE-link with an mask of 0xffffffff. This can also
be used to specify access to an aggregated set of destinations be used to specify access to an aggregated set of destinations
using a different mask. ex: 0xff000000. using a different mask. ex: 0xff000000.
Link-TE flags, Link-TE flags,
Link-TE TLVs Link-TE TLVs
The TE attributes of this route. These fields are optional and The TE attributes of this route. These fields are optional and
are provided only when one or more pre-engineered circuits can are provided only when one or more pre-engineered circuits can
be specified with the advertisement. Without these fields, be specified with the advertisement. Without these fields,
the LSA will simply state TE reachability info. the LSA will simply state TE reachability info.
Forwarding address Forwarding address
Data traffic for the advertised destination will be forwarded to Data traffic for the advertised destination will be forwarded to
this address. If the Forwarding address is set to 0.0.0.0, data this address. If the Forwarding address is set to 0.0.0.0, data
traffic will be forwarded instead to the LSA's originator (i.e., traffic will be forwarded instead to the LSA's originator (i.e.,
the responsible AS boundary router). the responsible AS boundary router).
External Route Tag External Route Tag
A 32-bit field attached to each external route. This is not A 32-bit field attached to each external route. This is not
used by the OSPF protocol itself. It may be used to communicate used by the OSPF protocol itself. It may be used to communicate
information between AS boundary routers; the precise nature of information between AS boundary routers; the precise nature of
such information is outside the scope of this specification. such information is outside the scope of this specification.
9. TE LSAs for non-packet network 9. TE LSAs for non-packet network
A non-packet network would use the TE LSAs described in the A non-packet network would use the TE LSAs described in the
previous section for a packet network with some variations. previous section for a packet network with some variations.
These variations are described in the following subsections. These variations are described in the following subsections.
Two new LSAs, TE-Positional-ring-network LSA and TE-Router-Proxy Two new LSAs, TE-Positional-ring-network LSA and TE-Router-Proxy
LSA are defined for use in non-packet TE networks. LSA are defined for use in non-packet TE networks.
Readers may refer to [SONET-SDH] for a detailed description of Readers may refer to [SONET-SDH] for a detailed description of
the terms used in the context of SONET/SDH TDM networks, the terms used in the context of SONET/SDH TDM networks,
9.1. TE-Router LSA (0x81) 9.1. TE-Router LSA (0x81)
The following fields are used to describe each router link (i.e., The following fields are used to describe each router link (i.e.,
interface). Each router link is typed (see the below Type field). interface). Each router link is typed (see the below Type field).
The Type field indicates the kind of link being described. The Type field indicates the kind of link being described.
Type Type
A new link type "Positional-Ring Type" (value 5) is defined. A new link type "Positional-Ring Type" (value 5) is defined.
This is essentially a connection to a TDM-Ring. TDM ring network This is essentially a connection to a TDM-Ring. TDM ring network
is different from LAN/NBMA transit network in that nodes on the is different from LAN/NBMA transit network in that nodes on the
TDM ring do not necessarily have a terminating path between TDM ring do not necessarily have a terminating path between
themselves. Secondly, the order of links is important in themselves. Secondly, the order of links is important in
determining the circuit path. Third, the protection switching determining the circuit path. Third, the protection switching
and the number of fibers from a node going into a ring are and the number of fibers from a node going into a ring are
determined by the ring characteristics. I.e., 2-fiber vs determined by the ring characteristics. I.e., 2-fiber vs
4-fiber ring and UPSR vs BLSR protected ring. 4-fiber ring and UPSR vs BLSR protected ring.
Type Description Type Description
__________________________________________________ __________________________________________________
1 Point-to-point connection to another router 1 Point-to-point connection to another router
2 Connection to a transit network 2 Connection to a transit network
3 Connection to a stub network 3 Connection to a stub network
4 Virtual link 4 Virtual link
5 Positional-Ring Type. 5 Positional-Ring Type.
Link ID Link ID
Identifies the object that this router link connects to. Identifies the object that this router link connects to.
Value depends on the link's Type. For a positional-ring type, Value depends on the link's Type. For a positional-ring type,
the Link ID shall be IP Network/Subnet number just as the case the Link ID shall be IP Network/Subnet number just as the case
with a broadcast transit network. The following table with a broadcast transit network. The following table
summarizes the updated Link ID values. summarizes the updated Link ID values.
Type Link ID Type Link ID
______________________________________ ______________________________________
1 Neighboring router's Router ID 1 Neighboring router's Router ID
2 IP address of Designated Router 2 IP address of Designated Router
3 IP network/subnet number 3 IP network/subnet number
4 Neighboring router's Router ID 4 Neighboring router's Router ID
5 IP network/subnet number 5 IP network/subnet number
Link Data Link Data
This depends on the link's Type field. For type-5 links, this This depends on the link's Type field. For type-5 links, this
specifies the router interface's IP address. specifies the router interface's IP address.
9.1.1. Router-TE flags - TE capabilities of the router 9.1.1. Router-TE flags - TE capabilities of the router
Flags specific to non-packet TE-nodes are described below. Flags specific to non-packet TE-nodes are described below.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L|L|P|T|L|F| |S|S|S|C| |L|L|P|T|L|F| |S|S|S|C|
|S|E|S|D|S|S| |T|E|I|S| |S|E|S|D|S|S| |T|E|I|S|
|R|R|C|M|C|C| |A|L|G|P| |R|R|C|M|C|C| |A|L|G|P|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->| |<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->|
Bit TDM Bit TDM
Indicates the node is TDM circuit switch capable. Indicates the node is TDM circuit switch capable.
Bit LSC Bit LSC
Indicates the node is Lambda switch Capable. Indicates the node is Lambda switch Capable.
Bit FSC Bit FSC
Indicates the node is Fiber (can also be a non-fiber link Indicates the node is Fiber (can also be a non-fiber link
type) switch capable. type) switch capable.
9.1.2. Link-TE options - TE capabilities of a TE-link 9.1.2. Link-TE options - TE capabilities of a TE-link
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|N|P|T|L|F|D| |S|L|B|C| |T|N|P|T|L|F|D| |S|L|B|C|
|E|T|K|D|S|S|B| |R|U|W|O| |E|T|K|D|S|S|B| |R|U|W|O|
| |E|T|M|C|C|S| |L|G|A|L| | |E|T|M|C|C|S| |L|G|A|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->| |<---- Boolean TE flags ------->|<- TE flags pointing to TLVs ->|
TDM, LSC, FSC bits TDM, LSC, FSC bits
- Same as defined for router TE options. - Same as defined for router TE options.
9.2. TE-Positional-ring-network LSA (0x82) 9.2. TE-Positional-ring-network LSA (0x82)
Network LSA is adequate for packet TE networks. A new Network LSA is adequate for packet TE networks. A new
TE-Positional-Ring-network-LSA is defined to represent type-5 TE-Positional-Ring-network-LSA is defined to represent type-5
link networks, found in non-packet networks such as SONET/SDH link networks, found in non-packet networks such as SONET/SDH
TDM rings. A type-5 ring is a collection of network elements TDM rings. A type-5 ring is a collection of network elements
(NEs) forming a closed loop. Each NE is connected to two (NEs) forming a closed loop. Each NE is connected to two
adjacent NEs via a duplex connection to provide redundancy adjacent NEs via a duplex connection to provide redundancy
in the ring. The sequence in which the NEs are placed on the in the ring. The sequence in which the NEs are placed on the
skipping to change at page 41, line 19 skipping to change at page 40, line 19
is not advertised by the network element, but rather by a trusted is not advertised by the network element, but rather by a trusted
TE-router Proxy. This is typically the scenario in a non-packet TE-router Proxy. This is typically the scenario in a non-packet
TE network, where some of the nodes do not have OSPF functionality TE network, where some of the nodes do not have OSPF functionality
and count on a helper node to do the advertisement for them. One and count on a helper node to do the advertisement for them. One
such example would be the SONET/SDH ADM nodes in a TDM ring. The such example would be the SONET/SDH ADM nodes in a TDM ring. The
nodes may principally depend upon the GNE (Gateway Network nodes may principally depend upon the GNE (Gateway Network
Element) to do the advertisement for them. TE-router-Proxy LSA Element) to do the advertisement for them. TE-router-Proxy LSA
shall not be used to advertise Area Border Routers and/or AS border shall not be used to advertise Area Border Routers and/or AS border
Routers. Routers.
0 1 2 3 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 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 | Options | 0x8e | | LS age | Options | 0x8e |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID (Router ID of the TE Network Element) | | Link State ID (Router ID of the TE Network Element) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
skipping to change at page 48, line 17 skipping to change at page 47, line 17
compromise the state and TE-LDSB on the node. Needless to say, the compromise the state and TE-LDSB on the node. Needless to say, the
least secure OSPF-xTE will become the Achilles heel and make the least secure OSPF-xTE will become the Achilles heel and make the
TE network vulnerable to security attacks. TE network vulnerable to security attacks.
15. Normative References 15. Normative References
[IETF-STD] Bradner, S., "Key words for use in RFCs to indicate [IETF-STD] Bradner, S., "Key words for use in RFCs to indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC 1700] J. Reynolds and J. Postel, "Assigned Numbers", [RFC 1700] J. Reynolds and J. Postel, "Assigned Numbers",
RFC 1700 RFC 1700
[RFC 2434] Narten, T. and H. Alvestrand, "Guidelines for [RFC 2434] Narten, T. and H. Alvestrand, "Guidelines for
writing an IANA Considerations Section in RFCs", writing an IANA Considerations Section in RFCs",
BCP 26, RFC 2434, October 1998. BCP 26, RFC 2434, October 1998.
[MPLS-TE] Awduche, D., et al, "Requirements for Traffic [MPLS-TE] Awduche, D., et al, "Requirements for Traffic
Engineering Over MPLS," RFC 2702, September 1999. Engineering Over MPLS," RFC 2702, September 1999.
[OSPF-v2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPF-v2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[SEC-OSPF] Murphy, S., Badger, M., and B. Wellington, "OSPF with [SEC-OSPF] Murphy, S., Badger, M., and B. Wellington, "OSPF with
Digital Signatures", RFC 2154, June 1997 Digital Signatures", RFC 2154, June 1997.
[OSPF-CAP] Lindem, A., Shen, N., Aggarwal, R., Schaffer, S., and
Vasseur, JP., "Extensions to OSPF for advertising
optional router capabilities",
draft-ietf-ospf-cap-04.txt (work in progress)
16. Informative References 16. Informative References
[RSVP-TE] Awduche, D., L. Berger, D. Gan, T. Li, V. Srinivasan, [RSVP-TE] Awduche, D., L. Berger, D. Gan, T. Li, V. Srinivasan,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, IETF, December 2001 Tunnels", RFC 3209, IETF, December 2001
[CR-LDP] Jamoussi, B. et al, "Constraint-Based LSP Setup [CR-LDP] Jamoussi, B. et al, "Constraint-Based LSP Setup
using LDP", RFC 3212, January 2002. using LDP", RFC 3212, January 2002.
[MOSPF] Moy, J., "Multicast Extensions to OSPF", RFC 1584, [MOSPF] Moy, J., "Multicast Extensions to OSPF", RFC 1584,
March 1994. March 1994.
[NSSA] P. Murphy, "The OSPF NSSA Option", RFC 3101, January [NSSA] P. Murphy, "The OSPF NSSA Option", RFC 3101, January
2003 2003
[OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370,
July 1998. July 1998.
[OPQLSA-TE] Katz, D., D. Yeung and K. Kompella, "Traffic [OPQLSA-TE] Katz, D., D. Yeung and K. Kompella, "Traffic
Engineering Extensions to OSPF", RFC 3630, September
Engineering Extensions to OSPF", RFC 3630, September
2003. 2003.
[SONET-SDH] Ming-CHwan Chow, "Understanding SONET/SDH Standards [SONET-SDH] Ming-CHwan Chow, "Understanding SONET/SDH Standards
and Applications" - A paperback or bound book, and Applications" - A paperback or bound book,
Published by Andan publisher. Published by Andan publisher.
[GMPLS-TE] L. Berger, "Generalized Multi Protocol Label [GMPLS-TE] L. Berger, "Generalized Multi Protocol Label
Switching (GMPLS) Signaling Functional Description", Switching (GMPLS) Signaling Functional Description",
RFC 3471, January 2003 RFC 3471, January 2003
Authors' Addresses 17. Authors' Addresses
Pyda Srisuresh Pyda Srisuresh
Caymas Systems, Inc. Caymas Systems, Inc.
1179-A North McDowell Blvd. 1179-A North McDowell Blvd.
Petaluma, CA 94954 Petaluma, CA 94954
U.S.A. U.S.A.
EMail: srisuresh@yahoo.com EMail: srisuresh@yahoo.com
Paul Joseph Paul Joseph
Force10 Networks Symbol Technologies
1440 McCarthy Boulevard
Milpitas, CA 95035
U.S.A. U.S.A.
EMail: pjoseph@Force10Networks.com EMail:
18. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights."
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 95 change blocks. 
255 lines changed or deleted 241 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/