<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-6man-why64" target="https://datatracker.ietf.org/doc/html/draft-ietf-6man-why64-07">
   <front>
      <title>Analysis of the 64-bit Boundary in IPv6 Addressing</title>
      <author initials="B. E." surname="Carpenter" fullname="Brian E. Carpenter">
         </author>
      <author initials="T." surname="Chown" fullname="Tim Chown">
         </author>
      <author initials="F." surname="Gont" fullname="Fernando Gont">
         </author>
      <author initials="S." surname="Jiang" fullname="Sheng Jiang">
         </author>
      <author initials="A." surname="Petrescu" fullname="Alexandre Petrescu">
         </author>
      <author initials="A." surname="Yourtchenko" fullname="Andrew Yourtchenko">
         </author>
      <date month="October" day="19" year="2014" />
      <abstract>
	 <t>   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6man-why64-07" />
   
</reference>
