idnits 2.17.00 (12 Aug 2021) /tmp/idnits1201/draft-ietf-ospf-rfc4970bis-06.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 (October 8, 2015) is 2417 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: April 10, 2016 R. Aggarwal 7 Arktan 8 S. Shaffer 9 Akamai 10 October 8, 2015 12 Extensions to OSPF for Advertising Optional Router Capabilities 13 draft-ietf-ospf-rfc4970bis-06.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 April 10, 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 . . . . . . . . . . . . . . 4 69 2.1. OSPFv2 Router Information (RI) Opaque LSA . . . . . . . . 4 70 2.2. OSPFv3 Router Information (RI) Opaque LSA . . . . . . . . 4 71 2.3. OSPF Router Information LSA TLV Format . . . . . . . . . 5 72 2.4. OSPF Router Informational Capabilities TLV . . . . . . . 6 73 2.5. Assigned OSPF Router Informational Capability Bits . . . 7 74 2.6. OSPF Router Functional Capabilities TLV . . . . . . . . . 8 75 2.7. Flooding Scope of the Router Information LSA . . . . . . 9 76 3. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9 77 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 78 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 79 5.1. OSPFv2 Opaque LSA Type Assignment . . . . . . . . . . . . 10 80 5.2. OSPFv3 LSA Function Code Assignment . . . . . . . . . . . 10 81 5.3. OSPF RI LSA TLV Type Assignment . . . . . . . . . . . . . 11 82 5.4. Registry for OSPF RI Informational Capability Bits . . . 12 83 5.5. Registry for OSPF RI Functional Capability Bits . . . . . 13 84 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 85 6.1. Normative References . . . . . . . . . . . . . . . . . . 13 86 6.2. Informative References . . . . . . . . . . . . . . . . . 13 87 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 90 1. Introduction 92 It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] 93 routing domain to know the capabilities of their neighbors and other 94 routers in the routing domain. This can be useful for both the 95 advertisement and discovery of OSPFv2 and OSPFv3 capabilities. 97 Throughout this document, OSPF will be used when the specification is 98 applicable to both OSPFv2 and OSPFv3. Similarly, OSPFv2 or OSPFv3 99 will be used when the text is protocol specific. 101 OSPF uses the options field in LSAs and hello packets to advertise 102 optional router capabilities. In the case of OSPFv2, all the bits in 103 this field have been allocated so additional optional capabilities 104 cannot be advertised. This document describes extensions to OSPF to 105 advertise these optional capabilities via opaque LSAs in OSPFv2 and 106 LSAs with a unique type in OSPFv3. For existing OSPF capabilities, 107 backward-compatibility issues dictate that this advertisement is used 108 primarily for informational purposes. For future OSPF extensions, 109 this advertisement MAY be used as the sole mechanism for 110 advertisement and discovery. 112 This document obsoletes RFC 4970 by providing a revised specification 113 including support for advertisement of multiple instances of the RI 114 LSA and a TLV for functional capabilities. 116 1.1. Requirements Notation 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in [RFC-KEYWORDS]. 122 1.2. Summary of Changes from RFC 4970 124 This document includes the following changes from RFC 4970 [RFC4970]: 126 1. The main change is that an OSPF router will be able to advertise 127 multiple instances of the OSPF Router Information LSA. This 128 change permeates through much of the document 130 2. Additionally, Section 2.5 includes an additional TLV for 131 functional capabilities. This is in contrast to the existing TLV 132 which is used to advertise capabilities for informational 133 purposes only. 135 3. The IANA allocation policy for the OSPFv3 LSA Function Code 136 registry and all the OSPF Router Information IANA registries has 137 been changed from "Standards Action" to "IETF Review" 138 [IANA-GUIDE]. 140 4. Finally, references have been updated for drafts that have become 141 RFCs and RFCs that have been obsoleted since the publication of 142 RFC 4970. 144 2. OSPF Router Information (RI) LSA 146 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 147 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information (RI) LSA 148 has an Opaque type of 4 and the Opaque ID is the RI LSA instance ID. 149 The first Opaque ID, i.e., 0, SHOULD always contain the Router 150 Informational Capabilities TLV and, if advertised, the Router 151 Functional Capabilities TLV. RI LSAs subsequence to the first can be 152 used for information that doesn't fit in the first instance. 154 2.1. OSPFv2 Router Information (RI) Opaque LSA 156 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 157 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has an 158 Opaque type of 4 and Opaque ID specifies the LSA instance ID with the 159 first instance always having an Instance ID of 0. 161 0 1 2 3 162 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 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | LS age | Options | 9, 10, or 11 | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | 4 | Opaque ID (Instance ID) | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+d-+-+-+-+-+-+-+-+-+-+-+ 168 | Advertising Router | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 | LS sequence number | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 | LS checksum | length | 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 | | 175 +- TLVs -+ 176 | ... | 178 OSPFv2 Router Information Opaque LSA 180 The format of the TLVs within the body of an RI LSA is as defined in 181 Section 2.3 183 2.2. OSPFv3 Router Information (RI) Opaque LSA 185 The OSPFv3 Router Information LSA has a function code of 12 while the 186 S1/S2 bits are dependent on the desired flooding scope for the LSA. 187 The U bit will be set indicating that the OSPFv3 RI LSA should be 188 flooded even if it is not understood. The Link State ID (LSID) value 189 for this LSA is the instance ID. The first instance ID, i.e., 0, 190 SHOULD always contain the Router Informational Capabilities TLV and, 191 if advertised, the Router Functional Capabilities TLV. OSPFv3 Router 192 Information LSAs subsequence to the first can be used for information 193 that doesn't fit in the first instance. OSPFv3 routers MAY advertise 194 multiple RI LSAs per flooding scope. 196 0 1 2 3 197 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 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | LS age |1|S12| 12 | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | Link State ID (Instance ID) | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | Advertising Router | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | LS sequence number | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | LS checksum | Length | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | | 210 +- TLVs -+ 211 | ... | 213 OSPFv3 Router Information LSA 215 The format of the TLVs within the body of an RI LSA is as defined in 216 Section 2.3 218 2.3. OSPF Router Information LSA TLV Format 220 The format of the TLVs within the body of an RI LSA is the same as 221 the format used by the Traffic Engineering Extensions to OSPF [TE]. 222 The LSA payload consists of one or more nested Type/Length/Value 223 (TLV) triplets. The format of each TLV is: 225 0 1 2 3 226 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 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 | Type | Length | 229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 | Value... | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 TLV Format 235 The Length field defines the length of the value portion in octets 236 (thus a TLV with no value portion would have a length of 0). The TLV 237 is padded to 4-octet alignment; padding is not included in the length 238 field (so a 3-octet value would have a length of 3, but the total 239 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 240 aligned. For example, a 1-byte value would have the length field set 241 to 1, and 3 octets of padding would be added to the end of the value 242 portion of the TLV. The padding is composed of undefined bits. 243 Unrecognized types are ignored. 245 When a new Router Information LSA TLV is defined, the specification 246 MUST explicitly state whether the TLV is applicable to OSPFv2 only, 247 OSPFv3 only, or both OSPFv2 and OSPFv3. 249 2.4. OSPF Router Informational Capabilities TLV 251 An OSPF router advertising an OSPF RI LSA MAY include the Router 252 Informational Capabilities TLV. If included, it MUST be the first 253 TLV in the first instance, i.e., instance 0, of the OSPF RI LSA. 254 Additionally, the TLV MUST accurately reflect the OSPF router's 255 capabilities in the scope advertised. However, the informational 256 capabilities advertised have no impact on the OSPF's operation, they 257 are advertised purely for informational purposes. 259 The format of the Router Informational Capabilities TLV is as 260 follows: 262 0 1 2 3 263 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 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | Type | Length | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Informational Capabilities | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 Type A 16-bit field set to 1. 272 Length A 16-bit field that indicates the length of the value 273 portion in octets and will be a multiple of 4 octets 274 dependent on the number of capabilities advertised. 275 Initially, the length will be 4, denoting 4 octets of 276 informational capability bits. 278 Value A variable length sequence of capability bits rounded 279 to a multiple of 4 octets padded with undefined bits. 280 Initially, there are 4 octets of capability bits. Bits 281 are numbered left-to-right starting with the most 282 significant bit being bit 0. 284 OSPF Router Informational Capabilities TLV 286 The Router Informational Capabilities TLV MAY be followed by optional 287 TLVs that further specify a capability. 289 2.5. Assigned OSPF Router Informational Capability Bits 291 The following informational capability bits are assigned: 293 Bit Capabilities 295 0 OSPF graceful restart capable [GRACE] 296 1 OSPF graceful restart helper [GRACE] 297 2 OSPF Stub Router support [STUB] 298 3 OSPF Traffic Engineering support [TE] 299 4 OSPF point-to-point over LAN [P2PLAN] 300 5 OSPF Experimental TE [EXP-TE] 301 6-31 Unassigned (IETF Review) 303 OSPF Router Informational Capabilities Bits 305 References for [GRACE], [STUB], [TE], [P2PLAN], and [EXP-TE] are 306 included herein. 308 2.6. OSPF Router Functional Capabilities TLV 310 This specification also defines the Router Functional Capabilities 311 TLV for advertisement within the OSPF Router Information LSA. An 312 OSPF router advertising an OSPF RI LSA MAY include the Router 313 Functional Capabilities TLV. If included, it MUST be the included in 314 the first instance of the LSA. Additionally, the TLV MUST be used to 315 reflect OSPF router functional capabilities. If the TLV is not 316 included or the length doesn't include the assigned OSPF functional 317 capability bit, the corresponding OSPF functional capability is 318 implicitly advertised as not being supported by the advertising OSPF 319 router. 321 The format of the Router Functional Capabilities TLV is as follows: 323 0 1 2 3 324 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 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | Type | Length | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | Functional Capabilities | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 331 Type A 16-bit field set to IANA TBD (Suggested value 2). 333 Length A 16-bit field that indicates the length of the value 334 portion in octets and will be a multiple of 4 octets 335 dependent on the number of capabilities advertised. 336 Initially, the length will be 4, denoting 4 octets of 337 informational capability bits. 339 Value A variable length sequence of capability bits rounded 340 to a multiple of 4 octets padded with undefined bits. 341 Initially, there are 4 octets of capability bits. Bits 342 are numbered left-to-right starting with the most 343 significant bit being bit 0. 345 OSPF Router Functional Capabilities TLV 347 The Router Functional Capabilities TLV MAY be followed by optional 348 TLVs that further specify a capability. In contrast to the Router 349 Informational Capabilities TLV, the OSPF extensions advertised in 350 this TLV MAY be used by other OSPF routers to dictate protocol 351 operation. The specifications for functional capabilities advertised 352 in this TLV MUST describe protocol behavior and address backward 353 compatibility. 355 2.7. Flooding Scope of the Router Information LSA 357 The flooding scope for a Router Information LSA is determined by the 358 LSA type. For OSPFv2, type 9 (link-scoped), type 10 (area-scoped), 359 or a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the 360 S1 and S2 bits in the LSA type determine the flooding scope. If AS- 361 wide flooding scope is chosen, the originating router should also 362 advertise area-scoped LSA(s) into any attached Not-So-Stubby Area 363 (NSSA) area(s). An OSPF router MAY advertise different capabilities 364 when both NSSA area scoped LSA(s) and an AS-scoped LSA are 365 advertised. This allows functional capabilities to be limited in 366 scope. For example, a router may be an area border router but only 367 support traffic engineering (TE) in a subset of its attached areas. 369 The choice of flooding scope is made by the advertising router and is 370 a matter of local policy. The originating router MAY advertise 371 multiple RI LSAs with the same instance ID as long as the flooding 372 scopes differ. TLV flooding scope rules will be specified on a per- 373 TLV basis and MUST be specified in the accompanying specifications 374 for future Router Information LSA TLVs. 376 3. Backward Compatibility 378 For backward compatibility, previously advertised Router Information 379 TLVs SHOULD continue to be advertised in the first instance, i.e., 0, 380 of the Router Information LSA. If a Router Information TLV is 381 advertised in multiple Router Information LSA instances and the 382 multiple instance processing is not explicitly specified in the RFC 383 defining that Router Information TLV, the Router Instance TLV in the 384 Router Information LSA with the numerically smallest Instance ID will 385 be used and subsequent instances will be ignored. 387 4. Security Considerations 389 This document describes both a generic mechanism for advertising 390 router capabilities and a TLV for advertising informational and 391 functional capability bits. The capability TLVs are less critical 392 than the topology information currently advertised by the base OSPF 393 protocol. The security considerations for the generic mechanism are 394 dependent on the future application and, as such, should be described 395 as additional capabilities are proposed for advertisement. Security 396 considerations for the base OSPF protocol are covered in [OSPF] and 397 [OSPFV3]. 399 5. IANA Considerations 401 5.1. OSPFv2 Opaque LSA Type Assignment 403 [RFC4970] defined the Router Information opaque LSA as type 4 in the 404 Opaque Link-State Advertisements (LSA) Option Types Registry. IANA 405 is asked to update the reference for that entry to point to this RFC. 407 5.2. OSPFv3 LSA Function Code Assignment 409 [RFC4970] created the registry for OSPFv3 LSA Function Codes. IANA 410 is requested to update the reference for that registry to point to 411 this RFC. References within that registry to [RFC4970] should be 412 updated to point to this RFC; references to other RFCs are unchanged. 413 The definition and assignment policy has been updated as follows. 415 This registry is now comprised of the fields Value, LSA function code 416 name, and Document Reference. The OSPFv3 LSA function code is 417 defined in section A.4.2.1 of [OSPFV3]. The OSPFv3 LSA function code 418 12 has been reserved for the OSPFv3 Router Information (RI) LSA. The 419 assignment policy has been updated for the range 16-255. 421 +-----------+-------------------------------------+ 422 | Range | Assignment Policy | 423 +-----------+-------------------------------------+ 424 | 0 | Reserved (not to be assigned) | 425 | | | 426 | 1-11 | Already assigned | 427 | | | 428 | 12 | OSPFv3 RI LSA (Assigned herein) | 429 | | | 430 | 13-15 | Already assigned | 431 | | | 432 | 16-255 | Unassigned (IETF Review) | 433 | | | 434 | 256-8175 | Reserved (No assignments) | 435 | | | 436 | 8176-8183 | Experimentation (No assignments) | 437 | | | 438 | 8184-8190 | Vendor Private Use (No assignments) | 439 | | | 440 | 8191 | Reserved (not to be assigned) | 441 +-----------+-------------------------------------+ 443 OSPFv3 LSA Function Codes 445 o OSPFv3 LSA function codes in the range 16-255 are to be assigned 446 subject to IETF Review. New values are assigned only through RFCs 447 that have been shepherded through the IESG as AD- Sponsored or 448 IETF WG Documents [IANA-GUIDE]. 450 o OSPFv3 LSA function codes in the range 8176-8181 are for 451 experimental use; these will not be registered with IANA and MUST 452 NOT be mentioned by RFCs. 454 o OSPFv3 LSAs with an LSA Function Code in the Vendor Private Use 455 range 8184-8191 MUST include the Enterprise Code [ENTERPRISE-CODE] 456 as the first 4 octets following the 20 octets of LSA header. 458 o If a new LSA Function Code is documented, the documentation MUST 459 include the valid combinations of the U, S2, and S1 bits for the 460 LSA. It SHOULD also describe how the Link State ID is to be 461 assigned. 463 5.3. OSPF RI LSA TLV Type Assignment 465 [RFC4970] created the registry for OSPF Router Information (RI) TLVs. 466 IANA is requested to update the reference for this registry to point 467 to this RFC. The definition and assignment policy has been updated 468 as follows. References within that registry to [RFC4970] should be 469 updated to point to this RFC; references to other RFCs are unchanged. 470 The definition and assignment policy has been updated as follows. 472 The registry is now comprised of the fields Value, TLV Name, and 473 Document Reference. The value of 1 for the informational 474 capabilities TLV is defined herein. The value IANA TBD (suggested 475 value 2) for the Router Functional Capabilities TLV is also defined 476 herein. 478 +-------------+-----------------------------------+ 479 | Range | Assignment Policy | 480 +-------------+-----------------------------------+ 481 | 0 | Reserved (not to be assigned) | 482 | | | 483 | 1 | Informational Capabilities | 484 | | | 485 | 2 | Unassigned (IETF Review) | 486 | | | 487 | TBD | Functional Capabilities | 488 | | | 489 | 3-9 | Already Assigned | 490 | | | 491 | 10-32767 | Unassigned (IETF Review) | 492 | | | 493 | 32768-32777 | Experimentation (No assignments) | 494 | | | 495 | 32778-65535 | Reserved (Not to be assigned) | 496 +-------------+-----------------------------------+ 498 OSPF RI TLVs 500 o Types in the range 2, 10-32767 are to be assigned subject to IETF 501 Review. New values are assigned only through RFCs that have been 502 shepherded through the IESG as AD-Sponsored or IETF WG Documents 503 [IANA-GUIDE]. 505 o Types in the range 32778-65535 are reserved and are not to be 506 assigned at this time. Before any assignments can be made in this 507 range, there MUST be a Standards Track RFC that specifies IANA 508 Considerations that covers the range being assigned. 510 5.4. Registry for OSPF RI Informational Capability Bits 512 [RFC4970] created the registry for OSPF Router Informational 513 Capability Bits. IANA is requested to update the reference for this 514 registry to point to this RFC. The definition and assignment policy 515 has been updated as follows. 517 o This registry is now comprised of the fields Bit Number, 518 Capability Name, and Document Reference. 520 o The values are defined in Section 2.4. All Router Informational 521 Capability TLV additions are to be assigned through IETF Review 522 [IANA-GUIDE]. 524 5.5. Registry for OSPF RI Functional Capability Bits 526 IANA is asked to create a registry for OSPF Router Functional 527 Capability Bits within the Open Shortest Path First v2 (OSPFv2) 528 Parameters Group. This registry will be comprised of the fields Bit 529 Number, Capability Name, and Document Reference. Initially, the sub- 530 registry will be empty but will be available for future capabilities. 531 All Router Functional Capability TLV additions are to be assigned 532 through IETF Review [IANA-GUIDE]. 534 6. References 536 6.1. Normative References 538 [OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 539 OSPF Opaque LSA Option", RFC 5250, July 2008. 541 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 543 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 544 for IPv6", RFC 5340, July 2008. 546 [RFC-KEYWORDS] 547 Bradner, S., "Key words for use in RFC's to Indicate 548 Requirement Levels", BCP 14, RFC 2119, March 1997. 550 [RFC4970] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 551 Shaffer, "Extensions to OSPF for Advertising Optional 552 Router Capabilities", RFC 4970, July 2007. 554 [TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 555 Extensions to OSPF", RFC 3630, September 2003. 557 6.2. Informative References 559 [ENTERPRISE-CODE] 560 Eronen, P. and D. Harrington, "Enterprise Number for 561 Documentation Use", RFC 5612, August 2009. 563 [EXP-TE] Srisuresh, P. and P. Joseph, "OSPF-xTE: Experimental 564 Extension to OSPF for Traffic Engineering", RFC 4973, July 565 2007. 567 [GRACE] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF 568 Restart", RFC 3623, November 2003. 570 [IANA-GUIDE] 571 Narten, T. and H. Alvestrand, "Guidelines for Writing an 572 IANA Considerations Section in RFCs", RFC 5226, May 2008. 574 [P2PLAN] Shen, N. and A. Zinin, "Point-to-point operation over LAN 575 in link-state routing protocols", RFC 5309, October 2008. 577 [STUB] Retana, A., Nguyen, L., White, R., Zinin, A., and D. 578 McPherson, "OSPF Stub Router Advertisement", RFC 6987, 579 September 2013. 581 Appendix A. Acknowledgments 583 The idea for this work grew out of a conversation with Andrew Partan 584 and we would like to thank him for his contribution. The authors 585 would like to thanks Peter Psenak for his review and helpful comments 586 on early versions of the document. 588 Special thanks to Tom Petch for providing the updated IANA text in 589 the BIS version of the document. 591 Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian 592 Farrel have been incorporated into later versions. 594 Thanks to Yingzhen Qu for acting as document shepherd. 596 Thanks to Chris Bowers, Alia Atlas, Shraddha Hegde, and Dan Romascanu 597 for review of the BIS version of this document. 599 The RFC text was produced using Marshall Rose's xml2rfc tool. 601 Authors' Addresses 603 Acee Lindem (editor) 604 Cisco Systems 605 301 Midenhall Way 606 Cary, NC 27513 607 USA 609 Email: acee@cisco.com 610 Naiming Shen 611 Cisco Systems 612 225 West Tasman Drive 613 San Jose, CA 95134 614 USA 616 Email: naiming@cisco.com 618 Jean-Philippe Vasseur 619 Cisco Systems 620 1414 Massachusetts Avenue 621 Boxborough, MA 01719 622 USA 624 Email: jpv@cisco.com 626 Rahul Aggarwal 627 Arktan 629 Email: raggarwa_1@yahoo.com 631 Scott Shaffer 632 Akamai 633 8 Cambridge Center 634 Cambridge, MA 02142 635 USA 637 Email: sshaffer@akamai.com