Re: UUID version 6 proposal, initial feedback

Brad Peabody <bradgareth@gmail.com> Sat, 01 February 2020 19:00 UTC

Return-Path: <bradgareth@gmail.com>
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 706DE120143 for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2020 11:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RxdehltRdIHC for <ietf@ietfa.amsl.com>; Sat, 1 Feb 2020 11:00:27 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1977F120118 for <ietf@ietf.org>; Sat, 1 Feb 2020 11:00:27 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id y1so4149594plp.7 for <ietf@ietf.org>; Sat, 01 Feb 2020 11:00:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=1apwJ6o84wydCpPkzXEheckOo4pvvhjlTpFoaK2b11U=; b=oI4l4vpxSLHyylfo1SjwtFGX73aSHYcoW4QKPKk8I6leWly1go720oUvhZr6rIFhyi KNSg2HczbnsnZoZ6TwXCb+s6CfAB9/+1kmC/n0AVlbbPUOHTjlVor+tHE/pD7qH6lFx8 QBx+j3b0LvvqjZtiOiG84Z+UZqhvPoKEqFGIU/i50Ff2U/NfCeuZZ7pVZaOpy+YeFKpN PKduMC+fqyVviEwExT7F4+OAEsO63ooAzzuELQy4Ucl6jeAhqCl1RokzAqP60h2lSw3O r1A31x1lCjMlbSg9eyQm304L2lLtwLCulRlGRwjOjZBPnNh10nXt3yV0Q9q//HAQ8Fj2 VdaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=1apwJ6o84wydCpPkzXEheckOo4pvvhjlTpFoaK2b11U=; b=o3CHcS/Nh09kFJWpp5nUdf2snCeY+WdziuBSI8F6Q6WDy+JSy5eEj2poyVmjLdgoFr TxgkB1ohimOmekd0zouEAtsS0EckJaB7NGEkkTpRT4zu8UuEkt3skHDpQILuDooSJf9U S33as6s3RqppOTH1bWWomsGwoL8k78n1bhXGwMyJZBVatleVPWFyjJNtHRFO10FeYdvj J6YR7MP9uvm3SSKapQtXnXUhay7xKMhEHEWmbtczn4sIDhk6yWiWEbpnSlMyGUHbJNOy ZboXmHPTO67SHcFhmCIQbn+bkpcqnjqahMcZgXOGSkEUseHhcwMxI/DqTHQXB8/J5FHU XlpQ==
X-Gm-Message-State: APjAAAVcHGe7muAeChTwwg62jpIvMgVcfoHDXrF0y1xKmhc2QuDXMdJ4 ItPYrpHsxvUV+Buin1d8Tpw=
X-Google-Smtp-Source: APXvYqzzRbVs7aghwLnnG0yaWSgJRjgTt8G66LbZkp8ngJQc6/ewthQFO6vX4lEpQeKdDMZKGyApAQ==
X-Received: by 2002:a17:902:8545:: with SMTP id d5mr15392899plo.116.1580583626317; Sat, 01 Feb 2020 11:00:26 -0800 (PST)
Received: from BGPMacBookPro.charter.com ([2600:6c50:7f:5954:5c5b:94de:cdfa:9b11]) by smtp.gmail.com with ESMTPSA id w8sm14338457pfn.186.2020.02.01.11.00.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 01 Feb 2020 11:00:25 -0800 (PST)
Subject: Re: UUID version 6 proposal, initial feedback
To: IETF discussion list <ietf@ietf.org>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>, "Salz, Rich" <rsalz@akamai.com>
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>
From: Brad Peabody <bradgareth@gmail.com>
Message-ID: <75dff0d7-3e2b-8f2a-c8b1-46d27004cce3@gmail.com>
Date: Sat, 01 Feb 2020 11:00:24 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <20200201060733.GD454818@mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c8FFJvrP3I9zh1IMmPHRzhlS1wI>
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 19:00:28 -0000

>>> What I laid out is essentially a collection of options that seem to come up time and again dealing with unique identifiers.? I think there is benefit in standardizing it.

>> Considerations in designing unique identifiers sounds like it could be a worthwhile RFC. I just don?t think they?re UUID?s.

> I concur. I think it would be a better proposal if they were called something else.

Cool - I will come up with some ideas for different names and send those 
around soon.


> As as you point at in [1], it's trivial to covert between your "version 6" and the V1 UUID --- it's just a matter of swapping the bytes. http://gh.peabody.io/uuidv6/
> /dev/urandom is a Linux specific thing.  The better choice is libuuid.

To clarify - the information at http://gh.peabody.io/uuidv6/ is out of 
date, and the new proposal (see 
https://docs.google.com/document/d/1bctTr14CrxzjHUIRAkT8jB46Jomr9aB2JQ9hDCh3cJg 
) includes things like variable amounts of random data and alternate 
text encodings - stuff that will almost certainly never end up in 
libuuid.  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.

I think it's pretty clear all around though that calling this new thing 
a UUID is just confusing, so yeah I'll think of some other name ideas.