Draft 04: MUST to SHOULD to reduce "absolute monotonicity" requirements

[kyzer-davis]

Change Proposal Template

Source (Select one.)

• [x] 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 6.2. Monotonicity and Counters

Current Text:

Additionally, care MUST be taken to ensure UUIDs generated in batches are also monotonic. 

Proposed Text:

Additionally, care SHOULD be taken to ensure UUIDs generated in batches are also monotonic. 

---

Other Supporting information below:

Feedback from IETF mailer community.

Reasoning:

• We have a few section sections that define ways to do things if "monotonicity is not an absolute requirement" but this paragraph makes it an absolute requirement. Relaxing to a SHOULD ensures the text lines up with the later sections.
• The MUST here puts a ton of strain on distributed nodes which will have a much harder time with an absolute in monotonicity.