Draft 05: MUST veribage in Reliability of 6.1

[kyzer-davis]

Change Proposal Template

Source (Select one.)

• [x] IETF Published Draft
• [ ] 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 05, Section 6.1.  Timestamp Granularity

Current Text:

   Reliability:
      Implementations SHOULD use the current timestamp from a reliable
      source to provide values that are time-ordered and continually
      increasing.  Care SHOULD be taken to ensure that timestamp changes
      from the environment or operating system are handled in a way that
      is consistent with implementation requirements.  For example, if
      it is possible for the system clock to move backward due to either
      manual adjustment or corrections from a time synchronization
      protocol, implementations must decide how to handle such cases.
      (See Altering, Fuzzing, or Smearing bullet below.)

Proposed Text:

   Reliability:
[..]
      is consistent with implementation requirements.  For example, if
      it is possible for the system clock to move backward due to either
      manual adjustment or corrections from a time synchronization
      protocol, implementations need to determine how to handle such cases.
      (See Altering, Fuzzing, or Smearing bullet below.)

---

Other Supporting information below:

Source: