Skip to content
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.

Draft 04: Define how to handle New UUID < Old UUD #105

Closed
2 of 8 tasks
kyzer-davis opened this issue Apr 18, 2022 · 0 comments · Fixed by #106
Closed
2 of 8 tasks

Draft 04: Define how to handle New UUID < Old UUD #105

kyzer-davis opened this issue Apr 18, 2022 · 0 comments · Fixed by #106
Assignees

Comments

@kyzer-davis
Copy link
Contributor

Change Proposal Template

Source (Select one.)

  • IETF Published Draft
  • 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)
  • New Text for additional context
  • Underlying XML Format Update
  • ASCII diagram updates (artwork, code samples, etc.)

Draft Number, Full Section, Name

Draft 04, Section Counters

Current Text:

n/a

Proposed Text:

To handle this scenario, the general guidance is that application MAY reuse the previous timestamp and increment the previous counter method.

Other Supporting information below:

From #60

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

Successfully merging a pull request may close this issue.

1 participant