![]() So why do we have an identifier in IPv6 explicitly but not in IPv4? A simplified explanation is that unicast IPv4 addresses were defined and deployed at a time when it was uncommon for a network endpoint (referred to as a node in IPv6) to have more than one network interface. In this IPv6 back-to-basics blog, we’ll take a closer look at IPv6 interface identifiers along with how they are configured and used in operations.Ī Brief History of IPv6 IIDs (or How I Learned to Stop Worrying and Decouple the Identification of Nodes from the Identification of Interfaces) Among other benefits, this facilitates the use of multicast instead of broadcast and thus reduces the volume of unnecessary traffic allowing switches and routers to operate more efficiently.Īnother example of a characteristic unique to IPv6 (and offering an operational benefit) is the concept and definition of an interface identifier (or IID) as part of the overall IPv6 address. ![]() But many elements did and the best of these exist to make deployment and management of the protocol easier and more efficient.įor example, IPv6 Neighbor Discovery provides automated layer 3 address management and communication on any single network segment. The original designers of IPv6 made sure to take advantage of the opportunity to rebuild the Internet Protocol from the “ground up.” Of course, not everything they proposed has yet found its way into typical network operations. Besides the virtually unlimited address space (a quantity that experts have argued will likely outlast the lifespan of the protocol itself), IPv6 offers many unique characteristics and features that are not found in IPv4 (i.e., the legacy Internet Protocol).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |