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

"Templin (US), Fred L" <> Tue, 12 January 2021 16:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F333D3A0B8C; Tue, 12 Jan 2021 08:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.119
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3Mkjw0OlECZi; Tue, 12 Jan 2021 08:42:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C9A5A3A0B5F; Tue, 12 Jan 2021 08:42:18 -0800 (PST)
Received: from localhost (localhost []) by (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 10CGgBZp010257; Tue, 12 Jan 2021 11:42:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=boeing-s1912; t=1610469735; bh=92VW55eexeH65lZeM2NFBKTJK2lkLR+Be82StB9Gh74=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=f1v1MqO0lELxISY+bd6SXXTXMXe+hfnx3noarNBTyNGUbPaZW3ks4JgSzTmD55hTm j7c9jHW1XMpr+vL9JPQEzIMxzNYSr8FjhO+pwm2DeibCq/vOk3M6rPjtGvDLE2ZsRi qH+3G712jwTbDd+RHU9mIOink1JBBnqJqfgMgpnYXOMIYbyVJTt+nW0WjMwklxnGJH bs/u0JqOiauUugQhT/ZlAKEB/qjCiBNFC3UUVuZxsoPn2mmyyhW9L9WGnNAUyDCaQx q+rEKpA8BENTUwPERuhUmEG86mxQvVIy081+zsnRJpoc+j7chOSLrWx9CGbAIbVn1Q kz02xB0Ivrw5w==
Received: from ( []) by (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 10CGg8Sv010221 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 12 Jan 2021 11:42:08 -0500
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 12 Jan 2021 08:42:07 -0800
Received: from ([fe80::1522:f068:5766:53b5]) by ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Tue, 12 Jan 2021 08:42:07 -0800
From: "Templin (US), Fred L" <>
To: "Eric Vyncke (evyncke)" <>, "" <>, dhcwg <>
CC: "Dickson (US), Sean M" <>
Subject: RE: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Topic: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Index: AdboRv1b8ifd9On5SaGFHM0jDP097wAqydiAAAN645A=
Date: Tue, 12 Jan 2021 16:42:07 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: 6932C87C31B8D82821CC64161953C5D18FC641A8D0A22E4E91E2B66EAD5218802000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Jan 2021 16:42:21 -0000

Eric, see below:

> -----Original Message-----
> From: Eric Vyncke (evyncke) []
> Sent: Tuesday, January 12, 2021 5:50 AM
> To: Templin (US), Fred L <>;; dhcwg <>
> Cc: Dickson (US), Sean M <>
> 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 <> on behalf of "Templin (US), Fred L" <>
> Date: Monday, 11 January 2021 at 19:47
> To: "" <>, dhcwg <>
> Cc: "Dickson (US), Sean M" <>
> 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 [] On Behalf Of
>     Sent: Monday, January 11, 2021 10:21 AM
>     To:
>     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:
>     There are also htmlized versions available at:
>     A diff from the previous version is available at:
>     Please note that it may take a couple of minutes from the time of submission
>     until the htmlized version and diff are available at
>     Internet-Drafts are also available by anonymous FTP at:
>     _______________________________________________
>     I-D-Announce mailing list
>     Internet-Draft directories:
>     or
>     --------------------------------------------------------------------
>     IETF IPv6 working group mailing list
>     Administrative Requests:
>     --------------------------------------------------------------------