[LAC-TF] Analysis of the 64-bit Boundary in IPv6 Addressing (Fwd: New Version Notification for draft-carpenter-6man-why64-01.txt)

[Fernando Gont]

FYI <http://www.ietf.org/internet-drafts/draft-carpenter-6man-why64-01.txt>

Sus comentarios serán bienvenidos.


-------- Original Message --------
Subject: New Version Notification for draft-carpenter-6man-why64-01.txt
Date: Wed, 05 Feb 2014 16:45:02 -0800
From: internet-drafts at ietf.org
To: Andrew Yourtchenko <ayourtch at cisco.com>, Tim Chown
<tjc at ecs.soton.ac.uk>, "Brian E. Carpenter"
<brian.e.carpenter at gmail.com>, "Sheng Jiang" <jiangsheng at huawei.com>,
Alexandru Petrescu <alexandru.petrescu at cea.fr>, "Andrew Yourtchenko"
<ayourtch at cisco.com>, "Tim Chown" <tjc at ecs.soton.ac.uk>, Fernando Gont
<fgont at si6networks.com>, "Fernando Gont" <fgont at si6networks.com>, Brian
Carpenter <brian.e.carpenter at gmail.com>, "Alexandru Petrescu"
<alexandru.petrescu at cea.fr>, Sheng Jiang <jiangsheng at huawei.com>


A new version of I-D, draft-carpenter-6man-why64-01.txt
has been successfully submitted by Brian Carpenter and posted to the
IETF repository.

Name:		draft-carpenter-6man-why64
Revision:	01
Title:		Analysis of the 64-bit Boundary in IPv6 Addressing
Document date:	2014-02-06
Group:		Individual Submission
Pages:		20
URL:
http://www.ietf.org/internet-drafts/draft-carpenter-6man-why64-01.txt
Status:         https://datatracker.ietf.org/doc/draft-carpenter-6man-why64/
Htmlized:       http://tools.ietf.org/html/draft-carpenter-6man-why64-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-carpenter-6man-why64-01

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.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat