From: Michael Richardson <mcr@sandelman.ca>
To: "Theodore Ts'o" <tytso@mit.edu>,
Chris Hofstaedtler <zeha@debian.org>,
util-linux@vger.kernel.org, Karel Zak <kzak@redhat.com>
Subject: Re: uuid and RFC4122
Date: Wed, 10 May 2023 14:33:43 -0400 [thread overview]
Message-ID: <5866.1683743623@localhost> (raw)
In-Reply-To: <23699.1676924882@localhost>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Hello again!
Michael Richardson <mcr@sandelman.ca> wrote:
> Hi, thanks for your work on debian packages. I'm contacting you
> wearing my IETF uuidrev WG co-chair on.
> The https://datatracker.ietf.org/wg/uuidrev/documents/ WG was chartered
> to update RFC4122 last summer, and we expect to start a WGLC on
> RFC4122bis in the next few weeks. This is just a heads up for now.
We have started the WGLC today.
It goes until June 9th. The document is still open for comments,
particularly of an editorial nature.
Did something confuse you? our fault, let us know.
We included a way to do SHA-2 based uuids into the v8 namespace based uuids,
which we think is future proof, and won't burn version numbers the way that
MD5 and SHA1 derived uuids did.
You may find this diff to be useful:
https://author-tools.ietf.org/iddiff?url1=draft-ietf-uuidrev-rfc4122bis-01&url2=draft-ietf-uuidrev-rfc4122bis-03&difftype=--html
Your comments to uuidrev@ietf.org, or to https://github.com/ietf-wg-uuidrev/rfc4122bis/issues
(or even send a PR)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2023-05-10 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14266.1676658860@localhost>
2023-02-19 17:01 ` uuid and RFC4122 Chris Hofstaedtler
2023-02-20 1:39 ` Theodore Ts'o
2023-02-20 12:26 ` Karel Zak
2023-02-20 20:28 ` Michael Richardson
2023-05-10 18:33 ` Michael Richardson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5866.1683743623@localhost \
--to=mcr@sandelman.ca \
--cc=kzak@redhat.com \
--cc=tytso@mit.edu \
--cc=util-linux@vger.kernel.org \
--cc=zeha@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.