RFC-4122 Obsoleted by RFC-9562

[akefirad]

Hi there,
The readme says this library is based on 4122 which is obsoleted by 9562. I compared the two RFCs and found no significant diff between the two. I checked briefly and only parts related to v7. Do you have any comments regarding this:

1. Does it matter which RFC we're talking about in this context? (At least for V7)
2. Any plan to change the underlying RFC to 9562?
3. Is it safe to use the current version of the library which is based on 4122?

Thanks.

[cowtowncoder]

I have not heard of anything suggesting implementation is incompatible with the later/-st spec, so I think you interpretation is correct.

I would be open to accepting a PR that simply updates README.md and other references to latest RFC.

[cowtowncoder]

But no, I do not know if there might be relevant changes wrt v7.

Comments like this, however:

There is an ITU-T Recommendation and an ISO/IEC Standard [[X667](https://datatracker.ietf.org/doc/html/rfc9562#X667)] that are derived from [[RFC4122](https://datatracker.ietf.org/doc/html/rfc4122)]. Both sets of specifications have been aligned and are fully technically compatible. Nothing in this document should be construed to override the DCE standards that defined UUIDs.

suggest that no actual changes were made to the specification.

I will create a PR for changing references.

[cowtowncoder]

Ok, I should have read question more carefully. This wasn't about minor changes wrt versions 6 and 7 but b/w "original" UUID from 2004 (rfc-4122) and recently formalized update (rfc-9562).

And yes, 9562 is a proper superset of 4122 and fully compatible wrt versions defined in 4122.

Further, as far as I know, JUG supports versions 6 and 7 (but not v8 since that is "build your own") as specified by RFC 9562, although implemented based on earlier proposed definitions.