RE: Updated IID length text

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Thu, 19 January 2017 03:24 UTC

Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4F43126579 for <ipv6@ietfa.amsl.com>; Wed, 18 Jan 2017 19:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 KMFsIdJchMJF for <ipv6@ietfa.amsl.com>; Wed, 18 Jan 2017 19:24:18 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86F1912947F for <ipv6@ietf.org>; Wed, 18 Jan 2017 19:24:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v0J3OI5i047163; Wed, 18 Jan 2017 20:24:18 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v0J3OFt0047143 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Wed, 18 Jan 2017 20:24:15 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 18 Jan 2017 19:24:14 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1178.000; Wed, 18 Jan 2017 19:24:15 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: Updated IID length text
Thread-Topic: Updated IID length text
Thread-Index: AQHScexT724zBn76p0KKsEzsg727/qE/EBsQgACTkID//320gA==
Date: Thu, 19 Jan 2017 03:24:14 +0000
Message-ID: <2889c46061ab47cfba8b54384778bd85@XCH15-06-11.nw.nos.boeing.com>
References: <148406593094.22166.2894840062954191477.idtracker@ietfa.amsl.com> <m2fukqbbwv.wl-randy@psg.com> <F6953234-3F85-4E28-9861-433ADD01A490@gmail.com> <m2wpdzhncn.wl-randy@psg.com> <82245ef2-cd34-9bd6-c04e-f262e285f983@gmail.com> <m2d1frhjfn.wl-randy@psg.com> <18e6e13c-e605-48ff-4906-2d5531624d64@gmail.com> <CAKD1Yr1cvZ8Y3+bHeML=Xwqr+YgDspZGnZi=jqQj4qe2kMc4zw@mail.gmail.com> <m2lguffnco.wl-randy@psg.com> <CAKD1Yr1TrTiPRdyutobmb_77XJ7guNzLrg=H_p7qi4BfQ8V=GA@mail.gmail.com> <m2d1frfm6m.wl-randy@psg.com> <CAKD1Yr2Njjd8_Mr+6TRFF6C5pdcX4yFgpFVyEkykDuytu2B8mg@mail.gmail.com> <2A5073777007277764473D78@PSB> <4596c3d4-a337-f08e-7909-f14270b7085f@gmail.com> <CAN-Dau06R3iYRpYLADhvHox4C9qdsJCuxFsJapRhOQcWT4qk_g@mail.gmail.com> <CAO42Z2weZcoHiBzN94QAQ9WGhWR16PmMMFNg=5YLmr_dhPjjpA@mail.gmail.com> <fcc7f136-b5da-527e-b495-5a2d7f7a3ce8@gmail.com> <55bb8bdbfbf4439da0aa702e5bc03e2c@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr2vmDkUTvSw7-GtKNeMDm1xtAppj+EW9X=-TeKZ6qkXrg@mail.gmail.com>
In-Reply-To: <CAKD1Yr2vmDkUTvSw7-GtKNeMDm1xtAppj+EW9X=-TeKZ6qkXrg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UVn170Q50wvfOb0_M38GBiskMdk>
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 19 Jan 2017 03:24:19 -0000

From: Lorenzo Colitti [mailto:lorenzo@google.com] 

>> Now that we have moved away from using the MAC address for SLAAC, it's
>> not clear to me why a host cannot wait for a RA, and then decide on
>> how many IID bits to use, based on the prefix length(s) advertised by
>> the router.
>
> The reason it can't do that is that in practice SLAAC only works well
> if the probability of collision is negligible. Even reducing that from
> 64 bits to 48 bits impacts that substantially.

Perhaps, but SLAAC has been deemed to work adequately well with only the 48-bit MAC address (presumably) being unique. So nothing would change in this "negligible collision" regard, if we allowed for 80-bit prefixes with SLAAC. You'd want to do duplicate address detection regardless.

Back in the 1980s, it probably seemed that 32 bits, to identify research computers, was way more than adequate. Clearly, people had not anticipated how this Internet was going to be used. Same applies now.

Bert