idnits 2.17.00 (12 Aug 2021) /tmp/idnits2848/draft-ietf-ospf-rfc4970bis-07.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 15, 2015) is 2403 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 17, 2016 R. Aggarwal 7 Arktan 8 S. Shaffer 9 Akamai 10 October 15, 2015 12 Extensions to OSPF for Advertising Optional Router Capabilities 13 draft-ietf-ospf-rfc4970bis-07.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 17, 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. Backwards 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 backwards compatibility issues dictate that this advertisement is 108 used primarily for informational purposes. For future OSPF 109 extensions, 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 2.1. OSPFv2 Router Information (RI) Opaque LSA 148 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 149 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information (RI) LSA 150 has an Opaque type of 4 and the Opaque ID is the RI LSA instance ID. 151 The first Opaque ID, i.e., 0, SHOULD always contain the Router 152 Informational Capabilities TLV and, if advertised, the Router 153 Functional Capabilities TLV. RI LSA instances subsequent to the 154 first can be used for information that doesn't fit in the first 155 instance. 157 OSPFv2 routers will advertise a link scoped, area-scoped, or AS- 158 scoped Opaque-LSA [OPAQUE]. The OSPFv2 Router Information LSA has an 159 Opaque type of 4 and Opaque ID specifies the LSA instance ID with the 160 first instance always having an Instance ID of 0. 162 0 1 2 3 163 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 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | LS age | Options | 9, 10, or 11 | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | 4 | Opaque ID (Instance ID) | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+d-+-+-+-+-+-+-+-+-+-+-+ 169 | Advertising Router | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | LS sequence number | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | LS checksum | length | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | | 176 +- TLVs -+ 177 | ... | 179 OSPFv2 Router Information Opaque LSA 181 The format of the TLVs within the body of an RI LSA is as defined in 182 Section 2.3 184 2.2. OSPFv3 Router Information (RI) Opaque LSA 186 The OSPFv3 Router Information LSA has a function code of 12 while the 187 S1/S2 bits are dependent on the desired flooding scope for the LSA. 188 The U bit will be set indicating that the OSPFv3 RI LSA should be 189 flooded even if it is not understood. The Link State ID (LSID) value 190 for this LSA is the instance ID. The first instance ID, i.e., 0, 191 SHOULD always contain the Router Informational Capabilities TLV and, 192 if advertised, the Router Functional Capabilities TLV. OSPFv3 Router 193 Information LSAs subsequence to the first can be used for information 194 that doesn't fit in the first instance. OSPFv3 routers MAY advertise 195 multiple RI LSAs per flooding scope. 197 0 1 2 3 198 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 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | LS age |1|S12| 12 | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Link State ID (Instance ID) | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | Advertising Router | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | LS sequence number | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 | LS checksum | Length | 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | | 211 +- TLVs -+ 212 | ... | 214 OSPFv3 Router Information LSA 216 The format of the TLVs within the body of an RI LSA is as defined in 217 Section 2.3 219 2.3. OSPF Router Information LSA TLV Format 221 The format of the TLVs within the body of an RI LSA is the same as 222 the format used by the Traffic Engineering Extensions to OSPF [TE]. 223 The LSA payload consists of one or more nested Type/Length/Value 224 (TLV) triplets. The format of each TLV is: 226 0 1 2 3 227 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 228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 | Type | Length | 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | Value... | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 234 TLV Format 236 The Length field defines the length of the value portion in octets 237 (thus a TLV with no value portion would have a length of 0). The TLV 238 is padded to 4-octet alignment; padding is not included in the length 239 field (so a 3-octet value would have a length of 3, but the total 240 size of the TLV would be 8 octets). Nested TLVs are also 4-octet 241 aligned. For example, a 1-octet value would have the length field 242 set to 1, and 3 octets of padding would be added to the end of the 243 value portion of the TLV. The padding is composed of undefined bits. 244 Unrecognized types are ignored. 246 When a new Router Information LSA TLV is defined, the specification 247 MUST explicitly state whether the TLV is applicable to OSPFv2 only, 248 OSPFv3 only, or both OSPFv2 and OSPFv3. 250 2.4. OSPF Router Informational Capabilities TLV 252 An OSPF router advertising an OSPF RI LSA MAY include the Router 253 Informational Capabilities TLV. If included, it MUST be the first 254 TLV in the first instance, i.e., instance 0, of the OSPF RI LSA. 255 Additionally, the TLV MUST accurately reflect the OSPF router's 256 capabilities in the scope advertised. However, the informational 257 capabilities advertised have no impact on OSPF protocol operation, 258 they are advertised purely for informational purposes. 260 The format of the Router Informational Capabilities TLV is as 261 follows: 263 0 1 2 3 264 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 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Type | Length | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Informational Capabilities | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 Type A 16-bit field set to 1. 273 Length A 16-bit field that indicates the length of the value 274 portion in octets and will be a multiple of 4 octets 275 dependent on the number of capabilities advertised. 276 Initially, the length will be 4, denoting 4 octets of 277 informational capability bits. 279 Value A variable length sequence of capability bits rounded 280 to a multiple of 4 octets padded with undefined bits. 281 Initially, there are 4 octets of capability bits. Bits 282 are numbered left-to-right starting with the most 283 significant bit being bit 0. 285 OSPF Router Informational Capabilities TLV 287 The Router Informational Capabilities TLV MAY be followed by optional 288 TLVs that further specify a capability. 290 2.5. Assigned OSPF Router Informational Capability Bits 292 The following informational capability bits are assigned: 294 Bit Capabilities 296 0 OSPF graceful restart capable [GRACE] 297 1 OSPF graceful restart helper [GRACE] 298 2 OSPF Stub Router support [STUB] 299 3 OSPF Traffic Engineering support [TE] 300 4 OSPF point-to-point over LAN [P2PLAN] 301 5 OSPF Experimental TE [EXP-TE] 302 6-31 Unassigned (IETF Review) 304 OSPF Router Informational Capabilities Bits 306 References for [GRACE], [STUB], [TE], [P2PLAN], and [EXP-TE] are 307 included herein. 309 2.6. OSPF Router Functional Capabilities TLV 311 This specification also defines the Router Functional Capabilities 312 TLV for advertisement within the OSPF Router Information LSA. An 313 OSPF router advertising an OSPF RI LSA MAY include the Router 314 Functional Capabilities TLV. If included, it MUST be the included in 315 the first instance of the LSA. Additionally, the TLV MUST reflect 316 the advertising OSPF router's actual functional capabilities since 317 the information will be used to dictate OSPF protocol operation in 318 the flooding-scope of the containing OSPF RI LSA. If the TLV is not 319 included or the length doesn't include the assigned OSPF functional 320 capability bit, the corresponding OSPF functional capability is 321 implicitly advertised as not being supported by the advertising OSPF 322 router. 324 The format of the Router Functional Capabilities TLV is as follows: 326 0 1 2 3 327 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 328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 | Type | Length | 330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 331 | Functional Capabilities | 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 Type A 16-bit field set to IANA TBD (Suggested value 2). 336 Length A 16-bit field that indicates the length of the value 337 portion in octets and will be a multiple of 4 octets 338 dependent on the number of capabilities advertised. 339 Initially, the length will be 4, denoting 4 octets of 340 informational capability bits. 342 Value A variable length sequence of capability bits rounded 343 to a multiple of 4 octets padded with undefined bits. 344 Initially, there are 4 octets of capability bits. Bits 345 are numbered left-to-right starting with the most 346 significant bit being bit 0. 348 OSPF Router Functional Capabilities TLV 350 The Router Functional Capabilities TLV MAY be followed by optional 351 TLVs that further specify a capability. In contrast to the Router 352 Informational Capabilities TLV, the OSPF extensions advertised in 353 this TLV MAY be used by other OSPF routers to dictate protocol 354 operation. The specifications for functional capabilities advertised 355 in this TLV MUST describe protocol behavior and address backwards 356 compatibility. 358 2.7. Flooding Scope of the Router Information LSA 360 The flooding scope for a Router Information LSA is determined by the 361 LSA type. For OSPFv2, type 9 (link-scoped), type 10 (area-scoped), 362 or a type 11 (AS-scoped) opaque LSA may be flooded. For OSPFv3, the 363 S1 and S2 bits in the LSA type determine the flooding scope. If AS- 364 wide flooding scope is chosen, the originating router should also 365 advertise area-scoped LSA(s) into any attached Not-So-Stubby Area 366 (NSSA) area(s). An OSPF router MAY advertise different capabilities 367 when both NSSA area scoped LSA(s) and an AS-scoped LSA are 368 advertised. This allows functional capabilities to be limited in 369 scope. For example, a router may be an area border router but only 370 support traffic engineering (TE) in a subset of its attached areas. 372 The choice of flooding scope is made by the advertising router and is 373 a matter of local policy. The originating router MAY advertise 374 multiple RI LSAs with the same instance ID as long as the flooding 375 scopes differ. TLV flooding scope rules will be specified on a per- 376 TLV basis and MUST be specified in the accompanying specifications 377 for future Router Information LSA TLVs. 379 3. Backwards Compatibility 381 For backwards compatibility, previously advertised Router Information 382 TLVs SHOULD continue to be advertised in the first instance, i.e., 0, 383 of the Router Information LSA. If a Router Information TLV is 384 advertised in multiple Router Information LSA instances and the 385 multiple instance processing is not explicitly specified in the RFC 386 defining that Router Information TLV, the Router Instance TLV in the 387 Router Information LSA with the numerically smallest Instance ID will 388 be used and subsequent instances will be ignored. 390 4. Security Considerations 392 This document describes both a generic mechanism for advertising 393 router capabilities and a TLV for advertising informational and 394 functional capability bits. The capability TLVs are less critical 395 than the topology information currently advertised by the base OSPF 396 protocol. The security considerations for the generic mechanism are 397 dependent on the future application and, as such, should be described 398 as additional capabilities are proposed for advertisement. Security 399 considerations for the base OSPF protocol are covered in [OSPF] and 400 [OSPFV3]. 402 5. IANA Considerations 404 5.1. OSPFv2 Opaque LSA Type Assignment 406 [RFC4970] defined the Router Information opaque LSA as type 4 in the 407 Opaque Link-State Advertisements (LSA) Option Types Registry. IANA 408 is asked to update the reference for that entry to point to this RFC. 410 5.2. OSPFv3 LSA Function Code Assignment 412 [RFC4970] created the registry for OSPFv3 LSA Function Codes. IANA 413 is requested to update the reference for that registry to point to 414 this RFC. References within that registry to [RFC4970] should be 415 updated to point to this RFC; references to other RFCs are unchanged. 416 The definition and assignment policy has been updated as follows. 418 This registry is now comprised of the fields Value, LSA function code 419 name, and Document Reference. The OSPFv3 LSA function code is 420 defined in section A.4.2.1 of [OSPFV3]. The OSPFv3 LSA function code 421 12 has been reserved for the OSPFv3 Router Information (RI) LSA. The 422 assignment policy has been updated for the range 16-255. 424 +-----------+-------------------------------------+ 425 | Range | Assignment Policy | 426 +-----------+-------------------------------------+ 427 | 0 | Reserved (not to be assigned) | 428 | | | 429 | 1-11 | Already assigned | 430 | | | 431 | 12 | OSPFv3 RI LSA (Assigned herein) | 432 | | | 433 | 13-15 | Already assigned | 434 | | | 435 | 16-255 | Unassigned (IETF Review) | 436 | | | 437 | 256-8175 | Reserved (No assignments) | 438 | | | 439 | 8176-8183 | Experimentation (No assignments) | 440 | | | 441 | 8184-8190 | Vendor Private Use (No assignments) | 442 | | | 443 | 8191 | Reserved (not to be assigned) | 444 +-----------+-------------------------------------+ 446 OSPFv3 LSA Function Codes 448 o OSPFv3 LSA function codes in the range 16-255 are to be assigned 449 subject to IETF Review. New values are assigned only through RFCs 450 that have been shepherded through the IESG as AD- Sponsored or 451 IETF WG Documents [IANA-GUIDE]. 453 o OSPFv3 LSA function codes in the range 8176-8181 are for 454 experimental use; these will not be registered with IANA and MUST 455 NOT be mentioned by RFCs. 457 o OSPFv3 LSAs with an LSA Function Code in the Vendor Private Use 458 range 8184-8191 MUST include the Enterprise Code [ENTERPRISE-CODE] 459 as the first 4 octets following the 20 octets of LSA header. 461 o If a new LSA Function Code is documented, the documentation MUST 462 include the valid combinations of the U, S2, and S1 bits for the 463 LSA. It SHOULD also describe how the Link State ID is to be 464 assigned. 466 5.3. OSPF RI LSA TLV Type Assignment 468 [RFC4970] created the registry for OSPF Router Information (RI) TLVs. 469 IANA is requested to update the reference for this registry to point 470 to this RFC. The definition and assignment policy has been updated 471 as follows. References within that registry to [RFC4970] should be 472 updated to point to this RFC; references to other RFCs are unchanged. 473 The definition and assignment policy has been updated as follows. 475 The registry is now comprised of the fields Value, TLV Name, and 476 Document Reference. The value of 1 for the informational 477 capabilities TLV is defined herein. The value IANA TBD (suggested 478 value 2) for the Router Functional Capabilities TLV is also defined 479 herein. 481 +-------------+-----------------------------------+ 482 | Range | Assignment Policy | 483 +-------------+-----------------------------------+ 484 | 0 | Reserved (not to be assigned) | 485 | | | 486 | 1 | Informational Capabilities | 487 | | | 488 | 2 | Unassigned (IETF Review) | 489 | | | 490 | TBD | Functional Capabilities | 491 | | | 492 | 3-9 | Already Assigned | 493 | | | 494 | 10-32767 | Unassigned (IETF Review) | 495 | | | 496 | 32768-32777 | Experimentation (No assignments) | 497 | | | 498 | 32778-65535 | Reserved (Not to be assigned) | 499 +-------------+-----------------------------------+ 501 OSPF RI TLVs 503 o Types in the range 2, 10-32767 are to be assigned subject to IETF 504 Review. New values are assigned only through RFCs that have been 505 shepherded through the IESG as AD-Sponsored or IETF WG Documents 506 [IANA-GUIDE]. 508 o Types in the range 32778-65535 are reserved and are not to be 509 assigned at this time. Before any assignments can be made in this 510 range, there MUST be a Standards Track RFC that specifies IANA 511 Considerations that covers the range being assigned. 513 5.4. Registry for OSPF RI Informational Capability Bits 515 [RFC4970] created the registry for OSPF Router Informational 516 Capability Bits. IANA is requested to update the reference for this 517 registry to point to this RFC. The definition and assignment policy 518 has been updated as follows. 520 o This registry is now comprised of the fields Bit Number, 521 Capability Name, and Document Reference. 523 o The values are defined in Section 2.4. All Router Informational 524 Capability TLV additions are to be assigned through IETF Review 525 [IANA-GUIDE]. 527 5.5. Registry for OSPF RI Functional Capability Bits 529 IANA is asked to create a registry for OSPF Router Functional 530 Capability Bits within the Open Shortest Path First v2 (OSPFv2) 531 Parameters Group. This registry will be comprised of the fields Bit 532 Number, Capability Name, and Document Reference. Initially, the sub- 533 registry will be empty but will be available for future capabilities. 534 All Router Functional Capability TLV additions are to be assigned 535 through IETF Review [IANA-GUIDE]. 537 6. References 539 6.1. Normative References 541 [OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 542 OSPF Opaque LSA Option", RFC 5250, July 2008. 544 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 546 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 547 for IPv6", RFC 5340, July 2008. 549 [RFC-KEYWORDS] 550 Bradner, S., "Key words for use in RFC's to Indicate 551 Requirement Levels", BCP 14, RFC 2119, March 1997. 553 [RFC4970] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 554 Shaffer, "Extensions to OSPF for Advertising Optional 555 Router Capabilities", RFC 4970, July 2007. 557 [TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 558 Extensions to OSPF", RFC 3630, September 2003. 560 6.2. Informative References 562 [ENTERPRISE-CODE] 563 Eronen, P. and D. Harrington, "Enterprise Number for 564 Documentation Use", RFC 5612, August 2009. 566 [EXP-TE] Srisuresh, P. and P. Joseph, "OSPF-xTE: Experimental 567 Extension to OSPF for Traffic Engineering", RFC 4973, July 568 2007. 570 [GRACE] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF 571 Restart", RFC 3623, November 2003. 573 [IANA-GUIDE] 574 Narten, T. and H. Alvestrand, "Guidelines for Writing an 575 IANA Considerations Section in RFCs", RFC 5226, May 2008. 577 [P2PLAN] Shen, N. and A. Zinin, "Point-to-point operation over LAN 578 in link-state routing protocols", RFC 5309, October 2008. 580 [STUB] Retana, A., Nguyen, L., White, R., Zinin, A., and D. 581 McPherson, "OSPF Stub Router Advertisement", RFC 6987, 582 September 2013. 584 Appendix A. Acknowledgments 586 The idea for this work grew out of a conversation with Andrew Partan 587 and we would like to thank him for his contribution. The authors 588 would like to thanks Peter Psenak for his review and helpful comments 589 on early versions of the document. 591 Special thanks to Tom Petch for providing the updated IANA text in 592 the BIS version of the document. 594 Comments from Abhay Roy, Vishwas Manral, Vivek Dubey, and Adrian 595 Farrel have been incorporated into later versions. 597 Thanks to Yingzhen Qu for acting as document shepherd. 599 Thanks to Chris Bowers, Alia Atlas, Shraddha Hegde, Dan Romascanu, 600 and Victor kuarsingh for review of the BIS version of this document. 602 The RFC text was produced using Marshall Rose's xml2rfc tool. 604 Authors' Addresses 606 Acee Lindem (editor) 607 Cisco Systems 608 301 Midenhall Way 609 Cary, NC 27513 610 USA 612 Email: acee@cisco.com 613 Naiming Shen 614 Cisco Systems 615 225 West Tasman Drive 616 San Jose, CA 95134 617 USA 619 Email: naiming@cisco.com 621 Jean-Philippe Vasseur 622 Cisco Systems 623 1414 Massachusetts Avenue 624 Boxborough, MA 01719 625 USA 627 Email: jpv@cisco.com 629 Rahul Aggarwal 630 Arktan 632 Email: raggarwa_1@yahoo.com 634 Scott Shaffer 635 Akamai 636 8 Cambridge Center 637 Cambridge, MA 02142 638 USA 640 Email: sshaffer@akamai.com