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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 12 January 2021 17:08 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 98EF63A0D3D; Tue, 12 Jan 2021 09:08:43 -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 Abuuc-3UzhM8; Tue, 12 Jan 2021 09:08:41 -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 8CD043A0D07; Tue, 12 Jan 2021 09:08:41 -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 10CH8chF006919; Tue, 12 Jan 2021 12:08:40 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1610471320; bh=3SQmbLI8Xfn5Q0dQPtFBZC2pUfxsiN+k9uNC1L9Zz4I=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=YSE/aU5KN2+tFGHSoYT1FNv8Jh6psYzuAV8MvOizy0k33xgsrmFnDVSsGg41luEUD FbDDIMbQHxQz0ivR4JjYHdT5ZZEbJXz1Ti6SoQUj7FlTO4JqFBSGUC6bjTMDKKh9v1 oE8sUEZDmGSqC9zR586oYjLMNDN/OuJCX5PdDLGqFc4TX3Sxz5Bdvm38X+JfqcTCag KJXrfJEsj+Um5izAkdygUCRrutDMQXw1r1z1XsTaQpin6Ho3V6DUVGLxhUHCykjq4z Bk9Znojx/+jWuLMA6mlvgAzBBhMGbXVhWKaSACWNfd7IUn6TYgqwRXUKi16dqjhPJQ fpfXnxakFvNvg==
Received: from XCH16-02-10.nos.boeing.com (xch16-02-10.nos.boeing.com [144.115.66.76]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 10CH8Y0l006901 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 12 Jan 2021 12:08:34 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-02-10.nos.boeing.com (144.115.66.76) 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 09:08:33 -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; Tue, 12 Jan 2021 09:08:33 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "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: AdboRv1b8ifd9On5SaGFHM0jDP097wAqydiAAAN645AAATdmEA==
Date: Tue, 12 Jan 2021 17:08:33 +0000
Message-ID: <2d1a41e7f687455a99c01719c8439f55@boeing.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:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: C34305229550BF25BA16576AD55177CA695A0B584F0C96F2308D66448DD36DB32000: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/JiEpYTgojIcNEURF7FT1rqP5RvE>
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 17:08:44 -0000

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