UUID Format Update
draft-peabody-dispatch-new-uuid-format-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dispatch                                                    BGP. Peabody
Internet-Draft                                         February 24, 2020
Updates: 4122 (if approved)
Intended status: Standards Track
Expires: August 27, 2020

                           UUID Format Update
               draft-peabody-dispatch-new-uuid-format-00

Abstract

   This document presents a new UUID format (version 6) which is suited
   for use as a database key.

   A common case for modern applications is to create a unique
   identifier to be used as a primary key in a database table that is
   ordered by creation time, difficult to guess and has a compact text
   format.  None of the existing UUID versions fulfill each of these
   requirements.  This document is a proposal to update RFC4122 with a
   new UUID version that addresses these concerns.

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 August 27, 2020.

Copyright Notice

   Copyright (c) 2020 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

Peabody                  Expires August 27, 2020                [Page 1]
Internet-Draft               new-uuid-format               February 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Summary of Changes  . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Version 6 . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Timestamp . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Clock Sequence and Node Parts . . . . . . . . . . . . . .   5
     3.4.  Alternate Text Formats  . . . . . . . . . . . . . . . . .   6
       3.4.1.  Base64 Text (Variant A) . . . . . . . . . . . . . . .   7
       3.4.2.  Base32 Text . . . . . . . . . . . . . . . . . . . . .   7
   4.  Uniquness Service . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Background

   A lot of things have changed in the time since UUIDs were originally
   created.  Modern applications have a need to use (and many have
   already implemented) UUIDs as database primary keys.  However some
   properties of the existing specification are not well suited to this
   task.

   The motivation for using UUIDs as database keys stems primarily from
   the fact that applications are increasingly distributed in nature.
   Simplistic "auto increment" schemes with integers in sequence do not
   work well in a distributed system since the effort required to
   synchronize such numbers across a network can easily become not worth
   it.  The fact that UUIDs can be used to create unique and reasonably
   short values in distributed systems without requiring synchronization
   makes them a good candidate for use as a database key in such
   environments.

Peabody                  Expires August 27, 2020                [Page 2]
Internet-Draft               new-uuid-format               February 2020

   However, most of the existing UUID versions have poor database index
   locality.  Meaning new values created in succession are not close to
   each other in the index and thus require inserts to be performed at
Show full document text