IETF Logo Mail Archive

Re: UUID version 6 proposal, initial feedback

"Salz, Rich" <rsalz@akamai.com> Sat, 01 February 2020 02:41 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 4D861120047 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2020 18:41:17 -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 AQ8L_lIq-R8Q for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2020 18:41:16 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 19A97120024 for <ietf@ietf.org>; Fri, 31 Jan 2020 18:41:16 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 0112dnHe014045; Sat, 1 Feb 2020 02:41:14 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=HJzvlWKeYo0gXX/fBx4zCcfe8hemd0ZOzEvTQwgy1Ns=; b=C/cKTQ/1R4qVpdbtDznpI9mXBiuQFV/b6f4HqQ5zUOY5TOzhV1CV7ug3gK9KI32ebdpR EZOf2+diHM6lb4NR0/aincbPem3HsLQrhE1wepBvMepiPBDl8iFp148LLwGntlpYSks0 EU8zQzD0i4doynyaA49bM9uB4QC7E2nH+fXYCrPVZzP/fzkVHU4mhIARppPlEFNib2jS iVwcoh/pTDqNxSBwAOP9NXk8o5+KRaSf+uO653XyDQ7eKiXB7jHtW9AdUp8ceY7PZ/jY jo+LI+adU9aZ1a8Zx1aHP4yMYe/3m5nCR1qa9KNtUDNbgHuYo6elyYDuiLjDcM6j6wbZ Jg==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2xuxpg8r0t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 01 Feb 2020 02:41:14 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 0112WdhG026341; Fri, 31 Jan 2020 18:41:13 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint5.akamai.com with ESMTP id 2xrmhc8g9a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 31 Jan 2020 18:41:13 -0800
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 31 Jan 2020 21:41:12 -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 21:41:12 -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: AQHV2Hhgst2kZLm7HUCciPkYEwPu1agFTnYAgABZ7QD///jNAA==
Date: Sat, 01 Feb 2020 02:41:12 +0000
Message-ID: <E49706DE-5A3A-4403-9A0B-F9F4804CFEA1@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>
In-Reply-To: <b4b73e11-7e21-03ae-0ebf-badcc2bf9d7e@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.251]
Content-Type: multipart/alternative; boundary="_000_E49706DE5A3A44039A0BF9F4804CFEA1akamaicom_"
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=928 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2002010013
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 clxscore=1015 lowpriorityscore=0 mlxlogscore=900 spamscore=0 phishscore=0 mlxscore=0 bulkscore=0 impostorscore=0 malwarescore=0 priorityscore=1501 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1911200001 definitions=main-2002010014
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EIwggL3iTXYRY9Ot3NHXpwAC89s>
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 02:41:17 -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.

> some applications can just read from /dev/urandom and be done with it.

That is fraught with danger, not going to get into it on this general public list.

v2.23.0 | Report a Bug | By Email