Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft 02 updates #14

Merged
merged 1 commit into from Jul 13, 2021
Merged

Draft 02 updates #14

merged 1 commit into from Jul 13, 2021

Conversation

kyzer-davis
Copy link
Contributor

  1. Added Changelog
  2. Fixed misc. grammatical errors
  3. Fixed section numbering issue
  4. Fixed some UUIDvX reference issues
  5. Changed all instances of "motonic" to "monotonic"
  6. Changed all instances of "#-bit" to "# bit"
  7. Revised UUIDv6 Clock Sequence Usage from random start to monotonic increment starting at 0

Thanks to Ville Skyttä (ville.skytta@iki.fi) for items number 2, 3, 4, 6 above submitted via IETF mailer.
Thanks to László GÖRÖG for confirming changes in item number 7 (source).

Github Housekeeping:

  • Moved 01 drafts to old-drafts folder
  • kept draft-peabody-dispatch-new-uuid-format-01.xml for easy diff checks
  • New 02 .xml, .txt, .html created based on changes.

@nerg4l
Copy link

nerg4l commented Jul 12, 2021

In uuid6/prototypes#2 (comment) you mentioned it would be an option to reduce the number of bits for subsec in case of v7 with nanosecond precision to 30 bits from 38 bits. Can I ask what made you decide to not include that change?

@kyzer-davis
Copy link
Contributor Author

kyzer-davis commented Jul 12, 2021

@nerg4l, I definitely plan to iron that item out with @bradleypeabody before a draft 02 resubmission to the IETF.

Once we have revised the text with better verbiage and pseudocode; I will open another PR just for the changes to 4.4.4.1. UUIDv7 Encoding

@bradleypeabody
Copy link
Contributor

Thanks @kyzer-davis - looks good to me! Merging.

I'm also going to try to organize getting a page put together which shows these three different versions visually and breaks out the different fields into separate readable values, showing the encoding of each. I think it would be an excellent complement to the draft and make the whole thing much more clear and easy to wrap one's wits around when writing or maintaining an implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants