Skip to main content

The IPv6 Address-based DHCPv6 Unique Identifier (DUID-IPv6)
draft-templin-duid-ipv6-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Author Fred Templin
Last updated 2021-01-07
RFC stream (None)
Formats
Additional resources
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-templin-duid-ipv6-00
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Standards Track                         January 7, 2021
Expires: July 11, 2021

      The IPv6 Address-based DHCPv6 Unique Identifier (DUID-IPv6)
                       draft-templin-duid-ipv6-00

Abstract

   This document defines a new DHCPv6 Unique Identifier (DUID) type
   called DUID-IPv6 that contains a single 128 bit IPv6 address.  DUID-
   IPv6 makes it possible for devices to use suitably-derived unique
   IPv6 addresses to identify themselves to DHCPv6 servers and/or other
   network nodes.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 11, 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Templin                   Expires July 11, 2021                 [Page 1]
Internet-Draft                  DUID-IPv6                   January 2021

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  DUID-IPv6 Format  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  DUID-IPv6 Uses  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Relation to Other DUID Types  . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   DHCP Unique Identifiers (DUIDs) are used in DHCPv6 control messages
   [RFC8415] to identify clients and servers (they may also be used in
   other protocol messages that import the format).  This document
   defines a new DUID type containing a single IPv6 address [RFC8200]
   that has been suitably derived through some means to ensure
   uniqueness.  The new DUID type is termed DUID-IPv6.

   Some methods of producing unique identifiers take care to ensure that
   the identifier includes a well-formed IPv6 address.  For example, the
   Host Identity Tag (HIT) [RFC7401][I-D.ietf-drip-rid] is a valid IPv6
   address and therefore occupies the same 128-bit space as for any IPv6
   address (in network byte order).  The only distinction needed within
   the DUID space is therefore a new DUID type value indicating the
   presence of a single IPv6 address.

   DUID-IPv6 makes it possible for devices to use suitably-derived IPv6
   addresses to identify themselves to DHCPv6 servers and vice versa.
   The DUID-IPv6 format makes no statement about the method used for
   generating the IPv6 address, but its use in control messages asserts
   that the address has been ensured unique through some unspecified
   means.  The following sections present the DUID-IPv6 format and type
   designation.

2.  Terminology

   IETF keywords discussed in [RFC2119][RFC8174].

Templin                   Expires July 11, 2021                 [Page 2]
Internet-Draft                  DUID-IPv6                   January 2021

3.  Background

   In DHCPv6, clients identify themselves to servers via DHCP Unique
   Identifiers (DUIDs) [RFC8415].  DUIDs are identifiers that DHCP
   servers treat as opaque objects with no internal structure.  DUIDs
   are intended to be globally unique, with no two devices using the
   same DUID.

   Four DUIDs types have been defined previously:

   DUID-LLT  the Link-Layer address of one of the device's network
      interfaces, concatenated with a timestamp.

   DUID-EN  an Enterprise Number plus additional information specific to
      the enterprise.

   DUID-LL  the Link-Layer address of one of the device's network
      interfaces.

   DUID-UUID  used in situations where there is a Universally Unique
      IDentifier (UUID) stored in a device's firmware settings
      [RFC6355].

   This document specifies a fifth DUID type, known as DUID-IPv6 and
   identified by DUID-Type value TBD which distinguishes it from all
   other types.

4.  DUID-IPv6 Format

   The DUID-IPv6 is carried within control messages.  It has the
   following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         DUID-Type (TBD)       |    IPv6 Address (128 bits)    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
      |                                                               |
      |                                                               |
      |                                -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

                        Figure 1: DUID-IPv6 Format

      DUID-Type - DUID-IPv6 (TBD) - (16 bits)

      IPv6 Address - An IPv6 Address (128 bits)

Templin                   Expires July 11, 2021                 [Page 3]
Internet-Draft                  DUID-IPv6                   January 2021

5.  DUID-IPv6 Uses

   The DUID-IPv6 may appear in DHCPv6 and/or other protocol control
   messages within a service domain when a unique ID based on an IPv6
   address is required.

6.  Relation to Other DUID Types

   DUID-IPv6 differs in size, format and contents from DUID-LLT, DUID-EN
   and DUID-LL.  DUID-IPv6 shares the same size and format as DUID-UUID,
   however DUID-UUID includes a UUID which is by definition not an IPv6
   address.  (A case could be considered for allowing the existing DUID-
   UUID format to also include an IPv6 address (i.e., instead of a
   UUID), however this would require a domain-wide observation of the
   alternate use.)

7.  IANA Considerations

   IANA is requested to assign a value TBD in the 'dhcpv6-parameters'
   registry for DUID-IPv6.

8.  Security Considerations

   DHCP traffic between a client and server is sent in the clear.  An
   eavesdropper residing on the path between the client and server could
   see DHCP traffic and obtain the unique IPv6 address asserted by a
   particular machine.  This may raise some privacy issues but is not a
   new issue brought on by the use of the DUID type defined in this
   document.

9.  Acknowledgements

   This work is aligned with the NASA Safe Autonomous Systems Operation
   (SASO) program under NASA contract number NNA16BD84C.

   This work is aligned with the FAA as per the SE2025 contract number
   DTFAWA-15-D-00030.

   This work is aligned with the Boeing Commercial Airplanes (BCA)
   Internet of Things (IoT) and autonomy programs.

   This work is aligned with the Boeing Information Technology (BIT)
   MobileNet program.

Templin                   Expires July 11, 2021                 [Page 4]
Internet-Draft                  DUID-IPv6                   January 2021

10.  References

10.1.  Normative References

   [I-D.ietf-drip-rid]
              Moskowitz, R., Card, S., Wiethuechter, A., and A. Gurtov,
              "UAS Remote ID", draft-ietf-drip-rid-06 (work in
              progress), December 2020.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC7401]  Moskowitz, R., Ed., Heer, T., Jokela, P., and T.
              Henderson, "Host Identity Protocol Version 2 (HIPv2)",
              RFC 7401, DOI 10.17487/RFC7401, April 2015,
              <https://www.rfc-editor.org/info/rfc7401>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8200]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", STD 86, RFC 8200,
              DOI 10.17487/RFC8200, July 2017,
              <https://www.rfc-editor.org/info/rfc8200>.

   [RFC8415]  Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
              Richardson, M., Jiang, S., Lemon, T., and T. Winters,
              "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
              RFC 8415, DOI 10.17487/RFC8415, November 2018,
              <https://www.rfc-editor.org/info/rfc8415>.

10.2.  Informative References

   [RFC6355]  Narten, T. and J. Johnson, "Definition of the UUID-Based
              DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355,
              DOI 10.17487/RFC6355, August 2011,
              <https://www.rfc-editor.org/info/rfc6355>.

Author's Address

Templin                   Expires July 11, 2021                 [Page 5]
Internet-Draft                  DUID-IPv6                   January 2021

   Fred L. Templin (editor)
   Boeing Research & Technology
   P.O. Box 3707
   Seattle, WA  98124
   USA

   Email: fltemplin@acm.org

Templin                   Expires July 11, 2021                 [Page 6]