<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML ><HEAD ><TITLE >Address types (host part)</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="Linux IPv6 HOWTO (en)" HREF="index.html"><LINK REL="UP" TITLE="Address types" HREF="chapter-addresstypes.html"><LINK REL="PREVIOUS" TITLE="Network part, also known as prefix" HREF="x512.html"><LINK REL="NEXT" TITLE="Prefix lengths for routing" HREF="x683.html"></HEAD ><BODY CLASS="SECT1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >Linux IPv6 HOWTO (en)</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="x512.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" >Chapter 3. Address types</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="x683.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="AEN658" ></A >3.3. Address types (host part)</H1 ><P >For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses.</P ><P >This host part can be inspected differently: </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN662" ></A >3.3.1. Automatically computed (also known as stateless)</H2 ><P >With auto-configuration, the host part of the address is computed by converting the MAC address of an interface (if available), with the EUI-64 method, to a unique IPv6 address. If no MAC address is available for this device (happens e.g. on virtual devices), something else (like the IPv4 address or the MAC address of a physical interface) is used instead.</P ><P >E.g. a NIC has following MAC address (48 bit):</P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >00:10:A4:E3:95:66</PRE ></FONT ></TD ></TR ></TABLE ><P >This would be expanded according to the<A HREF="http://standards.ieee.org/regauth/oui/tutorials/EUI64.html" TARGET="_top" >IEEE-Tutorial EUI-64</A > design for EUI-48 identifiers to the 64 bit interface identifier:</P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >0210:a4ff:fee3:9566</PRE ></FONT ></TD ></TR ></TABLE ><P >With a given prefix, the result is the IPv6 address shown in example above:</P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >2001:0db8:0100:f101:0210:a4ff:fee3:9566</PRE ></FONT ></TD ></TR ></TABLE ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A NAME="AEN672" ></A >3.3.1.1. Privacy problem with automatically computed addresses and a solution</H3 ><P >Because the "automatically computed" host part is globally unique (except when a vendor of a NIC uses the same MAC address on more than one NIC), client tracking is possible on the host when not using a proxy of any kind.</P ><P >This is a known problem, and a solution was defined: privacy extension, defined in <A HREF="http://www.faqs.org/rfcs/rfc3041.html" TARGET="_top" >RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6</A > (there is also already a newer draft available: <A HREF="http://www.ietf.org/ids.by.wg/ipv6.html" TARGET="_top" >draft-ietf-ipv6-privacy-addrs-v2-*</A >). Using a random and a static value a new suffix is generated from time to time. Note: this is only reasonable for outgoing client connections and isn't really useful for well-known servers.</P ></DIV ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN678" ></A >3.3.2. Manually set</H2 ><P >For servers, it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g. </P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >2001:0db8:100:f101::1</PRE ></FONT ></TD ></TR ></TABLE ><P >For manual suffixes like “::1” shown in the above example, it's required that the 7th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen ) bit combinations are reserved for anycast addresses, too.</P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="x512.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="x683.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Network part, also known as prefix</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="chapter-addresstypes.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Prefix lengths for routing</TD ></TR ></TABLE ></DIV ></BODY ></HTML >
