Skip to main content

IP6 ULAs with UUID Interface Identifiers (ULA-UUID)
draft-templin-6man-ula-uuid-01

Document Type Active Internet-Draft (individual)
Author Fred Templin
Last updated 2024-05-16
RFC stream (None)
Intended RFC status (None)
Formats
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-6man-ula-uuid-01
Network Working Group                                 F. L. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Informational                               16 May 2024
Expires: 17 November 2024

          IP6 ULAs with UUID Interface Identifiers (ULA-UUID)
                     draft-templin-6man-ula-uuid-01

Abstract

   Internet Protocol, version 6 (IPv6) defines a Unique Local IPv6
   Unicast Address (ULA) format based on the IANA-assigned prefix
   fc00::/7.  The structure for sub-prefix fd00::/8 is well defined, but
   the remaining sub-prefix fc00::/8 is reserved for future use.  This
   document proposes a use for sub-prefix fc00::/8 in conjunction with
   the Universally Unique Interface IDentifier (UUID).

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 17 November 2024.

Copyright Notice

   Copyright (c) 2024 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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Templin                 Expires 17 November 2024                [Page 1]
Internet-Draft            IPv6 ULA-UUID Address                 May 2024

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The IPv6 ULA-UUID Address . . . . . . . . . . . . . . . . . .   3
   3.  Assigning IPv6 ULA-UUIDs to an Interface  . . . . . . . . . .   4
   4.  Implementation Status . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   When two or more IPv6 [RFC8200] nodes come together within a common
   local operating region (e.g., during the formation of a Mobile Ad-hoc
   Network (MANET)), they must be able to assign unique local-use
   addresses and exchange IPv6 packets even if there is no operator
   infrastructure present.

   The key feature of these local-use IPv6 addresses is that they must
   be assured unique so that there is no chance of conflicting with an
   address assigned by another node.  There is no requirement that the
   addresses have topologically-oriented prefixes, since the (newly-
   formed) local network may not (yet) connect to any other
   Internetworking topologies.

   The local-use IPv6 addresses could then be used for continuous local
   communications and/or to bootstrap the assignment of topologically-
   oriented addresses under the IPv6 multi-addressing architecture
   [RFC4291].

   IPv6 defines a Unique Local IPv6 Unicast address (ULA) format
   [RFC4193] based on the IANA-assigned prefix fc00::/7.  The sub-prefix
   fd00::/8 is well defined, but the remaining sub-prefix fc00::/8 is
   reserved for future use.  This document proposes a use for sub-prefix
   fc00::/8 in conjunction with the Universally Unique Interface
   IDentifier (UUID) [RFC9562].

Templin                 Expires 17 November 2024                [Page 2]
Internet-Draft            IPv6 ULA-UUID Address                 May 2024

2.  The IPv6 ULA-UUID Address

   The IPv6 addressing architecture specified in [RFC4291] and [RFC4193]
   defines the supported IPv6 address forms for unicast, multicast and
   anycast.  Unicast addresses are typically assigned through Stateless
   Address AutoConfiguration (SLAAC) [RFC4862] and/or the Dynamic Host
   Configuration Protocol for IPv6 (DHCPv6) [RFC8415], but these
   services require the presence of IPv6 network infrastructure which
   may not be immediately available in spontaneously-formed MANETs or
   other isolated local networks.

   A new IPv6 address type known as the DRIP Entity Tag (DET) (or,
   Hierarchical Host Identity Tag (HHIT)) [RFC9374] provides a well-
   structured address format with exceptional uniqueness properties.  A
   portion of the address includes the node's self-generated Overlay
   Routable Cryptographic Hash IDentifier (ORCHID) while the remainder
   of the address includes a well-formed IPv6 prefix corresponding to an
   attestation service that supports address proof-of-ownership.
   Verification of the attestation aspect of the address requires access
   to network infrastructure, but this may not always be available.

   This document therefore proposes a new fully-self-generated IPv6
   unicast address format that can be used either instead of or in
   addition to a DET/HHIT and/or other IPv6 unicast address types
   (noting again that a single interface may have multiple IPv6
   addresses [RFC4291]).  The address uses the 8-bit ULA prefix fc00::/8
   along with a 120-bit interface identifier that includes the 120
   least-significant bits of a Universally Unique IDentifier (UUID).
   With reference to Figure 8 of [RFC9562] which depicts the UUIDv4
   format, this "IPv6 ULA-UUID address" format is shown in Figure 1:

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |1|1|1|1|1|1|0|0|                   random_a                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          random_a             |  ver  |       random_b        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |var|                       random_c                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           random_c                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                   Figure 1: IPv6 ULA-UUID Address Format

   To form an IPv6 ULA-UUID, the node creates a 128-bit UUIDv4 per
   [RFC9562] then simply replaces the most significant 8 bits with the
   constant string '11111100' (0xfc); the resulting 128-bit ULA-UUID

