Return to site

Modified Eui 64 Format

broken image


The TCP/IP Guide
9TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
9TCP/IP Internet Layer (OSI Network Layer) Protocols
9Internet Protocol (IP/IPv4, IPng/IPv6) and IP-Related Protocols (IP NAT, IPSec, Mobile IP)
9Internet Protocol Version 6 (IPv6) / IP Next Generation (IPng)
9IPv6 Addressing

The second half of the address (64-bits) is used by interface ID. Interface ID must be unique on the subnet and are derived from the hardware (MAC) address of the device. The resulting format is called modified EUI-64. The process of deriving address from MAC address is displayed in Figure 5. Package eui64 enables creation and parsing of Modified EUI-64 format interface identifiers, as described in RFC 4291, Section 2.5.1. mdlayher/eui64.

  1. Network Working Group Appendix A: Creating Modified EUI-64 Format Interface Identifiers.20 Appendix B: Changes from RFC 3513.
  2. A form of this format, called modified EUI-64, has been adopted for IPv6 interface identifiers. To get the modified EUI-64 interface ID for a device, you simply take the EUI-64 address and change the 7th bit from the left (the 'universal/local' or 'U/L' bit) from a zero to a one.
  3. The Modified EUI-64 format interface identifiers with the 'u' bit set to one (1) as universal. Excerpt from same RFC above, page 22. I've also read that a valid OUI should NEVER have a 1 in the 7th position so by 'flipping' the position, we are really just making sure it's set to '1' for local. Thoughts on this?
Eui
IPv6 Global Unicast Address Format
1
2
IPv6 Special Addresses: Reserved, Private (Link-Local / Site-Local), Unspecified and Loopback

IPv6 Interface Identifiers and Physical Address Mapping
(Page 1 of 2)

In IPv4, IP addresses have no relationship to the addresses used for underlying data link layer network technologies. Backyard baseball 2005 torrent. A host that connects to a TCP/IP network using an Ethernet network interface card (NIC) has an Ethernet MAC address and an IP address, but the two numbers are distinct and unrelated in any way. IP addresses are assigned manually by administrators without any regard for the underlying physical address.

Eui 64 Address

The Payoff of IPv6's Very Large Address Size

With the overhaul of addressing in IPv6, an opportunity presented itself to create a better way of mapping IP unicast addresses and physical network addresses. Implementing this superior mapping technique was one of the reasons why IPv6 addresses were made so large. With 128 total bits, as we saw in the previous topic, even with a full 45 bits reserved for network prefix and 16 bits for site subnet, we are still left with 64 bits to use for the interface identifier, which is analogous to the host ID under IPv4.

Modified eui 64 formats
IPv6 Global Unicast Address Format
1
2
IPv6 Special Addresses: Reserved, Private (Link-Local / Site-Local), Unspecified and Loopback

IPv6 Interface Identifiers and Physical Address Mapping
(Page 1 of 2)

In IPv4, IP addresses have no relationship to the addresses used for underlying data link layer network technologies. Backyard baseball 2005 torrent. A host that connects to a TCP/IP network using an Ethernet network interface card (NIC) has an Ethernet MAC address and an IP address, but the two numbers are distinct and unrelated in any way. IP addresses are assigned manually by administrators without any regard for the underlying physical address.

Eui 64 Address

The Payoff of IPv6's Very Large Address Size

With the overhaul of addressing in IPv6, an opportunity presented itself to create a better way of mapping IP unicast addresses and physical network addresses. Implementing this superior mapping technique was one of the reasons why IPv6 addresses were made so large. With 128 total bits, as we saw in the previous topic, even with a full 45 bits reserved for network prefix and 16 bits for site subnet, we are still left with 64 bits to use for the interface identifier, which is analogous to the host ID under IPv4.

Having so many bits at our disposal gives us great flexibility. Instead of using arbitrary 'made-up' identifiers for hosts, we can base the interface ID on the underlying data link layer hardware address, as long as that address is no greater than 64 bits in length. Since virtually all devices use layer two addresses of 64 bits or fewer, there is no problem in using those addresses for the interface identifier in IP addresses. This provides an immediate benefit: it makes networks easier to administer, since we don't have to record two arbitrary numbers for each host. The IP address can be derived from the MAC address and the network identifier. It also means we can in the future tell the IP address from the MAC address and vice-versa.

The IPv6 Modified EUI-64 Format

