3 ms·
I was a bit confused because this document is a draft and I couldn't find any mention of "approval." But here's a link to the published RFC that obsoletes the o
by stanleydrew 2y ago
I was a bit confused because this document is a draft and I couldn't find any mention of "approval." But here's a link to the published RFC that obsoletes the original UUID RFC 4122:
https://www.rfc-editor.org/rfc/rfc9562 https://www.rfc-editor.org/rfc/rfc9562
- falcor84 2y agoThanks, that's what I was looking for. @dang, could you please update the link to this?
- cesarb 2y agoThe metadata about the linked document (https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-01.html https://www.ietf.org/archive/id/draft-peabody-dispatch-new-u...) is at https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-uuid-format/01/ https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-... which shows that this is indeed a very old draft. The linked document is version 01 of the draft, that draft went up to version 04 before being replaced by draft-ietf-uuidrev-rfc4122bis (https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/00/ https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122b...), which then went up to version 14 before finally being approved as RFC 9562.