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

"Bernie Volz (volz)" <volz@cisco.com> Fri, 15 January 2021 20:14 UTC

Return-Path: <volz@cisco.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 8B12B3A114A; Fri, 15 Jan 2021 12:14:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Ur5qDzZS; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=hzgA4AVJ
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 SRffI4vbbWCh; Fri, 15 Jan 2021 12:14:56 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 190C03A1149; Fri, 15 Jan 2021 12:14:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32692; q=dns/txt; s=iport; t=1610741696; x=1611951296; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=/qcvugHQNHShqRfhhBeaBlBj3+zaQBGinw27ekVzXCc=; b=Ur5qDzZSYoCOkH4W9f1f/dCx0iq/MY4cIswFOHZsPiCRY3vabqDDY9fI pCYW9CO+a6BGbAw9s4RqZPqWcsNNuiHYT8FVQqY8bkDCnzB1PaiesNGyR NRa4SfDtqZZ52Cn7jgeVOwBDGMxx8Oq06bItdXvo1b/uwcq20KSwbgyVP 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AbQQ76RebKnlOJ0oe+pplR/7PlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwaQA9fR7P9FjeWQuKflCiQM4peE5XYFdpEEFx?= =?us-ascii?q?oIkt4fkAFoBsmZQVb6I/jnY21ffoxCWVZp8mv9PR1TH8DzNFfVr3y04ngZHR?= =?us-ascii?q?CsfQZwL/7+T4jVicn/3uuu+prVNgNPgjf1Yb57IBis6wvLscxDiop5IaF3wR?= =?us-ascii?q?zM8XY=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0APAgBz9gFg/4gNJK1YAQkaAQEBAQE?= =?us-ascii?q?BAQEBAQMBAQEBEgEBAQECAgEBAQFAgU8CgVFRB3ZbLy8KhDWDSAOOAgOKHIR?= =?us-ascii?q?0igOCUwNPBQsBAQENAQEYCwoCBAEBhEoCF4FWAiU4EwIDAQELAQEFAQEBAgE?= =?us-ascii?q?GBHGFNAEFAiUMQwEBBAsBhR4BAQEEAQEYCREMAQEsBAcBCwQCAQgRBAEBAQI?= =?us-ascii?q?CIwMCAgIfBgsUAQgIAQEEAQ0FCAELgxOCVQMuAQ6kPQKKJXaBMoMFAQEGgTM?= =?us-ascii?q?BAwIOQYMEDQuCEQmBDioBgnSEAYEKgUKDciYbggCBEAFDgVh+PoIbNwsBAQE?= =?us-ascii?q?BAQEVgRkBDgYaBRAPFIJeNIIsgU8JAWIHBjwkBC8iAQEUPAsLCwoVBysVBAE?= =?us-ascii?q?LGAEBCmWPNRIHgyWkFzlYCoJ3iS6NG4VAgyqBMIh/hWCPL5QZixqCeoMlixV?= =?us-ascii?q?HhDUCBAIEBQIOAQEGgW0jgVdwFRohgmkJRxcCDYE2AYxqDBeDToUUhUR0AjU?= =?us-ascii?q?CBgEJAQEDCXyFUIEQhC8BgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.79,350,1602547200"; d="scan'208";a="826173578"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Jan 2021 20:14:54 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 10FKEsZE017435 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 15 Jan 2021 20:14:54 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 15 Jan 2021 14:14:53 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 15 Jan 2021 15:14:52 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 15 Jan 2021 15:14:52 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=emrdHRhzg0pOZaHbsf7wHpfiSMFrGoYO9UaQDGOltOgqaVsY/ZCGqBujag5Ql9GKyIer1G0RIBiiOFHIRNTrvoN7X6MEqwRJN2XT8cwysIGZDzkZGjJHHhbTobPCa31/zj1EcVIlhvETyJlHj0ACo9XFJyP5HDg/afxwuAOnh515i1gUJIWsPb4wLaQQnksgX6iSXTJksuxCene7mgbvEPYY6DQuaWmYpBFmR6Arytq0sK2i/pZ+rSVsRGossgzzpbaRf95G0nQQN100gJDpNtdyZHZbe1AJ8tw1XVDAunnrucnkEQVDarigCwHYkOwCCQHabTy4kxOtfdA0axfDIQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/qcvugHQNHShqRfhhBeaBlBj3+zaQBGinw27ekVzXCc=; b=NCOYBEvapSvSfguUKdATv3YXW6MX3gHPQ0iJEGLgBUHXaqfi09/T2KJetVPjglhxgrvf3Na1FdEjZVrkHx3jIyF1fCGoGvrrstz2PPBfRSPfD5b1NehcYaoUeK3BnO2Q7/92rMC7TVj8J6MUx+WsN6Kqm0CLh0qD0uys/YUAKDsiEYeIrrjPtdOJBPN4ZZwFK8FaUk3nBpsXWs9VdLB1t4VZSTY+IE0tg1f58YdHiOilQPfkggVwVtGn3EPl3WuPif3417/fefTdEkHXHaEd7B/3rXMRk21d+/2mW7Sg3AsOyOcG1GoVo7qO8SdfZL+omlxS7aQRvlFOkl9pUVlM7A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/qcvugHQNHShqRfhhBeaBlBj3+zaQBGinw27ekVzXCc=; b=hzgA4AVJ4RZ5UcpFwAsnwdWvihjtwDWXnXuEX+zb1dVQRwBjpjzQuSa5DA3aBqByi2u1QBR7wvr1GmZwzvBEjUGeSeL8aDEZdEJ5g5DAInxah2P2tVtKoqJYbSKZ4M9+TfWB0B5GD+MRU1+rua89HyZDfae7vHE0eyCLf0OwBQc=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN6PR11MB1523.namprd11.prod.outlook.com (2603:10b6:405:10::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.11; Fri, 15 Jan 2021 20:14:50 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb%3]) with mapi id 15.20.3763.012; Fri, 15 Jan 2021 20:14:50 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, Bob Hinden <bob.hinden@gmail.com>
CC: dhcwg <dhcwg@ietf.org>, IPv6 List <ipv6@ietf.org>, "Dickson (US), Sean M" <sean.m.dickson@boeing.com>
Subject: RE: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Topic: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Index: AdbrdUQ2OSxT/RteQveHQZFWn6tS6wABNUSQ
Date: Fri, 15 Jan 2021 20:14:50 +0000
Message-ID: <BN7PR11MB2547CB47FF8CA2CD507E732ECFA70@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <905dd68e271546e1a01e3d56952f620c@boeing.com>
In-Reply-To: <905dd68e271546e1a01e3d56952f620c@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: boeing.com; dkim=none (message not signed) header.d=none;boeing.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [24.233.121.124]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: efa0b798-1a52-4111-d9a6-08d8b99236c2
x-ms-traffictypediagnostic: BN6PR11MB1523:
x-microsoft-antispam-prvs: <BN6PR11MB1523E70AB1C82F0C023A981ACFA70@BN6PR11MB1523.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: giwusyR8DcOwyOlC3cEV4j4rWTIcALlxnK2vo21r6ChqHBNw2J4ZcHe+k6uTIs/GAU/eOiNVOSo36Q7ntAXgUw5aHgLGKVNTYVVflyROEIrToTGruPAb836NmnmALUar2NUWDBPjynYo7Ok/ZZ1D8A9f0PbMgYSqmtyWKnBrhRJcF6LQEUjCcm0V9MAw9bf+r4rlznHNFfGeY4WupA9Gn/oT73SFpysbI5BSAemdGb9+J583nEfP4qOE8k7EN3sttfH/PXs8+Z7nDYT426RkE1xyESdnDgUBgTkWmBOAEJT/JZbWBgIX1Q7rrHsss4cONejJLi+aaNtnU16iL4Io1/0BY3KDB6Sarbk8qQMxypP7xNGNPD38J4ZsF5FDhvqNX+Rnlg5a43GR6UhoupH7r08Exz3foNEWm5CYUr/XCu0GBdiDfsEWIVfZPlDIC4HlAWM0g6/a+C/O2JfdFu3iAd11Go0N6T66h6Fo4E4pSpdSek3frj584n90/47xgkB+io3ToNvpL/1NH1p0sHY47EB0lFxdwtnapLsXswz6qePzXeVdmat6lUeq9lIiAA2gz2PpJ3R7lFts9TbLUZ7Vxg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(346002)(366004)(136003)(376002)(39860400002)(66946007)(64756008)(66476007)(71200400001)(66556008)(66446008)(2906002)(52536014)(76116006)(110136005)(54906003)(7696005)(30864003)(478600001)(83380400001)(53546011)(966005)(6506007)(186003)(26005)(86362001)(66574015)(5660300002)(33656002)(4326008)(8676002)(55016002)(9686003)(8936002)(316002)(579004); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: =?utf-8?B?aU96eFV1RDhZaHM1dmZFWnViUWdXa3F5K1pzYjV0S0IzSm5qVklxQ1pSaVpw?= =?utf-8?B?OXhMb25mM0grM254OVN1WjRPcUhnN2VkZFZiNDcvTzFsK1B5ZFdwWU8zV3pM?= =?utf-8?B?THcySnNwclBkN0VwQ04xckxJNlNOVUpjbHhJbVIwbXJiUzdLcks0UEc2UUdZ?= =?utf-8?B?ZzZWMmNpSXl4Y0pncmRqQXR3Zml2QjlwdjJuNnZVUnNVRUxEaExYbVltcTlm?= =?utf-8?B?aEMwcDVDV0xNQmdMMzRsZUg2cmlSd0NVMVZjK24wa0lGbVRmSndmaHhTM1Zx?= =?utf-8?B?UkJ3MGJUMUxyaDJVYklFNzlFQ21hY3NIV2JKSVNueG5XTEVBVUR5QVlmZFVs?= =?utf-8?B?S3pPaFpmWXZPT2RIQTFrSmY1TGxvU3FoL283ajRWYTNRL2luVmVWdWtDb2xZ?= =?utf-8?B?cFl2UEtYRThZQXVqVGlGajZiOVZtcDVVemtsZDdSTThQL0R2dWNpTkM4MDlN?= =?utf-8?B?Y3JJMnkwaVMzTUQxOEFsdlJHZkVWYUR4VytPZkozei9sbEVrY1RLQ3FaR2pv?= =?utf-8?B?eFZMaXBaY2VHOVhFV1FBRThFRjBVMURuSjBxeVd2aXVmeHRvYmF1cHNMNmtL?= =?utf-8?B?SE1UanFYa2RHNENhdG8wNXlGNVBLRVNoM0hnMHZzbmtvbDRIRkorZkY4eEh5?= =?utf-8?B?Vkg1cXVjbXJvbVFXTEJpTkd0d1RMVGJiVDEzM1lrTFB3eHVQVzliUy83bFhz?= =?utf-8?B?ODlaemw0TEh3TjhrMmZldldaVFk1Uko5K3FmSUNVNVl1Z1hNdE9rRTMvbTZD?= =?utf-8?B?YS8zQmZMQWQwK2JlQzJxSkpFZ2RueXEza2hQNGJHSUpVMThvSld2MWFxMzNF?= =?utf-8?B?V3J0MXAzaVM4ejZJZkFPVHM0VUVpSTZVSXYzYUZ2Sm5GeU1qajdSa3pJYmp2?= =?utf-8?B?V3ZJTDdUTHpRcDFJeW9Ha1pkTm5CMFNmdGNGSVgyVDZzK0liaUZlTy80Rklw?= =?utf-8?B?ZC9QaUlSUGdrZzdsaFh3MUJtUkdSbVYwcktOVjcwbHJjYXRBWWFNelNyTGFq?= =?utf-8?B?OERuNUJzRzJTWkQyZHZxaTdBUnRYN0JkNi82a0tGWnJkMUgxcXVmeXdXLytZ?= =?utf-8?B?SkRNbDBEMlZNdWJLMy9ZOTloeGEzUk9WQWFVS3pEVjgzY2lNMEJZT2l4OXVl?= =?utf-8?B?MEwrTUFRWWc3Wng1UmNOUW92T3UycDhvb3RQNzhueWxxcEtsd0VkempsNWRs?= =?utf-8?B?UDBRcFV6U0dCMHg2QTQwT0hjSEtYTVJVSFdxZFA5WkwwaWZYTnNHZDZaZ214?= =?utf-8?B?WGEvcUtZTzRka204YU01Q2d6cG1MNkRkVUdPM2ZBWTROVjlHaW1BdFhwS3lQ?= =?utf-8?Q?tYzqp9eDwWs8M=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2547.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: efa0b798-1a52-4111-d9a6-08d8b99236c2
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jan 2021 20:14:50.6579 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ob0KY+8RrsIQdswUVTlp3UdtLomXQXfQV7342RZy9aM4wfYux7DXnK9utSy+ZbnC
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1523
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_PMiyy0amkWh96nVkfsjW3Ohvxo>
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: Fri, 15 Jan 2021 20:15:00 -0000