Templin                 Expires 17 November 2024                [Page 3]
Internet-Draft            IPv6 ULA-UUID Address                 May 2024

   then has the format of an IPv6 address with an 8-bit subnet prefix
   and 120-bit interface identifier as permitted by the IPv6 addressing
   architecture.  For example:

      fc84:6c29:de12:4b74:884e:9d2a:73fc:2d94::/8

   After a node creates a ULA-UUID, it can use the address within the
   context of spontaneously-organized local networks in which two or
   more nodes come together in the absence of supporting infrastructure
   and can still exchange IPv6 packets with little or no chance of
   address collisions.  The use could be limited to bootstrapping the
   assignment of topologically correct IPv6 addresses through other
   means mentioned earlier, or it could extend to longer term usage
   patterns such as sustained communications with single-hop neighbors
   on a local link or even between multi-hop peers within a MANET.

   Note: while the ULA-UUID format specified above is relative to
   UUIDv4, the same format can be applied also to all other UUID
   versions specified in [RFC9562], i.e. by replacing the most
   significant 8 bits of the UUID with the constant string '11111100'
   (0xfc).

3.  Assigning IPv6 ULA-UUIDs to an Interface

   IPv6 ULA-UUID addresses based on the prefix "fc00::/8" have no
   topological orientation and can therefore be assigned to any of a
   node's IPv6 interfaces.  The addresses may serve as a basis for
   multihop forwarding over a MANET interface and/or for local
   neighborhood discovery over other IPv6 interface types.  Due to their
   uniqueness properties, IPv6 ULA-UUID addresses can be assigned to
   interfaces without invoking Duplicate Address Detection (DAD).

4.  Implementation Status

   In progress.

5.  IANA Considerations

   This document has no requirements for IANA.

6.  Security Considerations

   TBD.

Templin                 Expires 17 November 2024                [Page 4]
Internet-Draft            IPv6 ULA-UUID Address                 May 2024

7.  Acknowledgements

   This work was inspired by continued investigations into 5G MANET
   operations in cooperation with the Virginia Tech National Security
   Institute (VTNSI).

   Emerging discussions on the IPv6 maintenance (6man) mailing list are
   expected to shape future versions of this document.  The author
   acknowledges all those whose useful comments have helped further the
   understanding of this proposal.

   Kyzer Davis (RFC9562 author) is acknowledged for his review and
   comments that helped shape the document.

   Honoring life, liberty and the pursuit of happiness.

8.  References

8.1.  Normative References

   [RFC4193]  Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
              Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005,
              <https://www.rfc-editor.org/info/rfc4193>.

   [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
              Architecture", RFC 4291, DOI 10.17487/RFC4291, February
              2006, <https://www.rfc-editor.org/info/rfc4291>.

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

   [RFC9562]  Davis, K., Peabody, B., and P. Leach, "Universally Unique
              IDentifiers (UUIDs)", RFC 9562, DOI 10.17487/RFC9562, May
              2024, <https://www.rfc-editor.org/info/rfc9562>.

8.2.  Informative References

   [RFC4862]  Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
              Address Autoconfiguration", RFC 4862,
              DOI 10.17487/RFC4862, September 2007,
              <https://www.rfc-editor.org/info/rfc4862>.

Templin                 Expires 17 November 2024                [Page 5]
Internet-Draft            IPv6 ULA-UUID Address                 May 2024

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

   [RFC9374]  Moskowitz, R., Card, S., Wiethuechter, A., and A. Gurtov,
              "DRIP Entity Tag (DET) for Unmanned Aircraft System Remote
              ID (UAS RID)", RFC 9374, DOI 10.17487/RFC9374, March 2023,
              <https://www.rfc-editor.org/info/rfc9374>.

Appendix A.  Change Log

   << RFC Editor - remove prior to publication >>

   Differences from earlier versions:

   *  First draft publication.

Author's Address

   Fred L. Templin (editor)
   Boeing Research & Technology
   P.O. Box 3707
   Seattle, WA 98124
   United States of America
   Email: fltemplin@acm.org

Templin                 Expires 17 November 2024                [Page 6]