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: Correct IETF Verbiage in Fixed-Length Dedicated Counter Rollover Handling #65

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
[x] IETF Verbiage modification (MAY, MUST, SHOULD, SHOULD NOT, etc)
[ ] New Text for additional context
[ ] Underlying XML Format Update
[ ] ASCII diagram updates (artwork, code samples, etc.)

Draft Number, Full Section, Name

Draft 03, Section 5.2. Monotonicity and Counters

Current Text:

The general guidance is that applications should freeze the counter and wait for the timestamp to advance which ensures monotonicity is not broken.

Proposed Text:

The general guidance is that applications SHOULD freeze the counter and wait for the timestamp to advance which ensures monotonicity is not broken.

Other Supporting information below:

should > SHOULD