…t all of the bits in the resulting Interface IDs are treated as "opaque" bits [ RFC7136 ]. For example, the universal/local bit of Modified EUI-64 format identifiers is treated as any other bit of such an identifier. In theory, this might result in IPv6 address collisions and DAD…

…OT assign addresses that use a reserved IPv6 Interface Identifier [ RFC5453 ] [ RFC7136 ] [ IANA-RESERVED-IID ]. See [ RFC7969 ] for a more detailed discussion on how servers determine a client's location on the network. 13.2 . Assignment of Temporary Addresses A client may reque…

…t all of the bits in the resulting Interface IDs are treated as "opaque" bits [ RFC7136 ]. For example, the universal/local bit of Modified EUI-64 format identifiers is treated as any other bit of such an identifier. In theory, this might result in IPv6 address collisions and DAD…

…havior. A workflow example is shown in Appendix A of this document. Note that [ RFC7136 ] updates [ RFC4291 ], which allows the use of unicast addresses without u-bit, as long as they're not derived from an IEEE MAC-layer address. Therefore, the address mapping algorithm defined …

…havior. A workflow example is shown in Appendix A of this document. Note that [ RFC7136 ] updates [ RFC4291 ], which allows the use of unicast addresses without u-bit, as long as they're not derived from an IEEE MAC-layer address. Therefore, the address mapping algorithm defined …