idnits 2.17.00 (12 Aug 2021) /tmp/idnits37212/draft-ietf-ospf-ospfv3-autoconfig-12.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5340, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5340, updated by this document, for RFC5378 checks: 2004-11-30) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 16, 2015) is 2682 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 (==), 3 comments (--). 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 Updates: 5340 (if approved) J. Arkko 5 Intended status: Standards Track Ericsson 6 Expires: July 20, 2015 January 16, 2015 8 OSPFv3 Auto-Configuration 9 draft-ietf-ospf-ospfv3-autoconfig-12.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 20, 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 Thanks to Qin Wu for Operations & Management Area Directorate review 142 and comments. 144 Thanks to Robert Sparks for General Area (GEN-ART) review and 145 comments. 147 Special thanks go to Markus Stenberg for his implementation of this 148 specification in Bird. 150 Special thanks also go to David Lamparter for his implementation of 151 this specification in Quagga. 153 The RFC text was produced using Marshall Rose's xml2rfc tool. 155 2. OSPFv3 Default Configuration 157 For complete auto-configuration, OSPFv3 will need to choose suitable 158 configuration defaults. These include: 160 1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in 161 area 0. 163 2. OSPFv3 SHOULD be auto-configured for IPv6 on all interfaces 164 intended as general IPv6-capable routers. Optionally, an 165 interface MAY be excluded if it is clear that running OSPFv3 on 166 the interface is not required. For example, if manual 167 configuration or another condition indicates that an interface is 168 connected to an Internet Service Provider (ISP) and there is no 169 Border Gateway Protocol (BGP) [BGP] peering, there is typically 170 no need to employ OSPFv3. In fact, [IPv6-CPE] specifically 171 requires that IPv6 Customer Premise Equipment (CPE) routers do 172 not initiate any dynamic routing protocol by default on the 173 router's WAN, i.e., ISP-facing, interface. In home networking 174 environments, an interface where no OSPFv3 neighbors are found 175 but a DHCP IPv6 prefix can be acquired may be considered an ISP- 176 facing interface and running OSPFv3 is unnecessary. 178 3. OSPFv3 interfaces will be auto-configured to an interface type 179 corresponding to their layer-2 capability. For example, Ethernet 180 interfaces and vanilla Wi-Fi interfaces will be auto-configured 181 as OSPFv3 broadcast networks and Point-to-Point Protocol (PPP) 182 interfaces will be auto-configured as OSPFv3 Point-to-Point 183 interfaces. Most extant OSPFv3 implementations do this already. 184 Auto-configured operation over wireless networks requiring a 185 point-to-multipoint (P2MP) topology and dynamic metrics based on 186 wireless feedback is not within the scope of this document. 187 However, auto-configuration is not precluded in these 188 environments. 190 4. OSPFv3 interfaces MAY use an arbitrary HelloInterval and 191 RouterDeadInterval as specified in Section 3. Of course, an 192 identical HelloInterval and RouterDeadInterval will still be 193 required to form an adjacency with an OSPFv3 router not 194 supporting auto-configuration [OSPFV3]. 196 5. All OSPFv3 interfaces SHOULD be auto-configured to use an 197 Interface Instance ID of 0 that corresponds to the base IPv6 198 unicast address family instance ID as defined in [OSPFV3-AF]. 199 Similarly, if IPv4 unicast addresses are advertised in a separate 200 auto-configured OSPFv3 instance, the base IPv4 unicast address 201 family instance ID value, i.e., 64, SHOULD be auto-configured as 202 the Interface Instance ID for all interfaces corresponding to the 203 IPv4 unicast OSPFv3 instance [OSPFV3-AF]. 205 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility 207 Auto-configured OSPFv3 routers will not require an identical 208 HelloInterval and RouterDeadInterval to form adjacencies. Rather, 209 the received HelloInterval will be ignored and the received 210 RouterDeadInterval will be used to determine OSPFv3 liveliness with 211 the sending router. In other words, the Neighbor Inactivity Timer 212 (Section 10 of [OSPFV2]) for each neighbor will reflect that 213 neighbor's advertised RouterDeadInterval and MAY be different from 214 other OSPFv3 routers on the link without impacting adjacency 215 formation. A similar mechanism requiring additional signaling is 216 proposed for all OSPFv2 and OSPFv3 routers [ASYNC-HELLO]. 218 3.1. Wait Timer Reduction 220 In many situations, auto-configured OSPFv3 routers will be deployed 221 in environments where back-to-back ethernet connections are utilized. 222 When this is the case, an OSPFv3 broadcast interface will not come up 223 until the other OSPFv3 router is connected and the routers will wait 224 RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In 225 order to reduce this delay, an auto-configured OSPFv3 router MAY 226 reduce the wait interval to a value no less than (HelloInterval + 1). 227 Reducing the setting will slightly increase the likelihood of the 228 Designated Router (DR) flapping but is preferable to the long 229 adjacency formation delay. Note that this value is not included in 230 OSPFv3 Hello packets and does not impact interoperability. 232 4. OSPFv3 Minimal Authentication Configuration 234 In many deployments, the requirement for OSPFv3 authentication 235 overrides the goal of complete OSPFv3 autoconfiguration. Therefore, 236 it is RECOMMENDED that OSPFv3 routers supporting this specification 237 minimally offer an option to explicitly configure a single password 238 for HMAC-SHA authentication as described in [OSPFV3-AUTH-TRAILER]. 239 When configured, the password will be used on all auto-configured 240 interfaces with the Security Association Identifier (SA ID) set to 1 241 and HMAC-SHA-256 used as the authentication algorithm. 243 5. OSPFv3 Router ID Selection 245 An OSPFv3 router requires a unique Router ID within the OSPFv3 246 routing domain for correct protocol operation. An OSPFv3 router 247 implementing this specification will select a router-id that has a 248 high probability of uniqueness. A pseudo-random number SHOULD be 249 used for the OSPFv3 Router ID. The generation SHOULD be seeded with 250 a variable that is likely to be unique in the applicable OSPFv3 251 router deployment. A good choice of seed would be some portion or 252 hash of the Router-Hardware-Fingerprint as described in 253 Section 7.2.2. 255 Since there is a possibility of a Router ID collision, duplicate 256 Router ID detection and resolution are required as described in 257 Section 7 and Section 7.3. OSPFv3 routers SHOULD maintain the last 258 successfully chosen Router ID in non-volatile storage to avoid 259 collisions subsequent to when an autoconfigured OSPFv3 router is 260 first added to the OSPFv3 routing domain. 262 6. OSPFv3 Adjacency Formation 264 Since OSPFv3 uses IPv6 link-local addresses for all protocol messages 265 other than messages sent on virtual links (which are not applicable 266 to auto-configuration), OSPFv3 adjacency formation can proceed as 267 soon as a Router ID has been selected and the IPv6 link-local address 268 has completed Duplicate Address Detection (DAD) as specified in IPv6 269 Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only 270 changes to the OSPFv3 base specification are supporting 271 HelloInterval/RouterDeadInterval flexibility as described in 272 Section 3 and duplicate Router ID detection and resolution as 273 described in Section 7 and Section 7.3. 275 7. OSPFv3 Duplicate Router ID Detection and Resolution 277 There are two cases of duplicate OSPFv3 Router ID detection. One 278 where the OSPFv3 router with the duplicate Router ID is directly 279 connected and one where it is not. In both cases, the duplicate 280 resolution is for one of the routers to select a new OSPFv3 Router 281 ID. 283 7.1. Duplicate Router ID Detection for Neighbors 285 In this case, a duplicate Router ID is detected if any valid OSPFv3 286 packet is received with the same OSPFv3 Router ID but a different 287 IPv6 link-local source address. Once this occurs, the OSPFv3 router 288 with the numerically smaller IPv6 link-local address will need to 289 select a new Router ID as described in Section 7.3. Note that the 290 fact that the OSPFv3 router is a neighbor on a non-virtual interface 291 implies that the router is directly connected. An OSPFv3 router 292 implementing this specification should assure that the inadvertent 293 connection of multiple router interfaces to the same physical link is 294 not misconstrued as detection of an OSPFv3 neighbor with a duplicate 295 Router ID. 297 7.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 298 Neighbors 300 OSPFv3 routers implementing auto-configuration, as specified herein, 301 MUST originate an Auto-Configuration (AC) Link State Advertisement 302 (LSA) including the Router-Hardware-Fingerprint Type-Length-Value 303 (TLV). The Router-Hardware-Fingerprint TLV contains a variable 304 length value that has a very high probability of uniquely identifying 305 the advertising OSPFv3 router. An OSPFv3 router implementing this 306 specification MUST detect received Auto-Configuration LSAs with its 307 Router ID specified in the LSA header. LSAs received with the local 308 OSPFv3 Router's Router ID in the LSA header are perceived as self- 309 originated (see section 4.6 of [OSPFV3]). In these received Auto- 310 Configuration LSAs, the Router-Hardware-Fingerprint TLV is compared 311 against the OSPFv3 Router's own router hardware fingerprint. If the 312 fingerprints are not equal, there is a duplicate Router ID conflict 313 and the OSPFv3 router with the numerically smaller router hardware 314 fingerprint MUST select a new Router ID as described in Section 7.3. 316 This new LSA is designated for information related to OSPFv3 Auto- 317 configuration and, in the future, could be used for other auto- 318 configuration information, e.g., global IPv6 prefixes. However, this 319 is beyond the scope of this document. 321 7.2.1. OSPFv3 Router Auto-Configuration LSA 323 The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and 324 the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit 325 will be set indicating that the OSPFv3 AC LSA should be flooded even 326 if it is not understood. The Link State ID (LSID) value will be a 327 integer index used to discriminate between multiple AC LSAs 328 originated by the same OSPFv3 router. This specification only 329 describes the contents of an AC LSA with a Link State ID (LSID) of 0. 331 0 1 2 3 332 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 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | LS age |1|0|1| TBD | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Link State ID | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | Advertising Router | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | LS sequence number | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | LS checksum | Length | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | | 345 +- TLVs -+ 346 | ... | 348 OSPFv3 Auto-Configuration (AC) LSA 350 The format of the TLVs within the body of an AC LSA is the same as 351 the format used by the Traffic Engineering Extensions to OSPF [TE]. 352 The LSA payload consists of one or more nested Type/Length/Value 353 (TLV) triplets. The format of each TLV is: 355 0 1 2 3 356 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 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | Type | Length | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | Value... | 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 TLV Format 365 The Length field defines the length of the value portion in octets 366 (thus a TLV with no value portion would have a length of 0). The TLV 367 is padded to 4-octet alignment; padding is not included in the length 368 field (so a 3-octet value would have a length of 3, but the total 369 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 370 aligned. For example, a 1-byte value would have the length field set 371 to 1, and 3 octets of padding would be added to the end of the value 372 portion of the TLV. Unrecognized types are ignored. 374 The new LSA is designated for information related to OSPFv3 Auto- 375 configuration and, in the future, can be used other auto- 376 configuration information. 378 7.2.2. Router-Hardware-Fingerprint TLV 380 The Router-Hardware-Fingerprint TLV is the first TLV defined for the 381 OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be 382 advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD 383 occur, at most, once and the first instance of the TLV will take 384 precedence over subsequent TLV instances. The length of the Router- 385 Hardware-Fingerprint is variable but must be 32 octets or greater. 387 The contents of the hardware fingerprint MUST be some combination of 388 MAC addresses, CPU ID, or serial number(s) that provides an extremely 389 high probability of uniqueness. It is RECOMMENDED that one or more 390 available universal tokens (e.g., IEEE 802 48-bit MAC addresses or 391 IEEE EUI-64 Identifiers [EUI64]) associated with the OSPFv3 router be 392 included in the hardware fingerprint. It MUST be based on hardware 393 attributes that will not change across hard and soft restarts. 395 0 1 2 3 396 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 397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 398 | 1 | >32 | 399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 400 | Router Hardware Fingerprint | 401 o 402 o 403 o 404 | | 405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 407 Router-Hardware-Fingerprint TLV Format 409 7.3. Duplicate Router ID Resolution 411 The OSPFv3 router selected to resolve the duplicate OSPFv3 Router ID 412 condition must select a new OSPFv3 Router ID. After selecting a new 413 Router ID, all self-originated LSAs MUST be reoriginated, and any 414 OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router 415 retaining the Router ID causing the conflict will reoriginate or 416 purge stale any LSAs as described in Section 13.4 [OSPFV2]. 418 7.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA' 419 Processing 421 RFC 2328 [OSPFV2], Section 13.4, describes the processing of received 422 self-originated LSAs. If the received LSA doesn't exist, the 423 receiving router will purge it from the OSPF routing domain. If the 424 LSA is newer than the version in the Link State Database (LSDB), the 425 receiving router will originate a newer version by advancing the LSA 426 sequence number and reflooding. Since it is possible for an auto- 427 configured OSPFv3 router to choose a duplicate OSPFv3 Router ID, 428 OSPFv3 routers implementing this specification should detect when 429 multiple instances of the same self-originated LSA are purged or 430 reoriginated since this is indicative of an OSPFv3 router with a 431 duplicate Router ID in the OSPFv3 routing domain. When this 432 condition is detected, the OSPFv3 router SHOULD delay self-originated 433 LSA processing for LSAs that have recently been purged or reflooded. 434 This specification recommends 10 seconds as the interval defining 435 recent self-originated LSA processing and an exponential back off of 436 1 to 8 seconds for the processing delay. This additional delay 437 should allow for the mechanisms described in Section 7 to resolve the 438 duplicate OSPFv3 Router ID conflict. 440 8. Security Considerations 442 A unique OSPFv3 Interface Instance ID is used for auto-configuration 443 to prevent inadvertent OSPFv3 adjacency formation, see Section 2 445 The goals of security and complete OSPFv3 auto-configuration are 446 somewhat contradictory. When no explicit security configuration 447 takes place, auto-configuration implies that additional devices 448 placed in the network are automatically adopted as a part of the 449 network. However, auto-configuration can also be combined with 450 password configuration (see Section 4) or future extensions for 451 automatic pairing between devices. These mechanisms can help provide 452 an automatically configured, securely routed network. 454 In deployments where stronger authentification or encryption is 455 required, OSPFv3 IPsec [OSPFV3-IPSEC] or stronger OSPFv3 456 Authentication trailer [OSPFV3-AUTH-TRAILER] algorithms MAY be used 457 at the expense of additional configuration. The configuration and 458 operational description of such deployments is beyond the scope of 459 this document. 461 9. Management Considerations 463 It is RECOMMENDED that OSPFv3 routers supporting this specification 464 also allow explicit configuration of OSPFv3 parameters as specified 465 in Appendix C of [OSPFV3]. The would allow explicit override of 466 autoconfigured parameters in situations where it is required (e.g., 467 if the deployment requires multiple OSPFv3 areas). This is in 468 addition to the authentication key configuration recommended in 469 Section 4 which supports OSPFv3 authentication with the absolute 470 minimum manual configuration. 472 Since there is a small possibility of OSPFv3 Router ID collisions, 473 manual configuration of OSPFv3 Router IDs is RECOMMENDED in OSPFv3 474 routing domains where route recovergence due to a router ID change is 475 intolerable. 477 10. IANA Considerations 479 This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto- 480 Configuration (AC) LSA, as described in Section 7.2.1. The value TBD 481 will be allocated from the existing "OSPFv3 LSA Function Code" 482 registry for the OSPFv3 Auto-Configuration LSA. 484 This specification also creates a registry for OSPFv3 Auto- 485 Configuration (AC) LSA TLVs. This registry should be placed in the 486 existing OSPFv3 IANA registry, and new values can be allocated via 487 IETF Consensus or IESG Approval. 489 Three initial values are allocated: 491 o 0 is marked as reserved. 493 o 1 is Router-Hardware-Fingerprint TLV (Section 7.2.2). 495 o 65535 is an Auto-configuration-Experiment-TLV, a common value that 496 can be used for experimental purposes. 498 11. References 500 11.1. Normative References 502 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 504 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 505 for IPv6", RFC 5340, July 2008. 507 [OSPFV3-AF] 508 Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 509 Aggarwal, "Support of Address Families in OSPFv3", RFC 510 5838, April 2010. 512 [OSPFV3-AUTH-TRAILER] 513 Bhatia, M., Manral, V., and A. Lindem, "Supporting 514 Authentication Trailer for OSPFv3", RFC 7166, February 515 2012. 517 [RFC-KEYWORDS] 518 Bradner, S., "Key words for use in RFCs to Indicate 519 Requirement Levels", RFC 2119, March 1997. 521 [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless 522 Address Autoconfiguration", RFC 4862, September 2007. 524 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 525 Extensions to OSPF", RFC 3630, September 2003. 527 11.2. Informative References 529 [ASYNC-HELLO] 530 Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold 531 Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in 532 progress), June 2013. 534 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 535 Protocol 4 (BGP-4)", RFC 4271, January 2006. 537 [EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) 538 Registration Authority", IEEE Tutorial 539 http://standards.ieee.org/regauth/oui/tutorials/ 540 EUI64.html, March 1997. 542 [IPv6-CPE] 543 Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic 544 Requirements for IPv6 Customer Edge Routers", RFC 7084, 545 November 2013. 547 [OSPFV3-IPSEC] 548 Gupta, M. and S. Melam, "Authentication/Confidentiality 549 for OSPFv3", RFC 4552, June 2006. 551 Authors' Addresses 553 Acee Lindem 554 Cisco Systems 555 301 Midenhall Way 556 Cary, NC 27513 557 USA 559 Email: acee@cisco.com 561 Jari Arkko 562 Ericsson 563 Jorvas, 02420 564 Finland 566 Email: jari.arkko@piuha.net