Re: Extending a /64

otroan@employees.org Mon, 09 November 2020 10:38 UTC

Return-Path: <otroan@employees.org>
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 DFB603A0E50 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 02:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 iGL1wGJV9FiS for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 02:38:48 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D82E63A0E4C for <ipv6@ietf.org>; Mon, 9 Nov 2020 02:38:48 -0800 (PST)
Received: from astfgl.hanazo.no (77.16.210.144.tmi.telenormobil.no [77.16.210.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id DFFAC4E11AFD; Mon, 9 Nov 2020 10:38:46 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id CDBD8439A7C6; Mon, 9 Nov 2020 11:38:42 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Extending a /64
From: otroan@employees.org
In-Reply-To: <m1kc4Ri-0000KVC@stereo.hq.phicoh.net>
Date: Mon, 09 Nov 2020 11:38:42 +0100
Cc: 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <46496F56-7430-493C-8FF3-D1A0D6D3218A@employees.org>
References: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <da13ad27-7493-c350-5a0b-38776f5e065e@gmail.com> <634E73FD-5809-4C1E-AE8C-C94D9CDE034E@employees.org> <m1kc4Ri-0000KVC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Urlv2rwRZJhET1bkU2zkWXkVmNs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Nov 2020 10:38:50 -0000

Hi Philip,

>>> You need
>>> 
>>> R-5: Preserve existing security solutions
>>> R-6: Preserve existing privacy solutions
>>> R-7: Preserve e2e transparency
>> 
>> Yes. Although I'm a little unsure what you think of regarding R-5?
> 
> One thing to consider, though I don't know how to formulate that as a
> requirement is that if we change the lenght of IIDs, does that render all
> devices that only support 64 bit IIDs obsolete?
> 
> I.e., should we make changes to IPv6 that render all currently conforming
> implementations obsolete?
> 
> Of course we can create a nice bit of operatial chaos if we make shorter IIDs
> an optional feature.
> 
> So the requirement should be something to the effect that a change to the
> IPv6 standard that affect all hosts requires use cases that cannot be
> solved without updating all hosts.

Right. Take the following solution:

 - there is no subnet prefix / on-link prefix.
 - hosts are assigned single addresses via DHCPv6

The whole concept of interface-id's then become quite abstract.
And you could argue that the concept of interface-id's only exist within the constraints of subnet-prefixes and SLAAC.

Is it a requirement that solutions support SLAAC (or current SLAAC)? I would argue no.

Best regards,
Ole