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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 08 January 2014 19:17 UTC

Return-Path: <brian.e.carpenter@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 0EE391AE0F9 for <ipv6@ietfa.amsl.com>; Wed, 8 Jan 2014 11:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 UpxD4vN7o4SR for <ipv6@ietfa.amsl.com>; Wed, 8 Jan 2014 11:16:58 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id B319E1AE09C for <ipv6@ietf.org>; Wed, 8 Jan 2014 11:16:58 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id r10so2130538pdi.24 for <ipv6@ietf.org>; Wed, 08 Jan 2014 11:16:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SatKsc0oTxVE4X+OP3lgsO0cXAnNxlohF72Q6s8iuzw=; b=Q2Ln0X8DzOP+T27HCoZXk3Flht7OaxjtYZ66koYIvST11HpWaOZH0UVQf26bWIi0pc miDgSp/+dUtWlI/JGihpfb2FuWzlnVrMKFf/Wb9HLq6hh5uFmGo5shOM4V27PV5WT0p7 8kSvp91quy7AY6LztS3XILau7MT+W+RJcKOO4vnQRXfWzoPUbneNWaWqZD0H9GuyDy0+ FybmsW8R8thmhw4eAqiTvIM+XFNTRYfIu5xri31oN5EvYpX5G6gJeukttJymdv4+8oNU hzyVOQBCvtqCr39NOpLIf7dKkGWKg39UzlSgNrSRnnXBq9ot4xr3MyHxmSDdNBOVGzOe OiIw==
X-Received: by 10.66.227.104 with SMTP id rz8mr14993420pac.74.1389208609597; Wed, 08 Jan 2014 11:16:49 -0800 (PST)
Received: from [192.168.178.21] (81.196.69.111.dynamic.snap.net.nz. [111.69.196.81]) by mx.google.com with ESMTPSA id qz9sm4390778pbc.3.2014.01.08.11.16.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 11:16:48 -0800 (PST)
Message-ID: <52CDA427.80906@gmail.com>
Date: Thu, 09 Jan 2014 08:16:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
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> <52CD7A93.4030908@gmail.com>
In-Reply-To: <52CD7A93.4030908@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
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 19:17:01 -0000

EUI-64 came first; it's used by Firewire and there was some expectation
that Firewire would become very important, or in general that EUI-64
would come to replace EUI-48.

But maybe someone who has Christian's book could send a paraphrase
of his explanation.

Regards
   Brian

On 09/01/2014 05:19, Alexandru Petrescu wrote:
> 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
>> --------------------------------------------------------------------
>>
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>