uuid6 / uuid6-ietf-draft

Next Generation UUID Formats

https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-uuid-format/

187 stars 11 forks source link

Draft 03: Further Clarify Version to Variant Mappings #66

Closed kyzer-davis closed 2 years ago

kyzer-davis commented 2 years ago

Change Proposal Template

Source (Select one.)

[ ] IETF Published Draft
[x] Work in Progress Draft

Change Reason (Select all that apply.)

[ ] Typos and grammatical issues
[ ] Bad Reference
[ ] IETF Verbiage modification (MAY, MUST, SHOULD, SHOULD NOT, etc)
[x] New Text for additional context
[x] Underlying XML Format Update
[ ] ASCII diagram updates (artwork, code samples, etc.)

Draft Number, Full Section, Name

Draft 02, Section 4.1. Variant and Version Fields

Other Supporting information below:

My Suggested edits that will make this a bit more clear:

Add the Lower case epsilon (ε) nomenclature to the Draft 03 Variant and Version Fields if it helps drive the point home.
- Anywhere I reference UUIDv7/UUIDv8/Version 7/Version 8 change to UUIDv7ε/UUIDv8ε/Version 7ε/Version 8ε
I can also split Table 2 UUID versions defined by this specification into RFC 4122 Updated version reservations and Draft 03 Version reservations.
- Table A: Define RFC 4122 variant 10xx/89AB + Version 6 then fill out a table up to v15 with "Reserved for future definition"
- Table B: Define Variant 1110/E + Version 7ε and 8ε filling out the rest as "Reserved for future definition"

Changes from https://github.com/uuid6/uuid6-ietf-draft/issues/26#issuecomment-1055770942

kyzer-davis commented 2 years ago

I could not get xml2rfc tools to accept converting the lower case epsilon character from XML encoding to the .txt and .html. As such I have simply went with an uppercase E in place of ε for this change.