Future better UUID binary-to-text encoding #769

Open
opened 2024-09-15 13:27:50 -05:00 by sergeyprokhorenko · 3 comments
sergeyprokhorenko commented 2024-09-15 13:27:50 -05:00 (Migrated from github.com)

@KodrAus

The authors of RFC 9562 have resumed discussion about a better UUID binary-to-text encoding

@KodrAus The authors of [RFC 9562](https://datatracker.ietf.org/doc/html/rfc9562) [have resumed discussion](https://github.com/uuid6/new-uuid-encoding-techniques-ietf-draft) about a better UUID binary-to-text encoding
sergeyprokhorenko commented 2025-03-06 14:18:21 -06:00 (Migrated from github.com)
[Proposal for OOXML Extension to Support Interactive UUID Widgets](https://github.com/OfficeDev/open-xml-docs/issues/333)
KodrAus commented 2025-05-14 16:11:59 -05:00 (Migrated from github.com)

In uuid, we can support more encodings through additional types in the fmt module. Ideally anything we add there should have a unique length, so we can tell what encoding we're looking at without having to attempt to parse it first.

In `uuid`, we can support more encodings through additional types in the `fmt` module. Ideally anything we add there should have a unique length, so we can tell what encoding we're looking at without having to attempt to parse it first.
sergeyprokhorenko commented 2025-05-15 02:56:30 -05:00 (Migrated from github.com)

The most popular encoding for UUID is Crockford's Base32 (5 bits per character). It has become a de facto standard. It is also used for ULID.

UUID is encoded in a 26-character string.

See an example

The most popular encoding for UUID is [Crockford's Base32](https://www.crockford.com/base32.html) (5 bits per character). It has become a de facto standard. [It is also used for ULID](https://github.com/ulid/spec?tab=readme-ov-file#encoding). UUID is encoded in a [26-character string](https://github.com/ulid/spec?tab=readme-ov-file#overflow-errors-when-parsing-base32-strings). See an [example](https://docs.rs/ulid/latest/src/ulid/lib.rs.html#228-243)
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-uuid-rs/uuid#769
No description provided.