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

"Bernie Volz (volz)" <volz@cisco.com> Tue, 12 January 2021 21:41 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 F180A3A125B; Tue, 12 Jan 2021 13:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 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_H2=-0.001, 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=MGveSJ5L; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=odvSFsc5
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 6SLXVk3cOoDh; Tue, 12 Jan 2021 13:41:22 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB28F3A1239; Tue, 12 Jan 2021 13:41:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10412; q=dns/txt; s=iport; t=1610487681; x=1611697281; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+Mt+ubUGyNCHb2ddXtf5KoC9FI8wMHXqqW94D9i7VKI=; b=MGveSJ5LzMxN4OhNuwGWf7IkmJ41q5ikh39KCg/WvBpqtiZbqlhXoJhn NxjWXt1brnzbc6+VsYevxd7TIj5JbR16fWwo57wWnbfWaL+WmNYfl/Lal HOMsyjJz0SBIAvdxCaeAWD73BQhQt2EU3B8s/sBDLrbZL+eO++d5zuW26 c=;
X-IPAS-Result: =?us-ascii?q?A0A8AABDFv5fmIMNJK1YAQkaAQEBAQEBAQEBAQMBAQEBE?= =?us-ascii?q?gEBAQECAgEBAQFAgU+BUyMufVsvLgqENYNIA411A5kSglMDVAsBAQENAQEYC?= =?us-ascii?q?woCBAEBhEoCF4FaAiU4EwIDAQEBAwIDAQEBAQUBAQECAQYEFAEBAQEBAQEBh?= =?us-ascii?q?gkGJwyFcwEBAQMBAQEhEQwBASwLAQQHBAIBCBEBAgEBAQMCIwMCAgIlCxQBA?= =?us-ascii?q?gYIAQEEAQ0FCAGDHQGCVQMOIAEOpEICiiV2gTKDBAEBBoEzAQMCDkGDARiCE?= =?us-ascii?q?AmBDiqCdYJsTkSCTINyJhuCAIEQAUOCVj6CUgsBAQEBAQEVgRkBLgUQDxSCX?= =?us-ascii?q?jSCLIFPCQFpZgRDCAMDAQEURwUBEBQLBwE/KUePawcugneHWp1HCoJ3iSuSV?= =?us-ascii?q?oMpgTCIf48ahW6UEosWhh2LOCAChDMCBAIEBQIOAQEGgW0hgVlwFRohgmkJR?= =?us-ascii?q?xcCDYE3jGoJAw4Jg06FFIVEdAI1AgYBCQEBAwl8i04BgRABAQ?=
IronPort-PHdr: =?us-ascii?q?9a23=3AADV+RRJmCoz8iO67htmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeGvKs/hljEXIPUrflDjrmev6PhXDkG5pCM+DAHfYdXXh?= =?us-ascii?q?AIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtfH8v/YVKUqXq3vnYeHx?= =?us-ascii?q?zlPl9zIeL4UofZk8Ww0bW0/JveKwVFjTawe/V8NhKz+A7QrcIRx4BlL/U8?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,342,1602547200"; d="scan'208";a="647128062"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Jan 2021 21:41:20 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 10CLfKga030311 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 Jan 2021 21:41:20 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 15:41:20 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 15:41:19 -0600
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 12 Jan 2021 15:41:19 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WmT343apgjjryoqx8CTcTVFoppZ1ar1vYe8jMCFG1MejkNC1zcbRnnUCUmHmbiqCAfVNhQxtMANRsQed30vbq+TRBJq6J5pwOZW/X3FQd2wQfQN2XS1IaB5HCsHOwNShVKxW/Ds8y8gEhm4owj2qJElAD4UdwTcvLugbxDX/7bIOYgcTeb0mImIf8Mv0/ywFMeF32rQZLK+RJZaPCD8qrfd07/A3K6Kx3XNApuqHHNfc+3XsKRLmIroVcJm6yOvpAEIqN5c3fGFkktwp8hreOD90MaG4XkHcCL3zMnXDdrJZRHLNK5NzTZ8c/0Ilxggq10HhyB+OkfG85ybN9Sxncg==
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=+Mt+ubUGyNCHb2ddXtf5KoC9FI8wMHXqqW94D9i7VKI=; b=czezipA7p9/2BqG0bCi6EqXNdznBdhrJgJRmYv9HbjAFgMajuT0TI7JZTdTVZ+eIZRcL5T8us0mcSLV04+pUCteMyAVaNLHfkH0D9WtkF9BPKnxA0Elpvmog15v5TDYUfHih/XUXzZfKWOEvUjkvkcAdocppQYYotJ3nhiGEyGAxz8rR6GLUz/vNufdpvo5eLrnKDiScqGVXV8lgSXmcfFpFbsoCBNpznH6nRKzzThUz+DiBycdL1hhAWXqQvB4HXUQ/LBwCyujspgO6Fo1BZ13w8A7KOu7MP//ELpbzfUN3mlr5pw7uDYgde6CYXEAykLgC55TGYmOgPd3OFOvtxw==
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=+Mt+ubUGyNCHb2ddXtf5KoC9FI8wMHXqqW94D9i7VKI=; b=odvSFsc5cfzrWtGnfJ6EAt1Kn5JVjzvbPWNS1ZW6xQMZ1xmUmdyi9WoYdydMLT3m/zXGHi3h2NPa2c5OAZtc7r/sReh+RddbVJcFAjl4IriJpS8RsgnMVMlW3xluZXaUX8JTVbBX5DiBa++lLXhuI+ZJMSlNpI0lVmiVd+BfxnE=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN7PR11MB2788.namprd11.prod.outlook.com (2603:10b6:406:b2::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Tue, 12 Jan 2021 21:41:18 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d%4]) with mapi id 15.20.3742.012; Tue, 12 Jan 2021 21:41:18 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, dhcwg <dhcwg@ietf.org>
CC: "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: AdboRv1b8ifd9On5SaGFHM0jDP097wAqydiAAAN645AACqQb0A==
Date: Tue, 12 Jan 2021 21:41:18 +0000
Message-ID: <BN7PR11MB25479362C4C0274BA7EBCCAACFAA0@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <357eb2060b2e4b4083ab6d01349d297e@boeing.com> <B2D91A40-7AA7-48EC-BD8F-642ABE1E729B@cisco.com> <a05f8218827c4976818257baedd0cbed@boeing.com>
In-Reply-To: <a05f8218827c4976818257baedd0cbed@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: [173.38.117.69]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4a237b7e-8d4b-423f-222b-08d8b742cb96
x-ms-traffictypediagnostic: BN7PR11MB2788:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BN7PR11MB2788B64D51B15ACA1BF8B25ECFAA0@BN7PR11MB2788.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /0g3DHFQiIBv1QPuyclvQlFi2WrN0/Mk5rbZTO1f4wnnR5XyH6e/WwjPHt2iQwMvzABqb2tH5u4Zc696Uq1vSghtANUnGg2mKIRO8P2ewCE5hQ8Va8ot0Zrw3zeuDTmdeyxas5aHBv2SfkDKeLaKyBaMJf5+mA0DaLe3ws9tIEZ515hwdBDniwdEMp1Q3EiC5CocY0Aj/Aga5t8t5vS+Ptaan6mK6wmoak9Ar9lqYafgJ0Dkod3iGIriaF9PdsqRu6B+0JDDKuy4B+PZiDtjfmxtjeoYo+lFf00oU7Z7E9xSTKuyV4DLcCrc67yal5B9N8JAacDHQ9T/GmX5/eHhRxOKMQhTN6o4SleyYxfno3lOMTy/KgQFBAE8pFUMJ1OdG1HdVoc70ew/m4Qezr7MqylyQG5tY4vC8FNwZTb/moV9AYrgjoUyVZqhuoaAo0VADCabd26KLP5HFWGPoEqBHA==
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)(376002)(366004)(39860400002)(346002)(136003)(316002)(66476007)(8936002)(86362001)(9686003)(64756008)(66946007)(7696005)(110136005)(33656002)(66574015)(55016002)(76116006)(8676002)(83380400001)(71200400001)(966005)(2906002)(53546011)(4326008)(478600001)(52536014)(66556008)(26005)(66446008)(6506007)(5660300002)(186003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: =?utf-8?B?cy9DY0ZUKzJJM3hpTlZiVWhDVGpmRm9ySXhLcmlwTWZSU01sWVlkNy9DTTFQ?= =?utf-8?B?L05kYTRKalJGcHlwa1JrVUlLNWVYZE5VeDhSOGt2LzhsUktRSzVQelUxd0o2?= =?utf-8?B?SDRXWTJ3dHJXbkVjeG9jbUVwUHBYYmZOZFhPNEUrL2NsbEYydUtReVZxMHgz?= =?utf-8?B?UXI1em1QbGFzU2prNnE1Q2hLTU9jNXp5ZFRYSFl1Qy9EUmFSck5QVFhUTTNX?= =?utf-8?B?eWc1bkhZNDBIUUNBcDZCUFFHMzN3QVJnNExRNHFodmxWdVZBcXl5QTBoa0pu?= =?utf-8?B?N2RRdnl4Qy9QQlBHSkg3MVVMTXc4UXkyUC9Wc1N1NEhod0dLK0IyY0VrZFd4?= =?utf-8?B?UEc5SUF3OHIzaFNRcXY5ZlNnRE05Y2plb0FrM0VaVG5FekdxdSsxQjYwcGNo?= =?utf-8?B?c0xFN0dFVEhpVk90MjVzelJYREk0TUx0R0NXYzM3TE5MMW0zZk1peE85WmJC?= =?utf-8?B?dnRtTTNFTWtlbDkrN0lqWDBTbmFwZExzV2FXTE5NOWhQNlQzU2Q4WnRHSDh3?= =?utf-8?B?VGpIbUNpQll1ZDhCRmZHWkdYSFg2Umh0RmJUYzdnTzAzUmxPRFZleE1RT1Br?= =?utf-8?B?eEJnTzZaSXhhVnFqbEQ3RW9CaUtEQVhYYUZkMVdETVZJT3AyL3JPSlRtSXUv?= =?utf-8?B?clVVaDJoYlpJd1BCQmxYMUdYN2hoS2VrRm1MVGNSdW00TzRIZHdqV0piVnBV?= =?utf-8?B?NlZ2U2hCQmFGWU01SU9uTk5LQjhRTzZ2T2IzdjlQVU5BelZUVkxvVmo5N3Fp?= =?utf-8?B?MSszeFB4MXE4MlFablVEN29Kb1lvSTc3UTI4YWZJbGJzNlFoQ0FWcGQ3NzF2?= =?utf-8?B?OXdVcXVRVWdZd1F5M0RKMUlhLzZEdURXYzJNMTZ4Wm00TkZsNmVBWVFqNWNU?= =?utf-8?B?UTFrWi9MMVBYa3pxRm9Eb0JWOW1mcDJyV2pudUIxMzBuTFVCckRqWUhRZ09v?= =?utf-8?B?U0R3bFR3MStFUDdOdTJzbFU3a3hYOEJNcFZtN3RwWWQxMjBhU2FxMElIL0FR?= =?utf-8?B?Zy82VG1sb05aN01LZUlsdURPQUVEbW94RFIxR1Y2NStiZDcrMnVPeHZ0Vkhv?= =?utf-8?B?WXFLWnJ1OTN1djdHRVcvV1o1RHY0MURSWW1weUw3bnZKZ0dKWFpwQ00yRFYz?= =?utf-8?B?U0FkdEdXSDhsTzlJM2JwT0svMi9jWDBqdmd4ZFVSQ3duOURnZHdJUVlPZFdO?= =?utf-8?B?MEN5RmIvcm9NQ1k4bjJRNjBnbnFQM0pnV2FzUVUwN2RtZFp1ajZINVZSM0JZ?= =?utf-8?B?cWhXSTY5SWI3S2tiWGNtdXFMUGhHZVptM2pzL0c4bENNcC93dE1CdTJFdm9X?= =?utf-8?Q?NkrmqTgBvW6lE=3D?=
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: 4a237b7e-8d4b-423f-222b-08d8b742cb96
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2021 21:41:18.3174 (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: olv5/PIAhZilylQvJtkV832zNwhdtMcbeaxi4ba+AkjUfAOUi6g+wMISrdr770nG
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2788
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LlBYiA5WKB3HJHpb5k-F_DCEFA0>
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: Tue, 12 Jan 2021 21:41:26 -0000

BTW: If you used DUID-EN, you could easily do what we already do with the DUID:

For AERO's Enterprise-ID, you can in the identifier field add 2-bytes of type to start followed by the value. This would let AERO use many different DUID types under its enterprise number.

But this does require the Enterprise Number owner to assure that they always use the 2-bytes type in the future and have their own "IANA" to manage it.

(Organizations tend to be bad at managing vendor spaces as I only know too well - cost saving measures have usually meant that people assigned to manage these kinds of spaces are cut or moved elsewhere.)

It will be good too see an updated version which provides motivation for a new type - with a clear explanation of why none of the existing types are appropriate. Also, you may want to consider text that says something like only use this new type for these specific usages, otherwise you MUST use one of the other types.

- Bernie

-----Original Message-----
From: dhcwg <dhcwg-bounces@ietf.org> On Behalf Of Templin (US), Fred L
Sent: Tuesday, January 12, 2021 11:42 AM
To: Eric Vyncke (evyncke) <evyncke@cisco.com>om>; ipv6@ietf.org; dhcwg <dhcwg@ietf.org>
Cc: Dickson (US), Sean M <sean.m.dickson@boeing.com>
Subject: Re: [dhcwg] I-D Action: draft-templin-duid-ipv6-01.txt

Eric, see below:

> -----Original Message-----
> From: Eric Vyncke (evyncke) [mailto:evyncke@cisco.com]
> Sent: Tuesday, January 12, 2021 5:50 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>om>; ipv6@ietf.org; 
> dhcwg <dhcwg@ietf.org>
> Cc: Dickson (US), Sean M <sean.m.dickson@boeing.com>
> Subject: Re: I-D Action: draft-templin-duid-ipv6-01.txt
> 
> <without any hat>
> 
> Hello Fred,
> 
> Just wondering how would this new DUID could be used when several 
> interfaces sharing the same DUID will request some
> address(es)/prefix(es) over DHCPv6 ?

I think this may have been addressed in my response to Mark, but the intention is that an IPv6 address that is independent of any of the node's physical interfaces and that provides an identity for the node is the address that would go into the DUID. [RFC7401][draft-ietf-drip-rid] are two examples where a valid IPv6 address is generated and intended to provide an interface-independent, unique and long lived identity for the node. Other examples may be defined in the future as well.

> If you allow me to guess your use case, then would DUID type based on 
> the private enterprise number (FAA and EASA have ones) could be used ? 
> This would be simpler than requesting a new DUID type

I was actually thinking that DUID-UUID would be a candidate surrogate DUID because the body is exactly 128bits the same as for IPv6 addresses. But, by definition, UUIDs are *not* IPv6 addresses since they do not observe the [RFC4291] address architecture.
Per your suggestion, a private enterprise number could be gotten (AERO also already has one) and then use DUID-EN instead. But, then there would not be a standards track specification guaranteeing that the holder of the private enterprise number would consistently and forever always apply IPv6 address architecture semantics to their application of the private enterprise number.

Hence, the proposal for DUID-V6ADDR. Or, if folks would prefer a different name I could imagine alternatives such as DUID-IN6, DUID-IPV6, etc. Any preferences?

Thanks - Fred

> Hope this helps,
> 
> Regards
> 
> -éric
> 
> </without any hat>
> 
> -----Original Message-----
> From: ipv6 <ipv6-bounces@ietf.org> on behalf of "Templin (US), Fred L" 
> <Fred.L.Templin@boeing.com>
> Date: Monday, 11 January 2021 at 19:47
> To: "ipv6@ietf.org" <ipv6@ietf.org>rg>, dhcwg <dhcwg@ietf.org>
> Cc: "Dickson (US), Sean M" <sean.m.dickson@boeing.com>
> Subject: FW: I-D Action: draft-templin-duid-ipv6-01.txt
> 
>     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-ipv6/
> 
>     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-duid-ipv6-01
> 
>     A diff from the previous version is available at:
>     https://www.ietf.org/rfcdiff?url2=draft-templin-duid-ipv6-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
>     
> --------------------------------------------------------------------

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg