Re: UUID version 6 proposal, initial feedback

"Theodore Y. Ts'o" <tytso@mit.edu> Sat, 01 February 2020 21:29 UTC

Return-Path: <tytso@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A581200FE for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2020 13:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 iJm9ChhL6FnK for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2020 13:29:09 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 8B07F12004A for <ietf@ietf.org>; Sat, 1 Feb 2020 13:29:09 -0800 (PST)
Received: from callcc.thunk.org (75-104-86-204.mobility.exede.net [75.104.86.204] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 011LT0Ss014709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 1 Feb 2020 16:29:07 -0500
Received: by callcc.thunk.org (Postfix, from userid 15806) id 84D16420324; Sat, 1 Feb 2020 16:28:59 -0500 (EST)
Date: Sat, 01 Feb 2020 16:28:59 -0500
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Brad Peabody <bradgareth@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
Subject: Re: UUID version 6 proposal, initial feedback
Message-ID: <20200201212859.GB528198@mit.edu>
References: <D0894516-3F20-4545-BD7D-BE4FA96FAF75@gmail.com> <CABkgnnXSxqqinyK4QiwVv-VuzAraHFUGCrm0K0e9dJX_F80bWg@mail.gmail.com> <D3517A2C-1FCC-42D2-9AB6-248680BE89E1@gmail.com> <c5ba6f5d-7c61-bfdf-63e6-be7d640ee50c@gmail.com> <6E165220-7D1F-4AD8-B4F3-DDCB8F1DA6E2@akamai.com> <b4b73e11-7e21-03ae-0ebf-badcc2bf9d7e@gmail.com> <20200201060733.GD454818@mit.edu> <75dff0d7-3e2b-8f2a-c8b1-46d27004cce3@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <75dff0d7-3e2b-8f2a-c8b1-46d27004cce3@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ypACooSAM9pcHCihhvo3PXP1H68>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2020 21:29:11 -0000

On Sat, Feb 01, 2020 at 11:00:24AM -0800, Brad Peabody wrote:
> The issue being that many applications need something like a UUID but can't use
> an actual UUID for one reason or another (e.g. sorting properties,
> insufficient unguessability, too long, etc.); thus the new proposal.

Again, I'd urge you to consider that you should build on *top* of the
standard UUID spec, since there are already implementations that will
do the right thing as far as time-based and random-based UUID's (the
latter will provide all the unguessability you need) and then just
create a library which *transforms* the UUID into a convenient
encoding form that makes it be convenient for key-indexing, or a more
compact text encoding, etc.

There are already very good implementations for UUID generation, and
if you create something which re-invents the wheel at a spec level, it
will cause people to reinvent the wheel (possibly badly) at the
implementation level.

Cheers,

						- Ted