Re: [Fwd: I-D Action: draft-carpenter-6man-why64-00.txt]

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 08 January 2014 16:19 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A041ADFA7 for <ipv6@ietfa.amsl.com>; Wed, 8 Jan 2014 08:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJIkzro_rEy8 for <ipv6@ietfa.amsl.com>; Wed, 8 Jan 2014 08:19:45 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id D26431ADFB7 for <ipv6@ietf.org>; Wed, 8 Jan 2014 08:19:44 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s08GJZhY008580 for <ipv6@ietf.org>; Wed, 8 Jan 2014 17:19:35 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CBF15206439 for <ipv6@ietf.org>; Wed, 8 Jan 2014 17:20:34 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C4A19206319 for <ipv6@ietf.org>; Wed, 8 Jan 2014 17:20:34 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s08GJVSv025717 for <ipv6@ietf.org>; Wed, 8 Jan 2014 17:19:34 +0100
Message-ID: <52CD7A93.4030908@gmail.com>
Date: Wed, 08 Jan 2014 17:19:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: [Fwd: I-D Action: draft-carpenter-6man-why64-00.txt]
References: <52C9D788.8060606@gmail.com> <1389041504.19037.YahooMailNeo@web161905.mail.bf1.yahoo.com>
In-Reply-To: <1389041504.19037.YahooMailNeo@web161905.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 16:19:47 -0000

Le 06/01/2014 21:51, Mark ZZZ Smith a écrit :
> Hi,
>
> I've had a quick read through, I think this document would be quite
> useful.
>
> One thing I think would be good to capture is a bit of the
> history/rational behind the choice of 64 IID.
>
> I became aware of that history via Christian Huitema's "IPv6: The
> New Internet Protocol (2nd Edition)" book, I think it would be good
> if that history was a bit more widely available to explain and
> justify the choice.

Hi,

I dont have the book handy, but I would be interested to learn about how
this 64bit length came to life.  I remember some discussions of an 'h'
factor.

I suppose IEEE's EUI-64 design history is related, maybe because
triggered by same fear of address space depletion (48bit identifiers);
knowing that one may see how would an EUI-128 influence in any way IPv6
addressing.

Alex

>
> Regards, Mark.
>
>
> ----- Original Message -----
>> From: Brian E Carpenter <brian.e.carpenter@gmail.com> To: 6man
>> <ipv6@ietf.org> Cc: Sent: Monday, 6 January 2014 9:07 AM Subject:
>> [Fwd: I-D Action: draft-carpenter-6man-why64-00.txt]
>>
>> Hi,
>>
>> A group of us put this together following a discussion some weeks
>> ago on the v6ops list about the 64-bit boundary in IPv6 addresses.
>>  Discussion belongs in 6man, please.
>>
>> This draft is incomplete but we'd welcome input. Let me underline
>> an important comment in the introduction:
>>
>> _The purpose of this document is to analyse the issues around this
>>  question.  We make no proposal for change, but we do analyse the
>> possible effects of a change._
>>
>>
>> Brian + co-authors
>>
>> -------- Original Message -------- Subject: I-D Action:
>> draft-carpenter-6man-why64-00.txt Date: Sun, 05 Jan 2014 13:59:17
>> -0800 From: internet-drafts@ietf.org Reply-To:
>> internet-drafts@ietf.org To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>> Title           : Analysis of the 64-bit Boundary in IPv6
>> Addressing Authors         : Brian Carpenter Tim Chown Fernando
>> Gont Sheng Jiang Alexandru Petrescu Andrew Yourtchenko Filename :
>> draft-carpenter-6man-why64-00.txt Pages           : 14 Date :
>> 2014-01-05
>>
>> 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.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-6man-why64/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-carpenter-6man-why64-00
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------
>>
>>
>>
>>
>>
IETF IPv6 working group mailing list
>> ipv6@ietf.org Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>>
>>
>>
>>
--------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>