From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Theodore Ts'o" <tytso@mit.edu>,
Chris Hofstaedtler <zeha@debian.org>,
util-linux@vger.kernel.org
Subject: Re: uuid and RFC4122
Date: Mon, 20 Feb 2023 15:28:02 -0500 [thread overview]
Message-ID: <23699.1676924882@localhost> (raw)
In-Reply-To: <Y/LPN7pf6x75Xm9H@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Theodore Ts'o <tytso@mit.edu> wrote:
> I originally wrote the uuid implementation in util-linux. Originally,
> it was first in e2fsprogs, and then later the library was transferred
> to util-linux at least for most Linux distributions. Technically
> speaking, however, libuuid is still shipped in the e2fsprogs sourecs
> and that's the version which is used by Android and some non-Linux
> OS's including NetBSD and Darwin (MacOS may have forked the library,
> though, so if I shipped updates in e2fsprogs how quickly it would get
> picked up by Apple.) Libuuid is mostly in maintenance mode, actually;
> the sort of changes that have landed recently have been to support the
> getrandom(2) system call.
Good to hear, thanks for the reply.
> I'm not sure what the context is for this e-mail thread, or what
> you're asking for in terms of an LGTM?
Read the document, or just the diff:
https://author-tools.ietf.org/diff?doc_1=rfc4122&doc_2=draft-ietf-uuidrev-rfc4122bis-02
> Were you looking for comments
> on draft-ietf-uuidrev-rfc4122bis?
Email uuidrev@ietf.org ... we are especially interested in whether we have
left out/obsoleted some use case that you presently have, whether the new
version types are useful to you.
Do you use or care about MD5 or SHA1 based UUIDs?
We have proposed using namespace based UUIDs for future hash methods.
> Or were you hoping to see if folks
> might be interested in implementing the new UUID versions in
> draft-ietf-uuidrev-rfc4122bis so the libuuid in Linux might support
> those new variants?
No, I think that if you had a new use case/need, you'd have implemented
something already :-)
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
next prev parent reply other threads:[~2023-02-20 20:35 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 [this message]
2023-05-10 18:33 ` Michael Richardson
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=23699.1676924882@localhost \
--to=mcr+ietf@sandelman.ca \
--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.