draft-ietf-ospf-cap-08.txt   draft-ietf-ospf-cap-09.txt 
Network Working Group A. Lindem (Editor) Network Working Group A. Lindem (Editor)
Internet-Draft N. Shen Internet-Draft N. Shen
Expires: June 3, 2006 J. Vasseur Intended status: Standards Track J. Vasseur
Cisco Systems Expires: April 23, 2007 Cisco Systems
R. Aggarwal R. Aggarwal
Juniper Networks Juniper Networks
S. Shaffer S. Shaffer
BridgePort Networks BridgePort Networks
November 30, 2005 October 20, 2006
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-cap-08.txt draft-ietf-ospf-cap-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 June 3, 2006. This Internet-Draft will expire on April 23, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
It is useful for routers in an OSPFv2 or OSPFv3 routing domain to It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
know the capabilities of their neighbors and other routers in the know the capabilities of their neighbors and other routers in the
routing domain. This draft proposes extensions to OSPFv2 and OSPFv3 routing domain. This draft proposes extensions to OSPFv2 and OSPFv3
for advertising optional router capabilities. A new Router for advertising optional router capabilities. A new Router
Information (RI) LSA is proposed for this purpose. In OSPFv2, the RI Information (RI) LSA is proposed for this purpose. In OSPFv2, the RI
LSA will be implemented with a new opaque LSA type ID. In OSPFv3, LSA will be implemented with a new opaque LSA type ID. In OSPFv3,
the RI LSA will be implemented with a new LSA type function code. In the RI LSA will be implemented with a new LSA type function code. In
both protocols, the RI LSA can be advertised at any of the defined both protocols, the RI LSA can be advertised at any of the defined
flooding scopes (link, area, or AS). flooding scopes (link, area, or AS).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
2. OSPF Router Information (RI) LSA . . . . . . . . . . . . . . . 4 2. OSPF Router Information (RI) LSA . . . . . . . . . . . . . . . 4
2.1 OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . 4 2.1. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . 4
2.2 OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 5 2.2. OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 5
2.3 OSPF Router Informational Capabilities TLV . . . . . . . . 5 2.3. OSPF Router Informational Capabilities TLV . . . . . . . . 6
2.4 Assigned OSPF Router Informational Capability Bits . . . . 6 2.4. Assigned OSPF Router Informational Capability Bits . . . . 7
2.5 Flooding Scope of the Router Information LSA . . . . . . . 7 2.5. Flooding Scope of the Router Information LSA . . . . . . . 7
3. Router Information LSA Opaque Usage and Applicability . . . . 8 3. Router Information LSA Opaque Usage and Applicability . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Normative References . . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . . 11
6.2 Informative References . . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 14
1. Introduction 1. Introduction
It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3]
routing domain to know the capabilities of their neighbors and other routing domain to know the capabilities of their neighbors and other
routers in the routing domain. This can be useful for both the routers in the routing domain. This can be useful for both the
advertisement and discovery of OSPFv2 and OSPFv3 capabilities. advertisement and discovery of OSPFv2 and OSPFv3 capabilities.
Throughout this document, OSPF will be used when the specification is Throughout this document, OSPF will be used when the specification is
applicable to both OSPFv2 and OSPFv3. Similarly, OSPFv2 or OSPFv3 applicable to both OSPFv2 and OSPFv3. Similarly, OSPFv2 or OSPFv3
will be used when the text is protocol specific. will be used when the text is protocol specific.
skipping to change at page 3, line 26 skipping to change at page 3, line 26
optional router capabilities. In the case of OSPFv2, all the bits in optional router capabilities. In the case of OSPFv2, all the bits in
this field have been allocated and there is no way to advertise new this field have been allocated and there is no way to advertise new
optional capabilities. This document proposes extensions to OSPF to optional capabilities. This document proposes extensions to OSPF to
advertise these optional capabilities via opaque LSAs in OSPFv2 and advertise these optional capabilities via opaque LSAs in OSPFv2 and
new LSAs in OSPFv3. For existing OSPF capabilities, backward new LSAs in OSPFv3. For existing OSPF capabilities, backward
compatibility issues dictate that this advertisement is used compatibility issues dictate that this advertisement is used
primarily for informational purposes. For future OSPF features, this primarily for informational purposes. For future OSPF features, this
advertisement MAY be used as the sole mechanism for advertisement and advertisement MAY be used as the sole mechanism for advertisement and
discovery. discovery.
1.1 Requirements notation 1.1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119]. document are to be interpreted as described in RFC2119 [RFC2119].
2. OSPF Router Information (RI) LSA 2. OSPF Router Information (RI) LSA
OSPF routers MAY optionally advertise their optional capabilities in OSPF routers MAY optionally advertise their optional capabilities in
a link-scoped, area-scoped, or AS-scoped LSA. For existing OSPF a link-scoped, area-scoped, or AS-scoped LSA. For existing OSPF
capabilities, this advertisement will be used primarily for capabilities, this advertisement will be used primarily for
informational purposes. Future OSPF features could use the RI LSA as informational purposes. Future OSPF features could use the RI LSA as
the sole mechanism for advertisement and discovery. The RI LSA will the sole mechanism for advertisement and discovery. The RI LSA will
be originated initially when an OSPF router instance is created and be originated initially when an OSPF router instance is created and
whenever one of the advertised capabilities is configured or changed. whenever one of the advertised capabilities is configured or changed.
2.1 OSPFv2 Router Information (RI) Opaque LSA 2.1. OSPFv2 Router Information (RI) Opaque LSA
OSPFv2 routers will advertise a link scoped, area-scoped, or AS- OSPFv2 routers will advertise a link scoped, area-scoped, or AS-
scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has an scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has an
Opaque type of 4 and Opaque ID of 0. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 38 skipping to change at page 4, line 38
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+- TLVs -+ +- TLVs -+
| ... | | ... |
OSPFv2 Router Information Opaque LSA
The format of the TLVs within the body of an RI LSA is the same as The format of the TLVs within the body of an RI LSA is the same as
the format used by the Traffic Engineering Extensions to OSPF [TE]. the format used by the Traffic Engineering Extensions to OSPF [TE].
The LSA payload consists of one or more nested Type/Length/Value The LSA payload consists of one or more nested Type/Length/Value
(TLV) triplets. The format of each TLV is: (TLV) triplets. The format of each TLV is:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... | | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Format
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
the length field (so a three octet value would have a length of length field (so a three octet value would have a length of three,
three, but the total size of the TLV would be eight octets). Nested but the total size of the TLV would be eight octets). Nested TLVs
TLVs are also 32-bit aligned. For example, a one byte value would are also 32-bit aligned. For example, a one-byte value would have
have the length field set to 1, and three octets of padding would be the length field set to 1, and three octets of padding would be added
added to the end of the value portion of the TLV. Unrecognized types to the end of the value portion of the TLV. Unrecognized types are
are ignored. ignored.
2.2 OSPFv3 Router Information (RI) Opaque LSA 2.2. OSPFv3 Router Information (RI) Opaque LSA
The OSPFv3 Router Information LSA has a function code of 12 while the The OSPFv3 Router Information LSA has a function code of 12 while the
S1/S2 bit are dependent on the desired flooding scope for the LSA. S1/S2 bit are dependent on the desired flooding scope for the LSA.
The U bit will be set indicating the OSPFv3 RI LSA should be flooded The U bit will be set indicating the OSPFv3 RI LSA should be flooded
even if it is not understood. The Link State ID (LSID) value for 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 this LSA is 0. This is unambiguous since an OSPFv3 router will only
advertise a single RI LSA per flooding scope. advertise a single RI LSA per flooding scope.
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
skipping to change at page 5, line 39 skipping to change at page 6, line 4
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length | | LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+- TLVs -+ +- TLVs -+
| ... | | ... |
OSPFv3 Router Information LSA
The format of the TLVs within the body of an RI LSA as defined in The format of the TLVs within the body of an RI LSA as defined in
Section 2.1 Section 2.1
When a new Router Information LSA TLV is defined, the specification When a new Router Information LSA TLV is defined, the specification
MUST explicitly state whether the TLV is applicable to OSPFv2 only, MUST explicitly state whether the TLV is applicable to OSPFv2 only,
OSPFv3 only, or both OSPFv2 and OSPFv3. OSPFv3 only, or both OSPFv2 and OSPFv3.
2.3 OSPF Router Informational Capabilities TLV 2.3. OSPF Router Informational Capabilities TLV
The first defined TLV in the body of an RI LSA is the Router The first defined TLV in the body of an RI LSA is the Router
Informational Capabilities TLV. A router advertising an RI LSA MAY Informational Capabilities TLV. A router advertising an RI LSA MAY
include the Router Informational Capabilities TLV. If included, it include the Router Informational Capabilities TLV. If included, it
MUST be the first TLV in the LSA. Additionally, the TLV MUST MUST be the first TLV in the LSA. Additionally, the TLV MUST
accurately reflect the OSPF router's capabilities in the scope accurately reflect the OSPF router's capabilities in the scope
advertised. However, the informational capabilities advertised have advertised. However, the informational capabilities advertised have
no impact on the OSPF's operation - they are advertised purely for no impact on the OSPFs operation - they are advertised purely for
informational purposes informational purposes
The format of the Router Informational Capabilities TLV is as The format of the Router Informational Capabilities TLV is as
follows: 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Informational Capabilities | | Informational 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 octets and will be a multiple of 4 octets portion in octets and will be a multiple of 4 octets
dependent on the number of capabilities advertised. dependent on the number of capabilities advertised.
Initially, the length will be 4 denoting 4 octets of Initially, the length will be 4 denoting 4 octets of
informational capability bits. informational capability bits.
Value A variable length sequence of capability bits rounded Value A variable length sequence of capability bits rounded
to a multiple of 4 octets padded with undefined bits. to a multiple of 4 octets padded with undefined bits.
Initially, there are 4 octets of capability bits. Initially, there are 4 octets of capability bits. Bits
are numbered left-to-right starting with the most
significant bit being bit zero.
OSPF Router Informational Capabilities TLV
The Router Informational Capabilities TLV MAY be followed by optional The Router Informational Capabilities TLV MAY be followed by optional
TLVs that further specify a capability. TLVs that further specify a capability.
2.4 Assigned OSPF Router Informational Capability Bits 2.4. Assigned OSPF Router Informational Capability Bits
The following informational capability bits assigned: The following informational capability bits assigned:
Bit Capabilities Bit Capabilities
1 OSPF graceful restart capable [GRACE] 0 OSPF graceful restart capable [GRACE]
2 OSPF graceful restart helper [GRACE] 1 OSPF graceful restart helper [GRACE]
3 OSPF Stub Router support [STUB] 2 OSPF Stub Router support [STUB]
4 OSPF Traffic Engineering support [TE] 3 OSPF Traffic Engineering support [TE]
5 OSPF point-to-point over LAN [P2PLAN] 4 OSPF point-to-point over LAN [P2PLAN]
6 OSPF Experimental TE [EXPTE] 5 OSPF Experimental TE [EXPTE]
7-31 Future assignments 6-31 Future assignments
2.5 Flooding Scope of the Router Information LSA OSPF Router Informational Capabilities Bits
2.5. Flooding Scope of the Router Information LSA
The flooding scope for a Router Information LSA is determined by the The flooding scope for a Router Information LSA is determined by the
LSA type. For OSPFv2, type 9 (link-scoped), type 10 (area-scoped), LSA type. For OSPFv2, type 9 (link-scoped), type 10 (area-scoped),
or a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the or a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the
flooding scope is determined by the S1 and S2 bits in the LSA type. S1 and S2 bits in the LSA type determine flooding scope. If AS wide
If AS wide flooding scope is chosen, the originating router should flooding scope is chosen, the originating router should also
also advertise area scoped LSA(s) into any attached NSSA area(s). An advertise area scoped LSA(s) into any attached NSSA area(s). An OSPF
OSPF router MAY advertise different capabilities when both NSSA area router MAY advertise different capabilities when both NSSA area
scoped LSA(s) and an AS scoped LSA is advertised. This allows scoped LSA(s) and an AS scoped LSA are advertised. This allows
functional capabilities to be limited in scope. For example, a functional capabilities to be limited in scope. For example, a
router may be an area border router but only support traffic router may be an area border router but only support traffic
engineering (TE) in a subset of its attached areas. engineering (TE) in a subset of its attached areas.
The choice of flooding scope is made by the advertising router and is The choice of flooding scope is made by the advertising router and is
a matter of local policy. The originating router MAY advertise a matter of local policy. The originating router MAY advertise
multiple RI LSAs as long as the flooding scopes differ. TLV flooding multiple RI LSAs as long as the flooding scopes differ. TLV flooding
scope rules will be specified on a per-TLV basis and MUST be scope rules will be specified on a per-TLV basis and MUST be
specified in the accompanying specifications for new Router specified in the accompanying specifications for new Router
Information LSA TLVs. Information LSA TLVs.
skipping to change at page 10, line 19 skipping to change at page 10, line 19
1. The OSPFv2 opaque LSA type 4 will need to be reserved for the 1. The OSPFv2 opaque LSA type 4 will need to be reserved for the
OSPFv2 RI opaque LSA. OSPFv2 RI opaque LSA.
2. The OSPFv3 LSA type function code 18 will need to be reserved for 2. The OSPFv3 LSA type function code 18 will need to be reserved for
the OSPFv3 RI LSA. the OSPFv3 RI LSA.
New registries are defined for the following purposes: New registries are defined for the following purposes:
1. Registry for OSPF RI TLVs - The value of 1 for the capabilities 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 TLV is defined herein. All TLV additions are subject to review
review. by an expert designated by the IESG.
2. Registry for OSPF Router Informational Capability Bits - The 2. Registry for OSPF Router Informational Capability Bits - The
values defined in Section 2.3. All Router Informational values defined in Section 2.3. All Router Informational
Capability TLV additions are subject to OSPF WG review. Capability TLV additions are subject to review by an expert
designated by the IESG.
6. References 6. References
6.1 Normative References 6.1. Normative References
[OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370,
July 1998. 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", [OSPFV3] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999. RFC 2740, December 1999.
[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 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[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.
[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, McPherson, "OSPF Stub Router Advertisement", RFC 3137,
June 2001. June 2001.
Appendix A. Acknowledgments
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
would like to thanks Peter Psenak for his review and helpful comments
on early versions of the draft.
Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian
Farrel have been incorporated into later draft versions.
The RFC text was produced using Marshall Rose's xml2rfc tool.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
7025 Kit Creek Road 7025 Kit Creek Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Email: acee@cisco.com Email: acee@cisco.com
Naiming Shen Naiming Shen
Cisco Systems Cisco Systems
225 West Tasman Drive 225 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: naiming@cisco.com Email: naiming@cisco.com
Jean-Philippe Vasseur Jean-Philippe Vasseur
Cisco Systems Cisco Systems
skipping to change at page 13, line 5 skipping to change at page 14, line 5
Email: rahul@juniper.net Email: rahul@juniper.net
Scott Shaffer Scott Shaffer
BridgePort Networks BridgePort Networks
One Main Street, 7th Floor One Main Street, 7th Floor
Cambridge, MA 02142 Cambridge, MA 02142
USA USA
Email: sshafferl@bridgeport-networks.com Email: sshafferl@bridgeport-networks.com
Appendix A. Acknowledgments Full Copyright Statement
The idea for this work grew out of a conversation with Andrew Partan Copyright (C) The Internet Society (2006).
and we would like to thank him for his contribution. The authors
would like to thanks Peter Psenak for his review and helpful comments
on early versions of the draft.
Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian This document is subject to the rights, licenses and restrictions
Farrel have been incorporated into later draft versions. contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
The RFC text was produced using Marshall Rose's xml2rfc tool. 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.
Intellectual Property Statement Intellectual Property
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
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 14, line 29 skipping to change at page 14, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
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.
Copyright Statement
Copyright (C) The Internet Society (2005). 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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 37 change blocks. 
76 lines changed or deleted 89 lines changed or added

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