IETF Logo Mail Archive

Re: UUID version 6 proposal, initial feedback

"Salz, Rich" <rsalz@akamai.com> Fri, 31 January 2020 21:45 UTC

Return-Path: <rsalz@akamai.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 2A490120046 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2020 13:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=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=akamai.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 vVrySXM5Es2b for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2020 13:45:20 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 D833D120043 for <ietf@ietf.org>; Fri, 31 Jan 2020 13:45:19 -0800 (PST)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 00VLdNCu013863; Fri, 31 Jan 2020 21:45:17 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=sCiBKrNoo0gJavrSi5kQmgv9IAnBo/pbRvfAMbA8d1M=; b=VqVbWzvCW1i07UFZ6d9iqFBH2hHQypnBLFY4iNakTkvrPuXdQeMFlQP6lDlgEvM0aewx JCeSCJZ4jDdTjtoRol36ReKayaDy80VScNnkSzr7qEVmbIFkAj3ts2+TYpbT2+NNmWeC MYL/HhG+tXypzg7Mn4QmsYnjFJNl0n+NssKU1Vp+2sP/UenQxw3JdHXwjGavqHa8L+EX IPfIrbOanN7BBBX2YgBj35qYcnVs32jVr+NTX9N41p8BahJLoPpBHy7qmuCzySLr5qr7 ITAKwr0Sa7qzSDEoodglXqalOHagG1qZmzesor1LUUfyUCQzeps6F3YgHoI29GpyzFNG Ew==
Received: from prod-mail-ppoint4 (prod-mail-ppoint4.akamai.com [96.6.114.87] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2xuwxbke2f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 31 Jan 2020 21:45:17 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 00VLdpmr020041; Fri, 31 Jan 2020 16:45:16 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint4.akamai.com with ESMTP id 2xrhw1ywpb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 31 Jan 2020 16:45:15 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 31 Jan 2020 16:45:07 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Fri, 31 Jan 2020 16:45:07 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Brad Peabody <bradgareth@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: UUID version 6 proposal, initial feedback
Thread-Topic: UUID version 6 proposal, initial feedback
Thread-Index: AQHV2Hhgst2kZLm7HUCciPkYEwPu1agFTnYA
Date: Fri, 31 Jan 2020 21:45:07 +0000
Message-ID: <6E165220-7D1F-4AD8-B4F3-DDCB8F1DA6E2@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>
In-Reply-To: <c5ba6f5d-7c61-bfdf-63e6-be7d640ee50c@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.112.110]
Content-Type: multipart/alternative; boundary="_000_6E1652207D1F4AD8B4F3DDCB8F1DA6E2akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-01-31_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=978 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2001310174
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-01-31_07:2020-01-31, 2020-01-31 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 suspectscore=0 impostorscore=0 malwarescore=0 adultscore=0 bulkscore=0 spamscore=0 clxscore=1011 phishscore=0 mlxlogscore=933 priorityscore=1501 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1911200001 definitions=main-2001310174
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TrMOF-KRBdkDnHVc0792U65-Z1Q>
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: Fri, 31 Jan 2020 21:45:23 -0000

I don’t understand the purpose of all that mechanism.  UUID’s are supposed to be opaque identifiers; if you intend folks to look inside them, then you should not be using UUID, you should be using something else where the insides are on the outside, as it were.

UUID’s are very old, they were first part of Apollo’s Network Computing Architecture in the 1980’s.  If we were recreating them today, we’d just use a cryptographic nonce.  I suggest that’s what you do as well.

v2.23.0 | Report a Bug | By Email