draft-ietf-ospf-cap-05.txt   draft-ietf-ospf-cap-06.txt 
Network Working Group A. Lindem (Editor) Network Working Group A. Lindem (Editor)
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Expires: July 8, 2005 N. Shen Expires: August 8, 2005 N. Shen
Cisco Systems Cisco Systems
R. Aggarwal R. Aggarwal
Juniper Networks Juniper Networks
S. Shaffer S. Shaffer
BridgePort Networks BridgePort Networks
JP. Vasseur JP. Vasseur
Cisco Systems, Inc Cisco Systems, Inc
January 7, 2005 February 7, 2005
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-cap-05.txt draft-ietf-ospf-cap-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as 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/ietf/1id-abstracts.txt.
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.
This Internet-Draft will expire on July 8, 2005. This Internet-Draft will expire on August 8, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
It is useful for routers in an OSPF routing domain to know the It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
capabilities of their neighbors and other routers in the OSPF routing know the capabilities of their neighbors and other routers in the
domain. This draft proposes extensions to OSPF for advertising routing domain. This draft proposes extensions to OSPFv2 and OSPFv3
optional router capabilities. A new Router Information (RI) opaque for advertising optional router capabilities. A new Router
LSA is proposed for this purpose. Information (RI) LSA is proposed for this purpose.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OSPF Router Information (RI) Opaque LSA . . . . . . . . . . . 4 2. OSPF Router Information (RI) LSA . . . . . . . . . . . . . . . 4
2.1 OSPF Router Capabilities TLV . . . . . . . . . . . . . . . 5 2.1 OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . 4
2.2 Reserved OSPF Router Capability Bits . . . . . . . . . . . 6 2.2 OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 5
2.3 Flooding Scope of the Router Information LSA . . . . . . . 6 2.3 OSPF Router Capabilities TLV . . . . . . . . . . . . . . . 6
3. Router Information LSA Opaque Usage and Applicability . . . . 8 2.4 Assiged OSPF Router Capability Bits . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 2.5 Flooding Scope of the Router Information LSA . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 3. Router Information LSA Opaque Usage and Applicability . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6.1 Normative References . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6.2 Informative References . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 12
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 6.2 Informative References . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . 15
1. Introduction 1. Introduction
It is useful for routers in an OSPF routing domain to know the It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3]
capabilities of their neighbors and other routers in the OSPF routing routing domain to know the capabilities of their neighbors and other
domain. This can be useful for various applications: routers in the routing domain. This can be useful for both the
o In MPLS Traffic Engineering (TE), it can be used as a discovery advertisement and discovery of OSPFv2 and OSPFv3 capabilities.
mechanism [TECAP] to announce a LSR's TE capabilities like Path Throughout this document, OSPF will be used when the specification is
Computation Server capability (Capability of an LSR to be a Path applicable to both OSPFv2 and OSPFv3. Similiarly, OSPFv2 or OSPFv3
Computation Server for TE LSP path computation) or the intention will be used when the text is protocol specific.
of an LSR to be part of a particular MPLS TE mesh group.
o For network management and troubleshooting. It gives operators a
network wide view of OSPF capabilities on different routers. The
presence of a capability on a given router implies that the
software version supports the capability and the router is
configured to support it. On the other hand, the absence of an
expected capability on a particular router can imply either
misconfiguration or an incorrect software version. Hence, this
capability information can be used to track problems resulting
from misconfiguration or an incorrect software version.
OSPF uses the options field in the hello packet to advertise optional OSPF uses the options field in LSAs and hello packets to advertise
router capabilities [OSPF]. However, all the bits in this field have optional router capabilities. In the case of OSFPv2, all the bits in
been allocated and there is no way to advertise new optional or MPLS this field have been allocated and there is no way to advertise new
TE capabilities. This document proposes extensions to OSPF to optional capabilities. This document proposes extensions to OSPF to
advertise these optional capabilities. For existing OSPF advertise these optional capabilities. For existing OSPF
capabilities, this advertisement will be used primarily for capabilities, backward compatibility issues dictate that this
informational purposes. For MPLS TE features, it is used for advertisement is used primarily for informational purposes. For
advertisement and discovery. Future OSPF features could also use future OSPF features, this advertimsement MAY be used as the sole
this mechanism for advertisement and discovery. mechanism for advertisement and discovery.
2. OSPF Router Information (RI) Opaque LSA 2. OSPF Router Information (RI) LSA
OSPF routers will optionally advertise their optional capabilities in OSPF routers MAY optionally advertise their optional capabilities in
an area-scoped, local scope, or AS-scoped Opaque-LSA [OPAQUE]. If a a link-scoped, area-scoped, or AS-scoped LSA. For existing OSPF
router does not advertise this LSA, it does not imply that the router capabilities, this advertisement will be used primarily for
does not support one or more of the defined capabilities. For informational purposes. Future OSPF features could the RI LSA as the
existing OSPF capabilities, this advertisement will be used primarily sole mechanism for advertisement and discovery. The RI LSA will be
for informational purposes. For MPLS TE features, it is used for originated initially when an OSPF router instance is created and
advertisement and discovery. Future OSPF features could also use whenever one of the advertised capabilities is configured or changed.
this mechanism for advertisement and discovery. The RI opaque LSA
will be originated when one of the advertised capabilities is
configured or changed.
The Router Information LSA will have an Opaque type of 4 and Opaque 2.1 OSPFv2 Router Information (RI) Opaque LSA
ID of 0.
OSPFv2 routers will advertise a link scoped, area-scoped, or
AS-scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has
an Opaque type of 4 and Opaque ID of 0.
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 | 9, 10 or 11 | | LS age | Options | 9, 10 or 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 4 | 0 | | 4 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 19 skipping to change at page 5, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... | | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Length field defines the length of the value portion in octets The Length field defines the length of the value portion in octets
(thus a TLV with no value portion would have a length of zero). The (thus a TLV with no value portion would have a length of zero). The
TLV is padded to four-octet alignment; padding is not included in TLV is padded to four-octet alignment; padding is not included in
the length field (so a three octet value would have a length of the length field (so a three octet value would have a length of
three, but the total size of the TLV would be eight octets). Nested three, but the total size of the TLV would be eight octets). Nested
TLV's are also 32-bit aligned. For example, a one byte value would TLV's are also 32-bit aligned. For example, a one byte value would
have the length field set to 1, and three bytes of padding would be have the length field set to 1, and three octets of padding would be
added to the end of the value portion of the TLV. Unrecognized types added to the end of the value portion of the TLV. Unrecognized types
are ignored. are ignored.
2.1 OSPF Router Capabilities TLV 2.2 OSPFv3 Router Information (RI) Opaque LSA
The first defined TLV in the body of an RI opaque LSA is the Router The OSPFv3 Router Information LSA has a function code of 12 while the
Capabilities TLV. A router advertising an RI opaque LSA SHOULD S1/S2 bit are dependent on the desired flooding scope for the LSA.
include the Router Capabilities TLV and SHOULD correctly identify the The U bit will be set indicating the OSPFv3 RI LSA should be flooded
status of the capabilities defined in section 2.2. even if it is not understood. The Link State ID (LSID) value for
this LSA is 0. This is unambiguous since an OSPFv3 router will only
advertise a single RI LSA per flooding scope.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS age |1|S12| 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 (Link State ID) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- TLV's -+
| ... |
The format of the TLV's within the body of a router information LSA
as defined in Section 2.1
When a new Router Information LSA TLV is defined, the specification
MUST explicitly state whether the TLV is applicable to OSPFv2 only,
OSPFv3 only, or both OSPFv2 and OSPFv3.
2.3 OSPF Router Capabilities TLV
The first defined TLV in the body of an RI LSA is the Router
Capabilities TLV. A router advertising an RI LSA MUST include the
Router Capabilities TLV and it MUST be the first TLV in the LSA.
Additionally, the TLV MUST accurately reflect the OSPF router's
capabilities in the scope it is advertised.
The format of the Router Capabilities TLV is as follows: The format of the Router Capabilities TLV is 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Capabilities | | Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16 bit field set to 1. Type A 16 bit field set to 1.
Length A 16 bit field that indicates the length of the value Length A 16 bit field that indicates the length of the value
portion in bytes. Its set to N x 4 octets. N starts portion in octets and will be a multiple of 4 octets
from 1 and can be increased when there is a need. Each 4 dependent on the number of capabilities advertised. In
octets are referred to as a capability flag. this revision the length will be 4 denoting 4 octets of
Value This comprises one or more capability flags. For each 4 capability bits.
octets, the bits are indexed from the most significant Value A variable length sequence of capability flags rounded
to the least significant, where each bit represents one to a multiple of 4 octects padded with undefined bits.
router capability. When the first 32 capabilities are In this revision, there are 4 octets of capability bits.
defined, a new capability flag will be used to
accommodate the next capability.
The Router Capabilities TLV MAY be followed by optional TLV's that The Router Capabilities TLV MAY be followed by optional TLV's that
further specify a capability. further specify a capability.
2.2 Reserved OSPF Router Capability Bits 2.4 Assiged OSPF Router Capability Bits
The following bits in the first capability flag have been assigned: The following bits in the first capability flag have been assigned:
Bit Capabilities Bit Capabilities
0-3 Reserved 0-3 Unassigned
4 OSPF graceful restart capable [GRACE] 4 OSPF graceful restart capable [GRACE]
5 OSPF graceful restart helper [GRACE] 5 OSPF graceful restart helper [GRACE]
6 OSPF Stub Router support [STUB] 6 OSPF Stub Router support [STUB]
7 OSPF Traffic Engineering support [TE] 7 OSPF Traffic Engineering support [TE]
8 OSPF point-to-point over LAN [P2PLAN] 8 OSPF point-to-point over LAN [P2PLAN]
9 OSPF Path Computation Server discovery [TECAP] 9 OSPF Experimental TE [EXPTE]
10 OSPF Experimental TE [EXPTE] 10-31 Future assignments
11-31 Future assignments
2.3 Flooding Scope of the Router Information LSA 2.5 Flooding Scope of the Router Information LSA
The flooding scope for a Router Information opaque LSA is determined The flooding scope for a Router Information LSA is determined by the
by the LSA type. A type 9 (link-scope), type 10 (area-scoped), or a LSA type. For OSPFv2, type 9 (link-scope), type 10 (area-scoped), or
type 11 (AS-scoped) opaque LSA may be flooded. If a type 11 opaque a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the
LSA is chosen, the originating router should also advertise type 10 flooding scope is determined by the S1 and S2 bits in the LSA type.
LSA(s) into any attached NSSA/stub area(s). An OSPF router MAY If AS wide flooding scope is chosen, the originating router should
advertise different capabilities when both NSSA/stub area type 10 also advertise area scoped LSA(s) into any attached NSSA area(s). An
LSA(s) and an AS scoped type 11 opaque LSA is advertised. This OSPF router MAY advertise different capabilities when both NSSA area
allows functional capabilities to be limited in scope. For example, scoped LSA(s) and an AS scoped LSA is advertised. This allows
a router may be an area border router but only support traffic functional capabilities to be limited in scope. For example, a
router may be an area border router but only support traffic
engineering (TE) in a subset of its attached areas. The choice of engineering (TE) in a subset of its attached areas. The choice of
flooding scope is made by the advertising router and is a matter of flooding scope is made by the advertising router and is a matter of
local policy. The originating router MAY advertise multiple RI local policy. The originating router MAY advertise multiple RI LSAs
opaque LSAs as long as the flooding scopes differ. TLV flooding as long as the flooding scopes differ. TLV flooding scope rules will
scope rules will be specified on a per-TLV basis. be specified on a per-TLV basis and MUST be specified in the
accompanying specifications for new Router Information LSA TLVs.
3. Router Information LSA Opaque Usage and Applicability 3. Router Information LSA Opaque Usage and Applicability
The purpose of the Router Information (RI) opaque LSA is to advertise The purpose of the Router Information (RI) LSA is to advertise
information relating to the aggregate OSPF router. Normally, this information relating to the aggregate OSPF router. Normally, this
should be confined to TLVs with a single value or very few values. should be confined to TLVs with a single value or very few values.
It is not meant to be a generic container to carry any and all It is not meant to be a generic container to carry any and all
information. The intent is to both limit the size of the RI LSA to information. The intent is to both limit the size of the RI LSA to
the point where an OSPF router will always be able to contain the the point where an OSPF router will always be able to contain the
TLVs in a single LSA and to keep the task of determining what has TLVs in a single LSA and to keep the task of determining what has
changed between LSA instances reasonably simple. Hence, discretion changed between LSA instances reasonably simple. Hence, discretion
and sound engineering judgement MUST be adhered to when deciding and sound engineering judgement MUST be adhered to when deciding
whether newly proposed TLV(s) in support of a new function are whether newly proposed TLV(s) in support of a new application are
advertised in the RI opaque LSA or warrent the creation of a function advertised in the RI LSA or warrent the creation of an application
specific opaque LSA. specific LSA.
4. Security Considerations 4. Security Considerations
The function described in this document does not create any new The function described in this document does not create any new
security issues for the OSPF protocol. Security considerations for security issues for the OSPF protocol. Security considerations for
the base OSPF protocol are covered in [OSPF]. the base OSPF protocol are covered in [OSPF].
5. IANA Considerations 5. IANA Considerations
A new opaque LSA type will need to be assigned by IANA. The following IANA assignments are to be made from existing
Additionally, IANA will need to have registries for the Router registries:
Information opaque LSA TLV's. The TLV assignee will be responsible 1. The OSPFv2 opaque LSA type 4 will need to be reserved for the
for allocation of any sub-TLV's for the IANA assigned TLV. All TLV's OSPFv2 RI opaque LSA.
and sub-TLV's will be subject to OSPF WG review. 2. The OSPFv2 LSA type function code 18 will need to be reserved for
the OSPFv3 RI LSA.
New registries are defined for the following purposes:
1. Registry for OSPF RI TLVs - The value of 1 for the capabilities
TLV is defined herein. All TLV additions are subject to OSPF WG
review.
2. Registry for OSPF Router Capability Flags - The values defined in
Section 2.3. All Router Capability TLV additions are subject to
OSPF WG review.
6. References 6. References
6.1 Normative References 6.1 Normative References
[OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July
1998.
[OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[OSPFV3] Coltun, R., Ferguson, D. and J. Moy, "OSPF for IPv6", RFC
2740, April 1998.
[RFC2119] Bradner, S., "Key words for use in RFC's to Indicate [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate
Requirement Levels", RFC 2328, March 1977. Requirement Levels", RFC 2328, March 1977.
[TE] Katz, D., Yeung, D. and K. Kompella, "Traffic Engineering [TE] Katz, D., Yeung, D. and K. Kompella, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
6.2 Informative References 6.2 Informative References
[EXPTE] Srisuresh, P. and P. Joseph, "OSPF OSPF-TE: An [EXPTE] Srisuresh, P. and P. Joseph, "OSPF OSPF-TE: An
experimental extension to OSPF for Traffic Engineering", experimental extension to OSPF for Traffic Engineering",
draft-srisuresh-ospf-te-07.txt (work in progress). draft-srisuresh-ospf-te-07.txt (work in progress).
[GRACE] Moy, J., Pillay-Esnault, P. and A. Lindem, "Graceful OSPF [GRACE] Moy, J., Pillay-Esnault, P. and A. Lindem, "Graceful OSPF
Restart", RFC 3623, November 2003. Restart", RFC 3623, November 2003.
[OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July
1998.
[P2PLAN] Shen, N. and A. Zinin, "Point-to-point operation over LAN [P2PLAN] Shen, N. and A. Zinin, "Point-to-point operation over LAN
in link-state routing protocols", in link-state routing protocols",
draft-ietf-isis-igp-p2p-over-lan-05.txt (work in progress). draft-ietf-isis-igp-p2p-over-lan-05.txt (work in progress).
[STUB] Retana, A., Nguyen, L., White, R., Zinin, A. and D. [STUB] Retana, A., Nguyen, L., White, R., Zinin, A. and D.
McPherson, "OSPF Stub Router Advertisement", RFC 3137, June McPherson, "OSPF Stub Router Advertisement", RFC 3137, June
2001. 2001.
[T3CAP] Vasseur, JP., Psenak, P., Yasukawa, S. and JL. Le Roux, [T3CAP] Vasseur, JP., Psenak, P., Yasukawa, S. and JL. Le Roux,
"OSPF MPLS Traffic Engineering Capabilities", "OSPF MPLS Traffic Engineering Capabilities",
skipping to change at page 13, line 12 skipping to change at page 14, line 12
EMail: jpv@cisco.com EMail: jpv@cisco.com
Appendix A. Acknowledgments Appendix A. Acknowledgments
The idea for this work grew out of a conversation with Andrew Partan The idea for this work grew out of a conversation with Andrew Partan
and we would like to thank him for his contribution. The authors and we would like to thank him for his contribution. The authors
would like to thanks Peter Psenak for his review and helpful comments would like to thanks Peter Psenak for his review and helpful comments
early versions of the draft. early versions of the draft.
Comments from Abhay Roy, Vishwas Manral, and Vivek Dubey were Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian
incorporated into the final draft version. Farrel were incorporated into the final draft version.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/