idnits 2.17.1 draft-ietf-ospf-rfc4970bis-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 24, 2015) is 3136 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4970 (Obsoleted by RFC 7770) -- Obsolete informational reference (is this intentional?): RFC 5226 (ref. 'IANA-GUIDE') (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Lindem, Ed. 3 Internet-Draft N. Shen 4 Obsoletes: 4970 (if approved) J. Vasseur 5 Intended status: Standards Track Cisco Systems 6 Expires: March 27, 2016 R. Aggarwal 7 Arktan 8 S. Shaffer 9 Akamai 10 September 24, 2015 12 Extensions to OSPF for Advertising Optional Router Capabilities 13 draft-ietf-ospf-rfc4970bis-04.txt 15 Abstract 17 It is useful for routers in an OSPFv2 or OSPFv3 routing domain to 18 know the capabilities of their neighbors and other routers in the 19 routing domain. This document proposes extensions to OSPFv2 and 20 OSPFv3 for advertising optional router capabilities. The Router 21 Information (RI) Link State Advertisement (LSA) is defined for this 22 purpose. In OSPFv2, the RI LSA will be implemented with an opaque 23 LSA type ID. In OSPFv3, the RI LSA will be implemented with a unique 24 LSA type function code. In both protocols, the RI LSA can be 25 advertised at any of the defined flooding scopes (link, area, or 26 autonomous system (AS)). This document obsoletes RFC 4970 by 27 providing a revised specification including support for advertisement 28 of multiple instances of the RI LSA and a TLV for functional 29 capabilities. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on March 27, 2016. 48 Copyright Notice 50 Copyright (c) 2015 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 3 67 1.2. Summary of Changes from RFC 4970 . . . . . . . . . . . . 3 68 2. OSPF Router Information (RI) LSA . . . . . . . . . . . . . . 3 69 2.1. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . 4 70 2.2. OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 6 71 2.3. OSPF Router Informational Capabilities TLV . . . . . . . 6 72 2.4. Assigned OSPF Router Informational Capability Bits . . . 7 73 2.5. OSPF Router Functional Capabilities TLV . . . . . . . . . 8 74 2.6. Flooding Scope of the Router Information LSA . . . . . . 9 75 3. Backward Compatibility . . . . . . . . . . . . . . . . . . . 10 76 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 77 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 78 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 79 6.1. Normative References . . . . . . . . . . . . . . . . . . 13 80 6.2. Informative References . . . . . . . . . . . . . . . . . 13 81 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 84 1. Introduction 86 It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] 87 routing domain to know the capabilities of their neighbors and other 88 routers in the routing domain. This can be useful for both the 89 advertisement and discovery of OSPFv2 and OSPFv3 capabilities. 90 Throughout this document, OSPF will be used when the specification is 91 applicable to both OSPFv2 and OSPFv3. Similarly, OSPFv2 or OSPFv3 92 will be used when the text is protocol specific. 94 OSPF uses the options field in LSAs and hello packets to advertise 95 optional router capabilities. In the case of OSPFv2, all the bits in 96 this field have been allocated so additional optional capabilities 97 cannot be advertised. This document describes extensions to OSPF to 98 advertise these optional capabilities via opaque LSAs in OSPFv2 and 99 LSAs with a unique type in OSPFv3. For existing OSPF capabilities, 100 backward-compatibility issues dictate that this advertisement is used 101 primarily for informational purposes. For future OSPF extensions, 102 this advertisement MAY be used as the sole mechanism for 103 advertisement and discovery. 105 This document obsoletes RFC 4970 by providing a revised specification 106 including support for advertisement of multiple instances of the RI 107 LSA and a TLV for functional capabilities. 109 1.1. Requirements Notation 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in [RFC-KEYWORDS]. 115 1.2. Summary of Changes from RFC 4970 117 This document includes the following changes from RFC 4970 [RFC4970]: 119 1. The main change is that an OSPF router will be able to advertise 120 multiple instances of the OSPF Router Information LSA. This 121 change permeates through much of the document 123 2. Additionally, Section 2.5 includes an additional TLV for 124 functional capabilities. This is in contrast to the existing TLV 125 which is used to advertise capabilities for informational 126 purposes only. 128 3. The IANA allocation policy for the OSPFv3 LSA Function Code 129 registry and all the OSPF Router Information IANA registeries has 130 been changed from "Standards Action" to "IETF Review" 131 [IANA-GUIDE]. 133 4. Finally, references have been updated for drafts that have become 134 RFCs and RFCs that have been obsoleted since the publication of 135 RFC 4970. 137 2. OSPF Router Information (RI) LSA 139 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 140 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information (RI) LSA 141 has an Opaque type of 4 and the Opaque ID is the RI LSA instance ID. 142 The first Opaque ID, i.e., 0, SHOULD always contain the Router 143 Informational Capabilities TLV and, if advertised, the Router 144 Functional Capabilities TLV. RI LSAs subsequence to the first can be 145 used for information that doesn't fit in the first instance. 147 2.1. OSPFv2 Router Information (RI) Opaque LSA 149 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 150 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has an 151 Opaque type of 4 and Opaque ID specifies the LSA instance ID with the 152 first instance always having an Instance ID of 0. 154 0 1 2 3 155 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 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | LS age | Options | 9, 10, or 11 | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | 4 | Opaque ID (Instance ID) | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+d-+-+-+-+-+-+-+-+-+-+-+ 161 | Advertising Router | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | LS sequence number | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | LS checksum | length | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | | 168 +- TLVs -+ 169 | ... | 171 OSPFv2 Router Information Opaque LSA 173 The format of the TLVs within the body of an RI LSA is the same as 174 the format used by the Traffic Engineering Extensions to OSPF [TE]. 175 The LSA payload consists of one or more nested Type/Length/Value 176 (TLV) triplets. The format of each TLV is: 178 0 1 2 3 179 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 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Type | Length | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Value... | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 TLV Format 188 The Length field defines the length of the value portion in octets 189 (thus a TLV with no value portion would have a length of 0). The TLV 190 is padded to 4-octet alignment; padding is not included in the length 191 field (so a 3-octet value would have a length of 3, but the total 192 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 193 aligned. For example, a 1-byte value would have the length field set 194 to 1, and 3 octets of padding would be added to the end of the value 195 portion of the TLV. The padding is composed of zeros. Unrecognized 196 types are ignored. 198 2.2. OSPFv3 Router Information (RI) Opaque LSA 200 The OSPFv3 Router Information LSA has a function code of 12 while the 201 S1/S2 bits are dependent on the desired flooding scope for the LSA. 202 The U bit will be set indicating that the OSPFv3 RI LSA should be 203 flooded even if it is not understood. The Link State ID (LSID) value 204 for this LSA is the instance ID. The first instance ID, i.e., 0, 205 SHOULD always contain the Router Informational Capabilities TLV and, 206 if advertised, the Router Functional Capabilities TLV. OSPFv3 Router 207 Information LSAs subsequence to the first can be used for information 208 that doesn't fit in the first instance. OSPFv3 routers MAY advertise 209 multiple RI LSAs per flooding scope. 211 0 1 2 3 212 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 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | LS age |1|S12| 12 | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | Link State ID (Instance ID) | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | Advertising Router | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | LS sequence number | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | LS checksum | Length | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | | 225 +- TLVs -+ 226 | ... | 228 OSPFv3 Router Information LSA 230 The format of the TLVs within the body of an RI LSA is as defined in 231 Section 2.1 233 When a new Router Information LSA TLV is defined, the specification 234 MUST explicitly state whether the TLV is applicable to OSPFv2 only, 235 OSPFv3 only, or both OSPFv2 and OSPFv3. 237 2.3. OSPF Router Informational Capabilities TLV 239 An OSPF router advertising an OSPF RI LSA MAY include the Router 240 Informational Capabilities TLV. If included, it MUST be the first 241 TLV in the first instance, i.e., instance 0, of the OSPF RI LSA. 242 Additionally, the TLV MUST accurately reflect the OSPF router's 243 capabilities in the scope advertised. However, the informational 244 capabilities advertised have no impact on the OSPF's operation, they 245 are advertised purely for informational purposes. 247 The format of the Router Informational Capabilities TLV is as 248 follows: 250 0 1 2 3 251 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 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | Type | Length | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | Informational Capabilities | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 Type A 16-bit field set to 1. 260 Length A 16-bit field that indicates the length of the value 261 portion in octets and will be a multiple of 4 octets 262 dependent on the number of capabilities advertised. 263 Initially, the length will be 4, denoting 4 octets of 264 informational capability bits. 266 Value A variable length sequence of capability bits rounded 267 to a multiple of 4 octets padded with undefined bits. 268 Initially, there are 4 octets of capability bits. Bits 269 are numbered left-to-right starting with the most 270 significant bit being bit 0. 272 OSPF Router Informational Capabilities TLV 274 The Router Informational Capabilities TLV MAY be followed by optional 275 TLVs that further specify a capability. 277 2.4. Assigned OSPF Router Informational Capability Bits 279 The following informational capability bits are assigned: 281 Bit Capabilities 283 0 OSPF graceful restart capable [GRACE] 284 1 OSPF graceful restart helper [GRACE] 285 2 OSPF Stub Router support [STUB] 286 3 OSPF Traffic Engineering support [TE] 287 4 OSPF point-to-point over LAN [P2PLAN] 288 5 OSPF Experimental TE [EXP-TE] 289 6-31 Unassigned (IETF Review) 291 OSPF Router Informational Capabilities Bits 293 References for [GRACE], [STUB], [TE], [P2PLAN], and [EXP-TE] are 294 included herein. 296 2.5. OSPF Router Functional Capabilities TLV 298 This specification also defines the Router Functional Capabilities 299 TLV for advertisement within the OSPF Router Information LSA. An 300 OSPF router advertising an OSPF RI LSA MAY include the Router 301 Functional Capabilities TLV. If included, it MUST be the included in 302 the first instance of the LSA. Additionally, the TLV MUST be used to 303 reflect OSPF router functional capabilities. If the TLV is not 304 included or the length doesn't include the assigned OSPF functional 305 capability bit, the corresponding OSPF functional capability is 306 implicitly advertised as not being supported by the advertising OSPF 307 router. 309 The format of the Router Functional Capabilities TLV is as follows: 311 0 1 2 3 312 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 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | Type | Length | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | Functional Capabilities | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 Type A 16-bit field set to IANA TBD (Suggested value 2). 321 Length A 16-bit field that indicates the length of the value 322 portion in octets and will be a multiple of 4 octets 323 dependent on the number of capabilities advertised. 324 Initially, the length will be 4, denoting 4 octets of 325 informational capability bits. 327 Value A variable length sequence of capability bits rounded 328 to a multiple of 4 octets padded with undefined bits. 329 Initially, there are 4 octets of capability bits. Bits 330 are numbered left-to-right starting with the most 331 significant bit being bit 0. 333 OSPF Router Functional Capabilities TLV 335 The Router Functional Capabilities TLV MAY be followed by optional 336 TLVs that further specify a capability. In contrast to the Router 337 Informational Capabilities TLV, the OSPF extensions advertised in 338 this TLV MAY be used by other OSPF routers to dictate protocol 339 operation. The specifications for functional capabilities advertised 340 in this TLV MUST describe protocol behavior and address backward 341 compatibility. 343 2.6. Flooding Scope of the Router Information LSA 345 The flooding scope for a Router Information LSA is determined by the 346 LSA type. For OSPFv2, type 9 (link-scoped), type 10 (area-scoped), 347 or a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the 348 S1 and S2 bits in the LSA type determine the flooding scope. If AS- 349 wide flooding scope is chosen, the originating router should also 350 advertise area-scoped LSA(s) into any attached Not-So-Stubby Area 351 (NSSA) area(s). An OSPF router MAY advertise different capabilities 352 when both NSSA area scoped LSA(s) and an AS-scoped LSA are 353 advertised. This allows functional capabilities to be limited in 354 scope. For example, a router may be an area border router but only 355 support traffic engineering (TE) in a subset of its attached areas. 357 The choice of flooding scope is made by the advertising router and is 358 a matter of local policy. The originating router MAY advertise 359 multiple RI LSAs with the same instance ID as long as the flooding 360 scopes differ. TLV flooding scope rules will be specified on a per- 361 TLV basis and MUST be specified in the accompanying specifications 362 for future Router Information LSA TLVs. 364 3. Backward Compatibility 366 For backward compatibility, previously advertised Router Information 367 TLVs SHOULD continue to be advertised in the first instance, i.e., 0, 368 of the Router Information LSA. If a Router Information TLV is 369 advertised in multiple Router Information LSA instances and the 370 multiple instance processing is not explicitly specified in the RFC 371 defining that Router Information TLV, the Router Instance TLV in the 372 Router Information LSA with the numerically smallest Instance ID will 373 be used and subsequent instances will be ignored. 375 4. Security Considerations 377 This document describes both a generic mechanism for advertising 378 router capabilities and a TLV for advertising informational and 379 functional capability bits. The capability TLVs are less critical 380 than the topology information currently advertised by the base OSPF 381 protocol. The security considerations for the generic mechanism are 382 dependent on the future application and, as such, should be described 383 as additional capabilities are proposed for advertisement. Security 384 considerations for the base OSPF protocol are covered in [OSPF] and 385 [OSPFV3]. 387 5. IANA Considerations 389 The following IANA assignment was made from an existing registry: 391 The OSPFv2 opaque LSA type 4 has been reserved for the OSPFv2 RI 392 opaque LSA. 394 The following registries have been defined for the following 395 purposes: 397 1. Registry for OSPFv3 LSA Function Codes - This top-level registry 398 will be comprised of the fields Value, LSA function code name, 399 and Document Reference. The OSPFv3 LSA function code is defined 400 in section A.4.2.1 of [OSPFV3]. The OSPFv3 LSA function code 12 401 has been reserved for the OSPFv3 Router Information (RI) LSA. 403 +-----------+-------------------------------------+ 404 | Range | Assignment Policy | 405 +-----------+-------------------------------------+ 406 | 0 | Reserved (not to be assigned) | 407 | | | 408 | 1-11 | Already assigned | 409 | | | 410 | 12 | OSPFv3 RI LSA (Assigned herein) | 411 | | | 412 | 13-15 | Already assigned | 413 | | | 414 | 16-255 | Unassigned (IETF Review) | 415 | | | 416 | 256-8175 | Reserved (No assignments) | 417 | | | 418 | 8176-8183 | Experimentation (No assignments) | 419 | | | 420 | 8184-8190 | Vendor Private Use (No assignments) | 421 | | | 422 | 8191 | Reserved (not to be assigned) | 423 +-----------+-------------------------------------+ 425 OSPFv3 LSA Function Codes 427 * OSPFv3 LSA function codes in the range 16-255 are not be 428 assigned subject to IETF Review. New values are assigned only 429 through RFCs that have been shepherded through the IESG as AD- 430 Sponsored or IETF WG Documents [IANA-GUIDE]. 432 * OSPFv3 LSA function codes in the range 8176-8181 are for 433 experimental use; these will not be registered with IANA and 434 MUST NOT be mentioned by RFCs. 436 * OSPFv3 LSAs with an LSA Function Code in the Vendor Private 437 Use range 8184-8190 MUST include the Vendor Enterprise Code as 438 the first 4 octets following the 20 octets of LSA header. 440 * If a new LSA Function Code is documented, the documentation 441 MUST include the valid combinations of the U, S2, and S1 bits 442 for the LSA. It SHOULD also describe how the Link State ID is 443 to be assigned. 445 Changes to the OSPFv3 LSA Function Code registry from RFC 4970 446 include changing the allocation policy for the range 16-255 from 447 "Standard Action" to "IETF Review" and reservation of the 448 maxiumum value (8191). 450 2. Registry for OSPF RI TLVs - This top-level registry will be 451 comprised of the fields Value, TLV Name, and Document Reference. 452 The value of 1 for the informational capabilities TLV is defined 453 herein. The value IANA TBD (suggested value 2) for the Router 454 Functional Capabilities TLV is also defined herein. 456 +-------------+-----------------------------------+ 457 | Range | Assignment Policy | 458 +-------------+-----------------------------------+ 459 | 0 | Reserved (not to be assigned) | 460 | | | 461 | 1 | Informational Capabilities | 462 | | | 463 | 2 | Unassigned (IETF Review) | 464 | | | 465 | TBD | Functional Capabilities | 466 | | | 467 | 3-9 | Already Assigned | 468 | | | 469 | 10-32767 | Unassigned (IETF Review) | 470 | | | 471 | 32768-32777 | Experimentation (No assignments) | 472 | | | 473 | 32778-65535 | Reserved (Not to be assigned) | 474 +-----------+-------------------------------------+ 476 OSPF RI TLVs 478 * Types in the range 2, 10-32767 are to be assigned subject to 479 IETF Review. New values are assigned only through RFCs that 480 have been shepherded through the IESG as AD-Sponsored or IETF 481 WG Documents [IANA-GUIDE]. 483 * Types in the range 32778-65535 are reserved and are not to be 484 assigned at this time. Before any assignments can be made in 485 this range, there MUST be a Standards Track RFC that specifies 486 IANA Considerations that covers the range being assigned. 488 The only change to OSPF RI TLV registry from RFC 4970 is a change 489 to the allocation policy for the range 10-32767 from "Standard 490 Action" to "IETF Review". 492 3. Registry for OSPF Router Informational Capability Bits - This 493 sub-registry of the OSPF RI TLV registry will be comprised of the 494 fields Bit Number, Capability Name, and Document Reference. The 495 values are defined in Section 2.4. All Router Informational 496 Capability TLV additions are to be assigned through IETF Review. 498 This is changed from RFC 4970 where the allocation policy was 499 Standards Action. 501 4. Registry for OSPF Router Functional Capability Bits - This sub- 502 registry of the OSPF RI TLV registry will be comprised of the 503 fields Bit Number, Capability Name, and Document Reference. 504 Initially, the sub-registry will be empty but will be available 505 for future capabilities. All Router Functional Capability TLV 506 additions are to be assigned through IETF Review. This is 507 registery is added since RFC 4970 and will be added to the "OSPF 508 Shortest Path First v2 (OSPFv2) Parameters" group. 510 6. References 512 6.1. Normative References 514 [OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 515 OSPF Opaque LSA Option", RFC 5250, July 2008. 517 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 519 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 520 for IPv6", RFC 5340, July 2008. 522 [RFC-KEYWORDS] 523 Bradner, S., "Key words for use in RFC's to Indicate 524 Requirement Levels", BCP 14, RFC 2119, March 1997. 526 [RFC4970] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 527 Shaffer, "Extensions to OSPF for Advertising Optional 528 Router Capabilities", RFC 4970, July 2007. 530 [TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 531 Extensions to OSPF", RFC 3630, September 2003. 533 6.2. Informative References 535 [EXP-TE] Srisuresh, P. and P. Joseph, "OSPF-xTE: Experimental 536 Extension to OSPF for Traffic Engineering", RFC 4973, July 537 2007. 539 [GRACE] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF 540 Restart", RFC 3623, November 2003. 542 [IANA-GUIDE] 543 Narten, T. and H. Alvestrand, "Guidelines for Writing an 544 IANA Considerations Section in RFCs", RFC 5226, May 2008. 546 [P2PLAN] Shen, N. and A. Zinin, "Point-to-point operation over LAN 547 in link-state routing protocols", RFC 5309, October 2008. 549 [STUB] Retana, A., Nguyen, L., White, R., Zinin, A., and D. 550 McPherson, "OSPF Stub Router Advertisement", RFC 6987, 551 September 2013. 553 Appendix A. Acknowledgments 555 The idea for this work grew out of a conversation with Andrew Partan 556 and we would like to thank him for his contribution. The authors 557 would like to thanks Peter Psenak for his review and helpful comments 558 on early versions of the document. 560 Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian 561 Farrel have been incorporated into later versions. 563 Thanks to Yingzhen Qu for acting as document shepherd. 565 Thanks to Chris Bowers, Alia Atlas, Shraddha Hegde, and Tom Petch for 566 review of the BIS version of this document. 568 The RFC text was produced using Marshall Rose's xml2rfc tool. 570 Authors' Addresses 572 Acee Lindem (editor) 573 Cisco Systems 574 301 Midenhall Way 575 Cary, NC 27513 576 USA 578 Email: acee@cisco.com 580 Naiming Shen 581 Cisco Systems 582 225 West Tasman Drive 583 San Jose, CA 95134 584 USA 586 Email: naiming@cisco.com 587 Jean-Philippe Vasseur 588 Cisco Systems 589 1414 Massachusetts Avenue 590 Boxborough, MA 01719 591 USA 593 Email: jpv@cisco.com 595 Rahul Aggarwal 596 Arktan 598 Email: raggarwa_1@yahoo.com 600 Scott Shaffer 601 Akamai 602 8 Cambridge Center 603 Cambridge, MA 02142 604 USA 606 Email: sshaffer@akamai.com