idnits 2.17.00 (12 Aug 2021) /tmp/idnits38741/draft-ietf-ospf-ospfv3-autoconfig-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document 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 (October 20, 2013) is 3135 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 J. Arkko 4 Intended status: Standards Track Ericsson 5 Expires: April 23, 2014 October 20, 2013 7 OSPFv3 Auto-Configuration 8 draft-ietf-ospf-ospfv3-autoconfig-05.txt 10 Abstract 12 OSPFv3 is a candidate for deployments in environments where auto- 13 configuration is a requirement. One such environment is the IPv6 14 home network where users expect to simply plug in a router and have 15 it automatically use OSPFv3 for intra-domain routing. This document 16 describes the necessary mechanisms for OSPFv3 to be self-configuring. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 23, 2014. 35 Copyright Notice 37 Copyright (c) 2013 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 52 10, 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 55 Without obtaining an adequate license from the person(s) controlling 56 the copyright in such materials, this document may not be modified 57 outside the IETF Standards Process, and derivative works of it may 58 not be created outside the IETF Standards Process, except to format 59 it for publication as an RFC or to translate it into languages other 60 than English. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 66 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 67 2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5 68 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 7 69 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 7 70 4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 8 71 5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 9 72 6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 10 73 6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 10 74 6.2. Duplicate Router ID Detection for OSPFv3 Routers that 75 are not Neighbors . . . . . . . . . . . . . . . . . . . . 10 76 6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 10 77 6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 12 78 6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 12 79 6.4. Change to RFC 2328 Section 13.4, 'Receiving 80 Self-Originated LSA' Processing . . . . . . . . . . . . . 13 81 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 82 8. Management Considerations . . . . . . . . . . . . . . . . . . 15 83 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 84 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 85 10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 86 10.2. Informative References . . . . . . . . . . . . . . . . . . 17 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 89 1. Introduction 91 OSPFv3 [OSPFV3] is a candidate for deployments in environments where 92 auto-configuration is a requirement. Its operation is largely 93 unchanged from the base OSPFv3 protocol specification [OSPFV3]. 95 The following aspects of OSPFv3 auto-configuration are described: 97 1. Default OSPFv3 Configuration 99 2. HelloInterval/RouterDeadInterval Flexibility 101 3. Unique OSPFv3 Router-ID generation 103 4. OSPFv3 Adjacency Formation 105 5. Duplicate OSPFv3 Router-ID Resolution 107 1.1. Requirements notation 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 111 document are to be interpreted as described in [RFC-KEYWORDS]. 113 1.2. Acknowledgments 115 This specification was inspired by the work presented in the Homenet 116 working group meeting in October 2011 in Philadelphia, Pennsylvania. 117 In particular, we would like to thank Fred Baker, Lorenzo Colitti, 118 Ole Troan, Mark Townsley, and Michael Richardson. 120 Arthur Dimitrelis and Aidan Williams did prior work in OSPFv3 auto- 121 configuration in the expired "Autoconfiguration of routers using a 122 link state routing protocol" IETF Draft. There are many similarities 123 between the concepts and techniques in this document. 125 Thanks for Abhay Roy and Manav Bhatia for comments regarding 126 duplicate router-id processing. 128 Thanks for Alvaro Retana and Michael Barnes for comments regarding 129 OSPFv3 Instance ID auto-configuration. 131 Thanks to Faraz Shamim for review and comments. 133 Thanks to Mark Smith for the requirement to reduce the adjacency 134 formation delay in the back-to-back ethernet topologies that are 135 prevalent in home networks. 137 The RFC text was produced using Marshall Rose's xml2rfc tool. 139 Special thanks go to Markus Stenberg for his implementation of this 140 specification. 142 2. OSPFv3 Default Configuration 144 For complete auto-configuration, OSPFv3 will need to choose suitable 145 configuration defaults. These include: 147 1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in 148 area 0. 150 2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces 151 intended as general IPv6-capable routers. Optionally, an 152 interface MAY be excluded if it is clear that running OSPFv3 on 153 the interface is not required. For example, if manual 154 configuration or another condition indicates that an interface is 155 connected to an Internet Service Provider (ISP) and there is no 156 Border Gateway Protocol (BGP) [BGP] peering, there is typically 157 no need to employ OSPFv3. In fact, [IPv6-CPE] specifically 158 requires that IPv6 Customer Premise Equipment (CPE) routers do 159 not initiate any dynamic routing protocol by default on the 160 router's WAN, i.e., ISP-facing, interface. In home networking 161 environments, an interface where no OSPFv3 neighbors are found 162 but a DHCP IPv6 prefix can be acquired may be considered an ISP- 163 facing interface and running OSPFv3 is unnecessary. 165 3. OSPFv3 interfaces will be auto-configured to an interface type 166 corresponding to their layer-2 capability. For example, Ethernet 167 interfaces and vanilla Wi-Fi interfaces will be auto-configured 168 as OSPFv3 broadcast networks and Point-to-Point Protocol (PPP) 169 interfaces will be auto-configured as OSPFv3 Point-to-Point 170 interfaces. Most extant OSPFv3 implementations do this already. 171 Auto-configured operation over wireless networks requiring a 172 point-to-multipoint (P2MP) topology and dynamic metrics based on 173 wireless feedback is not within the scope of this document. 174 However, auto-configuration is not precluded in these 175 environments. 177 4. OSPFv3 interfaces MAY use an arbitrary HelloInterval and 178 RouterDeadInterval as specified in Section 3. Of course, an 179 identical HelloInterval and RouterDeadInterval will still be 180 required to form an adjacency with an OSPFv3 router not 181 supporting auto-configuration [OSPFV3]. 183 5. All OSPFv3 interfaces SHOULD be auto-configured to use an 184 Interface Instance ID of 0 that corresponds to the base IPv6 185 unicast address family instance ID as defined in [OSPFV3-AF]. 186 Similarly, if IPv4 unicast addresses are advertised in a separate 187 auto-configured OSPFv3 instance, the base IPv4 unicast address 188 family instance ID value, i.e., 64, SHOULD be auto-configured as 189 the Interface Instance ID for all interfaces corresponding to the 190 IPv4 unicast OSPFv3 instance [OSPFV3-AF]. 192 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility 194 Auto-configured OSPFv3 routers will not require an identical 195 HelloInterval and RouterDeadInterval to form adjacencies. Rather, 196 the received HelloInterval will be ignored and the received 197 RouterDeadInterval will be used to determine OSPFv3 liveliness with 198 the sending router. In other words, the Neighbor Inactivity Timer 199 (Section 10 of [OSPFV2]) for each neighbor will reflect that 200 neighbor's advertised RouterDeadInterval and MAY be different from 201 other OSPFv3 routers on the link without impacting adjacency 202 formation. A similar mechanism requiring additional signaling is 203 proposed for all OSPFv2 and OSPFv3 routers [ASYNC-HELLO]. 205 3.1. Wait Timer Reduction 207 In many situations, auto-configured OSPFv3 routers will be deployed 208 in environments where back-to-back ethernet connections are utilized. 209 When this is the case, an OSPFv3 broadcast interface will not come up 210 until the other OSPFv3 router is connected and the routers will wait 211 RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In 212 order to reduce this delay, an auto-configured OSPFv3 router MAY 213 reduce the wait interval to a value no less than (HelloInterval + 1). 214 Reducing the setting will slightly increase the likelihood of the 215 Designated Router (DR) flapping but is preferable to the long 216 adjacency formation delay. Note that this value is not included in 217 OSPFv3 Hello packets and does not impact interoperability. 219 4. OSPFv3 Router ID Selection 221 As OSPFv3 Router implementing this specification must select a unique 222 Router ID. A pseudo-random number SHOULD be used for the OSPFv3 223 Router ID. The generation should be seeded with a variable that is 224 likely to be unique in the applicable OSPFv3 router deployment. A 225 good choice of seed would be some portion or hash of the Route- 226 Hardware-Fingerprint as described in Section 6.2.2. 228 Since there is a possibility of a Router ID collision, duplicate 229 Router ID detection and resolution are required as described in 230 Section 6 and Section 6.3. 232 5. OSPFv3 Adjacency Formation 234 Since OSPFv3 uses IPv6 link-local addresses for all protocol messages 235 other than messages sent on virtual links (which are not applicable 236 to auto-configuration), OSPFv3 adjacency formation can proceed as 237 soon as a Router ID has been selected and the IPv6 link-local address 238 has completed Duplicate Address Detection (DAD) as specified in IPv6 239 Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only 240 changes to the OSPFv3 base specification are supporting 241 HelloInterval/RouterDeadInterval flexibility as described in 242 Section 3 and duplicate Router ID detection and resolution as 243 described in Section 6 and Section 6.3. 245 6. OSPFv3 Duplicate Router ID Detection and Resolution 247 There are two cases of duplicate OSPFv3 Router ID detection. One 248 where the OSPFv3 router with the duplicate Router ID is directly 249 connected and one where it is not. In both cases, the duplicate 250 resolution is for one of the routers to select a new OSPFv3 Router 251 ID. 253 6.1. Duplicate Router ID Detection for Neighbors 255 In this case, a duplicate Router ID is detected if any valid OSPFv3 256 packet is received with the same OSPFv3 Router ID but a different 257 IPv6 link-local source address. Once this occurs, the OSPFv3 router 258 with the numerically smaller IPv6 link-local address will need to 259 select a new Router ID as described in Section 6.3. Note that the 260 fact that the OSPFv3 router is a neighbor on a non-virtual interface 261 implies that the router is directly connected. An OSPFv3 router 262 implementing this specification should assure that the inadvertent 263 connection of multiple router interfaces to the same physical link is 264 not misconstrued as detection of an OSPFv3 neighbor with a duplicate 265 Router ID. 267 6.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 268 Neighbors 270 OSPFv3 Routers implementing auto-configuration, as specified herein, 271 MUST originate an Auto-Configuration (AC) Link State Advertisement 272 (LSA) including the Router-Hardware-Fingerprint Type-Length-Value 273 (TLV). The Router-Hardware-Fingerprint TLV contains a variable 274 length value that has a very high probability of uniquely identifying 275 the advertising OSPFv3 router. An OSPFv3 router implementing this 276 specification MUST compare a received self-originated Auto- 277 Configuration LSA's Router-Hardware-Fingerprint TLV against its own 278 router hardware fingerprint. If the fingerprints are not equal, 279 there is a duplicate Router ID conflict and the OSPFv3 Router with 280 the numerically smaller router hardware fingerprint MUST select a new 281 Router ID as described in Section 6.3. 283 This new LSA is designated for information related to OSPFv3 Auto- 284 configuration and, in the future, could be used other auto- 285 configuration information, e.g., global IPv6 prefixes. However, this 286 is beyond the scope of this document. 288 6.2.1. OSPFv3 Router Auto-Configuration LSA 290 The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and 291 the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit 292 will be set indicating that the OSPFv3 AC LSA should be flooded even 293 if it is not understood. The Link State ID (LSID) value will be a 294 integer index used to discriminate between multiple AC LSAs 295 originated by the same OSPFv3 Router. This specification only 296 describes the contents of an AC LSA with a Link State ID (LSID) of 0. 298 0 1 2 3 299 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 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 | LS age |1|0|1| TBD | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 | Link State ID | 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | Advertising Router | 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | LS sequence number | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 | LS checksum | Length | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | | 312 +- TLVs -+ 313 | ... | 315 OSPFv3 Auto-Configuration (AC) LSA 317 The format of the TLVs within the body of an AC LSA is the same as 318 the format used by the Traffic Engineering Extensions to OSPF [TE]. 319 The LSA payload consists of one or more nested Type/Length/Value 320 (TLV) triplets. The format of each TLV is: 322 0 1 2 3 323 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 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 | Type | Length | 326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 | Value... | 328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 TLV Format 332 The Length field defines the length of the value portion in octets 333 (thus a TLV with no value portion would have a length of 0). The TLV 334 is padded to 4-octet alignment; padding is not included in the length 335 field (so a 3-octet value would have a length of 3, but the total 336 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 337 aligned. For example, a 1-byte value would have the length field set 338 to 1, and 3 octets of padding would be added to the end of the value 339 portion of the TLV. Unrecognized types are ignored. 341 The new LSA is designated for information related to OSPFv3 Auto- 342 configuration and, in the future, can be used other auto- 343 configuration information. 345 6.2.2. Router-Hardware-Fingerprint TLV 347 The Router-Hardware-Fingerprint TLV is the first TLV defined for the 348 OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be 349 advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD 350 occur, at most, once and the first instance of the TLV will take 351 precedence over subsequent TLV instances. The length of the Router- 352 Hardware-Fingerprint is variable but must be 32 octets or greater. 354 The contents of the hardware fingerprint SHOULD be some combination 355 of MAC addresses, CPU ID, or serial number(s) that provides an 356 extremely high probability of uniqueness. It MUST be based on 357 hardware attributes that will not change across hard and soft 358 restarts. 360 0 1 2 3 361 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 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | 1 | >32 | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | Router Hardware Fingerprint | 366 o 367 o 368 o 369 | | 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 Router-Hardware-Fingerprint TLV Format 374 6.3. Duplicate Router ID Resolution 376 The OSPFv3 Router selected to resolve the duplicate OSPFv3 Router ID 377 condition must select a new OSPFv3 Router ID. After selecting a new 378 Router ID, all self-originated LSAs MUST be reoriginated, and any 379 OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router 380 retaining the Router ID causing the conflict will reoriginate or 381 purge stale any LSAs as described in Section 13.4 [OSPFV2]. 383 6.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA' 384 Processing 386 RFC 2328 [OSPFV2], Section 13.4, describes the processing of received 387 self-originated LSAs. If the received LSA doesn't exist, the 388 receiving router will purge it from the OSPF routing domain. If the 389 LSA is newer than the version in the Link State Database (LSDB), the 390 receiving router will originate a newer version by advancing the LSA 391 sequence number and reflooding. Since it is possible for an auto- 392 configured OSPFv3 router to choose a duplicate OSPFv3 Router ID, 393 OSPFv3 routers implementing this specification should detect when 394 multiple instances of the same self-originated LSA are purged or 395 reoriginated since this is indicative of an OSPFv3 router with a 396 duplicate Router ID in the OSPFv3 routing domain. When this 397 condition is detected, the OSPFv3 Router SHOULD delay self-originated 398 LSA processing for LSAs that have recently been purged or reflooded. 399 This specification recommends 10 seconds as the interval defining 400 recent self-originated LSA processing and an exponential back off of 401 1 to 8 seconds for the processing delay. This additional delay 402 should allow for the mechanisms described in Section 6 to resolve the 403 duplicate OSPFv3 Router ID conflict. 405 7. Security Considerations 407 A unique OSPFv3 Interface Instance ID is used for auto-configuration 408 to prevent inadvertent OSPFv3 adjacency formation, see Section 2 410 The goals of security and complete OSPFv3 auto-configuration are 411 somewhat contradictory. When no explicit security configuration 412 takes place, auto-configuration implies that additional devices 413 placed in the network are automatically adopted as a part of the 414 network. However, auto-configuration can also be combined with 415 password configuration (see below) or future extensions for automatic 416 pairing between devices. These mechanisms can help provide an 417 automatically configured, securely routed network. 419 It is RECOMMENDED that OSPFv3 routers supporting this specification 420 also offer an option to explicitly configure a password for HMAC-SHA 421 authentication as described in [OSPFV3-AUTH-TRAILER]. When 422 configured, the password will be used on all auto-configured 423 interfaces with the Security Association Identifier (SA ID) set to 1 424 and HMAC-SHA-256 used as the authentication algorithm. 426 8. Management Considerations 428 It is RECOMMENDED that OSPFv3 routers supporting this specification 429 also allow explicit configuration of OSPFv3 parameters as specified 430 in Appendix C of [OSPFV3]. This is in addition to the authentication 431 key configuration recommended in Section 7. However, it is 432 acknowledged that there may be some deployment scenarios where manual 433 authentication key configuration is not required. 435 9. IANA Considerations 437 This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto- 438 Configuration (AC) LSA, as described in Section 6.2.1. The value TBD 439 will be allocated from the existing "OSPFv3 LSA Function Code" 440 registry for the OSPFv3 Auto-Configuration LSA. 442 This specification also creates a registry for OSPFv3 Auto- 443 Configuration (AC) LSA TLVs. This registry should be placed in the 444 existing OSPFv3 IANA registry, and new values can be allocated via 445 IETF Consensus or IESG Approval. 447 Three initial values are allocated: 449 o 0 is marked as reserved. 451 o 1 is Router-Hardware-Fingerprint TLV (Section 6.2.2). 453 o 65535 is an Auto-configuration-Experiment-TLV, a common value that 454 can be used for experimental purposes. 456 10. References 458 10.1. Normative References 460 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 462 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 463 for IPv6", RFC 5340, July 2008. 465 [OSPFV3-AF] 466 Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 467 Aggarwal, "Support of Address Families in OSPFv3", 468 RFC 5838, April 2010. 470 [OSPFV3-AUTH-TRAILER] 471 Bhatia, M., Manral, V., and A. Lindem, "Supporting 472 Authentication Trailer for OSPFv3", RFC 6506, 473 February 2012. 475 [RFC-KEYWORDS] 476 Bradner, S., "Key words for use in RFCs to Indicate 477 Requirement Levels", RFC 2119, March 1997. 479 [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless 480 Address Autoconfiguration", RFC 4862, September 2007. 482 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 483 Extensions to OSPF", RFC 3630, September 2003. 485 10.2. Informative References 487 [ASYNC-HELLO] 488 Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold 489 Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in 490 progress). 492 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 493 Protocol 4 (BGP-4)", RFC 4271, January 2006. 495 [IPv6-CPE] 496 Singh, H., Beebee, W., Donley, C., Stark, B., and O. 497 Troan, "Basic Requirements for IPv6 Customer Edge 498 Routers", RFC 6204, April 2011. 500 Authors' Addresses 502 Acee Lindem 503 Ericsson 504 301 Midenhall Way 505 Cary, NC 27513 506 USA 508 Email: acee.lindem@ericsson.com 510 Jari Arkko 511 Ericsson 512 Jorvas, 02420 513 Finland 515 Email: jari.arkko@piuha.net