The actual mapping from data link layer addresses to IP interface identifiers depends on the particular technology. It is essential that all devices on the same network use the same mapping technique, of course. By far the most common type of layer 2 addresses in networking are IEEE 802 MAC addresses, used by Ethernet and other IEEE 802 Project networking technologies. As you may already know, these addresses have 48 bits, arranged into two blocks of 24. The upper 24 bits are arranged into a block called the organizationally unique identifier (OUI), with different values assigned to individual organizations; the lower 24 bits are then used for an identifier for each specific device. Gamepigeon 20 questions.

The IEEE has also defined a format called the 64-bit extended unique identifier, abbreviated EUI-64. It is similar to the 48-bit MAC format, except that while the OUI remains at 24 bits, the device identifier becomes 40 bits instead of 24. This provides gives each manufacturer 65,536 times as many device addresses within its OUI.

Modified Eui 64 Formats

A form of this format, called modified EUI-64, has been adopted for IPv6 interface identifiers. To get the modified EUI-64 interface ID for a device, you simply take the EUI-64 address and change the 7th bit from the left (the 'universal/local' or 'U/L' bit) from a zero to a one.


IPv6 Global Unicast Address Format
1
2
IPv6 Special Addresses: Reserved, Private (Link-Local / Site-Local), Unspecified and Loopback

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!


Home - Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.

Eui 64 Calculator

Re: [BEHAVE] Modified EUI-64 format

Rémi Després Fri, 03 July 2009 13:11 UTC

Roxio toast 9 titanium. Return-Path:
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D08B528C2D1 for ; Fri, 3 Jul 2009 06:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.455
X-Spam-Level:
X-Spam-Status: No, score=-1.455 tagged_above=-999 required=5 tests=[AWL=0.494, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8pERtKyIEeM for ; Fri, 3 Jul 2009 06:11:25 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id EC3863A6B81 for ; Fri, 3 Jul 2009 06:09:48 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id A5980E080A5; Fri, 3 Jul 2009 15:10:07 +0200 (CEST)
Received: from [192.168.0.13] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 32DA2E0807C; Fri, 3 Jul 2009 15:10:03 +0200 (CEST)
In-Reply-To:
References:
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <18256DC3-184D-48FE-B37C-2F9867597304@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?=
Date: Fri, 3 Jul 2009 15:10:01 +0200
To: Dave Thaler
X-Mailer: Apple Mail (2.753.1)
Cc: Behave WG , Xing Li
Subject: Re: [BEHAVE] Modified EUI-64 format
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 03 Jul 2009 13:11:25 -0000

  • [BEHAVE] Modified EUI-64 format Dave Thaler
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Brian E Carpenter
  • Re: [BEHAVE] Modified EUI-64 format Dave Thaler
  • Re: [BEHAVE] Modified EUI-64 format Dave Thaler
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Brian E Carpenter
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • [BEHAVE] Perils of structured host identifiers (w… Christian Huitema
  • Re: [BEHAVE] Perils of structured host identifiers marcelo bagnulo braun
  • Re: [BEHAVE] Modified EUI-64 format Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifiers Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Perils of structured host identifier… Christian Huitema
  • Re: [BEHAVE] Modified EUI-64 format Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Rémi Després
  • Re: [BEHAVE] Perils of structured host identifier… Christian Huitema
  • Re: [BEHAVE] Modified EUI-64 format Dave Thaler
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Dave Thaler
  • Re: [BEHAVE] Perils of structured host identifier… Dave Thaler
  • Re: [BEHAVE] Perils of structured host identifiers Dave Thaler
  • Re: [BEHAVE] Perils of structured host identifiers Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifiers marcelo bagnulo braun
  • Re: [BEHAVE] Perils of structured host identifiers Iljitsch van Beijnum
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Perils of structured host identifiers marcelo bagnulo braun
  • Re: [BEHAVE] Perils of structured host identifier… Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Brian E Carpenter
  • Re: [BEHAVE] Modified EUI-64 format Bob Hinden
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Christian Huitema
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Christian Huitema
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifier… Mark Andrews
  • Re: [BEHAVE] Perils of structured host identifier… Iljitsch van Beijnum
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Iljitsch van Beijnum
  • Re: [BEHAVE] Modified EUI-64 format Rémi Després
  • Re: [BEHAVE] Modified EUI-64 format Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifiers Dave Thaler
  • Re: [BEHAVE] Modified EUI-64 format Xing Li
  • Re: [BEHAVE] Perils of structured host identifiers Iljitsch van Beijnum
  • Re: [BEHAVE] Perils of structured host identifiers Dave Thaler
  • Re: [BEHAVE] Modified EUI-64 format Jari Arkko




broken image