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

To add a bit more to my last couple of messages, RFC4291 says the following
about IPv6 addresses:

   "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."

What I am proposing honors this fact because the IPv6 address
that would appear in the DUID-V6ADDR must also be assigned to
an interface of the node, and a loopback or some other manner
of virtual interface qualifies. I will update the draft to make sure
this is made clear.

Thanks - Fred

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Templin (US), Fred L
> Sent: Tuesday, January 12, 2021 8:42 AM
> To: Eric Vyncke (evyncke) <evyncke@cisco.com>; 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>; 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>, 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