idnits 2.17.00 (12 Aug 2021) /tmp/idnits35033/draft-ietf-ospf-ospfv3-autoconfig-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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 10, 2014) is 2841 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 6506 (ref. 'OSPFV3-AUTH-TRAILER') (Obsoleted by RFC 7166) -- Obsolete informational reference (is this intentional?): RFC 6204 (ref. 'IPv6-CPE') (Obsoleted by RFC 7084) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 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 Intended status: Standards Track J. Arkko 5 Expires: February 11, 2015 Ericsson 6 August 10, 2014 8 OSPFv3 Auto-Configuration 9 draft-ietf-ospf-ospfv3-autoconfig-07.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 February 11, 2015. 36 Copyright Notice 38 Copyright (c) 2014 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 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 67 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 68 2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5 69 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 7 70 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 7 71 4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 8 72 5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 9 73 6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 10 74 6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 10 75 6.2. Duplicate Router ID Detection for OSPFv3 Routers that 76 are not Neighbors . . . . . . . . . . . . . . . . . . . . 10 77 6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 10 78 6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 12 79 6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 13 80 6.4. Change to RFC 2328 Section 13.4, 'Receiving 81 Self-Originated LSA' Processing . . . . . . . . . . . . . 13 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 83 8. Management Considerations . . . . . . . . . . . . . . . . . . 15 84 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 85 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 86 10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 87 10.2. Informative References . . . . . . . . . . . . . . . . . . 17 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 90 1. Introduction 92 OSPFv3 [OSPFV3] is a candidate for deployments in environments where 93 auto-configuration is a requirement. Its operation is largely 94 unchanged from the base OSPFv3 protocol specification [OSPFV3]. 96 The following aspects of OSPFv3 auto-configuration are described: 98 1. Default OSPFv3 Configuration 100 2. HelloInterval/RouterDeadInterval Flexibility 102 3. Unique OSPFv3 Router-ID generation 104 4. OSPFv3 Adjacency Formation 106 5. Duplicate OSPFv3 Router-ID Resolution 108 1.1. Requirements notation 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in [RFC-KEYWORDS]. 114 1.2. Acknowledgments 116 This specification was inspired by the work presented in the Homenet 117 working group meeting in October 2011 in Philadelphia, Pennsylvania. 118 In particular, we would like to thank Fred Baker, Lorenzo Colitti, 119 Ole Troan, Mark Townsley, and Michael Richardson. 121 Arthur Dimitrelis and Aidan Williams did prior work in OSPFv3 auto- 122 configuration in the expired "Autoconfiguration of routers using a 123 link state routing protocol" IETF Draft. There are many similarities 124 between the concepts and techniques in this document. 126 Thanks for Abhay Roy and Manav Bhatia for comments regarding 127 duplicate router-id processing. 129 Thanks for Alvaro Retana and Michael Barnes for comments regarding 130 OSPFv3 Instance ID auto-configuration. 132 Thanks to Faraz Shamim for review and comments. 134 Thanks to Mark Smith for the requirement to reduce the adjacency 135 formation delay in the back-to-back ethernet topologies that are 136 prevalent in home networks. 138 Thanks to Les Ginsberg for document review and recommendations on 139 OSPFv3 hardware fingerprint content. 141 Thanks to Curtis Villamizar for document review and analysis of 142 duplicate router-id resolution nuances. 144 The RFC text was produced using Marshall Rose's xml2rfc tool. 146 Special thanks go to Markus Stenberg for his implementation of this 147 specification. 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 on 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 Router ID Selection 228 As OSPFv3 Router implementing this specification must select a unique 229 Router ID. A pseudo-random number SHOULD be used for the OSPFv3 230 Router ID. The generation should be seeded with a variable that is 231 likely to be unique in the applicable OSPFv3 router deployment. A 232 good choice of seed would be some portion or hash of the Router- 233 Hardware-Fingerprint as described in Section 6.2.2. 235 Since there is a possibility of a Router ID collision, duplicate 236 Router ID detection and resolution are required as described in 237 Section 6 and Section 6.3. OSPFv3 Routers SHOULD maintain the last 238 successfully chosen Router ID in non-volatile storage to avoid 239 collisions subsequent to when an autoconfigured OSPFv3 router is 240 first added to the OSPFv3 routing domain. 242 5. OSPFv3 Adjacency Formation 244 Since OSPFv3 uses IPv6 link-local addresses for all protocol messages 245 other than messages sent on virtual links (which are not applicable 246 to auto-configuration), OSPFv3 adjacency formation can proceed as 247 soon as a Router ID has been selected and the IPv6 link-local address 248 has completed Duplicate Address Detection (DAD) as specified in IPv6 249 Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only 250 changes to the OSPFv3 base specification are supporting 251 HelloInterval/RouterDeadInterval flexibility as described in 252 Section 3 and duplicate Router ID detection and resolution as 253 described in Section 6 and Section 6.3. 255 6. OSPFv3 Duplicate Router ID Detection and Resolution 257 There are two cases of duplicate OSPFv3 Router ID detection. One 258 where the OSPFv3 router with the duplicate Router ID is directly 259 connected and one where it is not. In both cases, the duplicate 260 resolution is for one of the routers to select a new OSPFv3 Router 261 ID. 263 6.1. Duplicate Router ID Detection for Neighbors 265 In this case, a duplicate Router ID is detected if any valid OSPFv3 266 packet is received with the same OSPFv3 Router ID but a different 267 IPv6 link-local source address. Once this occurs, the OSPFv3 router 268 with the numerically smaller IPv6 link-local address will need to 269 select a new Router ID as described in Section 6.3. Note that the 270 fact that the OSPFv3 router is a neighbor on a non-virtual interface 271 implies that the router is directly connected. An OSPFv3 router 272 implementing this specification should assure that the inadvertent 273 connection of multiple router interfaces to the same physical link is 274 not misconstrued as detection of an OSPFv3 neighbor with a duplicate 275 Router ID. 277 6.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 278 Neighbors 280 OSPFv3 Routers implementing auto-configuration, as specified herein, 281 MUST originate an Auto-Configuration (AC) Link State Advertisement 282 (LSA) including the Router-Hardware-Fingerprint Type-Length-Value 283 (TLV). The Router-Hardware-Fingerprint TLV contains a variable 284 length value that has a very high probability of uniquely identifying 285 the advertising OSPFv3 router. An OSPFv3 router implementing this 286 specification MUST compare a received self-originated Auto- 287 Configuration LSA's Router-Hardware-Fingerprint TLV against its own 288 router hardware fingerprint. If the fingerprints are not equal, 289 there is a duplicate Router ID conflict and the OSPFv3 Router with 290 the numerically smaller router hardware fingerprint MUST select a new 291 Router ID as described in Section 6.3. 293 This new LSA is designated for information related to OSPFv3 Auto- 294 configuration and, in the future, could be used other auto- 295 configuration information, e.g., global IPv6 prefixes. However, this 296 is beyond the scope of this document. 298 6.2.1. OSPFv3 Router Auto-Configuration LSA 300 The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and 301 the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit 302 will be set indicating that the OSPFv3 AC LSA should be flooded even 303 if it is not understood. The Link State ID (LSID) value will be a 304 integer index used to discriminate between multiple AC LSAs 305 originated by the same OSPFv3 Router. This specification only 306 describes the contents of an AC LSA with a Link State ID (LSID) of 0. 308 0 1 2 3 309 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 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | LS age |1|0|1| TBD | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 | Link State ID | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | Advertising Router | 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 | LS sequence number | 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 | LS checksum | Length | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | | 322 +- TLVs -+ 323 | ... | 325 OSPFv3 Auto-Configuration (AC) LSA 327 The format of the TLVs within the body of an AC LSA is the same as 328 the format used by the Traffic Engineering Extensions to OSPF [TE]. 329 The LSA payload consists of one or more nested Type/Length/Value 330 (TLV) triplets. The format of each TLV is: 332 0 1 2 3 333 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 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | Type | Length | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Value... | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 TLV Format 342 The Length field defines the length of the value portion in octets 343 (thus a TLV with no value portion would have a length of 0). The TLV 344 is padded to 4-octet alignment; padding is not included in the length 345 field (so a 3-octet value would have a length of 3, but the total 346 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 347 aligned. For example, a 1-byte value would have the length field set 348 to 1, and 3 octets of padding would be added to the end of the value 349 portion of the TLV. Unrecognized types are ignored. 351 The new LSA is designated for information related to OSPFv3 Auto- 352 configuration and, in the future, can be used other auto- 353 configuration information. 355 6.2.2. Router-Hardware-Fingerprint TLV 357 The Router-Hardware-Fingerprint TLV is the first TLV defined for the 358 OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be 359 advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD 360 occur, at most, once and the first instance of the TLV will take 361 precedence over subsequent TLV instances. The length of the Router- 362 Hardware-Fingerprint is variable but must be 32 octets or greater. 364 The contents of the hardware fingerprint MUST be some combination of 365 MAC addresses, CPU ID, or serial number(s) that provides an extremely 366 high probability of uniqueness. It is RECOMMENDED that one or more 367 available universal tokens (e.g., IEEE 802 48-bit MAC addresses or 368 IEEE EUI-64 Identifiers [EUI64]) associated with the OSPFv3 router be 369 included in the hardware fingerprint. It MUST be based on hardware 370 attributes that will not change across hard and soft restarts. 372 0 1 2 3 373 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 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 | 1 | >32 | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Router Hardware Fingerprint | 378 o 379 o 380 o 381 | | 382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 Router-Hardware-Fingerprint TLV Format 386 6.3. Duplicate Router ID Resolution 388 The OSPFv3 Router selected to resolve the duplicate OSPFv3 Router ID 389 condition must select a new OSPFv3 Router ID. After selecting a new 390 Router ID, all self-originated LSAs MUST be reoriginated, and any 391 OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router 392 retaining the Router ID causing the conflict will reoriginate or 393 purge stale any LSAs as described in Section 13.4 [OSPFV2]. 395 6.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA' 396 Processing 398 RFC 2328 [OSPFV2], Section 13.4, describes the processing of received 399 self-originated LSAs. If the received LSA doesn't exist, the 400 receiving router will purge it from the OSPF routing domain. If the 401 LSA is newer than the version in the Link State Database (LSDB), the 402 receiving router will originate a newer version by advancing the LSA 403 sequence number and reflooding. Since it is possible for an auto- 404 configured OSPFv3 router to choose a duplicate OSPFv3 Router ID, 405 OSPFv3 routers implementing this specification should detect when 406 multiple instances of the same self-originated LSA are purged or 407 reoriginated since this is indicative of an OSPFv3 router with a 408 duplicate Router ID in the OSPFv3 routing domain. When this 409 condition is detected, the OSPFv3 Router SHOULD delay self-originated 410 LSA processing for LSAs that have recently been purged or reflooded. 411 This specification recommends 10 seconds as the interval defining 412 recent self-originated LSA processing and an exponential back off of 413 1 to 8 seconds for the processing delay. This additional delay 414 should allow for the mechanisms described in Section 6 to resolve the 415 duplicate OSPFv3 Router ID conflict. 417 7. Security Considerations 419 A unique OSPFv3 Interface Instance ID is used for auto-configuration 420 to prevent inadvertent OSPFv3 adjacency formation, see Section 2 422 The goals of security and complete OSPFv3 auto-configuration are 423 somewhat contradictory. When no explicit security configuration 424 takes place, auto-configuration implies that additional devices 425 placed in the network are automatically adopted as a part of the 426 network. However, auto-configuration can also be combined with 427 password configuration (see below) or future extensions for automatic 428 pairing between devices. These mechanisms can help provide an 429 automatically configured, securely routed network. 431 It is RECOMMENDED that OSPFv3 routers supporting this specification 432 also offer an option to explicitly configure a password for HMAC-SHA 433 authentication as described in [OSPFV3-AUTH-TRAILER]. When 434 configured, the password will be used on all auto-configured 435 interfaces with the Security Association Identifier (SA ID) set to 1 436 and HMAC-SHA-256 used as the authentication algorithm. 438 8. Management Considerations 440 It is RECOMMENDED that OSPFv3 routers supporting this specification 441 also allow explicit configuration of OSPFv3 parameters as specified 442 in Appendix C of [OSPFV3]. This is in addition to the authentication 443 key configuration recommended in Section 7. However, it is 444 acknowledged that there may be some deployment scenarios where manual 445 authentication key configuration is not required. 447 Since there is a small possibility of OSPFv3 Router ID collisions, 448 manual configuration of OSPFv3 Router-IDs is RECOMMENDED in OSPFv3 449 routing domains where route recovergence due to a router ID change is 450 intolerable. 452 9. IANA Considerations 454 This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto- 455 Configuration (AC) LSA, as described in Section 6.2.1. The value TBD 456 will be allocated from the existing "OSPFv3 LSA Function Code" 457 registry for the OSPFv3 Auto-Configuration LSA. 459 This specification also creates a registry for OSPFv3 Auto- 460 Configuration (AC) LSA TLVs. This registry should be placed in the 461 existing OSPFv3 IANA registry, and new values can be allocated via 462 IETF Consensus or IESG Approval. 464 Three initial values are allocated: 466 o 0 is marked as reserved. 468 o 1 is Router-Hardware-Fingerprint TLV (Section 6.2.2). 470 o 65535 is an Auto-configuration-Experiment-TLV, a common value that 471 can be used for experimental purposes. 473 10. References 475 10.1. Normative References 477 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 479 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 480 for IPv6", RFC 5340, July 2008. 482 [OSPFV3-AF] 483 Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 484 Aggarwal, "Support of Address Families in OSPFv3", 485 RFC 5838, April 2010. 487 [OSPFV3-AUTH-TRAILER] 488 Bhatia, M., Manral, V., and A. Lindem, "Supporting 489 Authentication Trailer for OSPFv3", RFC 6506, 490 February 2012. 492 [RFC-KEYWORDS] 493 Bradner, S., "Key words for use in RFCs to Indicate 494 Requirement Levels", RFC 2119, March 1997. 496 [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless 497 Address Autoconfiguration", RFC 4862, September 2007. 499 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 500 Extensions to OSPF", RFC 3630, September 2003. 502 10.2. Informative References 504 [ASYNC-HELLO] 505 Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold 506 Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in 507 progress). 509 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 510 Protocol 4 (BGP-4)", RFC 4271, January 2006. 512 [EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) 513 Registration Authority", IEEE Tutorial http:// 514 standards.ieee.org/regauth/oui/tutorials/EUI64.html, 515 March 1997. 517 [IPv6-CPE] 518 Singh, H., Beebee, W., Donley, C., Stark, B., and O. 519 Troan, "Basic Requirements for IPv6 Customer Edge 520 Routers", RFC 6204, April 2011. 522 Authors' Addresses 524 Acee Lindem 525 Cisco Systems 526 301 Midenhall Way 527 Cary, NC 27513 528 USA 530 Email: acee@cisco.com 532 Jari Arkko 533 Ericsson 534 Jorvas, 02420 535 Finland 537 Email: jari.arkko@piuha.net