uuid6-ietf-draft

As someone who maintains a UUID library, this is definitely something that has been thought about, especially in the UUIDv6-v8 updates. But it was moved to be considered later as an extension after v6-v8 get approved fully. But all these were talked about and considered before it was punted to a later time. https://github.com/uuid6/uuid6-ietf-draft/issues/27 https://github.com/uuid6/new-uuid-encoding-techniques-ietf-d... https://github.com/uuid6/new-uuid-encoding-techniques-ietf-d... https://github.com/uuid6/new-uuid-encoding-techniques-ietf-d... But there is always TypeID in the meantime which uses UUIDv7 under the hood: https://github.com/jetify-com/typeid Either way, I am in favor of prefixing and using alternative encodings, but it will need some time to figure out the best route. In the mean time, there are so many alternatives. Type

Brad Peabody did the original -00 draft, which was discussed as an FYI at an IEFT meeting in March 2020. See [1], around 50 lines from the bottom. Kyzer Davis has since submitted two further revisions -01 and -02 in April and October 2021. See history in [2]. The current -02 draft is due to expire in April 2022. Presumably Kyzer Davis will try to get it discussed before then. The GitHub repo tracking these drafts is https://github.com/uuid6/uuid6-ietf-draft/. [1] https://datatracker.ietf.org/meeting/107/materials/minutes-1... [2] https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-...

At the moment anyway, that XML link won't render per an XML parsing error. For anyone who wants a quick look at what these XML docs look like here's one for UUID6 [0]. [0] https://github.com/uuid6/uuid6-ietf-draft/blob/master/draft-...

The author seems to be developing the draft on GitHub and there's a few edits since the v01 version linked here https://github.com/uuid6/uuid6-ietf-draft