Hi Fred:

As I've tried to point out, what I find in the draft is still insufficient. Comparing against just the DUID-UUID is not sufficient.

You need to explain why the existing forms (-LL, -LLT, -UUID) are insufficient; not just propose well I'll put my v6 address into the DUID-UUID as it is also 128 bits (but prefer not to overload as doesn't match UUID format). That's why you MUST NOT use DUID-UUID for your proposes (placing the IPv6 address into it).

As an example, look at https://tools.ietf.org/html/rfc6355#section-2 as that clearly provides details as why DUID-UUID has benefits over the 3 other formats at the time as why it should be a standardized format. You need material such as this. Without it, I would strongly recommend against this work because there is no rational for needing it (other than "hey I like this better.").

If you don't want to provide these arguments, then I highly recommend you use the DUID-EN under the AERO or whatever enterprise id you want to specify.

- Bernie

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Templin (US), Fred L
Sent: Friday, January 15, 2021 2:38 PM
To: Bob Hinden <bob.hinden@gmail.com>
Cc: 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

Another high-level point. People seem to forget that this all got started with a *draft*, and the draft does go into detailed discussion that many of the questioners seem not to have read:

https://www.ietf.org/archive/id/draft-templin-duid-ipv6-01.txt

The draft does discuss the relation to DUID-UUID at length. But, if people are fine with my putting a non-UUID 128-bit quantity in a DUID-UUID that is cool and I'm happy to do it - just let me know if that is what you want.

