< draft-ietf-ospf-rfc4970bis-05.txt   draft-ietf-ospf-rfc4970bis-06.txt >
Network Working Group A. Lindem, Ed. Network Working Group A. Lindem, Ed.
Internet-Draft N. Shen Internet-Draft N. Shen
Obsoletes: 4970 (if approved) J. Vasseur Obsoletes: 4970 (if approved) J. Vasseur
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: March 28, 2016 R. Aggarwal Expires: April 10, 2016 R. Aggarwal
Arktan Arktan
S. Shaffer S. Shaffer
Akamai Akamai
September 25, 2015 October 8, 2015
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-rfc4970bis-05.txt draft-ietf-ospf-rfc4970bis-06.txt
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 document proposes extensions to OSPFv2 and routing domain. This document proposes extensions to OSPFv2 and
OSPFv3 for advertising optional router capabilities. The Router OSPFv3 for advertising optional router capabilities. The Router
Information (RI) Link State Advertisement (LSA) is defined for this Information (RI) Link State Advertisement (LSA) is defined for this
purpose. In OSPFv2, the RI LSA will be implemented with an opaque purpose. In OSPFv2, the RI LSA will be implemented with an opaque
LSA type ID. In OSPFv3, the RI LSA will be implemented with a unique LSA type ID. In OSPFv3, the RI LSA will be implemented with a unique
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on March 28, 2016. This Internet-Draft will expire on April 10, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 3
1.2. Summary of Changes from RFC 4970 . . . . . . . . . . . . 3 1.2. Summary of Changes from RFC 4970 . . . . . . . . . . . . 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 . . . . . . . . 6 2.2. OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 4
2.3. OSPF Router Informational Capabilities TLV . . . . . . . 6 2.3. OSPF Router Information LSA TLV Format . . . . . . . . . 5
2.4. Assigned OSPF Router Informational Capability Bits . . . 7 2.4. OSPF Router Informational Capabilities TLV . . . . . . . 6
2.5. OSPF Router Functional Capabilities TLV . . . . . . . . . 8 2.5. Assigned OSPF Router Informational Capability Bits . . . 7
2.6. Flooding Scope of the Router Information LSA . . . . . . 9 2.6. OSPF Router Functional Capabilities TLV . . . . . . . . . 8
3. Backward Compatibility . . . . . . . . . . . . . . . . . . . 10 2.7. Flooding Scope of the Router Information LSA . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 3. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. OSPFv2 Opaque LSA Type Assignment . . . . . . . . . . . . 10 5.1. OSPFv2 Opaque LSA Type Assignment . . . . . . . . . . . . 10
5.2. OSPFv3 LSA Function Code Assignment . . . . . . . . . . . 10 5.2. OSPFv3 LSA Function Code Assignment . . . . . . . . . . . 10
5.3. OSPF RI LSA TLV Type Assignment . . . . . . . . . . . . . 12 5.3. OSPF RI LSA TLV Type Assignment . . . . . . . . . . . . . 11
5.4. Registry for OSPF RI Informational Capability Bits . . . 13 5.4. Registry for OSPF RI Informational Capability Bits . . . 12
5.5. Registry for OSPF RI Functional Capability Bits . . . . . 13 5.5. Registry for OSPF RI Functional Capability Bits . . . . . 13
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References . . . . . . . . . . . . . . . . . . 13 6.1. Normative References . . . . . . . . . . . . . . . . . . 13
6.2. Informative References . . . . . . . . . . . . . . . . . 14 6.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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.
OSPF uses the options field in LSAs and hello packets to advertise OSPF uses the options field in LSAs and hello packets to advertise
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 so additional optional capabilities this field have been allocated so additional optional capabilities
cannot be advertised. This document describes extensions to OSPF to cannot be advertised. This document describes extensions to OSPF to
advertise these optional capabilities via opaque LSAs in OSPFv2 and advertise these optional capabilities via opaque LSAs in OSPFv2 and
LSAs with a unique type in OSPFv3. For existing OSPF capabilities, LSAs with a unique type in OSPFv3. For existing OSPF capabilities,
skipping to change at page 3, line 42 skipping to change at page 3, line 44
1. The main change is that an OSPF router will be able to advertise 1. The main change is that an OSPF router will be able to advertise
multiple instances of the OSPF Router Information LSA. This multiple instances of the OSPF Router Information LSA. This
change permeates through much of the document change permeates through much of the document
2. Additionally, Section 2.5 includes an additional TLV for 2. Additionally, Section 2.5 includes an additional TLV for
functional capabilities. This is in contrast to the existing TLV functional capabilities. This is in contrast to the existing TLV
which is used to advertise capabilities for informational which is used to advertise capabilities for informational
purposes only. purposes only.
3. The IANA allocation policy for the OSPFv3 LSA Function Code 3. The IANA allocation policy for the OSPFv3 LSA Function Code
registry and all the OSPF Router Information IANA registeries has registry and all the OSPF Router Information IANA registries has
been changed from "Standards Action" to "IETF Review" been changed from "Standards Action" to "IETF Review"
[IANA-GUIDE]. [IANA-GUIDE].
4. Finally, references have been updated for drafts that have become 4. Finally, references have been updated for drafts that have become
RFCs and RFCs that have been obsoleted since the publication of RFCs and RFCs that have been obsoleted since the publication of
RFC 4970. RFC 4970.
2. OSPF Router Information (RI) LSA 2. OSPF Router Information (RI) LSA
OSPFv2 routers will advertise a link scoped, area-scoped, or AS- OSPFv2 routers will advertise a link scoped, area-scoped, or AS-
skipping to change at page 4, line 41 skipping to change at page 4, line 41
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | length | | LS checksum | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+- TLVs -+ +- TLVs -+
| ... | | ... |
OSPFv2 Router Information Opaque LSA 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 as defined in
the format used by the Traffic Engineering Extensions to OSPF [TE]. Section 2.3
The LSA payload consists of one or more nested Type/Length/Value
(TLV) triplets. The format of each TLV is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Format
The Length field defines the length of the value portion in octets
(thus a TLV with no value portion would have a length of 0). The TLV
is padded to 4-octet alignment; padding is not included in the length
field (so a 3-octet value would have a length of 3, but the total
size of the TLV would be 8 octets). Nested TLVs are also 32-bit
aligned. For example, a 1-byte value would have the length field set
to 1, and 3 octets of padding would be added to the end of the value
portion of the TLV. The padding is composed of zeros. Unrecognized
types are 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 bits are dependent on the desired flooding scope for the LSA. S1/S2 bits are dependent on the desired flooding scope for the LSA.
The U bit will be set indicating that the OSPFv3 RI LSA should be The U bit will be set indicating that the OSPFv3 RI LSA should be
flooded even if it is not understood. The Link State ID (LSID) value flooded even if it is not understood. The Link State ID (LSID) value
for this LSA is the instance ID. The first instance ID, i.e., 0, for this LSA is the instance ID. The first instance ID, i.e., 0,
SHOULD always contain the Router Informational Capabilities TLV and, SHOULD always contain the Router Informational Capabilities TLV and,
if advertised, the Router Functional Capabilities TLV. OSPFv3 Router if advertised, the Router Functional Capabilities TLV. OSPFv3 Router
skipping to change at page 6, line 38 skipping to change at page 5, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length | | LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+- TLVs -+ +- TLVs -+
| ... | | ... |
OSPFv3 Router Information LSA OSPFv3 Router Information LSA
The format of the TLVs within the body of an RI LSA is as defined in The format of the TLVs within the body of an RI LSA is as defined in
Section 2.1 Section 2.3
2.3. OSPF Router Information LSA TLV Format
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 LSA payload consists of one or more nested Type/Length/Value
(TLV) triplets. The format of each TLV is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Format
The Length field defines the length of the value portion in octets
(thus a TLV with no value portion would have a length of 0). The TLV
is padded to 4-octet alignment; padding is not included in the length
field (so a 3-octet value would have a length of 3, but the total
size of the TLV would be 8 octets). Nested TLVs are also 32-bit
aligned. For example, a 1-byte value would have the length field set
to 1, and 3 octets of padding would be added to the end of the value
portion of the TLV. The padding is composed of undefined bits.
Unrecognized types are ignored.
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.4. OSPF Router Informational Capabilities TLV
An OSPF router advertising an OSPF RI LSA MAY include the Router An OSPF router advertising an OSPF RI LSA MAY include the Router
Informational Capabilities TLV. If included, it MUST be the first Informational Capabilities TLV. If included, it MUST be the first
TLV in the first instance, i.e., instance 0, of the OSPF RI LSA. TLV in the first instance, i.e., instance 0, of the OSPF RI LSA.
Additionally, the TLV MUST accurately reflect the OSPF router's Additionally, the TLV MUST accurately reflect the OSPF router's
capabilities in the scope advertised. However, the informational capabilities in the scope advertised. However, the informational
capabilities advertised have no impact on the OSPF's operation, they capabilities advertised have no impact on the OSPF's operation, they
are advertised purely for informational purposes. are advertised purely for informational purposes.
The format of the Router Informational Capabilities TLV is as The format of the Router Informational Capabilities TLV is as
skipping to change at page 7, line 37 skipping to change at page 7, line 32
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. Bits Initially, there are 4 octets of capability bits. Bits
are numbered left-to-right starting with the most are numbered left-to-right starting with the most
significant bit being bit 0. significant bit being bit 0.
OSPF Router Informational Capabilities TLV 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.5. Assigned OSPF Router Informational Capability Bits
The following informational capability bits are assigned: The following informational capability bits are assigned:
Bit Capabilities Bit Capabilities
0 OSPF graceful restart capable [GRACE] 0 OSPF graceful restart capable [GRACE]
1 OSPF graceful restart helper [GRACE] 1 OSPF graceful restart helper [GRACE]
2 OSPF Stub Router support [STUB] 2 OSPF Stub Router support [STUB]
3 OSPF Traffic Engineering support [TE] 3 OSPF Traffic Engineering support [TE]
4 OSPF point-to-point over LAN [P2PLAN] 4 OSPF point-to-point over LAN [P2PLAN]
5 OSPF Experimental TE [EXP-TE] 5 OSPF Experimental TE [EXP-TE]
6-31 Unassigned (IETF Review) 6-31 Unassigned (IETF Review)
OSPF Router Informational Capabilities Bits OSPF Router Informational Capabilities Bits
References for [GRACE], [STUB], [TE], [P2PLAN], and [EXP-TE] are References for [GRACE], [STUB], [TE], [P2PLAN], and [EXP-TE] are
included herein. included herein.
2.5. OSPF Router Functional Capabilities TLV 2.6. OSPF Router Functional Capabilities TLV
This specification also defines the Router Functional Capabilities This specification also defines the Router Functional Capabilities
TLV for advertisement within the OSPF Router Information LSA. An TLV for advertisement within the OSPF Router Information LSA. An
OSPF router advertising an OSPF RI LSA MAY include the Router OSPF router advertising an OSPF RI LSA MAY include the Router
Functional Capabilities TLV. If included, it MUST be the included in Functional Capabilities TLV. If included, it MUST be the included in
the first instance of the LSA. Additionally, the TLV MUST be used to the first instance of the LSA. Additionally, the TLV MUST be used to
reflect OSPF router functional capabilities. If the TLV is not reflect OSPF router functional capabilities. If the TLV is not
included or the length doesn't include the assigned OSPF functional included or the length doesn't include the assigned OSPF functional
capability bit, the corresponding OSPF functional capability is capability bit, the corresponding OSPF functional capability is
implicitly advertised as not being supported by the advertising OSPF implicitly advertised as not being supported by the advertising OSPF
skipping to change at page 9, line 37 skipping to change at page 9, line 5
OSPF Router Functional Capabilities TLV OSPF Router Functional Capabilities TLV
The Router Functional Capabilities TLV MAY be followed by optional The Router Functional Capabilities TLV MAY be followed by optional
TLVs that further specify a capability. In contrast to the Router TLVs that further specify a capability. In contrast to the Router
Informational Capabilities TLV, the OSPF extensions advertised in Informational Capabilities TLV, the OSPF extensions advertised in
this TLV MAY be used by other OSPF routers to dictate protocol this TLV MAY be used by other OSPF routers to dictate protocol
operation. The specifications for functional capabilities advertised operation. The specifications for functional capabilities advertised
in this TLV MUST describe protocol behavior and address backward in this TLV MUST describe protocol behavior and address backward
compatibility. compatibility.
2.6. Flooding Scope of the Router Information LSA 2.7. 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
S1 and S2 bits in the LSA type determine the flooding scope. If AS- S1 and S2 bits in the LSA type determine the flooding scope. If AS-
wide flooding scope is chosen, the originating router should also wide flooding scope is chosen, the originating router should also
advertise area-scoped LSA(s) into any attached Not-So-Stubby Area advertise area-scoped LSA(s) into any attached Not-So-Stubby Area
(NSSA) area(s). An OSPF router MAY advertise different capabilities (NSSA) area(s). An OSPF router MAY advertise different capabilities
when both NSSA area scoped LSA(s) and an AS-scoped LSA are when both NSSA area scoped LSA(s) and an AS-scoped LSA are
advertised. This allows functional capabilities to be limited in advertised. This allows functional capabilities to be limited in
skipping to change at page 11, line 42 skipping to change at page 11, line 12
o OSPFv3 LSA function codes in the range 16-255 are to be assigned o OSPFv3 LSA function codes in the range 16-255 are to be assigned
subject to IETF Review. New values are assigned only through RFCs subject to IETF Review. New values are assigned only through RFCs
that have been shepherded through the IESG as AD- Sponsored or that have been shepherded through the IESG as AD- Sponsored or
IETF WG Documents [IANA-GUIDE]. IETF WG Documents [IANA-GUIDE].
o OSPFv3 LSA function codes in the range 8176-8181 are for o OSPFv3 LSA function codes in the range 8176-8181 are for
experimental use; these will not be registered with IANA and MUST experimental use; these will not be registered with IANA and MUST
NOT be mentioned by RFCs. NOT be mentioned by RFCs.
o OSPFv3 LSAs with an LSA Function Code in the Vendor Private Use o OSPFv3 LSAs with an LSA Function Code in the Vendor Private Use
range 8184-8191 MUST include the Vendor Enterprise Code as the range 8184-8191 MUST include the Enterprise Code [ENTERPRISE-CODE]
first 4 octets following the 20 octets of LSA header. as the first 4 octets following the 20 octets of LSA header.
o If a new LSA Function Code is documented, the documentation MUST o If a new LSA Function Code is documented, the documentation MUST
include the valid combinations of the U, S2, and S1 bits for the include the valid combinations of the U, S2, and S1 bits for the
LSA. It SHOULD also describe how the Link State ID is to be LSA. It SHOULD also describe how the Link State ID is to be
assigned. assigned.
5.3. OSPF RI LSA TLV Type Assignment 5.3. OSPF RI LSA TLV Type Assignment
[RFC4970] created the registry for OSPF Router Information (RI) TLVs. [RFC4970] created the registry for OSPF Router Information (RI) TLVs.
IANA is requested to update the reference for this registry to point IANA is requested to update the reference for this registry to point
skipping to change at page 13, line 21 skipping to change at page 13, line 7
o This registry is now comprised of the fields Bit Number, o This registry is now comprised of the fields Bit Number,
Capability Name, and Document Reference. Capability Name, and Document Reference.
o The values are defined in Section 2.4. All Router Informational o The values are defined in Section 2.4. All Router Informational
Capability TLV additions are to be assigned through IETF Review Capability TLV additions are to be assigned through IETF Review
[IANA-GUIDE]. [IANA-GUIDE].
5.5. Registry for OSPF RI Functional Capability Bits 5.5. Registry for OSPF RI Functional Capability Bits
IANA ia asked to create a registry for OSPF Router Functional IANA is asked to create a registry for OSPF Router Functional
Capability Bits within the Open Shortest Path First v2 (OSPFv2) Capability Bits within the Open Shortest Path First v2 (OSPFv2)
Parameters Group. This registry will be comprised of the fields Bit Parameters Group. This registry will be comprised of the fields Bit
Number, Capability Name, and Document Reference. Initially, the sub- Number, Capability Name, and Document Reference. Initially, the sub-
registry will be empty but will be available for future capabilities. registry will be empty but will be available for future capabilities.
All Router Functional Capability TLV additions are to be assigned All Router Functional Capability TLV additions are to be assigned
through IETF Review [IANA-GUIDE]. through IETF Review [IANA-GUIDE].
6. References 6. References
6.1. Normative References 6.1. Normative References
skipping to change at page 14, line 7 skipping to change at page 13, line 40
[RFC4970] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. [RFC4970] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S.
Shaffer, "Extensions to OSPF for Advertising Optional Shaffer, "Extensions to OSPF for Advertising Optional
Router Capabilities", RFC 4970, July 2007. Router Capabilities", RFC 4970, July 2007.
[TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
6.2. Informative References 6.2. Informative References
[ENTERPRISE-CODE]
Eronen, P. and D. Harrington, "Enterprise Number for
Documentation Use", RFC 5612, August 2009.
[EXP-TE] Srisuresh, P. and P. Joseph, "OSPF-xTE: Experimental [EXP-TE] Srisuresh, P. and P. Joseph, "OSPF-xTE: Experimental
Extension to OSPF for Traffic Engineering", RFC 4973, July Extension to OSPF for Traffic Engineering", RFC 4973, July
2007. 2007.
[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.
[IANA-GUIDE] [IANA-GUIDE]
Narten, T. and H. Alvestrand, "Guidelines for Writing an Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, May 2008. IANA Considerations Section in RFCs", RFC 5226, May 2008.
skipping to change at page 14, line 40 skipping to change at page 14, line 31
on early versions of the document. on early versions of the document.
Special thanks to Tom Petch for providing the updated IANA text in Special thanks to Tom Petch for providing the updated IANA text in
the BIS version of the document. the BIS version of the document.
Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian
Farrel have been incorporated into later versions. Farrel have been incorporated into later versions.
Thanks to Yingzhen Qu for acting as document shepherd. Thanks to Yingzhen Qu for acting as document shepherd.
Thanks to Chris Bowers, Alia Atlas, and Shraddha Hegde for review of Thanks to Chris Bowers, Alia Atlas, Shraddha Hegde, and Dan Romascanu
the BIS version of this document. for review of the BIS version of this document.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
Authors' Addresses Authors' Addresses
Acee Lindem (editor) Acee Lindem (editor)
Cisco Systems Cisco Systems
301 Midenhall Way 301 Midenhall Way
Cary, NC 27513 Cary, NC 27513
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
 End of changes. 21 change blocks. 
50 lines changed or deleted 61 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/