HEADS UP - new UUID formats and clarifications in RFC 4122bis
---------- Forwarded message ---------
From: Michael Richardson <mcr+ietf at sandelman.ca>
Date: Wed, Aug 17, 2022 at 8:06 AM
Subject: [dispatch] UUID Rev WG is chartering
To: <core at ietf.org>, <suit at ietf.org>, <dispatch at ietf.org>, <iotops at ietf.org>
Cc: <uuidrev at ietf.org>
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 at sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
_______________________________________________
dispatch mailing list
dispatch at ietf.orghttps://www.ietf.org/mailman/listinfo/dispatch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20220817/5f41e5cf/attachment.html>
-------------- next part --------------
-----BEGIN PGP SIGNATURE-----
iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmL82a0WHG1jcitpZXRm
QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZUoEB/4gMCG2XceFo+QyAKk5VdxPPwmD
MeE+ilOHapYWGsLBtoFL/bS1CBr52JXQ9NVJklwPsDaXsFuIZezDLLrK8eCai+j9
PxiJyJmh5dgz5bf//W5UluNyksSQJNhVHkR56z4PJ0IO9Gg5PVA061GEnzBWSdlM
Tu965IjhariQhrFYnr6iOwf3MSAEQ+RTje9h+r5rDmAlL0CxN4VnQt6OL5snfsPy
xfxbw8n2M/WxHwAocGETcERsGOH5DaVlISmxnpXJx2NLU3Q4FAZPAfyyLWy6fOR4
WBe66V06/CfkTgxRL372rDTYmmvpYX8M2Bx8QieMIh8mWWXGZ2iBEouuidX9
=Cjaq
-----END PGP SIGNATURE-----