Merge pull request #112 from ietf-wg-uuidrev/wglc-final

WGLC Final Merge

draft-ietf-uuidrev-rfc4122bis.md

@@ -1,6 +1,6 @@
 ---
 v: 3
-docname: draft-ietf-uuidrev-rfc4122bis-06
+docname: draft-ietf-uuidrev-rfc4122bis-07
 cat: std
 obsoletes: '4122'
 consensus: 'true'
@@ -29,10 +29,6 @@ author:
   name: P. Leach
   email: [email protected]
   org: University of Washington
-- ins: M. Mealling
-  name: M. Mealling
-  email: [email protected]
-  org: VeriSign, Inc.
 
 normative:
   C309:
@@ -472,6 +468,16 @@ OID
 ## Changelog {#changelog}
 {:removeinrfc}
 
+draft-07
+
+{: spacing="compact"}
+
+- Even more grammar tweaks! #109
+- Remove unnecessary "32 bit" in UUIDv7 example #108
+- Change "fixed millisecond" -> "millisecond by default" relating to v7… #110
+- Revert Max UUID Naming #107
+- Author Changes
+
 draft-06
 
 {: spacing="compact"}
@@ -485,7 +491,7 @@ draft-05
 
 {: spacing="compact"}
 
-- Changed Max UUID to Omni UUID to better complement Latin Nil UUID verbiage. #95
+- Changed Max UUID to Max UUID to better complement Latin Nil UUID verbiage. #95
 - Align Method 3 text with the 12 bits limitation #96
 - Make Version/version casing consistent across 5. UUID Layouts #97
 - Cite MS COM GUID as little-endian #95
@@ -531,7 +537,7 @@ draft-02
 {: spacing="compact"}
 
 - Change md5_high in SHA-1 section to sha1_mid #59
-- Describe Nil/Omni UUID in variant table #16
+- Describe Nil/Max UUID in variant table #16
 - Further Clarify that non-descript node IDs are the preferred method in distributed UUID Generation #49
 - Appendix B, consistent naming #55
 - Remove duplicate ABNF from IANA considerations #56
@@ -684,7 +690,7 @@ the letter "x" indicates a "don't-care" value.
 |    0 |    x | x    | Reserved, NCS backward compatibility and includes Nil UUID as per {{niluuid}}. |
 |    1 |    0 | x    | The variant specified in this document.                                        |
 |    1 |    1 | 0    | Reserved, Microsoft Corporation backward compatibility.                        |
-|    1 |    1 | 1    | Reserved for future definition and includes Omni UUID as per {{omniuuid}}.       |
+|    1 |    1 | 1    | Reserved for future definition and includes Max UUID as per {{maxuuid}}.       |
 {: #table1 title='UUID Variants'}
 
 Interoperability, in any form, with variants other than the one
@@ -1191,18 +1197,18 @@ The nil UUID is special form of UUID that is specified to have all
 
 A Nil UUID value can be useful to communicate the absence of any other UUID value in situations that otherwise require or use a 128-bit UUID.  A Nil UUID can express the concept "no such value here". Thus it is reserved for such use as needed for implementation-specific situations.
 
-## Omni UUID {#omniuuid}
+## Max UUID {#maxuuid}
 
-The Omni UUID is special form of UUID that is specified to have all 128 bits
+The Max UUID is special form of UUID that is specified to have all 128 bits
 set to 1. This UUID can be thought of as the inverse of Nil UUID defined
 in {{niluuid}}.
 
 ~~~~
 FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
 ~~~~
-{: title='Omni UUID Format'}
+{: title='Max UUID Format'}
 
-A Omni UUID value can be used as a sentinel value in situations where a 128-bit UUID is required but a concept such as "end of UUID list" needs to be expressed, and is reserved for such use as needed for implementation-specific situations.
+A Max UUID value can be used as a sentinel value in situations where a 128-bit UUID is required but a concept such as "end of UUID list" needs to be expressed, and is reserved for such use as needed for implementation-specific situations.
 
 # UUID Best Practices {#uuid_best_practices}
 
@@ -1800,6 +1806,7 @@ See {{RFC6151}} for MD5 Security Considerations and {{RFC6194}} for SHA-1 securi
 # Acknowledgements {#Acknowledgements}
 
 The authors gratefully acknowledge the contributions of Rich Salz,
+Michael Mealling,
 Ben Campbell,
 Ben Ramsey,
 Fabio Lima,