idnits 2.17.1 draft-ietf-v6ops-design-choices-04.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 document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 255: '... A router MUST be able to determi...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 18, 2015) is 3353 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-16) exists of draft-ietf-idr-dynamic-cap-14 == Outdated reference: A later version (-05) exists of draft-ietf-v6ops-ula-usage-recommendations-04 -- Obsolete informational reference (is this intentional?): RFC 3107 (Obsoleted by RFC 8277) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 V6OPS Working Group P. Matthews 3 Internet-Draft Alcatel-Lucent 4 Intended status: Informational V. Kuarsingh 5 Expires: August 22, 2015 Dyn 6 February 18, 2015 8 Some Design Choices for IPv6 Networks 9 draft-ietf-v6ops-design-choices-04 11 Abstract 13 This document presents advice on certain routing-related design 14 choices that arise when designing IPv6 networks (both dual-stack and 15 IPv6-only). The intended audience is someone designing an IPv6 16 network who is knowledgeable about best current practices around IPv4 17 network design, and wishes to learn the corresponding practices for 18 IPv6. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 22, 2015. 37 Copyright Notice 39 Copyright (c) 2015 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Design Choices . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. Interfaces . . . . . . . . . . . . . . . . . . . . . . . 3 57 2.1.1. Mix IPv4 and IPv6 on the Same Layer-3 Interface? . . 3 58 2.1.2. Interfaces with Only Link-Local Addresses? . . . . . 4 59 2.2. Static Routes . . . . . . . . . . . . . . . . . . . . . . 6 60 2.2.1. Link-Local Next-Hop in a Static Route? . . . . . . . 6 61 2.3. IGPs . . . . . . . . . . . . . . . . . . . . . . . . . . 6 62 2.3.1. IGP Choice . . . . . . . . . . . . . . . . . . . . . 7 63 2.4. BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 64 2.4.1. Which Transport for Which Routes? . . . . . . . . . . 8 65 2.4.1.1. BGP Sessions for Unlabeled Routes . . . . . . . . 10 66 2.4.1.2. BGP sessions for Labeled or VPN Routes . . . . . 11 67 2.4.2. eBGP Endpoints: Global or Link-Local Addresses? . . . 11 68 3. General Observations . . . . . . . . . . . . . . . . . . . . 12 69 3.1. Use of Link-Local Addresses . . . . . . . . . . . . . . . 12 70 3.2. Separation of IPv4 and IPv6 . . . . . . . . . . . . . . . 13 71 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 72 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 73 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 74 7. Informative References . . . . . . . . . . . . . . . . . . . 15 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 77 1. Introduction 79 This document discusses certain choices that arise when designing a 80 IPv6-only or dual-stack network. The focus is on routing-related 81 design choices that do not usually come up when designing an 82 IPv4-only network. The document presents each choice and the 83 alternatives, and then discusses the pros and cons of the 84 alternatives in detail. Where consensus currently exists around the 85 best practice, this is documented; otherwise the document simply 86 summarizes the current state of the discussion. Thus this document 87 serves to both document the reasoning behind best current practices 88 for IPv6, and to allow a designer to make an informed choice where no 89 such consensus exists. 91 This document does not present advice on strategies for adding IPv6 92 to a network, nor does it discuss transition mechanisms. For advice 93 in these areas, see [RFC6180] for general advice, [RFC6782] for 94 wireline service providers, [RFC6342] for mobile network providers, 95 [RFC5963] for exchange point operators, [RFC6883] for content 96 providers, and both [RFC4852] and [RFC7381] for enterprises. Nor 97 does this document discuss the particulars of creating an IPv6 98 addressing plan; for advice in this area, see [RFC5375] or 99 [v6-addressing-plan]. The use of ULAs instead of globally-routed 100 addresses is also not discussed; for this the reader is referred to 101 [I-D.ietf-v6ops-ula-usage-recommendations]. 103 Finally, this document focuses on unicast routing design only and 104 does not cover multicast or the issues involved in running MPLS over 105 IPv6 transport. 107 2. Design Choices 109 Each subsection below presents a design choice and discusses the pros 110 and cons of the various options. If there is consensus in the 111 industry for a particular option, then the consensus position is 112 noted. 114 2.1. Interfaces 116 2.1.1. Mix IPv4 and IPv6 on the Same Layer-3 Interface? 118 If a network is going to carry both IPv4 and IPv6 traffic, as many 119 networks do today, then a fundamental question arises: Should an 120 operator mix IPv4 and IPv6 traffic or keep them separated? More 121 specifically, should the design: 123 a. Mix IPv4 and IPv6 traffic on the same layer-3 interface, OR 125 b. Separate IPv4 and IPv6 by using separate interfaces (e.g., two 126 physical links or two VLANs on the same link)? 128 Option (a) implies a single layer-3 interface at each end of the 129 connection with both IPv4 and IPv6 addresses; while option (b) 130 implies two layer-3 interfaces at each end, one for IPv4 addresses 131 and one with IPv6 addresses. 133 The advantages of option (a) include: 135 o Requires only half as many layer 3 interfaces as option (b), thus 136 providing better scaling; 138 o May require fewer physical ports, thus saving money; 140 o Can make the QoS implementation much easier (for example, rate- 141 limiting the combined IPv4 and IPv6 traffic to or from a 142 customer); 144 o Works well in practice, as any increase in IPv6 traffic is usually 145 counter-balanced by a corresponding decrease in IPv4 traffic to or 146 from the same host (ignoring the common pattern of an overall 147 increase in Internet usage); 149 o And is generally conceptually simpler. 151 For these reasons, there is a relatively strong consensus in the 152 operator community that option (a) is the preferred way to go. Most 153 networks today use option (a) wherever possible. 155 However, there can be times when option (b) is the pragmatic choice. 156 Most commonly, option (b) is used to work around limitations in 157 network equipment. One big example is the generally poor level of 158 support today for individual statistics on IPv4 traffic vs IPv6 159 traffic when option (a) is used. Other, device-specific, limitations 160 exist as well. It is expected that these limitations will go away as 161 support for IPv6 matures, making option (b) less and less attractive 162 until the day that IPv4 is finally turned off. 164 2.1.2. Interfaces with Only Link-Local Addresses? 166 As noted in the introduction, this document does not cover the ins 167 and outs around creating an IPv6 addressing plan. However, there is 168 one fundamental question in this area that often arises: Should the 169 interface: 171 a. Use only link-local addresses ("unnumbered"), OR 173 b. Have global (or unique-local) addresses assigned in addition to 174 link-locals? 176 There are two advantages of unnumbered interfaces. The first 177 advantage is ease of configuration. In a network with a large number 178 of unnumbered interfaces, the operator can just enable an IGP on each 179 router, without going through the tedious process of assigning and 180 tracking the addresses for each interface. The second advantage is 181 security. Since packets with link-local destination addresses should 182 not be routed, it is very difficult to attack the associated 183 interfaces from an off-link device. This implies less effort around 184 maintaining security ACLs. 186 Countering this advantage are various disadvantages to unnumbered 187 interfaces in IPv6: 189 o It is not possible to ping an interface that has only a link-local 190 address from a device that is not directly attached to the link. 191 Thus, to troubleshoot, one must typically log into a device that 192 is directly attached to the device in question, and execute the 193 ping from there. 195 o A traceroute passing over the unnumbered link will return the 196 loopback or system address of the router, rather than the address 197 of the interface itself. 199 o In cases of parallel point to point links it is difficult to 200 determine which of the parallel links was taken when attempting to 201 troubleshoot unless one sends packets directly between the two 202 attached link-locals on the specific interfaces. Since many 203 network problems behave differently for traffic to/from a router 204 than for traffic through the router(s) in question, this can pose 205 a significant hurdle to some troubleshooting scenarios. 207 o On some devices, by default the link-layer address of the 208 interface is derived from the MAC address assigned to interface. 209 When this is done, swapping out the interface hardware (e.g. 210 interface card) will cause the link-layer address to change. In 211 some cases (peering config, ACLs, etc) this may require additional 212 changes. However, many devices allow the link-layer address of an 213 interface to be explicitly configured, which avoids this issue. 215 o The practice of naming router interfaces using DNS names is 216 difficult and not recommended when using link-locals only. More 217 generally, it is not recommended to put link-local addresses into 218 DNS; see [RFC4472]. 220 o It is often not possible to identify the interface or link (in a 221 database, email, etc) by giving just its address without also 222 specifying the link in some manner. 224 It should be noted that it is quite possible for the same link-local 225 address to be assigned to multiple interfaces. This can happen 226 because the MAC address is duplicated (due to manufacturing process 227 defaults or the use of virtualization), because a device deliberately 228 re-uses automatically-assigned link-local addresses on different 229 links, or because an operator manually assigns the same easy-to-type 230 link-local address to multiple interfaces. All these are allowed in 231 IPv6 as long as the addresses are used on different links. 233 For more discussion on the pros and cons, see [RFC7404]. See also 234 [RFC5375] for IPv6 unicast address assignment considerations. 236 Today, most operators use numbered interfaces (option b). 238 2.2. Static Routes 240 2.2.1. Link-Local Next-Hop in a Static Route? 242 For the most part, the use of static routes in IPv6 parallels their 243 use in IPv4. There is, however, one exception, which revolves around 244 the choice of next-hop address in the static route. Specifically, 245 should an operator: 247 a. Use the far-end's link-local address as the next-hop address, OR 249 b. Use the far-end's GUA/ULA address as the next-hop address? 251 Recall that the IPv6 specs for OSPF [RFC5340] and ISIS [RFC5308] 252 dictate that they always use link-locals for next-hop addresses. For 253 static routes, [RFC4861] section 8 says: 255 A router MUST be able to determine the link-local address for each 256 of its neighboring routers in order to ensure that the target 257 address in a Redirect message identifies the neighbor router by 258 its link-local address. For static routing, this requirement 259 implies that the next-hop router's address should be specified 260 using the link-local address of the router. 262 This implies that using a GUA or ULA as the next hop will prevent a 263 router from sending Redirect messages for packets that "hit" this 264 static route. All this argues for using a link-local as the next-hop 265 address in a static route. 267 However, there are two cases where using a link-local address as the 268 next-hop clearly does not work. One is when the static route is an 269 indirect (or multi-hop) static route. The second is when the static 270 route is redistributed into another routing protocol. In these 271 cases, the above text from RFC 4861 notwithstanding, either a GUA or 272 ULA must be used. 274 Furthermore, many network operators are concerned about the 275 dependency of the default link-local address on an underlying MAC 276 address, as described in the previous section. 278 Today most operators use GUAs as next-hop addresses. 280 2.3. IGPs 281 2.3.1. IGP Choice 283 One of the main decisions for an IPv6 implementer is the choice of 284 IGP (Interior Gateway Protocol) within the network. The primary 285 options are OSPF [RFC2328] [RFC5340] or IS-IS [RFC5120] [RFC5308], 286 though some operators may consider RIP [RFC2080] or non-standardized 287 protocols. Here we limit our discussion to the pros and cons of OSPF 288 vs. IS-IS. 290 The discussion in this section revolves around the options in the 291 table below: 293 +--------+--------+---------+---------+------------+----------------+ 294 | Option | IGP | IGP for | Known | Hard | Similar | 295 | | for | IPv6 | to work | separation | configuration | 296 | | IPv4 | | well | | possible | 297 +--------+--------+---------+---------+------------+----------------+ 298 | | | | | | | 299 +--------+--------+---------+---------+------------+----------------+ 300 | a | IS-IS | IS-IS | YES | - | YES | 301 +--------+--------+---------+---------+------------+----------------+ 302 | b | IS-IS | OSPFv3 | - | YES | - | 303 +--------+--------+---------+---------+------------+----------------+ 304 | | | | | | | 305 +--------+--------+---------+---------+------------+----------------+ 306 | c | OSPFv2 | IS-IS | YES | YES | - | 307 +--------+--------+---------+---------+------------+----------------+ 308 | d | OSPFv2 | OSPFv3 | YES | YES | YES | 309 +--------+--------+---------+---------+------------+----------------+ 310 | | | | | | | 311 +--------+--------+---------+---------+------------+----------------+ 312 | e | OSPFv3 | IS-IS | - | YES | - | 313 +--------+--------+---------+---------+------------+----------------+ 314 | f | OSPFv3 | OSPFv3 | - | - | YES | 315 +--------+--------+---------+---------+------------+----------------+ 317 Three of the options above are marked as "Known to work well". These 318 options have seen significant deployments and are generally 319 considered to be good choices. The other options represent valid 320 choices, but have not seen widespread use, so it is hard to offer 321 comments on how well they work. In particular, options (e) and (f) 322 use OSPFv3 to route IPv4 [RFC5838], which is still rather new and 323 untested. 325 A number of options are marked "Hard separation". These options use 326 a different IGP for IPv4 vs IPv6. With these options, a problem with 327 routing IPv6 is unlikely to affect IPv4 or visa-versa. 329 Three options are marked "Similar configuration possible". This 330 means it is possible (but not required) to use very similar IGP 331 configuration for IPv4 and IPv6: for example, the same area 332 boundaries, area numbering, link costing, etc. If you are happy with 333 your IPv4 IGP design, then this will likely be a consideration. By 334 contrast, the options that use IS-IS for one IP version and OSPF for 335 the other version will require considerably different configuration, 336 and will also require the operations staff to become familiar with 337 the difference between the two protocols. 339 With option (a), there is an additional choice of whether to run IS- 340 IS in single-topology mode (where IPv4 and IPv6 share a single 341 topology and a single set of link costs[RFC5308]) or multi-topology 342 mode (where IPv4 and IPv6 have separate topologies and potentially 343 different link costs[RFC5120]). A big problem with single-topology 344 mode is that it cannot easily accommodate devices that support 345 IPv4-only or IPv6-only. Thus, today there is general agreement that 346 multi-topology is the right choice as this gives the greatest 347 flexibility in network design. 349 It should be noted that a number of ISPs have run OSPF as their IPv4 350 IGP for quite a few years, but have selected IS-IS as their IPv6 IGP. 351 However, there are very few (none?) that have made the reverse 352 choice. This is, in part, because routers generally support more 353 nodes in an IS-IS area than in the corresponding OSPF area, and 354 because IS-IS is seen as more secure because it runs at layer 2. 356 2.4. BGP 358 2.4.1. Which Transport for Which Routes? 360 BGP these days is multi-protocol. It can carry routes from many 361 different families, and it can do this when the BGP session, or more 362 accurately the underlying TCP connection, runs over either IPv4 or 363 IPv6 (here referred to as either "IPv4 transport" or "IPv6 364 transport"). Given this flexibility, one of the biggest questions 365 when deploying BGP in a dual-stack network is the question of which 366 routes should be carried over sessions using IPv4 transport and which 367 should be carried over sessions using IPv6 transport. 369 To answer this question, consider the following table: 371 +----------------+-----------+----------------------+ 372 | Route Family | Transport | Comments | 373 +----------------+-----------+----------------------+ 374 | | | | 375 +----------------+-----------+----------------------+ 376 | Unlabeled IPv4 | IPv4 | Works well | 377 +----------------+-----------+----------------------+ 378 | Unlabeled IPv4 | IPv6 | Next-hop issues | 379 +----------------+-----------+----------------------+ 380 | Unlabeled IPv6 | IPv4 | Next-hop issues | 381 +----------------+-----------+----------------------+ 382 | Unlabeled IPv6 | IPv6 | Works well | 383 +----------------+-----------+----------------------+ 384 | | | | 385 +----------------+-----------+----------------------+ 386 | Labeled IPv4 | IPv4 | Works well | 387 +----------------+-----------+----------------------+ 388 | Labeled IPv4 | IPv6 | Next-hop issues | 389 +----------------+-----------+----------------------+ 390 | Labeled IPv6 | IPv4 | (6PE) Works well | 391 +----------------+-----------+----------------------+ 392 | Labeled IPv6 | IPv6 | Needs MPLS over IPv6 | 393 +----------------+-----------+----------------------+ 394 | | | | 395 +----------------+-----------+----------------------+ 396 | VPN IPv4 | IPv4 | Works well | 397 +----------------+-----------+----------------------+ 398 | VPN IPv4 | IPv6 | Next-hop issues | 399 +----------------+-----------+----------------------+ 400 | VPN IPv6 | IPv4 | (6VPE) Works well | 401 +----------------+-----------+----------------------+ 402 | VPN IPv6 | IPv6 | Needs MPLS over IPv6 | 403 +----------------+-----------+----------------------+ 405 The first column in this table lists various route families, where 406 "unlabeled" means SAFI 1, "labeled" means the routes carry an MPLS 407 label (SAFI 4, see [RFC3107]), and "VPN" means the routes are 408 normally associated with a layer-3 VPN (SAFI 128, see [RFC4364] ). 409 The second column lists the protocol used to transport the BGP 410 session, frequently specified by giving either an IPv4 or IPv6 411 address in the "neighbor" statement. 413 The third column comments on the combination in the first two 414 columns: 416 o For combinations marked "Works well", these combinations are 417 widely supported and are generally recommended. 419 o For combinations marked "Next-hop issues", these combinations are 420 less-widely supported and when supported, often have next-hop 421 issues. That is, the next-hop address is typically a v4-mapped 422 IPv6 address, which is based on some IPv4 address on the sending 423 router. This v4-mapped IPv6 address is often not reachable by 424 default using IPv6 routing. One common solution to this problem 425 is to use routing policy to change the next-hop to a different 426 IPv6 address. 428 o For combinations marked as "Needs MPLS over IPv6", these require 429 MPLS over IPv6 for full support, though special policy 430 configuration may allow them to be used with MPLS over IPv4. 432 Also, it is important to note that changing the set of address 433 families being carried over a BGP session requires the BGP session to 434 be reset (unless something like [I-D.ietf-idr-dynamic-cap] or 435 [I-D.ietf-idr-bgp-multisession] is in use). This is generally more 436 of an issue with eBGP sessions than iBGP sessions: for iBGP sessions 437 it is common practice for a router to have two iBGP sessions, one to 438 each member of a route reflector pair, so one can change the set of 439 address families on first one of the sessions and then the other. 441 The following subsections discuss specific scenarios in more detail. 443 2.4.1.1. BGP Sessions for Unlabeled Routes 445 Unlabeled routes are commonly carried on eBGP sessions, as well as on 446 iBGP sessions in networks where Internet traffic is carried unlabeled 447 across the network. In these scenarios, operators today most 448 commonly use two BGP sessions: one session is transported over IPv4 449 and carries the unlabeled IPv4 routes, while the second session is 450 transported over IPv6 and carries the unlabeled IPv6 routes. 452 There are several reasons for this choice: 454 o It gives a clean separation between IPv4 and IPv6. This can be 455 especially useful when first deploying IPv6 and troubleshooting 456 resulting problems. 458 o This avoids the next-hop problem described in note 1 above. 460 o The status of the routes follows the status of the underlying 461 transport. If, for example, the IPv6 data path between the two 462 BGP speakers fails, then the IPv6 session between the two speakers 463 will fail and the IPv6 routes will be withdrawn, which will allow 464 the traffic to be re-routed elsewhere. By contrast, if the IPv6 465 routes were transported over IPv4, then the failure of the IPv6 466 data path might leave a working IPv4 data path, so the BGP session 467 would remain up and the IPv6 routes would not be withdrawn, and 468 thus the IPv6 traffic would be sent into a black hole. 470 o It avoids resetting the BGP session when adding IPv6 to an 471 existing session, or when removing IPv4 from an existing session. 473 2.4.1.2. BGP sessions for Labeled or VPN Routes 475 In these scenarios, it is most common today to carry both the IPv4 476 and IPv6 routes over sessions transported over IPv4. This can be 477 done with either: (a) one session carrying both route families, or 478 (b) two sessions, one for each family. 480 Using a single session is usually appropriate for an iBGP session 481 going to a route reflector handling both route families. Using a 482 single session here usually means that the BGP session will reset 483 when changing the set of address families, but as noted above, this 484 is usually not a problem when redundant route reflectors are 485 involved. 487 In eBGP situations, two sessions are usually more appropriate. 489 2.4.2. eBGP Endpoints: Global or Link-Local Addresses? 491 When running eBGP over IPv6, there are two options for the addresses 492 to use at each end of the eBGP session (or more properly, the 493 underlying TCP session): 495 a. Use link-local addresses for the eBGP session, OR 497 b. Use global addresses for the eBGP session. 499 Note that the choice here is the addresses to use for the eBGP 500 sessions, and not whether the link itself has global (or unique- 501 local) addresses. In particular, it is quite possible for the eBGP 502 session to use link-local addresses even when the link has global 503 addresses. 505 The big attraction for option (a) is security: an eBGP session using 506 link-local addresses is extremely difficult to attack from a device 507 that is off-link. This provides very strong protection against TCP 508 RST and similar attacks. Though there are other ways to get an 509 equivalent level of security (e.g. GTSM [RFC5082], MD5 [RFC5925], or 510 ACLs), these other ways require additional configuration which can be 511 forgotten or potentially mis-configured. 513 However, there are a number of small disadvantages to using link- 514 local addresses: 516 o Using link-local addresses only works for single-hop eBGP 517 sessions; it does not work for multi-hop sessions. 519 o One must use "next-hop self" at both endpoints, otherwise re- 520 advertising routes learned via eBGP into iBGP will not work. 521 (Some products enable "next-hop self" in this situation 522 automatically). 524 o Operators and their tools are used to referring to eBGP sessions 525 by address only, something that is not possible with link-local 526 addresses. 528 o If one is configuring parallel eBGP sessions for IPv4 and IPv6 529 routes, then using link-local addresses for the IPv6 session 530 introduces extra operational differences between the two sessions 531 which could otherwise be avoided. 533 o On some products, an eBGP session using a link-local address is 534 more complex to configure than a session that uses a global 535 address. 537 o If hardware or other issues cause one to move the cable to a 538 different local interface, then reconfiguration is required at 539 both ends: at the local end because the interface has changed (and 540 with link-local addresses, the interface must always be specified 541 along with the address), and at the remote end because the link- 542 local address has likely changed. (Contrast this with using 543 global addresses, where less re-configuration is required at the 544 local end, and no reconfiguration is required at the remote end). 546 o Finally, a strict application of [RFC2545] forbids running eBGP 547 between link-local addresses, as [RFC2545] requires the BGP next- 548 hop field to contain at least a global address. 550 For these reasons, most operators today choose to have their eBGP 551 sessions use global addresses. 553 3. General Observations 555 There are two themes that run though many of the design choices in 556 this document. This section presents some general discussion on 557 these two themes. 559 3.1. Use of Link-Local Addresses 561 The proper use of link-local addresses is a common theme in the IPv6 562 network design choices. Link-layer addresses are, of course, always 563 present in an IPv6 network, but current network design practice 564 mostly ignores them, despite efforts such as [RFC7404]. 566 There are three main reasons for this current practice: 568 o Network operators are concerned about the volatility of link-local 569 addresses based on MAC addresses, despite the fact that this 570 concern can be overcome by manually-configuring link-local 571 addresses; 573 o It is very difficult to impossible to ping a link-local address 574 from a device that is not on the same subnet. This is a 575 troubleshooting disadvantage, though it can also be viewed as a 576 security advantage. 578 o Most operators are currently running networks that carry both IPv4 579 and IPv6 traffic, and wish to harmonize their IPv4 and IPv6 design 580 and operational practices where possible. 582 3.2. Separation of IPv4 and IPv6 584 Currently, most operators are running or planning to run networks 585 that carry both IPv4 and IPv6 traffic. Hence the question: To what 586 degree should IPv4 and IPv6 be kept separate? As can be seen above, 587 this breaks into two sub-questions: To what degree should IPv4 and 588 IPv6 traffic be kept separate, and to what degree should IPv4 and 589 IPv6 routing information be kept separate? 591 The general consensus around the first question is that IPv4 and IPv6 592 traffic should generally be mixed together. This recommendation is 593 driven by the operational simplicity of mixing the traffic, plus the 594 general observation that the service being offered to the end user is 595 Internet connectivity and most users do not know or care about the 596 differences between IPv4 and IPv6. Thus it is very desirable to mix 597 IPv4 and IPv6 on the same link to the end user. On other links, 598 separation is possible but more operationally complex, though it does 599 occasionally allow the operator to work around limitations on network 600 devices. The situation here is roughly comparable to IP and MPLS 601 traffic: many networks mix the two traffic types on the same links 602 without issues. 604 By contrast, there is more of an argument for carrying IPv6 routing 605 information over IPv6 transport, while leaving IPv4 routing 606 information on IPv4 transport. By doing this, one gets fate-sharing 607 between the control and data plane for each IP protocol version: if 608 the data plane fails for some reason, then often the control plane 609 will too. 611 4. IANA Considerations 613 This document makes no requests of IANA. 615 5. Security Considerations 617 This document introduces no new security considerations that are not 618 already documented elsewhere. 620 The following is a brief list of pointers to documents related to the 621 topics covered above that the reader may wish to review for security 622 considerations. 624 For general IPv6 security, [RFC4942] provides guidance on security 625 considerations around IPv6 transition and coexistence. 627 For OSPFv3, the base protocol specification [RFC5340] has a short 628 security considerations section which notes that the fundamental 629 mechanism for protecting OSPFv3 from attacks is the mechanism 630 described in [RFC4552]. 632 For IS-IS, [RFC5308] notes that ISIS for IPv6 raises no new security 633 considerations over ISIS for IPv4 over those documented in [ISO10589] 634 and [RFC5304]. 636 For BGP, [RFC2545] notes that BGP for IPv6 raises no new security 637 considerations over those present in BGP for IPv4. However, there 638 has been much discussion of BGP security recently, and the interested 639 reader is referred to the documents of the IETF's SIDR working group. 641 6. Acknowledgements 643 Many, many people in the V6OPS working group provided comments and 644 suggestions that made their way into this document. A partial list 645 includes: Rajiv Asati, Fred Baker, Michael Behringer, Marc Blanchet, 646 Ron Bonica, Randy Bush, Cameron Byrne, Brian Carpenter, KK 647 Chittimaneni, Tim Chown, Lorenzo Colitti, Gert Doering, Francis 648 Dupont, Bill Fenner, Kedar K Gaonkar, Chris Grundemann, Steinar Haug, 649 Ray Hunter, Joel Jaeggli, Victor Kuarsingh, Jen Linkova, Ivan 650 Pepelnjak, Alexandru Petrescu, Rob Shakir, Mark Smith, Jean-Francois 651 Tremblay, Dave Thaler, Tina Tsou, Eric Vyncke, Dan York, and 652 Xuxiaohu. 654 The authors would also like to thank Pradeep Jain and Alastair 655 Johnson for helpful comments on a very preliminary version of this 656 document. 658 7. Informative References 660 [I-D.ietf-idr-bgp-multisession] 661 Scudder, J., Appanna, C., and I. Varlashkin, "Multisession 662 BGP", draft-ietf-idr-bgp-multisession-07 (work in 663 progress), September 2012. 665 [I-D.ietf-idr-dynamic-cap] 666 Ramachandra, S. and E. Chen, "Dynamic Capability for BGP- 667 4", draft-ietf-idr-dynamic-cap-14 (work in progress), 668 December 2011. 670 [I-D.ietf-v6ops-ula-usage-recommendations] 671 Liu, B. and S. Jiang, "Considerations For Using Unique 672 Local Addresses", draft-ietf-v6ops-ula-usage- 673 recommendations-04 (work in progress), October 2014. 675 [ISO10589] 676 International Standards Organization, "Intermediate system 677 to Intermediate system intra-domain routeing information 678 exchange protocol for use in conjunction with the protocol 679 for providing the connectionless-mode Network Service (ISO 680 8473)", International Standard 10589:2002, Nov 2002. 682 [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, 683 January 1997. 685 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 687 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 688 Extensions for IPv6 Inter-Domain Routing", RFC 2545, March 689 1999. 691 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 692 BGP-4", RFC 3107, May 2001. 694 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 695 Networks (VPNs)", RFC 4364, February 2006. 697 [RFC4472] Durand, A., Ihren, J., and P. Savola, "Operational 698 Considerations and Issues with IPv6 DNS", RFC 4472, April 699 2006. 701 [RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality 702 for OSPFv3", RFC 4552, June 2006. 704 [RFC4852] Bound, J., Pouffary, Y., Klynsma, S., Chown, T., and D. 705 Green, "IPv6 Enterprise Network Analysis - IP Layer 3 706 Focus", RFC 4852, April 2007. 708 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 709 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 710 September 2007. 712 [RFC4942] Davies, E., Krishnan, S., and P. Savola, "IPv6 Transition/ 713 Co-existence Security Considerations", RFC 4942, September 714 2007. 716 [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. 717 Pignataro, "The Generalized TTL Security Mechanism 718 (GTSM)", RFC 5082, October 2007. 720 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 721 Topology (MT) Routing in Intermediate System to 722 Intermediate Systems (IS-ISs)", RFC 5120, February 2008. 724 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 725 Authentication", RFC 5304, October 2008. 727 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October 728 2008. 730 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 731 for IPv6", RFC 5340, July 2008. 733 [RFC5375] Van de Velde, G., Popoviciu, C., Chown, T., Bonness, O., 734 and C. Hahn, "IPv6 Unicast Address Assignment 735 Considerations", RFC 5375, December 2008. 737 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 738 Aggarwal, "Support of Address Families in OSPFv3", RFC 739 5838, April 2010. 741 [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP 742 Authentication Option", RFC 5925, June 2010. 744 [RFC5963] Gagliano, R., "IPv6 Deployment in Internet Exchange Points 745 (IXPs)", RFC 5963, August 2010. 747 [RFC6180] Arkko, J. and F. Baker, "Guidelines for Using IPv6 748 Transition Mechanisms during IPv6 Deployment", RFC 6180, 749 May 2011. 751 [RFC6342] Koodli, R., "Mobile Networks Considerations for IPv6 752 Deployment", RFC 6342, August 2011. 754 [RFC6782] Kuarsingh, V. and L. Howard, "Wireline Incremental IPv6", 755 RFC 6782, November 2012. 757 [RFC6883] Carpenter, B. and S. Jiang, "IPv6 Guidance for Internet 758 Content Providers and Application Service Providers", RFC 759 6883, March 2013. 761 [RFC7381] Chittimaneni, K., Chown, T., Howard, L., Kuarsingh, V., 762 Pouffary, Y., and E. Vyncke, "Enterprise IPv6 Deployment 763 Guidelines", RFC 7381, October 2014. 765 [RFC7404] Behringer, M. and E. Vyncke, "Using Only Link-Local 766 Addressing inside an IPv6 Network", RFC 7404, November 767 2014. 769 [v6-addressing-plan] 770 SurfNet, "Preparing an IPv6 Address Plan", 2013, 771 . 775 Authors' Addresses 777 Philip Matthews 778 Alcatel-Lucent 779 600 March Road 780 Ottawa, Ontario K2K 2E6 781 Canada 783 Phone: +1 613-784-3139 784 Email: philip_matthews@magma.ca 786 Victor Kuarsingh 787 Dyn 788 150 Dow Street 789 Manchester, NH 03101 790 USA 792 Email: victor@jvknet.com