Re: I-D Action: draft-templin-duid-ipv6-01.txt

Simon Hobson <linux@thehobsons.co.uk> Sat, 16 January 2021 11:57 UTC

Return-Path: <linux@thehobsons.co.uk>
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 E59DA3A1710; Sat, 16 Jan 2021 03:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 TbSiR7lrwy-m; Sat, 16 Jan 2021 03:57:53 -0800 (PST)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBD8F3A170F; Sat, 16 Jan 2021 03:57:53 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.137.104] (unknown [192.168.137.104]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id E62D91BC66; Sat, 16 Jan 2021 11:57:49 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: I-D Action: draft-templin-duid-ipv6-01.txt
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <7a6dd09d8bd34e75be166a65a523f7ae@boeing.com>
Date: Sat, 16 Jan 2021 11:57:49 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <30971E6D-AD34-4E7C-B6BF-FE5BE950DB48@thehobsons.co.uk>
References: <905dd68e271546e1a01e3d56952f620c@boeing.com> <BN7PR11MB2547CB47FF8CA2CD507E732ECFA70@BN7PR11MB2547.namprd11.prod.outlook.com> <73dc5fa141614813aa2820792f7a5d81@boeing.com> <BBBFB8B2-4E84-4AE6-974C-B217A117294B@gmail.com> <7a6dd09d8bd34e75be166a65a523f7ae@boeing.com>
To: IPv6 List <ipv6@ietf.org>, dhcwg <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/E7cJly4rHQ5P_NkH5U1EWoczOn8>
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: Sat, 16 Jan 2021 11:57:55 -0000

Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:

> Bob, see below for a replay of what I have answered and will continue to answer:
> 
>> Again, why do you need to use an IPv6 address for this?    Why can’t one of the current DUID approaches be used?
> 
> [RFC7401] and [draft-ietf-drip-rid] are examples of IPv6 address generation
> methods that generate an address intended to be used as an *identity* but
> possible not as a *locator*. In other words, the address could appear in control
> message ID fields but may or may not be "ping'able" in the data plane. And,
> even if it were "ping'able", pervasive use of the address for data communications
> could present an unacceptable privacy exposure.

Please don't take this as a personal attack, it's intended to (try to) be helpful.

There is a disconnect between the question you were asked, and the question you have answered. It's sounding very much like the interviews where the interviewer is asking a question, but the politician has decided one the different question they want to answer - and no matter how many times the interviewer tries to get the question answered, the politician persists in answering their different choice of question.
I sense a frustration on both sides : you perceive that you keep being asked a question you've already answered; other perceive that you are refusing to answer it; while the reality is that there's been a misunderstanding that leads to the perceptions remaining.

The question was : "why can't one of the existing methods be used ?"
The question you have answered is : "what allows other types to be created ?"

As others have been trying to say, just because you **can** doesn't mean that you **should**. So far you've been saying "we can do this", but you've given no indication of "why" anyone should do that. You need to document specific use cases where your ID works, but an existing ID type cannot be used - until you do that, the question will remain as to "why not use something that's already defined ?"

And both Bernie and Bob have given considerable detail as to why your suggestion might not be (note, "might not be", not "is not") a suitable identifier - i.e. points that do need addressing if the idea is to be taken seriously.

So, as I see it :
You need to say **why** existing types are unsuitable for the use cases you have in mind.
Clearly articulate what those use cases are.
Address the technical issues (mostly around lifetime and guarantee of uniqueness) that have been raised.

Simon