RE: [dhcwg] [EXTERNAL] Re: I-D Action: draft-templin-duid-ipv6-01.txt

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 14 January 2021 20:42 UTC

Return-Path: <Fred.L.Templin@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 BBC703A1646; Thu, 14 Jan 2021 12:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 LFy2cIpUpz1M; Thu, 14 Jan 2021 12:42:40 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 E5E763A1644; Thu, 14 Jan 2021 12:42:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 10EKgZJt014431; Thu, 14 Jan 2021 15:42:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1610656958; bh=SMOCEhYIHtJHx+ANAzR2zqBdxM7P/mPkwBEpUJcuwko=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=LvG5b4CLF+8hMuqXLUZ58yV7FTdnHcKjXxvWWyyISdgjvWha6Ky/NgM7uBlRuLAxL T0pia4uWpvhWC+ChMFaIUaf51wqqtDbHkRoBCnNXhYjx1Vw8DkidTI5B+J2q8O/QvF Vz4nFP4ILPUJKhq2P/XEslRBtW5x14fEivLG8HJgxzBcZIlCvRdStQxrRXAteyeRX1 mWibhl/ZLu1gfmfNaY5ti3zxU+kSEbQGf78Ty9DbJS3T3FNdmpHG6XKK/6m6PIMGyI DKpyolrr/kvQ8fkgmjJERpOvExqQkHr4j7sXXj/OLBVCUwvvd371AzH4fDng3GEbIo LWo2FJ7WazFyQ==
Received: from XCH16-02-12.nos.boeing.com (xch16-02-12.nos.boeing.com [144.115.66.78]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 10EKgVcg014392 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 14 Jan 2021 15:42:31 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-02-12.nos.boeing.com (144.115.66.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Thu, 14 Jan 2021 12:42:30 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Thu, 14 Jan 2021 12:42:30 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
CC: Bob Hinden <bob.hinden@gmail.com>, dhcwg <dhcwg@ietf.org>, IPv6 List <ipv6@ietf.org>, "Dickson (US), Sean M" <sean.m.dickson@boeing.com>
Subject: RE: [dhcwg] [EXTERNAL] Re: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Topic: [dhcwg] [EXTERNAL] Re: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Index: AQHW6pXTRFz21hDoPUmc8dx7bbRVMaon+1WA//+Gu5CAAJbsgP//fC0g
Date: Thu, 14 Jan 2021 20:42:30 +0000
Message-ID: <a337f8f5fa354b5882d097b0d5de59dd@boeing.com>
References: <cb1cb55e5b634ceea3dde33b8c8816c1@boeing.com> <085F29A9-B8F0-44DF-AD4A-9EFD39FAB183@employees.org>
In-Reply-To: <085F29A9-B8F0-44DF-AD4A-9EFD39FAB183@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: DB5EB82D7C89BB3B3F490DFB8473FC008ED894816F76313F2DF8FC418C592B1B2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_TLCu4Idpwoe85ABQAcEI3H44Jk>
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: Thu, 14 Jan 2021 20:42:42 -0000


> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Thursday, January 14, 2021 12:30 PM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Bob Hinden <bob.hinden@gmail.com>om>; dhcwg <dhcwg@ietf.org>rg>; IPv6 List <ipv6@ietf.org>rg>; Dickson (US), Sean M
> <sean.m.dickson@boeing.com>
> Subject: Re: I-D Action: draft-templin-duid-ipv6-01.txt
> 
> 
> > On 14 Jan 2021, at 20:46, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> > A different poster (Ole) made an assertion that seemed to call into question
> > why more than one DUID type is necessary - the above text was included to
> > to justify why multiple DUIDs are provided by RFC8415, and why additional
> > DUIDs can be added through future standards actions.
> 
> No. I questioned the purpose of having an IPv6 address in something that’s supposed to be an opaque identifier.

And, I said that if it were *truly* opaque to *all* examinations and references, then
there would only ever be *one* DUID type for all time. But, RFC8415 clearly shows
that multiple DUID types are defined and that new ones can be added through
future standards action.

> Cheers
> Ole=