Fwd: [dispatch] UUID Rev WG is chartering

Ira McDonald via ipp <[email protected]> Wed, 17 Aug 2022 11:17:43 -0400
Newsgroups	gmane.ietf.ipp
Message-ID	<CAN40gSumv3gjFeRd3cHgy1VteuJ+6JboK1HcCFCpNsB2YW8M5Q@mail.gmail.com>
HEADS UP - new UUID formats and clarifications in RFC 4122bis

---------- Forwarded message ---------
From: Michael Richardson <[email protected]>
Date: Wed, Aug 17, 2022 at 8:06 AM
Subject: [dispatch] UUID Rev WG is chartering
To: <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>
Cc: <[email protected]>



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 <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




_______________________________________________
dispatch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dispatch

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc (text/plain, 525 B)