idnits 2.17.00 (12 Aug 2021) /tmp/idnits36283/draft-ietf-ospf-ospfv3-autoconfig-11.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 (January 15, 2015) is 2683 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Lindem 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track J. Arkko 5 Expires: July 19, 2015 Ericsson 6 January 15, 2015 8 OSPFv3 Auto-Configuration 9 draft-ietf-ospf-ospfv3-autoconfig-11.txt 11 Abstract 13 OSPFv3 is a candidate for deployments in environments where auto- 14 configuration is a requirement. One such environment is the IPv6 15 home network where users expect to simply plug in a router and have 16 it automatically use OSPFv3 for intra-domain routing. This document 17 describes the necessary mechanisms for OSPFv3 to be self-configuring. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 19, 2015. 36 Copyright Notice 38 Copyright (c) 2015 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 55 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 56 2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . 4 57 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 5 58 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . 5 59 4. OSPFv3 Minimal Authentication Configuration . . . . . . . . . 5 60 5. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . 6 61 6. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . 6 62 7. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 6 63 7.1. Duplicate Router ID Detection for Neighbors . . . . . . . 6 64 7.2. Duplicate Router ID Detection for OSPFv3 Routers that are 65 not Neighbors . . . . . . . . . . . . . . . . . . . . . . 7 66 7.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . 7 67 7.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 9 68 7.3. Duplicate Router ID Resolution . . . . . . . . . . . . . 9 69 7.4. Change to RFC 2328 Section 13.4, 'Receiving Self- 70 Originated LSA' Processing . . . . . . . . . . . . . . . 9 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 72 9. Management Considerations . . . . . . . . . . . . . . . . . . 10 73 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 74 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 75 11.1. Normative References . . . . . . . . . . . . . . . . . . 11 76 11.2. Informative References . . . . . . . . . . . . . . . . . 12 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 79 1. Introduction 81 OSPFv3 [OSPFV3] is a candidate for deployments in environments where 82 auto-configuration is a requirement. Its operation is largely 83 unchanged from the base OSPFv3 protocol specification [OSPFV3]. 85 The following aspects of OSPFv3 auto-configuration are described: 87 1. Default OSPFv3 Configuration 89 2. HelloInterval/RouterDeadInterval Flexibility 91 3. Unique OSPFv3 Router ID generation 93 4. OSPFv3 Adjacency Formation 95 5. Duplicate OSPFv3 Router ID Resolution 97 1.1. Requirements notation 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in [RFC-KEYWORDS]. 103 1.2. Acknowledgments 105 This specification was inspired by the work presented in the Homenet 106 working group meeting in October 2011 in Philadelphia, Pennsylvania. 107 In particular, we would like to thank Fred Baker, Lorenzo Colitti, 108 Ole Troan, Mark Townsley, and Michael Richardson. 110 Arthur Dimitrelis and Aidan Williams did prior work in OSPFv3 auto- 111 configuration in the expired "Autoconfiguration of routers using a 112 link state routing protocol" IETF Draft. There are many similarities 113 between the concepts and techniques in this document. 115 Thanks for Abhay Roy and Manav Bhatia for comments regarding 116 duplicate router-id processing. 118 Thanks for Alvaro Retana and Michael Barnes for comments regarding 119 OSPFv3 Instance ID auto-configuration. 121 Thanks to Faraz Shamim for review and comments. 123 Thanks to Mark Smith for the requirement to reduce the adjacency 124 formation delay in the back-to-back ethernet topologies that are 125 prevalent in home networks. 127 Thanks to Les Ginsberg for document review and recommendations on 128 OSPFv3 hardware fingerprint content. 130 Thanks to Curtis Villamizar for document review and analysis of 131 duplicate router-id resolution nuances. 133 Thanks to Uma Chunduri for comments during OSPF WG last call. 135 Thanks to Martin Vigoureux for Routing Area Directorate review and 136 comments. 138 Thanks to Adam Montville for Security Area Directorate review and 139 comments. 141 Special thanks go to Markus Stenberg for his implementation of this 142 specification in Bird. 144 Special thanks also go to David Lamparter for his implementation of 145 this specification in Quagga. 147 The RFC text was produced using Marshall Rose's xml2rfc tool. 149 2. OSPFv3 Default Configuration 151 For complete auto-configuration, OSPFv3 will need to choose suitable 152 configuration defaults. These include: 154 1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in 155 area 0. 157 2. OSPFv3 SHOULD be auto-configured for IPv6 on all interfaces 158 intended as general IPv6-capable routers. Optionally, an 159 interface MAY be excluded if it is clear that running OSPFv3 on 160 the interface is not required. For example, if manual 161 configuration or another condition indicates that an interface is 162 connected to an Internet Service Provider (ISP) and there is no 163 Border Gateway Protocol (BGP) [BGP] peering, there is typically 164 no need to employ OSPFv3. In fact, [IPv6-CPE] specifically 165 requires that IPv6 Customer Premise Equipment (CPE) routers do 166 not initiate any dynamic routing protocol by default on the 167 router's WAN, i.e., ISP-facing, interface. In home networking 168 environments, an interface where no OSPFv3 neighbors are found 169 but a DHCP IPv6 prefix can be acquired may be considered an ISP- 170 facing interface and running OSPFv3 is unnecessary. 172 3. OSPFv3 interfaces will be auto-configured to an interface type 173 corresponding to their layer-2 capability. For example, Ethernet 174 interfaces and vanilla Wi-Fi interfaces will be auto-configured 175 as OSPFv3 broadcast networks and Point-to-Point Protocol (PPP) 176 interfaces will be auto-configured as OSPFv3 Point-to-Point 177 interfaces. Most extant OSPFv3 implementations do this already. 178 Auto-configured operation over wireless networks requiring a 179 point-to-multipoint (P2MP) topology and dynamic metrics based on 180 wireless feedback is not within the scope of this document. 181 However, auto-configuration is not precluded in these 182 environments. 184 4. OSPFv3 interfaces MAY use an arbitrary HelloInterval and 185 RouterDeadInterval as specified in Section 3. Of course, an 186 identical HelloInterval and RouterDeadInterval will still be 187 required to form an adjacency with an OSPFv3 router not 188 supporting auto-configuration [OSPFV3]. 190 5. All OSPFv3 interfaces SHOULD be auto-configured to use an 191 Interface Instance ID of 0 that corresponds to the base IPv6 192 unicast address family instance ID as defined in [OSPFV3-AF]. 193 Similarly, if IPv4 unicast addresses are advertised in a separate 194 auto-configured OSPFv3 instance, the base IPv4 unicast address 195 family instance ID value, i.e., 64, SHOULD be auto-configured as 196 the Interface Instance ID for all interfaces corresponding to the 197 IPv4 unicast OSPFv3 instance [OSPFV3-AF]. 199 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility 201 Auto-configured OSPFv3 routers will not require an identical 202 HelloInterval and RouterDeadInterval to form adjacencies. Rather, 203 the received HelloInterval will be ignored and the received 204 RouterDeadInterval will be used to determine OSPFv3 liveliness with 205 the sending router. In other words, the Neighbor Inactivity Timer 206 (Section 10 of [OSPFV2]) for each neighbor will reflect that 207 neighbor's advertised RouterDeadInterval and MAY be different from 208 other OSPFv3 routers on the link without impacting adjacency 209 formation. A similar mechanism requiring additional signaling is 210 proposed for all OSPFv2 and OSPFv3 routers [ASYNC-HELLO]. 212 3.1. Wait Timer Reduction 214 In many situations, auto-configured OSPFv3 routers will be deployed 215 in environments where back-to-back ethernet connections are utilized. 216 When this is the case, an OSPFv3 broadcast interface will not come up 217 until the other OSPFv3 router is connected and the routers will wait 218 RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In 219 order to reduce this delay, an auto-configured OSPFv3 router MAY 220 reduce the wait interval to a value no less than (HelloInterval + 1). 221 Reducing the setting will slightly increase the likelihood of the 222 Designated Router (DR) flapping but is preferable to the long 223 adjacency formation delay. Note that this value is not included in 224 OSPFv3 Hello packets and does not impact interoperability. 226 4. OSPFv3 Minimal Authentication Configuration 228 In many deployments, the requirement for OSPFv3 authentication 229 overrides the goal of complete OSPFv3 autoconfiguration. Therefore, 230 it is RECOMMENDED that OSPFv3 routers supporting this specification 231 minimally offer an option to explicitly configure a single password 232 for HMAC-SHA authentication as described in [OSPFV3-AUTH-TRAILER]. 233 When configured, the password will be used on all auto-configured 234 interfaces with the Security Association Identifier (SA ID) set to 1 235 and HMAC-SHA-256 used as the authentication algorithm. 237 5. OSPFv3 Router ID Selection 239 An OSPFv3 router requires a unique Router ID within the OSPFv3 240 routing domain for correct protocol operation. An OSPFv3 router 241 implementing this specification will select a router-id that has a 242 high probability of uniqueness. A pseudo-random number SHOULD be 243 used for the OSPFv3 Router ID. The generation SHOULD be seeded with 244 a variable that is likely to be unique in the applicable OSPFv3 245 router deployment. A good choice of seed would be some portion or 246 hash of the Router-Hardware-Fingerprint as described in 247 Section 7.2.2. 249 Since there is a possibility of a Router ID collision, duplicate 250 Router ID detection and resolution are required as described in 251 Section 7 and Section 7.3. OSPFv3 routers SHOULD maintain the last 252 successfully chosen Router ID in non-volatile storage to avoid 253 collisions subsequent to when an autoconfigured OSPFv3 router is 254 first added to the OSPFv3 routing domain. 256 6. OSPFv3 Adjacency Formation 258 Since OSPFv3 uses IPv6 link-local addresses for all protocol messages 259 other than messages sent on virtual links (which are not applicable 260 to auto-configuration), OSPFv3 adjacency formation can proceed as 261 soon as a Router ID has been selected and the IPv6 link-local address 262 has completed Duplicate Address Detection (DAD) as specified in IPv6 263 Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only 264 changes to the OSPFv3 base specification are supporting 265 HelloInterval/RouterDeadInterval flexibility as described in 266 Section 3 and duplicate Router ID detection and resolution as 267 described in Section 7 and Section 7.3. 269 7. OSPFv3 Duplicate Router ID Detection and Resolution 271 There are two cases of duplicate OSPFv3 Router ID detection. One 272 where the OSPFv3 router with the duplicate Router ID is directly 273 connected and one where it is not. In both cases, the duplicate 274 resolution is for one of the routers to select a new OSPFv3 Router 275 ID. 277 7.1. Duplicate Router ID Detection for Neighbors 279 In this case, a duplicate Router ID is detected if any valid OSPFv3 280 packet is received with the same OSPFv3 Router ID but a different 281 IPv6 link-local source address. Once this occurs, the OSPFv3 router 282 with the numerically smaller IPv6 link-local address will need to 283 select a new Router ID as described in Section 7.3. Note that the 284 fact that the OSPFv3 router is a neighbor on a non-virtual interface 285 implies that the router is directly connected. An OSPFv3 router 286 implementing this specification should assure that the inadvertent 287 connection of multiple router interfaces to the same physical link is 288 not misconstrued as detection of an OSPFv3 neighbor with a duplicate 289 Router ID. 291 7.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 292 Neighbors 294 OSPFv3 routers implementing auto-configuration, as specified herein, 295 MUST originate an Auto-Configuration (AC) Link State Advertisement 296 (LSA) including the Router-Hardware-Fingerprint Type-Length-Value 297 (TLV). The Router-Hardware-Fingerprint TLV contains a variable 298 length value that has a very high probability of uniquely identifying 299 the advertising OSPFv3 router. An OSPFv3 router implementing this 300 specification MUST detect received Auto-Configuration LSAs with its 301 Router ID specified in the LSA header. LSAs received with the local 302 OSPFv3 Router's Router ID in the LSA header are perceived as self- 303 originated (see section 4.6 of [OSPFV3]). In these received Auto- 304 Configuration LSAs, the Router-Hardware-Fingerprint TLV is compared 305 against the OSPFv3 Router's own router hardware fingerprint. If the 306 fingerprints are not equal, there is a duplicate Router ID conflict 307 and the OSPFv3 router with the numerically smaller router hardware 308 fingerprint MUST select a new Router ID as described in Section 7.3. 310 This new LSA is designated for information related to OSPFv3 Auto- 311 configuration and, in the future, could be used other auto- 312 configuration information, e.g., global IPv6 prefixes. However, this 313 is beyond the scope of this document. 315 7.2.1. OSPFv3 Router Auto-Configuration LSA 317 The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and 318 the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit 319 will be set indicating that the OSPFv3 AC LSA should be flooded even 320 if it is not understood. The Link State ID (LSID) value will be a 321 integer index used to discriminate between multiple AC LSAs 322 originated by the same OSPFv3 router. This specification only 323 describes the contents of an AC LSA with a Link State ID (LSID) of 0. 325 0 1 2 3 326 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 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | LS age |1|0|1| TBD | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Link State ID | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | Advertising Router | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | LS sequence number | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | LS checksum | Length | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | | 339 +- TLVs -+ 340 | ... | 342 OSPFv3 Auto-Configuration (AC) LSA 344 The format of the TLVs within the body of an AC LSA is the same as 345 the format used by the Traffic Engineering Extensions to OSPF [TE]. 346 The LSA payload consists of one or more nested Type/Length/Value 347 (TLV) triplets. The format of each TLV is: 349 0 1 2 3 350 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 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | Type | Length | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | Value... | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 TLV Format 359 The Length field defines the length of the value portion in octets 360 (thus a TLV with no value portion would have a length of 0). The TLV 361 is padded to 4-octet alignment; padding is not included in the length 362 field (so a 3-octet value would have a length of 3, but the total 363 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 364 aligned. For example, a 1-byte value would have the length field set 365 to 1, and 3 octets of padding would be added to the end of the value 366 portion of the TLV. Unrecognized types are ignored. 368 The new LSA is designated for information related to OSPFv3 Auto- 369 configuration and, in the future, can be used other auto- 370 configuration information. 372 7.2.2. Router-Hardware-Fingerprint TLV 374 The Router-Hardware-Fingerprint TLV is the first TLV defined for the 375 OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be 376 advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD 377 occur, at most, once and the first instance of the TLV will take 378 precedence over subsequent TLV instances. The length of the Router- 379 Hardware-Fingerprint is variable but must be 32 octets or greater. 381 The contents of the hardware fingerprint MUST be some combination of 382 MAC addresses, CPU ID, or serial number(s) that provides an extremely 383 high probability of uniqueness. It is RECOMMENDED that one or more 384 available universal tokens (e.g., IEEE 802 48-bit MAC addresses or 385 IEEE EUI-64 Identifiers [EUI64]) associated with the OSPFv3 router be 386 included in the hardware fingerprint. It MUST be based on hardware 387 attributes that will not change across hard and soft restarts. 389 0 1 2 3 390 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 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | 1 | >32 | 393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 394 | Router Hardware Fingerprint | 395 o 396 o 397 o 398 | | 399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 401 Router-Hardware-Fingerprint TLV Format 403 7.3. Duplicate Router ID Resolution 405 The OSPFv3 router selected to resolve the duplicate OSPFv3 Router ID 406 condition must select a new OSPFv3 Router ID. After selecting a new 407 Router ID, all self-originated LSAs MUST be reoriginated, and any 408 OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router 409 retaining the Router ID causing the conflict will reoriginate or 410 purge stale any LSAs as described in Section 13.4 [OSPFV2]. 412 7.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA' 413 Processing 415 RFC 2328 [OSPFV2], Section 13.4, describes the processing of received 416 self-originated LSAs. If the received LSA doesn't exist, the 417 receiving router will purge it from the OSPF routing domain. If the 418 LSA is newer than the version in the Link State Database (LSDB), the 419 receiving router will originate a newer version by advancing the LSA 420 sequence number and reflooding. Since it is possible for an auto- 421 configured OSPFv3 router to choose a duplicate OSPFv3 Router ID, 422 OSPFv3 routers implementing this specification should detect when 423 multiple instances of the same self-originated LSA are purged or 424 reoriginated since this is indicative of an OSPFv3 router with a 425 duplicate Router ID in the OSPFv3 routing domain. When this 426 condition is detected, the OSPFv3 router SHOULD delay self-originated 427 LSA processing for LSAs that have recently been purged or reflooded. 428 This specification recommends 10 seconds as the interval defining 429 recent self-originated LSA processing and an exponential back off of 430 1 to 8 seconds for the processing delay. This additional delay 431 should allow for the mechanisms described in Section 7 to resolve the 432 duplicate OSPFv3 Router ID conflict. 434 8. Security Considerations 436 A unique OSPFv3 Interface Instance ID is used for auto-configuration 437 to prevent inadvertent OSPFv3 adjacency formation, see Section 2 439 The goals of security and complete OSPFv3 auto-configuration are 440 somewhat contradictory. When no explicit security configuration 441 takes place, auto-configuration implies that additional devices 442 placed in the network are automatically adopted as a part of the 443 network. However, auto-configuration can also be combined with 444 password configuration (see Section 4) or future extensions for 445 automatic pairing between devices. These mechanisms can help provide 446 an automatically configured, securely routed network. 448 In deployments where stronger authentification or encryption is 449 required, OSPFv3 IPsec [OSPFV3-IPSEC] or stronger OSPFv3 450 Authentication trailer [OSPFV3-AUTH-TRAILER] algorithms MAY be used 451 at the expense of additional configuration. The configuration and 452 operational description of such deployments is beyond the scope of 453 this document. 455 9. Management Considerations 457 It is RECOMMENDED that OSPFv3 routers supporting this specification 458 also allow explicit configuration of OSPFv3 parameters as specified 459 in Appendix C of [OSPFV3]. This is in addition to the authentication 460 key configuration recommended in Section 4. However, it is 461 acknowledged that there may be some deployment scenarios where manual 462 authentication key configuration is not required. 464 Since there is a small possibility of OSPFv3 Router ID collisions, 465 manual configuration of OSPFv3 Router IDs is RECOMMENDED in OSPFv3 466 routing domains where route recovergence due to a router ID change is 467 intolerable. 469 10. IANA Considerations 471 This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto- 472 Configuration (AC) LSA, as described in Section 7.2.1. The value TBD 473 will be allocated from the existing "OSPFv3 LSA Function Code" 474 registry for the OSPFv3 Auto-Configuration LSA. 476 This specification also creates a registry for OSPFv3 Auto- 477 Configuration (AC) LSA TLVs. This registry should be placed in the 478 existing OSPFv3 IANA registry, and new values can be allocated via 479 IETF Consensus or IESG Approval. 481 Three initial values are allocated: 483 o 0 is marked as reserved. 485 o 1 is Router-Hardware-Fingerprint TLV (Section 7.2.2). 487 o 65535 is an Auto-configuration-Experiment-TLV, a common value that 488 can be used for experimental purposes. 490 11. References 492 11.1. Normative References 494 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 496 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 497 for IPv6", RFC 5340, July 2008. 499 [OSPFV3-AF] 500 Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 501 Aggarwal, "Support of Address Families in OSPFv3", RFC 502 5838, April 2010. 504 [OSPFV3-AUTH-TRAILER] 505 Bhatia, M., Manral, V., and A. Lindem, "Supporting 506 Authentication Trailer for OSPFv3", RFC 7166, February 507 2012. 509 [RFC-KEYWORDS] 510 Bradner, S., "Key words for use in RFCs to Indicate 511 Requirement Levels", RFC 2119, March 1997. 513 [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless 514 Address Autoconfiguration", RFC 4862, September 2007. 516 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 517 Extensions to OSPF", RFC 3630, September 2003. 519 11.2. Informative References 521 [ASYNC-HELLO] 522 Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold 523 Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in 524 progress), June 2013. 526 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 527 Protocol 4 (BGP-4)", RFC 4271, January 2006. 529 [EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) 530 Registration Authority", IEEE Tutorial 531 http://standards.ieee.org/regauth/oui/tutorials/ 532 EUI64.html, March 1997. 534 [IPv6-CPE] 535 Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic 536 Requirements for IPv6 Customer Edge Routers", RFC 7084, 537 November 2013. 539 [OSPFV3-IPSEC] 540 Gupta, M. and S. Melam, "Authentication/Confidentiality 541 for OSPFv3", RFC 4552, June 2006. 543 Authors' Addresses 545 Acee Lindem 546 Cisco Systems 547 301 Midenhall Way 548 Cary, NC 27513 549 USA 551 Email: acee@cisco.com 553 Jari Arkko 554 Ericsson 555 Jorvas, 02420 556 Finland 558 Email: jari.arkko@piuha.net