< draft-bitar-rao-ospf-diffserv-mpls-00.txt   draft-bitar-rao-ospf-diffserv-mpls-01.txt >
Network Working Group Nabil Bitar TE Working Group Nabil Bitar
Internet Draft Roshan Rao Internet Draft Roshan Rao
Expiration Date: September 2001 Lucent Technologies Inc. Expiration Date: December 2001 Karthik Muthukrishnan
Lucent Technologies Inc.
March 2001 July 2001
Traffic Engineering Extensions to OSPF Traffic Engineering Extensions to OSPF
draft-bitar-rao-ospf-diffserv-mpls-00.txt draft-bitar-rao-ospf-diffserv-mpls-01.txt
Status Status
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 49 skipping to change at page 1, line 50
1. Introduction 1. Introduction
In [1], a new OSPF Link State Advertisement (LSA), called the Traffic In [1], a new OSPF Link State Advertisement (LSA), called the Traffic
Engineering LSA (TE-LSA), was defined. This LSA advertises the link Engineering LSA (TE-LSA), was defined. This LSA advertises the link
maximum and reservable bandwidth as well as the un-reservable maximum and reservable bandwidth as well as the un-reservable
bandwidth at each of 8 priority levels. bandwidth at each of 8 priority levels.
This document defines new Link sub-TLV extensions to those defined in This document defines new Link sub-TLV extensions to those defined in
[1] in order to support differentiated services and MPLS. The need or [1] in order to support differentiated services and MPLS. The need or
requirements to provide such support in OSPF and IS-IS are discussed requirements to provide such support in OSPF and IS-IS are discussed
in details in [2]. Differentiated services (Diffserv) enable the in detail in [2]. Differentiated services (Diffserv) enable the
support of different per-hop behaviors (PHBs) [3] on a link. These support of different per-hop behaviors (PHBs) [3] on a link. These
per-hop behaviors enable packets passing through a link to get per-hop behaviors enable packets passing through a link to get
different forwarding treatment depending on the behavior aggregate to different forwarding treatment depending on the behavior aggregate to
which they belong. Each behavior aggregate maps to a PHB. MPLS-aware which they belong. Each behavior aggregate maps to a PHB. MPLS-aware
switches/routers (LSRs), that implement the Diffserv extensions to switches/routers (LSRs), that implement the Diffserv extensions to
MPLS [4], will be able to request and setup label-switched paths MPLS [4], will be able to request and setup label-switched paths
(LSPs) that carry different behavior aggregates. At routers, the (LSPs) that carry different behavior aggregates. At routers, the
label and/or EXP field of the top label in the shim header of a label and/or EXP field of the top label in the shim header of a
labeled packet indicates the behavior aggregate to which the labeled labeled packet indicates the behavior aggregate to which the labeled
skipping to change at page 2, line 29 skipping to change at page 2, line 29
document were proposed in [5]. However, this document defines the document were proposed in [5]. However, this document defines the
actual encoding of these extensions based on the PHBIDs defined in actual encoding of these extensions based on the PHBIDs defined in
[6] as opposed to the class-type suggested in [5]. PHBIDs are used [6] as opposed to the class-type suggested in [5]. PHBIDs are used
to identify Diffserv PHB/PHB-groups in a standard way. Additionally, to identify Diffserv PHB/PHB-groups in a standard way. Additionally,
the encoding proposed in this document can be looked at as defining the encoding proposed in this document can be looked at as defining
the class type in [5] as a concatenation of PHBIDs. the class type in [5] as a concatenation of PHBIDs.
In addition to defining sub-TLVs that relay the link support for In addition to defining sub-TLVs that relay the link support for
Diffserv, a new Link sub-TLV is defined to advertise the MPLS Diffserv, a new Link sub-TLV is defined to advertise the MPLS
capability and the state of MPLS-related resources for that link. capability and the state of MPLS-related resources for that link.
Modifications to some Link sub-TLVs defined in [1] are also proposed. It is also proposed that the Maximum reservable Bandwdth Link sub-TLV
defined in [1] be modified.
This document does not discuss how the actual route selection for an This document does not discuss how the actual route selection for an
LSP can be done. Route computation will be the subject of another LSP can be done. Route computation will be the subject of another
discussion. discussion.
2. TLV format 2. TLV format
This document adopts the TLV format used in [1]. This document adopts the TLV format used in [1].
3. Link TLV 3. Link TLV
skipping to change at page 2, line 51 skipping to change at page 2, line 52
This document defines sub-TLVs to be encoded in the value field of This document defines sub-TLVs to be encoded in the value field of
the link TLV defined in [1]. The following sub-TLVs are defined: the link TLV defined in [1]. The following sub-TLVs are defined:
1- Diffserv Available Bandwidth 1- Diffserv Available Bandwidth
2- Oversubscription 2- Oversubscription
3- Diffserv Capability 3- Diffserv Capability
4- Diffserv Max Delay 4- Diffserv Max Delay
5- Link Propagation Delay 5- Link Propagation Delay
6- Priority Reserved Bandwidth 6- Priority Reserved Bandwidth
7- Link Capability/Resources 7- Link Capability/Resources
8- Link-data TLV
All the sub-TLVs defined in this document are optional. However, a All the sub-TLVs defined in this document are optional. However, a
router must support all Diffserv TLVs or none. Each sub-TLV may occur router must support all Diffserv TLVs or none. Each sub-TLV may occur
only once. Unrecognized types are ignored but still flooded. only once. Unrecognized types are ignored but still flooded.
Modifications to the following sub-TLVs defined in [1] are also A Modification to the the defnition of the Maximum Reservable
proposed: Bandwidth sub-TLV defined in [1] is also proposed:
1- Local Interface IP Address
2- Maximum Reservable Bandwidth
3.1 Diffserv Available Bandwidth 3.1 Diffserv Available Bandwidth
The Diffserv Available Bandwidth sub-TLV is used to advertise the The Diffserv Available Bandwidth sub-TLV is used to advertise the
available bandwidth for each PHB/PHB group or set of PHB/PHB-groups available bandwidth for each PHB/PHB group or set of PHB/PHB-groups
configured on the advertised link from the advertising router configured on the advertised link from the advertising router
direction. In the latter case, a set of PHB/PHB groups is allocated direction. In the latter case, a set of PHB/PHB groups is allocated
a sharable bandwidth chunk of the link. Each PHB or PHB group is a sharable bandwidth chunk of the link. Each PHB or PHB group is
identified by a 16-bit PHB identifier (PHBID) [6]. The absence of a identified by a 16-bit PHB identifier (PHBID) [6]. The absence of a
PHBID from this sub-TLV can be interpreted to mean that the PHBID from this sub-TLV can be interpreted to mean that the
particular PHB group is not supported on that link unless it is particular PHB group is not supported on that link unless it is
advertised in the Diffserv capability TLV. Routing can take advertised in the Diffserv capability TLV. Routing can take
advantage of this information in selecting a path for an LSP that advantage of this information in selecting a path for an LSP that
desires a particular PHB. The Diffserv available bandwidth sub-TLV desires a particular PHB. The Diffserv available bandwidth sub-TLV
has type 10. Its value consists of a sequence of elements where type is TBD. Its value consists of a sequence of elements where
each element has the following format: each element has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|#PHB=n | Oversubscription | Available Bandwidth | |#PHB=n | Oversubscription | Available Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Available bandwidth(cont.) | PHBID1 | | Available bandwidth(cont.) | PHBID1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ---------- | PHBIDn | | ---------- | PHBIDn |
skipping to change at page 4, line 7 skipping to change at page 4, line 7
The number of elements advertised in each sub-TLV can be deduced The number of elements advertised in each sub-TLV can be deduced
from the sub-TLV length and the #PHB field(s). Each element has from the sub-TLV length and the #PHB field(s). Each element has
length (6 + n * 2) bytes, where 6 bytes account for the #PHB, length (6 + n * 2) bytes, where 6 bytes account for the #PHB,
oversubscription and the available bandwidth fields, and n is the oversubscription and the available bandwidth fields, and n is the
number of PHBIDs advertised in that element. number of PHBIDs advertised in that element.
3.2 Over-Subscription 3.2 Over-Subscription
A Link TLV that includes the Over-Subscription sub-TLV MUST also A Link TLV that includes the Over-Subscription sub-TLV MUST also
include the Maximum Reservable Bandwidth sub-TLV as proposed to be include the Maximum Reservable Bandwidth sub-TLV as proposed to be
defined in Section 3.11 and is correlated with it. The defined in Section 3.8 and is correlated with it. The
Over-Subscription sub-TLV is type 11 and it is encoded in percentage Over-Subscription sub-TLV type is TBD. It is encoded in percentage
as a 16-bit integer value using the following format: as a 16-bit integer value using the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Over-subscription factor | Reserved =0 | | Over-subscription factor | Reserved =0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Over-Subscription sub-TLV length is 4 bytes. The Over-Subscription sub-TLV length is 4 bytes.
3.3 Diffserv Capability 3.3 Diffserv Capability
The Diffserv Capability sub-TLV has type 12. It is used to advertise The Diffserv Capability sub-TLV type is TBD. It is used to advertise
the PHB/PHB groups supported on a link. Its value consists of a the PHB/PHB groups supported on a link. Its value consists of a
sequence of PHBIDs as follows: sequence of PHBIDs 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PHBID1 | PHBID2 | | PHBID1 | PHBID2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ------ | ------ | | ------ | ------ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 5 skipping to change at page 5, line 5
be imposed by the application(s) whose packets are to be transported be imposed by the application(s) whose packets are to be transported
in that LSP. An operator may want to configure a Diffserv PHB/PHB in that LSP. An operator may want to configure a Diffserv PHB/PHB
group that will be applied to such packets. Therefore, it becomes group that will be applied to such packets. Therefore, it becomes
important to advertise the maximum delay associated with that important to advertise the maximum delay associated with that
PHB/PHB group at each link. When setting up an LSP with certain PHB/PHB group at each link. When setting up an LSP with certain
delay/delay variation requirement, this maximum delay can be used delay/delay variation requirement, this maximum delay can be used
as a metric to select the LSP path. The Maximum delay advertised in as a metric to select the LSP path. The Maximum delay advertised in
this sub-TLV is only due to queuing delay. The delay variation is this sub-TLV is only due to queuing delay. The delay variation is
considered to be the same as maximum delay. considered to be the same as maximum delay.
The Maximum Delay TLV is type 13. It is used to advertise the The Maximum Delay TLV type is TBD. It is used to advertise the
maximum queuing delay that can be encountered by a packet that maximum queuing delay that can be encountered by a packet that
belongs to a behavior aggregate corresponding to the associated belongs to a behavior aggregate corresponding to the associated
PHBID. Its value consists of a sequence of 4-octet elements where PHBID. Its value consists of a sequence of 4-octet elements where
each element has the following format: each element has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PHBID | Max Delay value | | PHBID | Max Delay value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Max Delay value is specified as an unsigned-integer in units of The Max Delay value is specified as an unsigned-integer in units of
microsecond. Thus, maximum delay can be 65536 microseconds. The microsecond. Thus, maximum delay can be 65536 microseconds. The
length field in the sub-TLV will be equal to (4* number of length field in the sub-TLV will be equal to (4* number of
advertised elements). advertised elements).
3.5 Link Propagation Delay 3.5 Link Propagation Delay
The Link Propagation Delay sub-TLV is type 14. It is 4-octet The Link Propagation Delay sub-TLV type is TBD. The delay value is
encoded in the value field of the sub-TLV in IEEE floating point 4 octets encoded in the value field of the sub-TLV in IEEE floating
format. It is in units of microseconds. point format. It is in units of microseconds.
3.6 Priority Reserved Bandwidth 3.6 Priority Reserved Bandwidth
This sub-TLV advertises the reserved bandwidth at each of the eight This sub-TLV advertises the reserved bandwidth at each of the eight
priority levels specified in CR-LDP [7] and RSVP-TE [8]. An operator priority levels specified in CR-LDP [7] and RSVP-TE [8]. An operator
may configure PHB(s)/PHB groups to have fixed allocations of the may configure PHB(s)/PHB groups to have fixed allocations of the
bandwidth while allow others to share the remaining bandwidth or bandwidth while allow others to share the remaining bandwidth or
chunks of the bandwidth. In addition, an operator can configure chunks of the bandwidth. In addition, an operator can configure
certain priority levels but not all for certain PHB groups. In this certain priority levels but not all for certain PHB groups. In this
latter case, it makes sense to advertise the reserved bandwidth for latter case, it makes sense to advertise the reserved bandwidth for
each of the configured priorities per PHB/PHB-group. When a set of each of the configured priorities per PHB/PHB-group. When a set of
PHB/PHB-groups is advertised to have a sharable bandwidth (i.e. PHB/PHB-groups is advertised to have a sharable bandwidth (i.e.
as a set), the reserved bandwidth per priority level applies to the as a set), the reserved bandwidth per priority level applies to the
set not to individual PHBs/PHB-groups. set not to individual PHBs/PHB-groups.
This TLV is type 15. Its value consists of a sequence of elements This TLV type is TBD. Its value consists of a sequence of elements
where each element has the following format: where each element has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| #PHBID = n| Re| pri bit map | Reserved Bandwidth 1 | | #PHBID = n| Re| pri bit map | Reserved Bandwidth 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved Bandwidth 1 (cont.) | ------------ | | Reserved Bandwidth 1 (cont.) | ------------ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ---------- | ------------- | | ---------- | ------------- |
skipping to change at page 6, line 17 skipping to change at page 6, line 17
least significant bit corresponding to priority 7. If the bit is least significant bit corresponding to priority 7. If the bit is
cleared, the corresponding priority level is not supported. If the cleared, the corresponding priority level is not supported. If the
bit is set, the corresponding priority level is supported. For those bit is set, the corresponding priority level is supported. For those
supported priority levels, the reserved bandwidth is listed in supported priority levels, the reserved bandwidth is listed in
decreasing priority order (i.e. starting with 0 down to 7). The decreasing priority order (i.e. starting with 0 down to 7). The
number of reserved bandwidth fields can be obtained by summing up number of reserved bandwidth fields can be obtained by summing up
the number of 1's in the bit map. the number of 1's in the bit map.
3.7 Link Capability/Resources 3.7 Link Capability/Resources
The Link Capability/Resources sub-TLV has type 16. Its value is a The Link Capability/Resources sub-TLV type is TBD. Its value is a
32-bit map with the following defined bits: 32-bit map with the following defined bits:
Bit 0 (most significant bit): corresponds to MPLS-specific Bit 0 (most significant bit): corresponds to MPLS-specific
resources on the link (e.g., out of labels, out of memory). It resources on the link (e.g., out of labels, out of memory). It
is set when a resource essential to the setup of an LSP is is set when a resource essential to the setup of an LSP is
exhausted. exhausted.
Bit 31: set to 1 if the router supports RSVP-TE. It is clear Bit 31: set to 1 if the router supports RSVP-TE. It is clear
otherwise. otherwise.
Bit 30: set to 1 if the router supports CR-LDP. It is clear Bit 30: set to 1 if the router supports CR-LDP. It is clear
otherwise. otherwise.
3.8 Link Data 3.8 Maximum Reservable Bandwidth
The Link Data sub-TLV is type 17 and has a 4-octet long value. It
specifies the local interface IP address on numbered links.
On unnumbered links, the Link Data sub-TLV specifies the IfIndex of
the interface. How the IfIndex is generated is vendor-specific as
long as it is unique on the advertising router. This information is
what would be contained in the link data part of a link advertised
in the router LSA. It is needed to uniquely associate a TE-TLV with
a link listed in the router LSA of the advertising router.
3.9 Local Interface IP Address
This documents proposes that the Local Interface IP Address sub-TLV
defined in [1] be omitted if the Link Data sub-TLV is accepted and
made mandatory.
3.10 Maximum Reservable Bandwidth
According to [1], the Maximum Reservable Bandwidth sub-TLV (type-7) According to [1], the Maximum Reservable Bandwidth sub-TLV (type-7)
specifies the maximum bandwidth that may be reserved on this link in specifies the maximum bandwidth that may be reserved on this link in
this direction, in IEEE floating point format. It is proposed that this direction, in IEEE floating point format. It is proposed that
this sub-TLV advertise the maximum reservable bandwidth, including this sub-TLV advertise the maximum reservable bandwidth, including
oversubscription, on the link excluding what is advertised in the oversubscription, on the link excluding what is advertised in the
Diffserv available bandwidth TLVs if any. Diffserv available bandwidth TLVs if any.
4. Elements of Procedure 4. Elements of Procedure
skipping to change at page 7, line 26 skipping to change at page 7, line 8
refreshes, whenever there is a significant change in the advertised refreshes, whenever there is a significant change in the advertised
information that was previously advertised by these LSAs. information that was previously advertised by these LSAs.
5. Security Considerations 5. Security Considerations
This document raises no new security issues for OSPF. This document raises no new security issues for OSPF.
6. References 6. References
[1] Katz, Dave and Yeung, Derek, "Traffic Engineering Extensions to [1] Katz, Dave and Yeung, Derek, "Traffic Engineering Extensions to
OSPF," draft-katz-yeung-ospf-traffic-03.txt, September 2000. OSPF," draft-katz-yeung-ospf-traffic-04.txt, February 2001.
[2] Le Faucheur et. al., "Requirements for support of [2] Le Faucheur et. al., "Requirements for support of
Diff-Serv-aware MPLS Traffic Engineering," draft-ietf-mpls-diff- Diff-Serv-aware MPLS Traffic Engineering," draft-ietf-tewg-diff-
te-reqts-00.txt," November 2000. te-reqts-00.txt," February 2001.
[3] Blake, S. et. al., "An Architecture for Differentiated Services," [3] Blake, S. et. al., "An Architecture for Differentiated Services,"
RFC 2475, December 1998. RFC 2475, December 1998.
[4] Le Faucheur et. al., "MPLS Support of Differentiated Services," [4] Le Faucheur et. al., "MPLS Support of Differentiated Services,"
draft-ietf-mpls-diff-ext-08.txt, February 2001. draft-ietf-mpls-diff-ext-08.txt, February 2001.
[5] Le Faucheur et. al., " Extensions to OSPF for support of [5] Le Faucheur et. al., " Extensions to OSPF for support of
Diff-Serv-aware MPLS Traffic Engineering," draft-lefaucheur-diff- Diff-Serv-aware MPLS Traffic Engineering," draft-ietf-ospf-diff-
te-ospf-01.txt, November 2000. te-00.txt, February 2001.
[6] Brim, S. et al, "Per Hop Behavior Identification Codes," [6] Brim, S. et al, "Per Hop Behavior Identification Codes,"
RFC 2836, May 2000. RFC 2836, May 2000.
[7] Jamoussi, B. et. al. "Constraint-Based LSP Setup using LDP," [7] Jamoussi, B. et. al. "Constraint-Based LSP Setup using LDP,"
draft-ietf-mpls-cr-ldp-05.txt, February 2001. draft-ietf-mpls-cr-ldp-05.txt, February 2001.
[8] Awduche, D. et al, "RSVP-TE: Extensions to RSVP for LSP Tunnels," [8] Awduche, D. et al, "RSVP-TE: Extensions to RSVP for LSP Tunnels,"
draft-ietf-mpls-rsvp-lsp-tunnel-08.txt, February 2001. draft-ietf-mpls-rsvp-lsp-tunnel-08.txt, February 2001.
skipping to change at line 389 skipping to change at page 7, line 48
Westford, MA 01889 Westford, MA 01889
USA USA
E-mail: nbitar@lucent.com E-mail: nbitar@lucent.com
Roshan Rao Roshan Rao
Lucent Technologies Lucent Technologies
1 Robbins Road, 1 Robbins Road,
Westford, MA 01889 Westford, MA 01889
USA USA
E-mail: rrao@lucent.com E-mail: rrao@lucent.com
Karthik Muthukrishnan
Lucent Technologies
1 Robbins Road,
Westford, MA 01889
USA
E-mail: mkarthik@lucent.com
 End of changes. 20 change blocks. 
45 lines changed or deleted 26 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/