{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

The selection of the appropriate algorithm is link

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ines 0xFF and 0xFF as the bits to be inserted to create an IEEE EUI-64 identifier from an IEEE MAC- 48 identifier. starting The 0xFF and 0xFE values are used when with an IEEE EUI-48 identifier. was used The incorrect value in earlier versions of the specification due to a misunderstanding about the differences between IEEE MAC-48 and EUI-48 identifiers. This document purposely continues the use of 0xFF and 0xFE because it meets the requirements for IPv6 interface identifiers (i.e., that they must be unique on the link), IEEE EUI-48 and MAC-48 identifiers are syntactically equivalent, and that it doesn't cause any problems in practice. Appendix B: Changes from RFC 3513 The following changes were made from RFC 3513, "IP Version 6 Addressing Architecture": o The restrictions on using IPv6 anycast addresses were removed because there is now sufficient experience with the use of anycast addresses, the issues are not specific to IPv6, and the GROW working group is working in this area. o Deprecated the Site-Local unicast prefix. the Changes include following: Hinden [Page 22] Standards Track RFC 4291 February 2006 IPv6 Addressing Architecture - Removed Site-Local from special list of prefixes in Section 2.4. - Split section titled "Local-use IPv6 Unicast Addresses" into two sections, "Link-Local IPv6 Unicast Address...
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online