[core] UUID Rev WG is chartering

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 17 August 2022 12:06 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1001C157901; Wed, 17 Aug 2022 05:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jVLkmn8didx2; Wed, 17 Aug 2022 05:06:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80A3FC14792F; Wed, 17 Aug 2022 05:06:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3D8CB189B9; Wed, 17 Aug 2022 08:25:45 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id f-hI8Gbbfvy1; Wed, 17 Aug 2022 08:25:43 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 56C19189C7; Wed, 17 Aug 2022 08:25:42 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1660739142; bh=5F+I45d2n+JNf79A+EIGg9d8CuNjt18uFQjFPsnf23E=; h=From:To:cc:Reply-To:Subject:Date:From; b=Mcb8LP0vzBaKnx2OxtvP2Mm1rwKYgh0BtO0sE/xpSvJBwYrvVqAcRp+65Hk7v214X TbEU1ghhJVlDw+C423063LbldXuCNjbhFNxUO6g/w4EE9rQXawZbKqPCCuBkuzNazU SfiA7el5ghB1Dl58SLxw6Fa3BB6pMXw1XR0a7nQVk8pYZQSirtz+zVE3djEEOvhPUz Bu078EAsA9tzlRIqzWdM5554wpSrtEIWx3g2mNAT8wFZUKWBZ8ziBePclFUOjUCMik kTVEVL05jn5N6+XO7NPe5r4qj47LQR1JIPxglgA54cYieFhNqBYHtvQPkdZdFeRdq4 94ZcqYXMaI5Pg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 428D3334; Wed, 17 Aug 2022 08:06:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: core@ietf.org, suit@ietf.org, dispatch@ietf.org, iotops@ietf.org
cc: uuidrev@ietf.org
Reply-To: uuidrev@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 17 Aug 2022 08:06:06 -0400
Message-ID: <22434.1660737966@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/HMJjXV2RtG7ER7kK4Jl4dZeCFb4>
Subject: [core] UUID Rev WG is chartering
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2022 12:06:19 -0000

Hi, in case you didn't follow DISPATCH, or haven't unpacked from IETF114 yet,
UUIDREV is in the chartering process.  I picked a few splatters of
places were there may be interested parties.  I'm sure that I missed a few,
so please forward if you think of them.

The ML is up and some links:

https://datatracker.ietf.org/wg/uuidrev/about/
https://mailarchive.ietf.org/arch/browse/uuidrev/

Jim Fenton and I are co-chairs, and we are meeting today to discuss virtual
interim dates, processes and the like.  My preference is to have a regular
(monthly) virtual interims so that we can reach a higher velocity.

I think the IESG could vote on the charter as soon as next week.
If you are interested in being WG secretary or being a document shepherd,
please let the chairs know.

Knowing what time zones are involved would be VERY good.


that proposed Charter again:

Since the publication of RFC 4122 in 2005, a number of additional versions
of universally unique IDs (UUIDs) have been proposed. A number of errata
have also been verified against the original specification, motivating
a full revision of the UUID specification with the additional versions added.

This working group will produce a standard-track RFC4122bis specification
based on limited review of RFC4122 that will include resolution of verified or
held errata and incorporation of the following additional UUID versions,
using draft-peabody-dispatch-new-uuid-format as a guide:

- Field-compatible version of UUIDv1 optimized for improved database locality
- Time-ordered UUID based on Unix epoch timestamp
- UUID version for vendor-specific use cases

Other aspects of UUIDs, such as alternative representations and UUIDs that
are other than 128 bits in length, will also be considered and the working
group may produce specifications on those topics.  They will not be
considered, however, prior to completion of RFC4122bis, and such milestones
will be negotiated with the responsible AD prior to work commencing.

Milestones:

  Mar 2023 - Submit RFC4122bis to the IESG for publication as Proposed
  Standard



--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide