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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 17 January 2014 19:59 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 38D391A1F61 for <ipv6@ietfa.amsl.com>; Fri, 17 Jan 2014 11:59:29 -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 IodjoLV7vthA for <ipv6@ietfa.amsl.com>; Fri, 17 Jan 2014 11:59:27 -0800 (PST)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 256441A1F00 for <ipv6@ietf.org>; Fri, 17 Jan 2014 11:59:27 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id rq2so4513931pbb.31 for <ipv6@ietf.org>; Fri, 17 Jan 2014 11:59:14 -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=NjOHuzb6czPm3oETBOunz0YmEDDeUGls9Q6Go75Yb7g=; b=L9U6iDsnOr2z4NpwaWcafbHRga/xJX7EjSYSgJPvktCCghxU/LOLWoWwdkFZohw5EN DBDMqDvltGiqAubiqOa4vXF3I6dzO5TLxuOSDQz3vubOBM+KYtij9bLEI/5zQmoztMf5 Cei2H/6uz8uD4deOcseRPvF5PI2YzcYp061qlEz0G5XmOafAG8rAzO+oxYhJzvrHf7oF nd4M++kBNapoWHakIoZo0Y78WAIcHrvWIBwMmgoXFLx1M1f5Q8uy0pGuzGt2dPeCmFve 9eO0RKF00UpkW0/xmtU4nELH/paxCE8CPNodJMHvEPp0gULZS+ZF7HW3lVNy4TUgvEAC ynKg==
X-Received: by 10.68.114.163 with SMTP id jh3mr4027529pbb.99.1389988754701; Fri, 17 Jan 2014 11:59:14 -0800 (PST)
Received: from [192.168.178.23] (166.199.69.111.dynamic.snap.net.nz. [111.69.199.166]) by mx.google.com with ESMTPSA id kk1sm24912756pbd.22.2014.01.17.11.59.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 Jan 2014 11:59:13 -0800 (PST)
Message-ID: <52D98B95.3090507@gmail.com>
Date: Sat, 18 Jan 2014 08:59:17 +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: Christian Huitema <huitema@microsoft.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> <52CDA427.80906@gmail.com> <C91E67751B1EFF41B857DE2FE1F68ABA3606371E@TK5EX14MBXC303.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA3606371E@TK5EX14MBXC303.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "ipv6@ietf.org" <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: Fri, 17 Jan 2014 19:59:29 -0000

Yes, Christian's explanation of "Why 128?" corresponds to what
I remember (and of course there were also arguments for a variable
length format, but that is another thread entireley).

>  Many examples show an 80 bit prefix and a 48 bit MAC address.

Indeed - and the story about EUI-64 came a little later, after
RFC 1884 and during the development of draft-ietf-ipngwg-addr-arch-v2.
Some archive trawling suggests that Firewire addresses were first
mentioned during an IPng Working Group interim meeting,
February 27 & 28, 1997, Palo Alto, CA USA. The context was a
discussion of the 8+8 proposal.

https://www.sixxs.net/archive/docs/ipng-archives/

    Brian

On 17/01/2014 18:47, Christian Huitema wrote:
>> But maybe someone who has Christian's book could send a paraphrase
>> of his explanation.
> 
> I have of course a few copies on my shelves. Mark ZZZ Smith is probably referring to the Chapter 4 of "IPv6, the new Internet Protocol," which was published in 1996. The chapter deals with "plug and play," and the first paragraph reads:
> 
> "By the end of June 1994, the IPng saga was coming to a close. The IPng selection committee had almost made up its' mind. The choice had to be based on the SIPP proposal, but SIPP could not be bought lock, stock, and barrel. A substantial number of directorate members thought that the 64-bit addresses were too narrow, that they would not provide enough flexibility to implement proper routing protocols. There was a compromise in sight, if only the SIPP proponents would agree to increase the address size to 128 bits. The IETF decision process is based on building consensus, part of which implies polling opinion leaders. I was one of those leaders by this time, or so they thought, so they polled me. Would I accept inflating the address to 128 bits? I had publicly stated many times that 64 bits was more than enough and I could back my opinion with substantial mathematical analysis. However, I did not hesitate too long. Going to 128 bits was a little price to pay to reach conse
nsus and save the Internet. Moreover, 128-bit addresses have a definite advantage. They have twice the width that routing procedures require, hence they make a lot of room avail-able for proper implementation of auto configuration procedures. "
> 
> I then go on to explain how auto configuration works by concatenation of a network prefix and a unique identifier of the host, normally a MAC address. The 1996 version of the book was written before the ND specifications was finalized, and does not actually specify the 64 bit prefix size. Many examples show an 80 bit prefix and a 48 bit MAC address.
> 
> -- Christian Huitema
> 
>