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