Re: draft-bourbaki-6man-classless-ipv6-00

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 13 June 2017 05:09 UTC

Return-Path: <brian.e.carpenter@gmail.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 0C457129557 for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 22:09:10 -0700 (PDT)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 whfMdAr9-pjy for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 22:09:08 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 517601294C4 for <ipv6@ietf.org>; Mon, 12 Jun 2017 22:09:08 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id 83so61652255pfr.0 for <ipv6@ietf.org>; Mon, 12 Jun 2017 22:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=J1syTwgCuqXEwr6DoQhBfUBEsdVuf9NDGJSY1C94+Lc=; b=j67zlfnwc503Sy3W2oCFs7eJ/Lxc7M4sDInTkbfk5QFNiLawhp0q9wzUOJSecfiun6 YqB9pUZKtFJ5gaaDjXnrfigse6nxuF1ivWSOjgpVRvxWx79ia+NhmvbOyXLhmx1NMtXg 1T26L3xzq65EplPK8oRfb+8jB5QI9lEO8kRYOpeARuuAXHqRGWLwewB67IRbjGBcimhs Tzlr3mhxcQORn9b5e5a5t6yXyvOKXZt52FdYwdmKzsP0j1OHnWcZgfmT4FSNE+CXUjVY jwD11jaNw++bqLlHeON2jPzRCZntTp1oL/zuAs9/HAcpbqQmTcQgA/72GQP+lroXf3Ok IqjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=J1syTwgCuqXEwr6DoQhBfUBEsdVuf9NDGJSY1C94+Lc=; b=sbvBlMiOxIcrpkKxnUe1LmcXcY78/lT7z7nnuaksSXWaaZBWgzTV3mV3NScjMtsrz8 vNvPK5OaMf+Mx7VeV68QkNiaFYK1avjuKAxBQbykJONnBqQDhYHB9XM1JzCoGvE0CG9z 5Hg5Jb6xaSGo8jvcMqI2OBfA2DalfcwQ+KyPQIY3hxBMv0f+44dEG7JvkP4wJSOU6Ew9 sCvlFxuAh8mD/poc5QmLpDnDcJTx+nxfyBH75qcJjdCM8uglua38bzj5eFS/MxskjXjM oY5dfHrbsi+cBxM8ZPE3xVx8qw5ccF4eIkXTsXaIEKDwAARYG3w+9dNdYKqXxQ6OIYfZ XJ8Q==
X-Gm-Message-State: AODbwcDO6N1Xropm6dsdZYJKzT3BYN8ZG+MUQEMutckJyq9QKLIGeEn+ 8tpr/cMtL0X9kYzC
X-Received: by 10.99.172.17 with SMTP id v17mr62049809pge.234.1497330547580; Mon, 12 Jun 2017 22:09:07 -0700 (PDT)
Received: from ?IPv6:2406:e007:7b4b:1:28cc:dc4c:9703:6781? ([2406:e007:7b4b:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id t5sm20922607pgt.19.2017.06.12.22.09.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 22:09:06 -0700 (PDT)
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <91c3c0f4-eb8b-cdf7-b9c9-7d1eecb7fe64@gmail.com> <CAKD1Yr0_WR_TB+OC0U1Qt2h6WzUp9EGvrqC1ZKW2mwFeBd3bCQ@mail.gmail.com> <4021a559-5b6d-b3fb-19cd-afbe9041e8f2@gmail.com> <34A29D4D-3670-40BC-B62E-85C4EABC55D5@employees.org> <6e03e25e-fd6a-6311-390e-4834281a76f7@si6networks.com> <1B580CBB-B29D-4860-9EC8-BECD1D5E0006@employees.org> <4b2f5200-86a1-7711-e5ff-7436572be467@gmail.com> <E02C4C99-155A-4358-A845-F00F8BB071C1@employees.org> <b3ca5271-21b1-ab33-2dff-82735ebe9128@gmail.com> <235143da452c4ff4aec39a26ba918e7e@XCH15-06-11.nw.nos.boeing.com> <1489a50a-2616-f9ac-4109-16c595e15f90@gmail.com> <FA3032F9-F44B-45B4-9AFF-01EBC84F1448@employees.org> <b1c5c13d-ef69-ef30-546c-9178a2655caf@si6networks.com> <391c730c-fa75-7596-bb6b-383ea6583131@gmail.com> <f2ac9e0a467b4015a0a78d549c0fbbf0@XCH15-06-11.nw.nos.boeing.com> <a32c0313eeca44ff97e0c7c8b2daf2b6@XCH15-06-11.nw.nos.boeing.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fb121db3-ce68-c68b-fea3-657283978f74@gmail.com>
Date: Tue, 13 Jun 2017 17:09:03 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <a32c0313eeca44ff97e0c7c8b2daf2b6@XCH15-06-11.nw.nos.boeing.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/X8Ru4qlteSS-pIQ2PIUHCwLztJ8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 13 Jun 2017 05:09:10 -0000

On 13/06/2017 14:30, Manfredi, Albert E wrote:
> I should add,
> 
> The IID length used by all SLAAC hosts on a link would be the same, because presumably, they all receive the same RAs. With the same RAs, their IIDs would have to come out to be the same length.
> 
> And, most of this change doesn't even apply to RFC 4862. 

It applies to the fact that the IID length must be known before forming
a LL address, and that it must be the same length as implied by a
*later* RA/PIO with A=1. So actually I think there is quite some
work to be done on RFC4862, and it isn't clear to me that it could
be backwards-compatible.

Also see Gengyu Wei's message: when devices roam, what happens if
the LL IID length for a given interface is supposed to change?
DIP switches again?

I don't think we're going to see a different IID length for any
link type that's already using 64 today; too many things would
have to change.

> For the most part, it applies to RFC 2464-bis. The main points of RFC 4862 remain the same.

It doesn't matter. If it isn't backwards compatible with deployed
code, IMHO it isn't going to happen on Ethernet or Wi-Fi.

   Brian