idnits 2.17.1 draft-ietf-ospf-ospfv3-autoconfig-02.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 (April 15, 2013) is 4029 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) == Outdated reference: A later version (-01) exists of draft-madhukar-ospf-agr-asymmetric-00 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 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 J. Arkko 4 Intended status: Standards Track Ericsson 5 Expires: October 17, 2013 April 15, 2013 7 OSPFv3 Auto-Configuration 8 draft-ietf-ospf-ospfv3-autoconfig-02.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 October 17, 2013. 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 . . . . . 6 69 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 6 70 4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 7 71 5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 8 72 6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 9 73 6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 9 74 6.2. Duplicate Router ID Detection for OSPFv3 Routers that 75 are not Neighbors . . . . . . . . . . . . . . . . . . . . 9 76 6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 9 77 6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 11 78 6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 11 79 6.4. Change to Received Self-Originated LSA Processing . . . . 12 80 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 81 8. Management Considerations . . . . . . . . . . . . . . . . . . 14 82 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 83 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 84 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 85 10.2. Informative References . . . . . . . . . . . . . . . . . . 16 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 88 1. Introduction 90 OSPFv3 [OSPFV3] is a candidate for deployments in environments where 91 auto-configuration is a requirement. Its operation is largely 92 unchanged from the base OSPFv3 protocol specification [OSPFV3]. 94 The following aspects of OSPFv3 auto-configuration are described: 96 1. Default OSPFv3 Configuration 98 2. HelloInterval/RouterDeadInterval Flexibility 100 3. Unique OSPFv3 Router-ID generation 102 4. OSPFv3 Adjacency Formation 104 5. Duplicate OSPFv3 Router-ID Resolution 106 1.1. Requirements notation 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in [RFC-KEYWORDS]. 112 1.2. Acknowledgments 114 This specification was inspired by the work presented in the Homenet 115 working group meeting in October 2011 in Philadelphia, Pennsylvania. 116 In particular, we would like to thank Fred Baker, Lorenzo Colitti, 117 Ole Troan, Mark Townsley, and Michael Richardson. 119 Arthur Dimitrelis and Aidan Williams did prior work in OSPFv3 auto- 120 configuration in the expired "Autoconfiguration of routers using a 121 link state routing protocol" IETF Draft. There are many similarities 122 between the concepts and techniques in this document. 124 Thanks for Abhay Roy and Manav Bhatia for comments regarding 125 duplicate router-id processing. 127 Thanks for Alvaro Retana and Michael Barnes for comments regarding 128 OSPFv3 Instance ID auto-configuration. 130 Thanks to Faraz Shamim for review and comments. 132 Thanks to Mark Smith for the requirement to reduce the adjacency 133 formation delay in the back-to-back ethernet topologies that are 134 prevalent in home networks. 136 The RFC text was produced using Marshall Rose's xml2rfc tool. 138 2. OSPFv3 Default Configuration 140 For complete auto-configuration, OSPFv3 will need to choose suitable 141 configuration defaults. These include: 143 1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in 144 area 0. 146 2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces 147 intended as general IPv6-capable routers. Optionally, an 148 interface MAY be excluded if it is clear that running OSPFv3 on 149 the interface is not required. For example, if manual 150 configuration or another condition indicates that an interface is 151 connected to an Internet Service Provider (ISP) and there is no 152 Border Gateway Protocol (BGP) [BGP] peering, there is typically 153 no need to employ OSPFv3. However, note that in many 154 environments it can be useful to test whether an OSPFv3 adjacency 155 can be established. In home networking environments, an 156 interface where no OSPFv3 neighbors are found but a DHCP IPv6 157 prefix can be acquired may be considered an ISP-facing interface 158 and running OSPFv3 is unnecessary. 160 3. OSPFv3 interfaces will be auto-configured to an interface type 161 corresponding to their layer-2 capability. For example, Ethernet 162 interfaces will be auto-configured as broadcast networks and 163 Point-to-Point Protocol (PPP) interfaces will be auto-configured 164 as Point-to-Point interfaces. Most extant OSPFv3 implementations 165 do this already. Auto-configured operation over wireless 166 networks requiring a point-to-multipoint (P2MP) topology and 167 dynamic metrics based on wireless feedback is not within the 168 scope of this document. However, auto-configuration is not 169 precluded in these environments. 171 4. OSPFv3 interfaces MAY use an arbitrary HelloInterval and 172 RouterDeadInterval as specified in Section 3. Of course, an 173 identical HelloInterval and RouterDeadInterval will still be 174 required to form an adjacency with an OSPFv3 router not 175 supporting auto-configuration [OSPFV3]. 177 5. All OSPFv3 interfaces SHOULD be auto-configured to use an 178 Interface Instance ID of 0 that corresponds to the base IPv6 179 unicast address family instance ID as defined in [OSPFV3-AF]. 180 Similarly, if IPv4 unicast addresses are advertised in a separate 181 auto-configured OSPFv3 instance, the base IPv4 unicast address 182 family instance ID value, i.e., 64, SHOULD be auto-configured as 183 the Interface Instance ID for all interfaces corresponding to the 184 OSPFv3 instance [OSPFV3-AF]. 186 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility 188 Auto-configured OSPFv3 routers will not require an identical 189 HelloInterval and RouterDeadInterval to form adjacencies. Rather, 190 the received HelloInterval will be ignored and the received 191 RouterDeadInterval will be used to determine OSPFv3 liveliness with 192 the sending router. In other words, the Inactivity Timer for each 193 neighbor will reflect that neighbor's advertised RouterDeadInterval 194 and MAY be different from other OSPFv3 routers on the link without 195 impacting adjacency formation. A similar mechanism requiring 196 additional signaling is proposed for all OSPFv2 and OSPFv3 routers 197 [ASYNC-HELLO]. 199 3.1. Wait Timer Reduction 201 In many situations, auto-configured OSPFv3 routers will be deployed 202 in environments where back-to-back ethernet connections are utilized. 203 When this is the case, an OSPFv3 broadcast interface will not come up 204 until the other OSPFv3 router is connected and the routers will wait 205 RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In 206 order to reduce this delay, an auto-configured OSPFv3 router MAY 207 reduce the wait interval to a value no less than (HelloInterval + 1), 208 i.e., 11 seconds. Reducing the setting will slightly increase the 209 likelihood of the Designated Router (DR) flapping but is preferable 210 to the long adjacency formation delay. Note that this value is not 211 included in OSPFv3 Hello packets and does not impact 212 interoperability. 214 4. OSPFv3 Router ID Selection 216 As OSPFv3 Router implementing this specification must select a unique 217 Router ID. A pseudo-random number SHOULD be used for the OSPFv3 218 Router ID. The generation should be seeded with a variable that is 219 likely to be unique in that environment. A good choice of seed would 220 be some portion or hash of the Route-Hardware-Fingerprint as 221 described in Section 6.2.2. 223 Since there is a possibility of a Router ID collision, duplicate 224 Router ID detection and resolution are required as described in 225 Section 6 and Section 6.3. 227 5. OSPFv3 Adjacency Formation 229 Since OSPFv3 uses IPv6 link-local addresses for all protocol messages 230 other than messages sent on virtual links (which are not applicable 231 to auto-configuration), OSPFv3 adjacency formation can proceed as 232 soon as a Router ID has been selected and the IPv6 link-local address 233 has completed Duplicate Address Detection (DAD) as specified in IPv6 234 Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only 235 changes to the OSPFv3 base specification are supporting 236 HelloInterval/RouterDeadInterval flexibility as described in 237 Section 3 and duplicate Router ID detection and resolution as 238 described in Section 6 and Section 6.3. 240 6. OSPFv3 Duplicate Router ID Detection and Resolution 242 There are two cases of duplicate OSPFv3 Router ID detection. One 243 where the OSPFv3 router with the duplicate Router ID is directly 244 connected and one where it is not. In both cases, the resolution is 245 for one of the routers with the duplicate OSPFv3 Router ID to select 246 a new one. 248 6.1. Duplicate Router ID Detection for Neighbors 250 In this case, a duplicate Router ID is detected if any valid OSPFv3 251 packet is received with the same OSPFv3 Router ID but a different 252 IPv6 link-local source address. Once that occurs, the OSPFv3 router 253 with the numerically smaller IPv6 link-local address will need to 254 select a new Router ID as described in Section 6.3. Note that the 255 fact that the OSPFv3 router is a neighbor on a non-virtual interface 256 implies that the router is directly connected. An OSPFv3 router 257 implementing this specification should assure that the inadvertent 258 connection of multiple router interfaces to the same physical link is 259 not misconstrued as detection of a different OSPFv3 router with a 260 duplicate Router ID. 262 6.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 263 Neighbors 265 OSPFv3 Routers implementing auto-configuration, as specified herein, 266 MUST originate an Auto-Config (AC) Link State Advertisement (LSA) 267 including the Router-Hardware-Fingerprint Type-Length-Value (TLV). 268 The Router-Hardware-Fingerprint TLV contains a variable length value 269 that has a very high probability of uniquely identifying the 270 advertising OSPFv3 router. An OSPFv3 router implementing this 271 specification MUST compare a received self-originated Auto-Config 272 LSA's Router-Hardware-Fingerprint TLV against its own router hardware 273 fingerprint. If the fingerprints are not equal, there is a Router ID 274 conflict and the OSPFv3 Router with the numerically smaller router 275 hardware fingerprint MUST select a new Router ID as described in 276 Section 6.3. 278 This new LSA is designated for information related to OSPFv3 Auto- 279 configuration and, in the future, could be used other auto- 280 configuration information, e.g., global IPv6 prefixes. However, this 281 is beyond the scope of this document. 283 6.2.1. OSPFv3 Router Auto-Configuration LSA 285 The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and 286 the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit 287 will be set indicating that the OSPFv3 AC LSA should be flooded even 288 if it is not understood. The Link State ID (LSID) value will be a 289 integer index used to discriminate between multiple AC LSAs 290 originated by the same OSPFv3 Router. This specification only 291 describes the contents of an AC LSA with a Link State ID (LSID) of 0. 293 0 1 2 3 294 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 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | LS age |1|0|1| TBD | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 | Link State ID | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | Advertising Router | 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 | LS sequence number | 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | LS checksum | Length | 305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 306 | | 307 +- TLVs -+ 308 | ... | 310 OSPFv3 Auto-Configuration (AC) LSA 312 The format of the TLVs within the body of an AC LSA is the same as 313 the format used by the Traffic Engineering Extensions to OSPF [TE]. 314 The LSA payload consists of one or more nested Type/Length/Value 315 (TLV) triplets. The format of each TLV is: 317 0 1 2 3 318 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 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | Type | Length | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | Value... | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 TLV Format 327 The Length field defines the length of the value portion in octets 328 (thus a TLV with no value portion would have a length of 0). The TLV 329 is padded to 4-octet alignment; padding is not included in the length 330 field (so a 3-octet value would have a length of 3, but the total 331 size of the TLV would be 8 octets). Nested TLVs are also 32-bit 332 aligned. For example, a 1-byte value would have the length field set 333 to 1, and 3 octets of padding would be added to the end of the value 334 portion of the TLV. Unrecognized types are ignored. 336 The new LSA is designated for information related to OSPFv3 Auto- 337 configuration and, in the future, can be used other auto- 338 configuration information, e.g., global IPv6 prefixes. 340 6.2.2. Router-Hardware-Fingerprint TLV 342 The Router-Hardware-Fingerprint TLV is the first TLV defined for the 343 OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be 344 advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD 345 occur, at most, once and the first instance of the TLV will take 346 precedence over subsequent TLV instances. The length of the Router- 347 Hardware-Fingerprint is variable but must be 32 bytes or greater. 349 The contents of the hardware fingerprint should be some combination 350 of MAC addresses, CPU ID, or serial number(s) that provides an 351 extremely high probability of uniqueness. It MUST be based on 352 hardware attributes that will not change across hard and soft 353 restarts. 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 | 1 | >32 | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | Router Hardware Fingerprint | 361 o 362 o 363 o 364 | | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 Router-Hardware-Fingerprint TLV Format 369 6.3. Duplicate Router ID Resolution 371 The OSPFv3 Router selected to resolve the duplicate OSPFv3 Router ID 372 condition must select a new OSPFv3 Router ID. After selecting a new 373 Router ID, the Router-LSA with the prior duplicate Router ID MUST be 374 purged. All self-originated LSAs MUST be reoriginated, and any 375 OSPFv3 neighbor adjacencies MUST be reestablished. 377 6.4. Change to Received Self-Originated LSA Processing 379 RFC 2328 [OSPFV2], Section 13.4, describes the processing of received 380 self-originated LSAs. If the received LSA doesn't exist, the 381 receiving router will purge it from the OSPF routing domain. If the 382 LSA is newer than the version in the Link State Database (LSDB), the 383 receiving router will originate a newer version by advancing the LSA 384 sequence number and reflooding. Since it is possible for an auto- 385 configured OSPFv3 router to choose a duplicate OSPFv3 Router ID, 386 OSPFv3 routers implementing this specification should detect when 387 multiple instances of the same self-originated LSA are purged or 388 reoriginated since this is indicative of an OSPFv3 router with a 389 duplicate Router ID in the OSPFv3 routing domain. When this 390 condition is detected, the OSPFv3 Router SHOULD delay self-originated 391 LSA processing for LSAs that have recently been purged or reflooded. 392 This specification recommends 10 seconds as the interval defining 393 recent self-originated LSA processing and an exponential back off of 394 1 to 8 seconds for the processing delay. 396 7. Security Considerations 398 A unique OSPFv3 Interface Instance ID is used for auto-configuration 399 to prevent inadvertent OSPFv3 adjacency formation, see Section 2 401 The goals of security and complete OSPFv3 auto-configuration are 402 somewhat contradictory. When no explicit security configuration 403 takes place, auto-configuration implies that additional devices 404 placed in the network are automatically adopted as a part of the 405 network. However, auto-configuration can also be combined with 406 password configuration (see below) or future extensions for automatic 407 pairing between devices. These mechanisms can help provide an 408 automatically configured, securely routed network. 410 It is RECOMMENDED that OSPFv3 routers supporting this specification 411 also offer an option to explicitly configure a password for HMAC-SHA 412 authentication as described in [OSPFV3-AUTH-TRAILER]. When 413 configured, the password will be used on all auto-configured 414 interfaces with the Security Association Identifier (SA ID) set to 1 415 and HMAC-SHA-256 used as the authentication algorithm. 417 8. Management Considerations 419 It is RECOMMENDED that OSPFv3 routers supporting this specification 420 also allow explicit configuration of OSPFv3 parameters as specified 421 in Appendix C of [OSPFV3]. This is in addition to the authentication 422 key configuration recommended in Section 7. However, it is 423 acknowledged that there may be some deployment scenarios where manual 424 authentication key configuration is not required. 426 9. IANA Considerations 428 This specification allocates a new OSPFv3 LSA, OSPFv3 Auto- 429 Configuration (AC) LSA, TBD, as described in Section 6.2.1. 431 This specification also creates a registry for OSPFv3 Auto- 432 Configuration (AC) LSA TLVs. This registry should be placed in the 433 existing OSPFv3 IANA registry, and new values can be allocated via 434 IETF Consensus or IESG Approval. 436 Three initial values are allocated: 438 o 0 is marked as reserved. 440 o 1 is Router-Hardware-Fingerprint TLV (Section 6.2.2). 442 o 65535 is an Auto-configuration-Experiment-TLV, a common value that 443 can be used for experimental purposes. 445 10. References 447 10.1. Normative References 449 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 451 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 452 for IPv6", RFC 5340, July 2008. 454 [OSPFV3-AF] 455 Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 456 Aggarwal, "Support of Address Families in OSPFv3", 457 RFC 5838, April 2010. 459 [OSPFV3-AUTH-TRAILER] 460 Bhatia, M., Manral, V., and A. Lindem, "Supporting 461 Authentication Trailer for OSPFv3", RFC 6506, 462 February 2012. 464 [RFC-KEYWORDS] 465 Bradner, S., "Key words for use in RFCs to Indicate 466 Requirement Levels", RFC 2119, March 1997. 468 [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless 469 Address Autoconfiguration", RFC 4862, September 2007. 471 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 472 Extensions to OSPF", RFC 3630, September 2003. 474 10.2. Informative References 476 [ASYNC-HELLO] 477 Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold 478 Timer", draft-madhukar-ospf-agr-asymmetric-00.txt (work in 479 progress). 481 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 482 Protocol 4 (BGP-4)", RFC 4271, January 2006. 484 Authors' Addresses 486 Acee Lindem 487 Ericsson 488 102 Carric Bend Court 489 Cary, NC 27519 490 USA 492 Email: acee.lindem@ericsson.com 494 Jari Arkko 495 Ericsson 496 Jorvas, 02420 497 Finland 499 Email: jari.arkko@piuha.net