Analysis of the 64-bit Boundary in IPv6 Addressing
draft-carpenter-6man-why64-01
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian E. Carpenter , Tim Chown , Fernando Gont , Sheng Jiang , Alexandre Petrescu , Andrew Yourtchenko | ||
| Last updated | 2014-03-26 (Latest revision 2014-02-05) | ||
| Replaced by | draft-ietf-6man-why64 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-why64 | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 E. Carpenter
Tim Chown
Fernando Gont
Sheng Jiang
Alexandre Petrescu
Andrew Yourtchenko
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)