idnits 2.17.1 draft-ietf-6man-rfc4291bis-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 : ---------------------------------------------------------------------------- == There are 16 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 237 has weird spacing: '...address is an...' == 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 27, 2016) is 2918 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) -- Looks like a reference, but probably isn't: '1' on line 913 -- Looks like a reference, but probably isn't: '5' on line 917 == Outdated reference: A later version (-13) exists of draft-ietf-6man-rfc2460bis-04 -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-6man-rfc2460bis' == Outdated reference: A later version (-16) exists of draft-ietf-6man-default-iids-10 -- Obsolete informational reference (is this intentional?): RFC 3513 (Obsoleted by RFC 4291) -- Obsolete informational reference (is this intentional?): RFC 4941 (Obsoleted by RFC 8981) Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Hinden 3 Internet-Draft Check Point Software 4 Obsoletes: 4291 (if approved) S. Deering 5 Intended status: Standards Track Retired 6 Expires: October 29, 2016 April 27, 2016 8 IP Version 6 Addressing Architecture 9 draft-ietf-6man-rfc4291bis-02 11 Abstract 13 This specification defines the addressing architecture of the IP 14 Version 6 (IPv6) protocol. The document includes the IPv6 addressing 15 model, text representations of IPv6 addresses, definition of IPv6 16 unicast addresses, anycast addresses, and multicast addresses, and an 17 IPv6 node's required addresses. 19 This document obsoletes RFC 4291, "IP Version 6 Addressing 20 Architecture". 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on October 29, 2016. 39 Copyright Notice 41 Copyright (c) 2016 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 This document may contain material from IETF Documents or IETF 55 Contributions published or made publicly available before November 56 10, 2008. The person(s) controlling the copyright in some of this 57 material may not have granted the IETF Trust the right to allow 58 modifications of such material outside the IETF Standards Process. 59 Without obtaining an adequate license from the person(s) controlling 60 the copyright in such materials, this document may not be modified 61 outside the IETF Standards Process, and derivative works of it may 62 not be created outside the IETF Standards Process, except to format 63 it for publication as an RFC or to translate it into languages other 64 than English. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2. IPv6 Addressing . . . . . . . . . . . . . . . . . . . . . . . 3 70 2.1. Addressing Model . . . . . . . . . . . . . . . . . . . . 4 71 2.2. Text Representation of IPv6 Addresses . . . . . . . . . . 4 72 2.2.1. Text Representation of Addresses . . . . . . . . . . 4 73 2.2.2. Text Representation of Address Prefixes . . . . . . . 5 74 2.2.3. Recommendation for outputting IPv6 addresses . . . . 7 75 2.3. Address Type Identification . . . . . . . . . . . . . . . 9 76 2.4. Unicast Addresses . . . . . . . . . . . . . . . . . . . . 10 77 2.4.1. Interface Identifiers . . . . . . . . . . . . . . . . 11 78 2.4.2. The Unspecified Address . . . . . . . . . . . . . . . 12 79 2.4.3. The Loopback Address . . . . . . . . . . . . . . . . 12 80 2.4.4. Global Unicast Addresses . . . . . . . . . . . . . . 12 81 2.4.5. IPv6 Addresses with Embedded IPv4 Addresses . . . . . 13 82 2.4.5.1. IPv4-Compatible IPv6 Address . . . . . . . . . . 13 83 2.4.5.2. IPv4-Mapped IPv6 Address . . . . . . . . . . . . 13 84 2.4.6. Link-Local IPv6 Unicast Addresses . . . . . . . . . . 14 85 2.4.7. Site-Local IPv6 Unicast Addresses . . . . . . . . . . 14 86 2.5. Anycast Addresses . . . . . . . . . . . . . . . . . . . . 14 87 2.5.1. Required Anycast Address . . . . . . . . . . . . . . 15 88 2.6. Multicast Addresses . . . . . . . . . . . . . . . . . . . 16 89 2.6.1. Pre-Defined Multicast Addresses . . . . . . . . . . . 19 90 2.7. A Node's Required Addresses . . . . . . . . . . . . . . . 20 91 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 92 4. Security Considerations . . . . . . . . . . . . . . . . . . . 21 93 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 94 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 95 6.1. Normative References . . . . . . . . . . . . . . . . . . 22 96 6.2. Informative References . . . . . . . . . . . . . . . . . 22 98 Appendix A. Modified EUI-64 Format Interface Identifiers . . . . 24 99 A.1. Creating Modified EUI-64 Format Interface Identifiers . . 25 100 Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 27 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 103 1. Introduction 105 This specification defines the addressing architecture of the IP 106 Version 6 protocol. It includes the basic formats for the various 107 types of IPv6 addresses (unicast, anycast, and multicast). 109 2. IPv6 Addressing 111 IPv6 addresses are 128-bit identifiers for interfaces and sets of 112 interfaces (where "interface" is as defined in Section 2 of 113 [I-D.ietf-6man-rfc2460bis]). There are three types of addresses: 115 Unicast: An identifier for a single interface. A packet sent 116 to a unicast address is delivered to the interface 117 identified by that address. 119 Anycast: An identifier for a set of interfaces (typically 120 belonging to different nodes). A packet sent to an 121 anycast address is delivered to one of the interfaces 122 identified by that address (the "nearest" one, 123 according to the routing protocols' measure of 124 distance). 126 Multicast: An identifier for a set of interfaces (typically 127 belonging to different nodes). A packet sent to a 128 multicast address is delivered to all interfaces 129 identified by that address. 131 There are no broadcast addresses in IPv6, their function being 132 superseded by multicast addresses. 134 In this document, fields in addresses are given a specific name, for 135 example, "subnet". When this name is used with the term "ID" for 136 identifier after the name (e.g., "subnet ID"), it refers to the 137 contents of the named field. When it is used with the term "prefix" 138 (e.g., "subnet prefix"), it refers to all of the address from the 139 left up to and including this field. 141 In IPv6, all zeros and all ones are legal values for any field, 142 unless specifically excluded. Specifically, prefixes may contain, or 143 end with, zero-valued fields. 145 2.1. Addressing Model 147 IPv6 addresses of all types are assigned to interfaces, not nodes. 148 An IPv6 unicast address refers to a single interface. Since each 149 interface belongs to a single node, any of that node's interfaces' 150 unicast addresses may be used as an identifier for the node. 152 All interfaces are required to have at least one Link-Local unicast 153 address (see Section 2.8 for additional required addresses). A 154 single interface may also have multiple IPv6 addresses of any type 155 (unicast, anycast, and multicast) or scope. Unicast addresses with a 156 scope greater than link-scope are not needed for interfaces that are 157 not used as the origin or destination of any IPv6 packets to or from 158 non-neighbors. This is sometimes convenient for point-to-point 159 interfaces. There is one exception to this addressing model: 161 A unicast address or a set of unicast addresses may be assigned to 162 multiple physical interfaces if the implementation treats the 163 multiple physical interfaces as one interface when presenting it 164 to the internet layer. This is useful for load-sharing over 165 multiple physical interfaces. 167 Currently, IPv6 continues the IPv4 model in that a subnet prefix is 168 associated with one link. Multiple subnet prefixes may be assigned 169 to the same link. 171 2.2. Text Representation of IPv6 Addresses 173 2.2.1. Text Representation of Addresses 175 There are three conventional forms for representing IPv6 addresses as 176 text strings: 178 1. The preferred form is x:x:x:x:x:x:x:x, where the 'x's are one to 179 four hexadecimal digits of the eight 16-bit pieces of the address. 180 Examples: 182 abcd:ef01:2345:6789:abcd:ef01:2345:6789 183 2001:db8:0:0:8:800:200c:417a 185 Note that it is not necessary to write the leading zeros in an 186 individual field, but there must be at least one numeral in every 187 field (except for the case described in 2.). 189 2. Due to some methods of allocating certain styles of IPv6 190 addresses, it will be common for addresses to contain long strings 191 of zero bits. In order to make writing addresses containing zero 192 bits easier, a special syntax is available to compress the zeros. 193 The use of "::" indicates one or more groups of 16 bits of zeros. 194 The "::" can only appear once in an address. The "::" can also be 195 used to compress leading or trailing zeros in an address. 197 For example, the following addresses 199 2001:db8:0:0:8:800:200c:417a a unicast address 200 ff01:0:0:0:0:0:0:101 a multicast address 201 0:0:0:0:0:0:0:1 the loopback address 202 0:0:0:0:0:0:0:0 the unspecified address 204 may be represented as 206 2001:db8::8:800:200c:417a a unicast address 207 ff01::101 a multicast address 208 ::1 the loopback address 209 :: the unspecified address 211 3. An alternative form that is sometimes more convenient when dealing 212 with a mixed environment of IPv4 and IPv6 nodes is 213 x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values of 214 the six high-order 16-bit pieces of the address, and the 'd's are 215 the decimal values of the four low-order 8-bit pieces of the 216 address (standard IPv4 representation). Examples: 218 0:0:0:0:0:0:13.1.68.3 219 0:0:0:0:0:ffff:129.144.52.38 221 or in compressed form: 223 ::13.1.68.3 224 ::ffff:129.144.52.38 226 2.2.2. Text Representation of Address Prefixes 228 The text representation of IPv6 address prefixes is similar to the 229 way IPv4 address prefixes are written in Classless Inter-Domain 230 Routing (CIDR) notation [RFC4632]. An IPv6 address prefix is 231 represented by the notation: 233 ipv6-address/prefix-length 235 where 237 ipv6-address is an IPv6 address in any of the notations listed in 238 Section 2.2. 240 prefix-length is a decimal value specifying how many of the leftmost 241 contiguous bits of the address comprise the prefix. 243 For example, the following are legal representations of the 60-bit 244 prefix 20010db80000cd3 (hexadecimal): 246 2001:0db8:0000:cd30:0000:0000:0000:0000/60 248 2001:0db8::cd30:0:0:0:0/60 250 2001:0db8:0:cd30::/60 252 The following are NOT legal representations of the above prefix: 254 2001:0db8:0:cd3/60 may drop leading zeros, but not trailing 255 zeros, within any 16-bit chunk of the address 257 2001:0db8::cd30/60 address to left of "/" expands to 258 2001:0db8:0000:0000:0000:0000:0000:cd30 260 2001:0db8::cd3/60 address to left of "/" expands to 261 2001:0db8:0000:0000:0000:0000:0000:0cd3 263 When writing both a node address and a prefix of that node address 264 (e.g., the node's subnet prefix), the two can be combined as follows: 266 the node address 2001:0db8:0:cd30:123:4567:89ab:cdef 267 and its subnet number 2001:0db8:0:cd30::/60 269 can be abbreviated as 2001:0db8:0:cd30:123:4567:89ab:cdef/60 271 2.2.3. Recommendation for outputting IPv6 addresses 273 This section provides a recommendation for systems generating and 274 outputting IPv6 addresses as text. Note, all implementations must 275 accept and process all addresses in the formats defined in the 276 previous two sections of this document. The recommendations are as 277 follows: 279 1. The hexadecimal digits "a", "b", "c", "d", "e", and "f" in an IPv6 280 address must be represented in lowercase. 282 2. Leading zeros in a 16-Bit Field must be suppressed. For example, 284 2001:0db8::0001 286 is not correct and must be represented as 288 2001:db8::1 290 3. A single 16-bit 0000 field must be represented as 0. 292 The use of the symbol "::" must be used to its maximum capability. 293 For example: 295 2001:db8:0:0:0:0:2:1 297 must be shortened to 299 2001:db8::2:1 301 Likewise, 303 2001:db8::0:1 305 is not correct, because the symbol "::" could have been used to 306 produce a shorter representation 307 2001:db8::1. 309 4. When there is an alternative choice in the placement of a "::", 310 the longest run of consecutive 16-bit 0 fields must be shortened, 311 that is, in 313 2001:0:0:1:0:0:0:1 315 the sequence with three consecutive zero fields is shortened to 317 2001:0:0:1::1 319 5. When the length of the consecutive 16-bit 0 fields are equal, for 320 example 322 2001:db8:0:0:1:0:0:1 324 the first sequence of zero bits must be shortened. For example 326 2001:db8::1:0:0:1 328 is the correct representation. 330 6. The symbol "::" must not be used to shorten just one 16-bit 0 331 field. For example, the representation 333 2001:db8:0:1:1:1:1:1 335 is correct, but 337 2001:db8::1:1:1:1:1 339 is not correct. 341 7. The text representation method describe in this section should 342 also be use for text Representation of IPv6 Address Prefixes. For 343 example 345 0:0:0:0:0:ffff:192.0.2.1 347 should be shown as 349 ::ffff:192.0.2.1 351 8. The text representation method describe in this section should be 352 applied for IPv6 addresses with embedded IPv4 address. For 353 example 355 2001:0db8:0000:cd30:0000:0000:0000:0000/60 357 should be shown as 359 2001:0db8:0:cd30::/60 361 2.3. Address Type Identification 363 The type of an IPv6 address is identified by the high-order bits of 364 the address, as follows: 366 Address type Binary prefix IPv6 notation Section 367 ------------ ------------- ------------- ------- 368 Unspecified 00...0 (128 bits) ::/128 2.5.2 369 Loopback 00...1 (128 bits) ::1/128 2.5.3 370 Multicast 11111111 ff00::/8 2.7 371 Link-Local unicast 1111111010 fe80::/10 2.5.6 372 Global Unicast (everything else) 374 Anycast addresses are taken from the unicast address spaces (of any 375 scope) and are not syntactically distinguishable from unicast 376 addresses. 378 The general format of Global Unicast addresses is described in 379 Section 2.5.4. Some special-purpose subtypes of Global Unicast 380 addresses that contain embedded IPv4 addresses (for the purposes of 381 IPv4-IPv6 interoperation) are described in Section 2.5.5. 383 Future specifications may redefine one or more sub-ranges of the 384 Global Unicast space for other purposes, but unless and until that 385 happens, implementations must treat all addresses that do not start 386 with any of the above-listed prefixes as Global Unicast addresses. 388 The current assigned IPv6 prefixes and references to their usage can 389 be found in the IANA Internet Protocol Version 6 Address Space 390 registry [IANA-AD] and the IANA IPv6 Special-Purpose Address Registry 391 [IANA-SP]. 393 2.4. Unicast Addresses 395 IPv6 unicast addresses are aggregatable with prefixes of arbitrary 396 bit-length, similar to IPv4 addresses under Classless Inter-Domain 397 Routing. 399 There are several types of unicast addresses in IPv6, in particular, 400 Global Unicast, site-local unicast (deprecated, see Section 2.5.7), 401 and Link-Local unicast. There are also some special-purpose subtypes 402 of Global Unicast, such as IPv6 addresses with embedded IPv4 403 addresses. Additional address types or subtypes can be defined in 404 the future. 406 IPv6 nodes may have considerable or little knowledge of the internal 407 structure of the IPv6 address, depending on the role the node plays 408 (for instance, host versus router). At a minimum, a node may 409 consider that unicast addresses (including its own) have no internal 410 structure: 412 | 128 bits | 413 +-----------------------------------------------------------------+ 414 | node address | 415 +-----------------------------------------------------------------+ 417 A slightly sophisticated host (but still rather simple) may 418 additionally be aware of subnet prefix(es) for the link(s) it is 419 attached to, where different addresses may have different values for 420 n: 422 | n bits | 128-n bits | 423 +-------------------------------+---------------------------------+ 424 | subnet prefix | interface ID | 425 +-------------------------------+---------------------------------+ 426 Though a very simple router may have no knowledge of the internal 427 structure of IPv6 unicast addresses, routers will more generally have 428 knowledge of one or more of the hierarchical boundaries for the 429 operation of routing protocols. The known boundaries will differ 430 from router to router, depending on what positions the router holds 431 in the routing hierarchy. 433 Except for the knowledge of the subnet boundary discussed in the 434 previous paragraphs, nodes should not make any assumptions about the 435 structure of an IPv6 address. 437 2.4.1. Interface Identifiers 439 Interface identifiers in IPv6 unicast addresses are used to identify 440 interfaces on a link. They are required to be unique within a subnet 441 prefix. It is recommended that the same interface identifier not be 442 assigned to different nodes on a link. They may also be unique over 443 a broader scope. The same interface identifier may be used on 444 multiple interfaces on a single node, as long as they are attached to 445 different subnets. 447 Interface IDs must be viewed outside of the node that created 448 Interface ID as an opaque bit string without any internal structure. 450 Note that the uniqueness of interface identifiers is independent of 451 the uniqueness of IPv6 addresses. For example, a Global Unicast 452 address may be created with an interface identifier that is only 453 unique on a single subnet, and a Link-Local address may be created 454 with interface identifier that is unique over multiple subnets. 456 For all unicast addresses, except those that start with the binary 457 value 000, Interface IDs are required to be 64 bits long. 459 The details of forming interface identifiers are defined in other 460 specifications, such as "Privacy Extensions for Stateless Address 461 Autoconfiguration in IPv6" [RFC4941] and "Recommendation on Stable 462 IPv6 Interface Identifiers" [I-D.ietf-6man-default-iids]. Specific 463 cases are described in appropriate "IPv6 over " specifications, 464 such as "IPv6 over Ethernet" [RFC2464] and "Transmission of IPv6 465 Packets over ITU-T G.9959 Networks" [RFC7428]. 467 Earlier versions of this document described a method of forming 468 interface identifiers derived from IEEE MAC-layer addresses call 469 Modified EUI-64 format. These are described in Appendix A and are no 470 longer recommended. 472 2.4.2. The Unspecified Address 474 The address 0:0:0:0:0:0:0:0 is called the unspecified address. It 475 must never be assigned to any node. It indicates the absence of an 476 address. One example of its use is in the Source Address field of 477 any IPv6 packets sent by an initializing host before it has learned 478 its own address. 480 The unspecified address must not be used as the destination address 481 of IPv6 packets or in IPv6 Routing headers. An IPv6 packet with a 482 source address of unspecified must never be forwarded by an IPv6 483 router. 485 2.4.3. The Loopback Address 487 The unicast address 0:0:0:0:0:0:0:1 is called the loopback address. 488 It may be used by a node to send an IPv6 packet to itself. It must 489 not be assigned to any physical interface. It is treated as having 490 Link-Local scope, and may be thought of as the Link-Local unicast 491 address of a virtual interface (typically called the "loopback 492 interface") to an imaginary link that goes nowhere. 494 The loopback address must not be used as the source address in IPv6 495 packets that are sent outside of a single node. An IPv6 packet with 496 a destination address of loopback must never be sent outside of a 497 single node and must never be forwarded by an IPv6 router. A packet 498 received on an interface with a destination address of loopback must 499 be dropped. 501 2.4.4. Global Unicast Addresses 503 The general format for IPv6 Global Unicast addresses is as follows: 505 | n bits | m bits | 128-n-m bits | 506 +------------------------+-----------+----------------------------+ 507 | global routing prefix | subnet ID | interface ID | 508 +------------------------+-----------+----------------------------+ 510 where the global routing prefix is a (typically hierarchically- 511 structured) value assigned to a site (a cluster of subnets/links), 512 the subnet ID is an identifier of a link within the site, and the 513 interface ID is as defined in Section 2.5.1. 515 All Global Unicast addresses other than those that start with binary 516 000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as 517 described in Section 2.5.1. Global Unicast addresses that start with 518 binary 000 have no such constraint on the size or structure of the 519 interface ID field. 521 Examples of Global Unicast addresses that start with binary 000 are 522 the IPv6 address with embedded IPv4 addresses described in 523 Section 2.5.5. An example of global addresses starting with a binary 524 value other than 000 (and therefore having a 64-bit interface ID 525 field) can be found in [RFC3587]. 527 2.4.5. IPv6 Addresses with Embedded IPv4 Addresses 529 Two types of IPv6 addresses are defined that carry an IPv4 address in 530 the low-order 32 bits of the address. These are the "IPv4-Compatible 531 IPv6 address" and the "IPv4-mapped IPv6 address". 533 2.4.5.1. IPv4-Compatible IPv6 Address 535 The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6 536 transition. The format of the "IPv4-Compatible IPv6 address" is as 537 follows: 539 | 80 bits | 16 | 32 bits | 540 +--------------------------------------+--------------------------+ 541 |0000..............................0000|0000| IPv4 address | 542 +--------------------------------------+----+---------------------+ 544 Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" 545 must be a globally-unique IPv4 unicast address. 547 The "IPv4-Compatible IPv6 address" is now deprecated because the 548 current IPv6 transition mechanisms no longer use these addresses. 549 New or updated implementations are not required to support this 550 address type. 552 2.4.5.2. IPv4-Mapped IPv6 Address 554 A second type of IPv6 address that holds an embedded IPv4 address is 555 defined. This address type is used to represent the addresses of 556 IPv4 nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 557 address" is as follows: 559 | 80 bits | 16 | 32 bits | 560 +--------------------------------------+--------------------------+ 561 |0000..............................0000|ffff| IPv4 address | 562 +--------------------------------------+----+---------------------+ 564 See [RFC4038] for background on the usage of the "IPv4-mapped IPv6 565 address". 567 2.4.6. Link-Local IPv6 Unicast Addresses 569 Link-Local addresses are for use on a single link. Link-Local 570 addresses have the following format: 572 | 10 | 573 | bits | 54 bits | 64 bits | 574 +----------+-------------------------+----------------------------+ 575 |1111111010| 0 | interface ID | 576 +----------+-------------------------+----------------------------+ 578 Link-Local addresses are designed to be used for addressing on a 579 single link for purposes such as automatic address configuration, 580 neighbor discovery, or when no routers are present. 582 Routers must not forward any packets with Link-Local source or 583 destination addresses to other links. 585 2.4.7. Site-Local IPv6 Unicast Addresses 587 Site-Local addresses were originally designed to be used for 588 addressing inside of a site without the need for a global prefix. 589 Site-local addresses are now deprecated as defined in [RFC3879]. 591 Site-Local addresses have the following format: 593 | 10 | 594 | bits | 54 bits | 64 bits | 595 +----------+-------------------------+----------------------------+ 596 |1111111011| subnet ID | interface ID | 597 +----------+-------------------------+----------------------------+ 599 The special behavior of this prefix defined in [RFC3513] must no 600 longer be supported in new implementations (i.e., new implementations 601 must treat this prefix as Global Unicast). 603 Existing implementations and deployments may continue to use this 604 prefix. 606 2.5. Anycast Addresses 608 An IPv6 anycast address is an address that is assigned to more than 609 one interface (typically belonging to different nodes), with the 610 property that a packet sent to an anycast address is routed to the 611 "nearest" interface having that address, according to the routing 612 protocols' measure of distance. 614 Anycast addresses are allocated from the unicast address space, using 615 any of the defined unicast address formats. Thus, anycast addresses 616 are syntactically indistinguishable from unicast addresses. When a 617 unicast address is assigned to more than one interface, thus turning 618 it into an anycast address, the nodes to which the address is 619 assigned must be explicitly configured to know that it is an anycast 620 address. 622 For any assigned anycast address, there is a longest prefix P of that 623 address that identifies the topological region in which all 624 interfaces belonging to that anycast address reside. Within the 625 region identified by P, the anycast address must be maintained as a 626 separate entry in the routing system (commonly referred to as a "host 627 route"); outside the region identified by P, the anycast address may 628 be aggregated into the routing entry for prefix P. 630 Note that in the worst case, the prefix P of an anycast set may be 631 the null prefix, i.e., the members of the set may have no topological 632 locality. In that case, the anycast address must be maintained as a 633 separate routing entry throughout the entire Internet, which presents 634 a severe scaling limit on how many such "global" anycast sets may be 635 supported. Therefore, it is expected that support for global anycast 636 sets may be unavailable or very restricted. 638 One expected use of anycast addresses is to identify the set of 639 routers belonging to an organization providing Internet service. 640 Such addresses could be used as intermediate addresses in an IPv6 641 Routing header, to cause a packet to be delivered via a particular 642 service provider or sequence of service providers. 644 Some other possible uses are to identify the set of routers attached 645 to a particular subnet, or the set of routers providing entry into a 646 particular routing domain. 648 2.5.1. Required Anycast Address 650 The Subnet-Router anycast address is predefined. Its format is as 651 follows: 653 | n bits | 128-n bits | 654 +------------------------------------------------+----------------+ 655 | subnet prefix | 00000000000000 | 656 +------------------------------------------------+----------------+ 658 The "subnet prefix" in an anycast address is the prefix that 659 identifies a specific link. This anycast address is syntactically 660 the same as a unicast address for an interface on the link with the 661 interface identifier set to zero. 663 Packets sent to the Subnet-Router anycast address will be delivered 664 to one router on the subnet. All routers are required to support the 665 Subnet-Router anycast addresses for the subnets to which they have 666 interfaces. 668 The Subnet-Router anycast address is intended to be used for 669 applications where a node needs to communicate with any one of the 670 set of routers. 672 2.6. Multicast Addresses 674 An IPv6 multicast address is an identifier for a group of interfaces 675 (typically on different nodes). An interface may belong to any 676 number of multicast groups. Multicast addresses have the following 677 format: 679 | 8 | 4 | 4 | 112 bits | 680 +------ -+----+----+---------------------------------------------+ 681 |11111111|flgs|scop| group ID | 682 +--------+----+----+---------------------------------------------+ 684 binary 11111111 at the start of the address identifies the address 685 as being a multicast address. 687 +-+-+-+-+ 688 flgs is a set of 4 flags: |0|R|P|T| 689 +-+-+-+-+ 691 The high-order flag is reserved, and must be initialized to 0. 693 T = 0 indicates a permanently-assigned ("well-known") multicast 694 address, assigned by the Internet Assigned Numbers Authority 695 (IANA). 697 T = 1 indicates a non-permanently-assigned ("transient" or 698 "dynamically" assigned) multicast address. 700 The P flag's definition and usage can be found in [RFC3306]. 702 The R flag's definition and usage can be found in [RFC3956]. 704 scop is a 4-bit multicast scope value used to limit the scope of 705 the multicast group. The values are as follows: 707 0 reserved 708 1 Interface-Local scope 709 2 Link-Local scope 710 3 Realm-Local scope 711 4 Admin-Local scope 712 5 Site-Local scope 713 6 (unassigned) 714 7 (unassigned) 715 8 Organization-Local scope 716 9 (unassigned) 717 A (unassigned) 718 B (unassigned) 719 C (unassigned) 720 D (unassigned) 721 E Global scope 722 F reserved 724 Interface-Local scope spans only a single interface on a node 725 and is useful only for loopback transmission of multicast. 726 Packets with interface-local scope received from another node 727 must be discarded. 729 Link-Local multicast scope spans the same topological region as 730 the corresponding unicast scope. 732 Interface-Local, Link-Local, and Realm-Local scope boundaries 733 are automatically derived from physical connectivity or other 734 non-multicast-related configurations. Global scope has no 735 boundary. The boundaries of all other non-reserved scopes of 736 Admin-Local or larger are administratively configured. For 737 reserved scopes, the way of configuring their boundaries will 738 be defined when the semantics of the scope are defined. 740 According to [RFC4007], the zone of a Realm-Local scope must 741 fall within zones of larger scope. Because the zone of a 742 Realm-Local scope is configured automatically while the zones 743 of larger scopes are configured manually, care must be taken in 744 the definition of those larger scopes to ensure that the 745 inclusion constraint is met. 747 Realm-Local scopes created by different network technologies 748 are considered to be independent and will have different zone 749 indices (see Section 6 of [RFC4007]). A router with interfaces 750 on links using different network technologies does not forward 751 traffic between the Realm-Local multicast scopes defined by 752 those technologies. 754 Site-Local scope is intended to span a single site. 756 Organization-Local scope is intended to span multiple sites 757 belonging to a single organization. 759 scopes labeled "(unassigned)" are available for administrators 760 to define additional multicast regions. 762 group ID identifies the multicast group, either permanent or 763 transient, within the given scope. Additional definitions of the 764 multicast group ID field structure are provided in [RFC3306]. 766 The "meaning" of a permanently-assigned multicast address is 767 independent of the scope value. For example, if the "NTP servers 768 group" is assigned a permanent multicast address with a group ID of 769 101 (hex), then 771 ff01:0:0:0:0:0:0:101 means all NTP servers on the same interface 772 (i.e., the same node) as the sender. 774 ff02:0:0:0:0:0:0:101 means all NTP servers on the same link as the 775 sender. 777 ff05:0:0:0:0:0:0:101 means all NTP servers in the same site as the 778 sender. 780 ff0e:0:0:0:0:0:0:101 means all NTP servers in the Internet. 782 Non-permanently-assigned multicast addresses are meaningful only 783 within a given scope. For example, a group identified by the non- 784 permanent, site-local multicast address ff15:0:0:0:0:0:0:101 at one 785 site bears no relationship to a group using the same address at a 786 different site, nor to a non-permanent group using the same group ID 787 with a different scope, nor to a permanent group with the same group 788 ID. 790 Multicast addresses must not be used as source addresses in IPv6 791 packets or appear in any Routing header. 793 Routers must not forward any multicast packets beyond the scope 794 indicated by the scop field in the destination multicast address. 796 Nodes must not originate a packet to a multicast address whose scop 797 field contains the reserved value 0; if such a packet is received, it 798 must be silently dropped. Nodes should not originate a packet to a 799 multicast address whose scop field contains the reserved value F; if 800 such a packet is sent or received, it must be treated the same as 801 packets destined to a global (scop E) multicast address. 803 2.6.1. Pre-Defined Multicast Addresses 805 The following well-known multicast addresses are pre-defined. The 806 group IDs defined in this section are defined for explicit scope 807 values. 809 Use of these group IDs for any other scope values, with the T flag 810 equal to 0, is not allowed. 812 reserved multicast addresses: ff00:0:0:0:0:0:0:0 813 ff01:0:0:0:0:0:0:0 814 ff02:0:0:0:0:0:0:0 815 ff03:0:0:0:0:0:0:0 816 ff04:0:0:0:0:0:0:0 817 ff05:0:0:0:0:0:0:0 818 ff06:0:0:0:0:0:0:0 819 ff07:0:0:0:0:0:0:0 820 ff08:0:0:0:0:0:0:0 821 ff09:0:0:0:0:0:0:0 822 ff0a:0:0:0:0:0:0:0 823 ff0b:0:0:0:0:0:0:0 824 ff0c:0:0:0:0:0:0:0 825 ff0d:0:0:0:0:0:0:0 826 ff0e:0:0:0:0:0:0:0 827 ff0f:0:0:0:0:0:0:0 829 The above multicast addresses are reserved and shall never be 830 assigned to any multicast group. 832 all nodes addresses: ff01:0:0:0:0:0:0:1 833 ff02:0:0:0:0:0:0:1 835 The above multicast addresses identify the group of all IPv6 nodes, 836 within scope 1 (interface-local) or 2 (link-local). 838 all routers addresses: ff01:0:0:0:0:0:0:2 839 ff02:0:0:0:0:0:0:2 840 ff05:0:0:0:0:0:0:2 842 The above multicast addresses identify the group of all IPv6 routers, 843 within scope 1 (interface-local), 2 (link-local), or 5 (site-local). 845 Solicited-Node Address: ff02:0:0:0:0:1:ffxx:xxxx 847 Solicited-Node multicast address are computed as a function of a 848 node's unicast and anycast addresses. A Solicited-Node multicast 849 address is formed by taking the low-order 24 bits of an address 850 (unicast or anycast) and appending those bits to the prefix 851 FF02:0:0:0:0:1:FF00::/104 resulting in a multicast address in the 852 range 854 ff02:0:0:0:0:1:ff00:0000 856 to 858 ff02:0:0:0:0:1:ffff:ffff 860 For example, the Solicited-Node multicast address corresponding to 861 the IPv6 address 4037::01:800:200e:8c6c is ff02::1:ff0e:8c6c. IPv6 862 addresses that differ only in the high-order bits (e.g., due to 863 multiple high-order prefixes associated with different aggregations) 864 will map to the same Solicited-Node address, thereby reducing the 865 number of multicast addresses a node must join. 867 A node is required to compute and join (on the appropriate interface) 868 the associated Solicited-Node multicast addresses for all unicast and 869 anycast addresses that have been configured for the node's interfaces 870 (manually or automatically). 872 2.7. A Node's Required Addresses 874 A host is required to recognize the following addresses as 875 identifying itself: 877 o Its required Link-Local address for each interface. 879 o Any additional Unicast and Anycast addresses that have been 880 configured for the node's interfaces (manually or 881 automatically). 883 o The loopback address. 885 o The All-Nodes multicast addresses defined in Section 2.7.1. 887 o The Solicited-Node multicast address for each of its unicast 888 and anycast addresses. 890 o Multicast addresses of all other groups to which the node 891 belongs. 893 A router is required to recognize all addresses that a host is 894 required to recognize, plus the following addresses as identifying 895 itself: 897 o The Subnet-Router Anycast addresses for all interfaces for 898 which it is configured to act as a router. 900 o All other Anycast addresses with which the router has been 901 configured. 903 o The All-Routers multicast addresses defined in Section 2.7.1. 905 3. IANA Considerations 907 The "IPv4-Compatible IPv6 address" is deprecated by this document. 908 The IANA should continue to list the address block containing these 909 addresses at http://www.iana.org/assignments/ipv6-address-space as 910 "Reserved by IETF" and not reassign it for any other purpose. For 911 example: 913 0000::/8 Reserved by IETF [RFC3513] [1] 915 The IANA has added the following note and link to this address block. 917 [5] 0000::/96 was previously defined as the "IPv4-Compatible IPv6 918 address" prefix. This definition has been deprecated by 919 [RFC4291]. 921 The IANA has updated the references for the IPv6 Address Architecture 922 in the IANA registries accordingly. 924 4. Security Considerations 926 IPv6 addressing documents do not have any direct impact on Internet 927 infrastructure security. Authentication of IPv6 packets is defined 928 in [RFC4302]. 930 5. Acknowledgments 932 The authors would like to acknowledge the contributions of Paul 933 Francis, Scott Bradner, Jim Bound, Brian Carpenter, Matt Crawford, 934 Deborah Estrin, Roger Fajman, Bob Fink, Peter Ford, Bob Gilligan, 935 Dimitry Haskin, Tom Harsch, Christian Huitema, Tony Li, Greg 936 Minshall, Thomas Narten, Erik Nordmark, Yakov Rekhter, Bill Simpson, 937 Sue Thomson, Markku Savela, Larry Masinter, Jun-ichiro Itojun Hagino, 938 Tatuya Jinmei, Suresh Krishnan, and Mahmood Ali. 940 The authors would also like to acknowledge the authors of the 941 updating RFCs that were incorporated in this version of the document 942 to move IPv6 to Internet Standard. This includes Marcelo Bagnulo, 943 Congxiao Bao, Mohamed Boucadair, Brian Carpenter, Ralph Droms, 944 Christian Huitema, Sheng Jiang, Seiichi Kawamura, Masanobu Kawashima, 945 Xing Li, and Stig Venaas. 947 6. References 949 6.1. Normative References 951 [I-D.ietf-6man-rfc2460bis] 952 Deering, S. and R. Hinden, "Internet Protocol, Version 6 953 (IPv6) Specification", draft-ietf-6man-rfc2460bis-04 (work 954 in progress), March 2016. 956 6.2. Informative References 958 [EUI64] "IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) 959 Registration Authority"", March 1997, 960 . 963 [I-D.ietf-6man-default-iids] 964 Gont, F., Cooper, A., Thaler, D., and S. LIU, 965 "Recommendation on Stable IPv6 Interface Identifiers", 966 draft-ietf-6man-default-iids-10 (work in progress), 967 February 2016. 969 [IANA-AD] "Internet Protocol Version 6 Address Space", 970 . 973 [IANA-SP] "IANA IPv6 Special-Purpose Address Registry", 974 . 977 [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet 978 Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, 979 . 981 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 982 Multicast Addresses", RFC 3306, DOI 10.17487/RFC3306, 983 August 2002, . 985 [RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 986 (IPv6) Addressing Architecture", RFC 3513, DOI 10.17487/ 987 RFC3513, April 2003, 988 . 990 [RFC3587] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global 991 Unicast Address Format", RFC 3587, DOI 10.17487/RFC3587, 992 August 2003, . 994 [RFC3879] Huitema, C. and B. Carpenter, "Deprecating Site Local 995 Addresses", RFC 3879, DOI 10.17487/RFC3879, September 996 2004, . 998 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 999 Point (RP) Address in an IPv6 Multicast Address", RFC 1000 3956, DOI 10.17487/RFC3956, November 2004, 1001 . 1003 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 1004 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, DOI 1005 10.17487/RFC4007, March 2005, 1006 . 1008 [RFC4038] Shin, M-K., Ed., Hong, Y-G., Hagino, J., Savola, P., and 1009 E. Castro, "Application Aspects of IPv6 Transition", RFC 1010 4038, DOI 10.17487/RFC4038, March 2005, 1011 . 1013 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 1014 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 1015 2006, . 1017 [RFC4302] Kent, S., "IP Authentication Header", RFC 4302, DOI 1018 10.17487/RFC4302, December 2005, 1019 . 1021 [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing 1022 (CIDR): The Internet Address Assignment and Aggregation 1023 Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August 1024 2006, . 1026 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 1027 Extensions for Stateless Address Autoconfiguration in 1028 IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, 1029 . 1031 [RFC7428] Brandt, A. and J. Buron, "Transmission of IPv6 Packets 1032 over ITU-T G.9959 Networks", RFC 7428, DOI 10.17487/ 1033 RFC7428, February 2015, 1034 . 1036 Appendix A. Modified EUI-64 Format Interface Identifiers 1038 Modified EUI-64 format-based interface identifiers may have universal 1039 scope when derived from a universal token (e.g., IEEE 802 48-bit MAC 1040 or IEEE EUI-64 identifiers [EUI64]) or may have local scope where a 1041 global token is not being used (e.g., serial links, tunnel end- 1042 points) or where global tokens are undesirable (e.g., temporary 1043 tokens for privacy [RFC4941]. 1045 Modified EUI-64 format interface identifiers are formed by inverting 1046 the "u" bit (universal/local bit in IEEE EUI-64 terminology) when 1047 forming the interface identifier from IEEE EUI-64 identifiers. In 1048 the resulting Modified EUI-64 format, the "u" bit is set to one (1) 1049 to indicate universal scope, and it is set to zero (0) to indicate 1050 local scope. The first three octets in binary of an IEEE EUI-64 1051 identifier are as follows: 1053 0 0 0 1 1 2 1054 |0 7 8 5 6 3| 1055 +----+----+----+----+----+----+ 1056 |cccc|ccug|cccc|cccc|cccc|cccc| 1057 +----+----+----+----+----+----+ 1059 written in Internet standard bit-order, where "u" is the universal/ 1060 local bit, "g" is the individual/group bit, and "c" is the bits of 1061 the company_id. Appendix A, "Creating Modified EUI-64 Format 1062 Interface Identifiers", provides examples on the creation of Modified 1063 EUI-64 format-based interface identifiers. 1065 The motivation for inverting the "u" bit when forming an interface 1066 identifier is to make it easy for system administrators to hand 1067 configure non-global identifiers when hardware tokens are not 1068 available. This is expected to be the case for serial links and 1069 tunnel end-points, for example. The alternative would have been for 1070 these to be of the form 0200:0:0:1, 0200:0:0:2, etc., instead of the 1071 much simpler 0:0:0:1, 0:0:0:2, etc. 1073 IPv6 nodes are not required to validate that interface identifiers 1074 created with modified EUI-64 tokens with the "u" bit set to universal 1075 are unique. 1077 A.1. Creating Modified EUI-64 Format Interface Identifiers 1079 Depending on the characteristics of a specific link or node, there 1080 are a number of approaches for creating Modified EUI-64 format 1081 interface identifiers. This appendix describes some of these 1082 approaches. 1084 Links or Nodes with IEEE EUI-64 Identifiers 1086 The only change needed to transform an IEEE EUI-64 identifier to an 1087 interface identifier is to invert the "u" (universal/local) bit. An 1088 example is a globally unique IEEE EUI-64 identifier of the form: 1090 |0 1|1 3|3 4|4 6| 1091 |0 5|6 1|2 7|8 3| 1092 +----------------+----------------+----------------+----------------+ 1093 |cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm| 1094 +----------------+----------------+----------------+----------------+ 1096 where "c" is the bits of the assigned company_id, "0" is the value of 1097 the universal/local bit to indicate universal scope, "g" is 1098 individual/group bit, and "m" is the bits of the manufacturer- 1099 selected extension identifier. The IPv6 interface identifier would 1100 be of the form: 1102 |0 1|1 3|3 4|4 6| 1103 |0 5|6 1|2 7|8 3| 1104 +----------------+----------------+----------------+----------------+ 1105 |cccccc1gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm| 1106 +----------------+----------------+----------------+----------------+ 1108 The only change is inverting the value of the universal/local bit. 1110 Links or Nodes with IEEE 802 48-bit MACs 1112 [EUI64] defines a method to create an IEEE EUI-64 identifier from an 1113 IEEE 48-bit MAC identifier. This is to insert two octets, with 1114 hexadecimal values of 0xFF and 0xFE (see the Note at the end of 1115 appendix), in the middle of the 48-bit MAC (between the company_id 1116 and vendor-supplied id). An example is the 48-bit IEEE MAC with 1117 Global scope: 1119 |0 1|1 3|3 4| 1120 |0 5|6 1|2 7| 1121 +----------------+----------------+----------------+ 1122 |cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm| 1123 +----------------+----------------+----------------+ 1125 where "c" is the bits of the assigned company_id, "0" is the value of 1126 the universal/local bit to indicate Global scope, "g" is individual/ 1127 group bit, and "m" is the bits of the manufacturer- selected 1128 extension identifier. The interface identifier would be of the form: 1130 |0 1|1 3|3 4|4 6| 1131 |0 5|6 1|2 7|8 3| 1132 +----------------+----------------+----------------+----------------+ 1133 |cccccc1gcccccccc|cccccccc11111111|11111110mmmmmmmm|mmmmmmmmmmmmmmmm| 1134 +----------------+----------------+----------------+----------------+ 1136 When IEEE 802 48-bit MAC addresses are available (on an interface or 1137 a node), an implementation may use them to create interface 1138 identifiers due to their availability and uniqueness properties. 1140 Links with Other Kinds of Identifiers 1142 There are a number of types of links that have link-layer interface 1143 identifiers other than IEEE EUI-64 or IEEE 802 48-bit MACs. Examples 1144 include LocalTalk and Arcnet. The method to create a Modified EUI-64 1145 format identifier is to take the link identifier (e.g., the LocalTalk 1146 8-bit node identifier) and zero fill it to the left. For example, a 1147 LocalTalk 8-bit node identifier of hexadecimal value 0x4F results in 1148 the following interface identifier: 1150 |0 1|1 3|3 4|4 6| 1151 |0 5|6 1|2 7|8 3| 1152 +----------------+----------------+----------------+----------------+ 1153 |0000000000000000|0000000000000000|0000000000000000|0000000001001111| 1154 +----------------+----------------+----------------+----------------+ 1156 Note that this results in the universal/local bit set to "0" to 1157 indicate local scope. 1159 Links without Identifiers 1161 There are a number of links that do not have any type of built-in 1162 identifier. The most common of these are serial links and configured 1163 tunnels. Interface identifiers that are unique within a subnet 1164 prefix must be chosen. 1166 When no built-in identifier is available on a link, the preferred 1167 approach is to use a universal interface identifier from another 1168 interface or one that is assigned to the node itself. When using 1169 this approach, no other interface connecting the same node to the 1170 same subnet prefix may use the same identifier. 1172 If there is no universal interface identifier available for use on 1173 the link, the implementation needs to create a local-scope interface 1174 identifier. The only requirement is that it be unique within a 1175 subnet prefix. There are many possible approaches to select a 1176 subnet-prefix-unique interface identifier. These include the 1177 following: 1179 Manual Configuration 1180 Node Serial Number 1181 Other Node-Specific Token 1183 The subnet-prefix-unique interface identifier should be generated in 1184 a manner such that it does not change after a reboot of a node or if 1185 interfaces are added or deleted from the node. 1187 The selection of the appropriate algorithm is link and implementation 1188 dependent. The details on forming interface identifiers are defined 1189 in the appropriate "IPv6 over " specification. It is strongly 1190 recommended that a collision detection algorithm be implemented as 1191 part of any automatic algorithm. 1193 Note: [EUI64] actually defines 0xFF and 0xFF as the bits to be 1194 inserted to create an IEEE EUI-64 identifier from an IEEE MAC- 1195 48 identifier. The 0xFF and 0xFE values are used when 1196 starting with an IEEE EUI-48 identifier. The incorrect value 1197 was used in earlier versions of the specification due to a 1198 misunderstanding about the differences between IEEE MAC-48 and 1199 EUI-48 identifiers. 1201 This document purposely continues the use of 0xFF and 0xFE 1202 because it meets the requirements for IPv6 interface 1203 identifiers (i.e., that they must be unique on the link), IEEE 1204 EUI-48 and MAC-48 identifiers are syntactically equivalent, 1205 and that it doesn't cause any problems in practice. 1207 Appendix B. CHANGES SINCE RFC 4291 1209 This document has the following changes from RFC4291, "IP Version 6 1210 Addressing Architecture". Numbers identify the Internet-Draft 1211 version that the change was made.: 1213 Working Group Internet Drafts 1214 02) Remove changes made by RFC7371 because there isn't any known 1215 implementation experience. 1217 01) Revised Section 2.4.1 on Interface Identifiers to reflect 1218 current approach, this included saying Modified EUI-64 1219 identifiers not recommended and moved the text describing the 1220 format to Appendix A. 1222 01) Editorial changes. 1224 00) Working Group Draft. 1226 00) Editorial changes. 1228 Individual Internet Drafts 1230 06) Incorporate the updates made by RFC7371. The changes were to 1231 the flag bits and their definitions in Section 2.6. 1233 05) Incorporate the updates made by RFC7346. The change was to 1234 add Realm-Local scope to the multicast scope table in 1235 Section 2.6, and add the updating text to the same section. 1237 04) Incorporate the updates made by RFC6052. The change was to 1238 add a text in Section 2.3 that points to the IANA registries 1239 that records the prefix defined in RFC6052 and a number of 1240 other special use prefixes. 1242 03) Incorporate the updates made by RFC7136 to deprecate the U 1243 and G bits in Modified EUI-64 format Internet IDs. 1245 03) Add note to the reference section acknowledging the authors 1246 of the updating documents. 1248 03) Editorial changes. 1250 02) Updates to resolve the open Errata on RFC4291. These are: 1252 Errata ID: 3480: Corrects the definition of Interface- 1253 Local multicast scope to also state that packets with 1254 interface-local scope received from another node must be 1255 discarded. 1257 Errata ID: 1627: Remove extraneous "of" in Section 2.7. 1259 Errata ID: 2702: This errata is marked rejected. No 1260 change is required. 1262 Errata ID: 2735: This errata is marked rejected. No 1263 change is required. 1265 Errata ID: 4406: This errata is marked rejected. No 1266 change is required. 1268 Errata ID: 2406: This errata is marked rejected. No 1269 change is required. 1271 Errata ID: 863: This errata is marked rejected. No change 1272 is required. 1274 Errata ID: 864: This errata is marked rejected. No change 1275 is required. 1277 Errata ID: 866: This errata is marked rejected. No change 1278 is required. 1280 02) Update references to current versions. 1282 02) Editorial changes. 1284 01) Incorporate the updates made by RFC5952 regarding the text 1285 format when outputting IPv6 addresses. A new section was 1286 added for this and addresses shown in this document were 1287 changed to lower case. 1289 01) Revise this Section to document to show the changes from 1290 RFC4291. 1292 01) Editorial changes. 1294 00) Establish a baseline from RFC4291. The only intended changes 1295 are formatting (XML is slightly different from .nroff), 1296 differences between an RFC and Internet Draft, fixing a few 1297 ID Nits, and updates to the authors information. There 1298 should not be any content changes to the specification. 1300 Authors' Addresses 1301 Robert M. Hinden 1302 Check Point Software 1303 959 Skyway Road 1304 San Carlos, CA 94070 1305 USA 1307 Email: bob.hinden@gmail.com 1309 Stephen E. Deering 1310 Retired 1311 Vancouver, British Columbia 1312 Canada