Fred

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Templin (US), 
> Fred L
> Sent: Friday, January 15, 2021 10:57 AM
> To: Bob Hinden <bob.hinden@gmail.com>
> Cc: dhcwg <dhcwg@ietf.org>rg>; IPv6 List <ipv6@ietf.org>rg>; Dickson (US), 
> Sean M <sean.m.dickson@boeing.com>
> Subject: Re: [dhcwg] [EXTERNAL] Re: I-D Action: 
> draft-templin-duid-ipv6-01.txt
> 
> To everyone who has commented, this is the particular exchange for 
> which I have been expecting but have not received follow-up discussion 
> on the answer I provided. I will not answer any more questions, 
> because I would simply be reiterating the same answer I provided in this exchange below.
> 
> If I get no follow-discussion (especially from Bob Hinden) I will 
> consider the DUID-V6ADDR idea "dead" and revert to using DUID-UUID to 
> encode 128-bit values of all types *even if they are not UUIDs*. Would 
> everyone be cool with that?
> 
> Fred
> 
> > -----Original Message-----
> > From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Templin 
> > (US), Fred L
> > Sent: Thursday, January 14, 2021 11:46 AM
> > To: Bob Hinden <bob.hinden@gmail.com>
> > Cc: dhcwg <dhcwg@ietf.org>rg>; IPv6 List <ipv6@ietf.org>rg>; Dickson (US), 
> > Sean M <sean.m.dickson@boeing.com>
> > Subject: Re: [dhcwg] [EXTERNAL] Re: I-D Action: 
> > draft-templin-duid-ipv6-01.txt
> >
> > Bob,
> >
> > > -----Original Message-----
> > > From: Bob Hinden [mailto:bob.hinden@gmail.com]
> > > Sent: Thursday, January 14, 2021 10:44 AM
> > > 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: [dhcwg] [EXTERNAL] Re: I-D Action: 
> > > draft-templin-duid-ipv6-01.txt
> > >
> > > Fred,
> > >
> > > > On Jan 14, 2021, at 8:53 AM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> > > >
> > > > Bob, I think the answer to your question is quite simple. 
> > > > RFC8415, Section 11 provides the motivation for having more than 
> > > > one type of DUID, and RFC6355 is an example of how new DUID types are added through standards action.
> > > > The precedent for adding new DUID types according to published 
> > > > procedures is therefore established.
> > >
> > > That wasn’t the question.   I didn’t ask if other types of DUID were allowed,
> >
> > 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.
> >
> > > I asked:
> > >
> > >  "It's unclear to me what the purpose of putting an IPv6 address in the DUID is. Would you mind clarifying that?”
> > >
> > > Several other people asked similar questions.
> > >
> > > > In the specific instance of the proposal for establishing a new 
> > > > DUID type to carry an IPv6 address, the intended use case is for 
> > > > IPv6 address generation methods that produce an address that is 
> > > > designed to be a unique and stable identifier for the node, 
> > > > which meets the requirements of what can be used as a DUID per 
> > > > RFC8415, Section 11. This is certainly the case for (H)HIT per 
> > > > RFC7401 and draft-ietf-drip-rid, and I suppose the same case 
> > > > could be made for other cryptographically generated IPv6 
> > > > addresses such as RFC3972. Future IPv6 address generation 
> > > > methods (whether or not cryptographic) could also be designed to produce a unique and stable identifier for the node, and would be covered under the proposed new DUID type as well.
> > >
> > > 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.
> >
> > > I note that DHCPv6 is usually used to get an IPv6 address, so using an IPv6 to get an IPv6 address seems very odd.
> >
> > Continuing from what I said above, yes this would entail using one 
> > type of IPv6 address (a pure identifier) to obtain one or more IPv6 
> > addresses or prefixes that can be used as the source/destination addresses for IPv6 data plane packets.
> >
> > Fred
> >
> > > Bob
> > >
> > >
> > > >
> > > > Before we go down the rathole of "IPv6 addresses must be 
> > > > assigned to an interface and not a node", please refer to the 
> > > > earlier messages on this thread where the suggestion was made 
> > > > that the stable and unique address could be assigned to a 
> > > > virtual interface (e.g., a loopback) and not an interface that 
> > > > may be subject to change such as due to a hot-swap of an 
> > > > interface card. Finally,
> > > > RFC4291 says the following:
> > > >
> > > >   "IPv6 addresses of all types are assigned to interfaces, not nodes.
> > > >   An IPv6 unicast address refers to a single interface.  Since each
> > > >   interface belongs to a single node, any of that node's interfaces'
> > > >   unicast addresses may be used as an identifier for the node."
> > > >
> > > > From this text, we see that an IPv6 address may be used as an 
> > > > identifier for the node, which is exactly what a DUID is. And, 
> > > > an IPv6 address is unlike any of the existing DUID types, since 
> > > > by definition the address must be in the format specified by RFC4291. Hence, a new DUID type is requested.
> > > >
> > > > Fred
> > > >
> > > >> -----Original Message-----
> > > >> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of 
> > > >> Templin (US), Fred L
> > > >> Sent: Thursday, January 14, 2021 8:19 AM
> > > >> To: Bob Hinden <bob.hinden@gmail.com>
> > > >> Cc: dhcwg <dhcwg@ietf.org>rg>; IPv6 List <ipv6@ietf.org>rg>; Dickson 
> > > >> (US), Sean M <sean.m.dickson@boeing.com>
> > > >> Subject: Re: [dhcwg] [EXTERNAL] Re: I-D Action: 
> > > >> draft-templin-duid-ipv6-01.txt
> > > >>
> > > >> Bob, I have been offline until just now due to windstorms that 
> > > >> knocked out power and Internet access in the Seattle area over 
> > > >> the past couple of days. I will reply to your question shortly.
> > > >>
> > > >> Fred
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> > > >>> Sent: Tuesday, January 12, 2021 4:43 PM
> > > >>> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> > > >>> Cc: Bob Hinden <bob.hinden@gmail.com>om>; Ole Trøan 
> > > >>> <otroan@employees.org>rg>; 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
> > > >>>
> > > >>> Fred,
> > > >>>
> > > >>>> On Jan 12, 2021, at 3:05 PM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> > > >>>>
> > > >>>> Ole,
> > > >>>>
> > > >>>>> -----Original Message-----
> > > >>>>> From: otroan@employees.org [mailto:otroan@employees.org]
> > > >>>>> Sent: Tuesday, January 12, 2021 1:34 PM
> > > >>>>> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> > > >>>>> Cc: Bob Hinden <bob.hinden@gmail.com>om>; dhcwg 
> > > >>>>> <dhcwg@ietf.org>rg>; 6man WG <ipv6@ietf.org>rg>; Dickson (US), 
> > > >>>>> Sean M <sean.m.dickson@boeing.com>
> > > >>>>> Subject: [EXTERNAL] Re: I-D Action: 
> > > >>>>> draft-templin-duid-ipv6-01.txt
> > > >>>>>
> > > >>>>> Fred,
> > > >>>>>
> > > >>>>> It's unclear to me what the purpose of putting an IPv6 address in the DUID is. Would you mind clarifying that?
> > > >>>>
> > > >>>> I will add words to the next draft version.
> > > >>>
> > > >>> How about telling us now.
> > > >>>
> > > >>> Bob
> > > >>>
> > > >>>
> > > >>>>
> > > >>>>> Are you also aware of the following restriction in RFC8415:
> > > >>>>>  "Clients and servers MUST treat DUIDs as opaque values and 
> > > >>>>> MUST only  compare DUIDs for equality.  Clients and servers 
> > > >>>>> SHOULD NOT in any  other way interpret DUIDs."
> > > >>>>
> > > >>>> Yes, but then what is the reason why we currently have 4 DUID 
> > > >>>> types instead of just 1? If the text you quoted above is all 
> > > >>>> there was to it, and end of story, there would never be a 
> > > >>>> need to differentiate DUID-LL from DUID-LLA from DUID-EN from 
> > > >>>> DUID-UUID. So, this suggests there is more to the story than 
> > > >>>> just the short text you quoted above. And, the community has supported the definition of new DUIDs in the past (e.g., DUID-UUID).
> > > >>>>
> > > >>>> Thanks - Fred
> > > >>>>
> > > >>>>> Best regards,
> > > >>>>> Ole
> > > >>>>>
> > > >>>>>> On 12 Jan 2021, at 19:40, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> > > >>>>>>
> > > >>>>>> Bob, please see my subsequent reply to Eric Vyncke that discusses motivation:
> > > >>>>>>
> > > >>>>>> https://mailarchive.ietf.org/arch/msg/ipv6/yOfWHSnt36Hvjr44
> > > >>>>>> OERjK0OFvhw/ 
> > > >>>>>> https://mailarchive.ietf.org/arch/msg/dhcwg/YZq_aPf1C82ZFT_
> > > >>>>>> bTdXOXVXTPW0/
> > > >>>>>>
> > > >>>>>> Per your comment, perhaps a new section on "motivation" 
> > > >>>>>> could be added to the draft?
> > > >>>>>>
> > > >>>>>> Thanks - Fred
> > > >>>>>>
> > > >>>>>>> -----Original Message-----
> > > >>>>>>> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> > > >>>>>>> Sent: Tuesday, January 12, 2021 10:22 AM
> > > >>>>>>> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> > > >>>>>>> Cc: Bob Hinden <bob.hinden@gmail.com>om>; Mark Smith 
> > > >>>>>>> <markzzzsmith@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
> > > >>>>>>>
> > > >>>>>>> Fred,
> > > >>>>>>>
> > > >>>>>>> Mark asked:
> > > >>>>>>>
> > > >>>>>>> "I don't understand what problem this is trying to solve 
> > > >>>>>>> or see any benefits of it. What is wrong with existing DUIDs?”
> > > >>>>>>>
> > > >>>>>>> I have the same question.   I read the draft but have no idea why this is needed.
> > > >>>>>>>
> > > >>>>>>> Bob
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>> On Jan 12, 2021, at 8:26 AM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>> Mark, thanks for the comments. I gather your concern is 
> > > >>>>>>>> for the longevity and immutability of the IPv6 address 
> > > >>>>>>>> that would go into the DUID, since DUIDs are meant to 
> > > >>>>>>>> identify the device and not change over time. But, there 
> > > >>>>>>>> are IPv6 address generation methods that generate 
> > > >>>>>>>> addresses not for the purpose of assigning them to a 
> > > >>>>>>>> physical interface (e.g., Ethernet, WiFi and the like), 
> > > >>>>>>>> but instead to provide a unique node ID for the device 
> > > >>>>>>>> that never changes [RFC7401][draft-ietf-drip-rid]. Also, 
> > > >>>>>>>> [RFC7721] mentions several other IPv6 address generation methods that could be considered for use for generating a unique node ID, and other IPv6 address generation methods intended to create a unique node ID could be defined in the future.
> > > >>>>>>>>
> > > >>>>>>>> So, again, this is not about using an IPv6 address 
> > > >>>>>>>> assigned to a physical interface as a DUID; it is about 
> > > >>>>>>>> using an IPv6 address that was intentionally generated to be a unique identifier for the node and may also be assigned to a virtual interface.
> > > >>>>>>>>
> > > >>>>>>>> Thanks - Fred
> > > >>>>>>>>
> > > >>>>>>>>> -----Original Message-----
> > > >>>>>>>>> From: Mark Smith [mailto:markzzzsmith@gmail.com]
> > > >>>>>>>>> Sent: Monday, January 11, 2021 5:32 PM
> > > >>>>>>>>> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> > > >>>>>>>>> Cc: ipv6@ietf.org; dhcwg <dhcwg@ietf.org>rg>; Dickson (US), 
> > > >>>>>>>>> Sean M <sean.m.dickson@boeing.com>
> > > >>>>>>>>> Subject: Re: FW: I-D Action: 
> > > >>>>>>>>> draft-templin-duid-ipv6-01.txt
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Hi Fred,
> > > >>>>>>>>>
> > > >>>>>>>>> I don't understand what problem this is trying to solve 
> > > >>>>>>>>> or see any benefits of it. What is wrong with existing DUIDs?
> > > >>>>>>>>>
> > > >>>>>>>>> DHCP Unique IDentifiers are, per RFC 8415,
> > > >>>>>>>>>
> > > >>>>>>>>> "...  designed to be unique across all DHCP clients and 
> > > >>>>>>>>> servers, and stable for any specific client or server.  
> > > >>>>>>>>> That is, the DUID used by a client or server SHOULD NOT 
> > > >>>>>>>>> change over time if at all possible; for example, a 
> > > >>>>>>>>> device's DUID should not change as a result of a change 
> > > >>>>>>>>> in the device's network hardware or changes to virtual 
> > > >>>>>>>>> interfaces (e.g.,
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Mrugalski, et al.            Standards Track                   [Page 32]
> > > >>>>>>>>>
> > > >>>>>>>>> ________________________________
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> RFC 8415                      DHCP for IPv6                November 2018
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> logical PPP (over Ethernet) interfaces that may come and 
> > > >>>>>>>>> go in Customer Premises Equipment routers).  The client 
> > > >>>>>>>>> may change its DUID as specified in [RFC7844]."
> > > >>>>>>>>>
> > > >>>>>>>>> The only IPv6 address that I can think of that might 
> > > >>>>>>>>> come close to meeting those requirements would be an 
> > > >>>>>>>>> EUI-64 derived Link-Local address, and that is assuming 
> > > >>>>>>>>> that the EUI-64/hardware MAC address never changes. MAC 
> > > >>>>>>>>> address randomisation and the RFC8064 recommendation for 
> > > >>>>>>>>> use of RFC7217 for SLAAC means that Link-Local addresses 
> > > >>>>>>>>> may not meet the DUID requirements above either (RFC7217 
> > > >>>>>>>>> can result in link-specific link-local addresses 
> > > >>>>>>>>> (specifically the IID portion is link specifc), even though the link-local prefix itself is constant across all links).
> > > >>>>>>>>>
> > > >>>>>>>>> There's also a circular dependency if the DUID is based 
> > > >>>>>>>>> on a GUA or ULA address and DHCPv6 is to then be used 
> > > >>>>>>>>> for stateful GAU/ULA address assignment, unless you 
> > > >>>>>>>>> mandated that SLAAC and stateful DHCPv6 are used in 
> > > >>>>>>>>> parallel so that SLAAC could be used to derive the DUID 
> > > >>>>>>>>> that is then used to acquire further ULA/GUA addresses via stateful DHCPv6 IA_NAs and IA_TAs.
> > > >>>>>>>>>
> > > >>>>>>>>> "The DUID-V6ADDR may appear in DHCPv6 and/or other 
> > > >>>>>>>>> protocol control messages (such as IPv6 ND) within a 
> > > >>>>>>>>> service domain when a unique ID based on an IPv6 address is required."
> > > >>>>>>>>>
> > > >>>>>>>>> In the latter case, why not use IPv6 addresses 
> > > >>>>>>>>> themselves? Using
> > > >>>>>>>>> DHCPv6 Unique Identifiers outside of the DHCP protocol 
> > > >>>>>>>>> would be an abuse of a DUID.
> > > >>>>>>>>>
> > > >>>>>>>>> Regards,
> > > >>>>>>>>> Mark.
> > > >>>>>>>>>
> > > >>>>>>>>> On Tue, 12 Jan 2021 at 05:47, Templin (US), Fred L 
> > > >>>>>>>>> <Fred.L.Templin@boeing.com> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>> Hi, more and more IPv6 address generation methods are 
> > > >>>>>>>>>> being specified that intend to generate IPv6 addresses 
> > > >>>>>>>>>> that are highly likely to be unique on either a global 
> > > >>>>>>>>>> scale or unique within a bounded service domain. So 
> > > >>>>>>>>>> much so, that some address generation methods intend for the IPv6 addresses to be usable as node identifiers.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Recognizing this, this document proposes a new DHCPv6 
> > > >>>>>>>>>> DUID type known as "DHCP-V6ADDR" that includes an IPv6 
> > > >>>>>>>>>> address in the body of the DUID. In this way, IPv6 
> > > >>>>>>>>>> addresses produced by address generation methods 
> > > >>>>>>>>>> intending to generate a node ID can be used as unique 
> > > >>>>>>>>>> identifiers in DHCPv6 message exchanges. This would introduce a single new DUID type, for which the IANA allocation policy is  "standards action".
> > > >>>>>>>>>>
> > > >>>>>>>>>> Alternatively, a separate DUID type could be allocated 
> > > >>>>>>>>>> for each IPv6 address generation method. However, that 
> > > >>>>>>>>>> approach may result in additional IANA allocations and 
> > > >>>>>>>>>> would require implementation updates every time a new 
> > > >>>>>>>>>> address generation method is specified. Hence, a single generic DUID type for all IPv6 generation methods is proposed, but open for discussion.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Comments on the list welcome.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Fred
> > > >>>>>>>>>>
> > > >>>>>>>>>> -----Original Message-----
> > > >>>>>>>>>> From: I-D-Announce 
> > > >>>>>>>>>> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of 
> > > >>>>>>>>>> internet-drafts@ietf.org
> > > >>>>>>>>>> Sent: Monday, January 11, 2021 10:21 AM
> > > >>>>>>>>>> To: i-d-announce@ietf.org
> > > >>>>>>>>>> Subject: I-D Action: draft-templin-duid-ipv6-01.txt
> > > >>>>>>>>>>
> > > >>>>>>>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>>     Title           : The IPv6 Address-based DHCPv6 Unique Identifier (DUID-V6ADDR)
> > > >>>>>>>>>>     Author          : Fred L. Templin
> > > >>>>>>>>>>     Filename        : draft-templin-duid-ipv6-01.txt
> > > >>>>>>>>>>     Pages           : 7
> > > >>>>>>>>>>     Date            : 2021-01-11
> > > >>>>>>>>>>
> > > >>>>>>>>>> Abstract:
> > > >>>>>>>>>> This document defines a new DHCPv6 Unique Identifier 
> > > >>>>>>>>>> (DUID) type called DUID-V6ADDR that contains a single 128 bit IPv6 address.
> > > >>>>>>>>>> DUID-V6ADDR makes it possible for devices to use 
> > > >>>>>>>>>> suitably-derived unique IPv6 addresses to identify 
> > > >>>>>>>>>> themselves to DHCPv6 servers and/or other network nodes.
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> The IETF datatracker status page for this draft is:
> > > >>>>>>>>>> https://datatracker.ietf.org/doc/draft-templin-duid-ipv
> > > >>>>>>>>>> 6/
> > > >>>>>>>>>>
> > > >>>>>>>>>> There are also htmlized versions available at:
> > > >>>>>>>>>> https://tools.ietf.org/html/draft-templin-duid-ipv6-01
> > > >>>>>>>>>> https://datatracker.ietf.org/doc/html/draft-templin-dui
> > > >>>>>>>>>> d-ipv6-01
> > > >>>>>>>>>>
> > > >>>>>>>>>> A diff from the previous version is available at:
> > > >>>>>>>>>> https://www.ietf.org/rfcdiff?url2=draft-templin-duid-ip
> > > >>>>>>>>>> v6-01
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> Please note that it may take a couple of minutes from 
> > > >>>>>>>>>> the time of submission until the htmlized version and diff are available at tools.ietf.org.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
> > > >>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> _______________________________________________
> > > >>>>>>>>>> I-D-Announce mailing list I-D-Announce@ietf.org 
> > > >>>>>>>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
> > > >>>>>>>>>> Internet-Draft directories: 
> > > >>>>>>>>>> http://www.ietf.org/shadow.html or 
> > > >>>>>>>>>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > >>>>>>>>>>
> > > >>>>>>>>>> -------------------------------------------------------
> > > >>>>>>>>>> ------------- IETF IPv6 working group mailing list 
> > > >>>>>>>>>> ipv6@ietf.org Administrative Requests: 
> > > >>>>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
> > > >>>>>>>>>> -------------------------------------------------------
> > > >>>>>>>>>> -------------
> > > >>>>>>>> ---------------------------------------------------------
> > > >>>>>>>> ----------- IETF IPv6 working group mailing list 
> > > >>>>>>>> ipv6@ietf.org Administrative Requests: 
> > > >>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
> > > >>>>>>>> ---------------------------------------------------------
> > > >>>>>>>> -----------
> > > >>>>>>
> > > >>>>>> -----------------------------------------------------------
> > > >>>>>> --------- IETF IPv6 working group mailing list 
> > > >>>>>> ipv6@ietf.org Administrative Requests: 
> > > >>>>>> https://www.ietf.org/mailman/listinfo/ipv6
> > > >>>>>> -----------------------------------------------------------
> > > >>>>>> ---------
> > > >>>>
> > > >>
> > > >> _______________________________________________
> > > >> dhcwg mailing list
> > > >> dhcwg@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/dhcwg
> >
> > _______________________________________________
> > dhcwg mailing list
> > dhcwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------