Analysis of the 64-bit Boundary in IPv6 Addressing
draft-carpenter-6man-why64-01

Document Type Replaced Internet-Draft (6man WG)
Last updated 2014-03-26 (latest revision 2014-02-05)
Replaced by draft-ietf-6man-why64
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-6man-why64
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-carpenter-6man-why64-01.txt

Abstract

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. Historically the interface identifier has been defined as 64 bits long, leaving 64 bits for the prefix. This document discusses the reasons for this fixed boundary and the issues involved in treating it as a variable boundary.

Authors

Brian Carpenter (brian.e.carpenter@gmail.com)
Tim Chown (tjc@ecs.soton.ac.uk)
Fernando Gont (fgont@si6networks.com)
Sheng Jiang (jiangsheng@huawei.com)
Alexandru Petrescu (alexandru.petrescu@cea.fr)
Andrew Yourtchenko (ayourtch@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)