items from #83

draft-ietf-uuidrev-rfc4122bis.md

@@ -223,12 +223,29 @@ informative:
     author:
     - org: IANA
     date: 2022-11-18
+  Python:
+    target: https://docs.python.org/3/library/uuid.html
+    title: UUID objects according to RFC
+    author:
+    - org: Python
+    date: 2023-05-23
+  Microsoft:
+    target: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/a66edeb1-52a0-4d64-a93b-2f5c833d7d92
+    title: curly braced GUID string
+    author:
+    - org: Microsoft
+    date: 2023-04-03
+  IBM_NCS:
+    target: https://www.ibm.com/docs/en/aix/7.1?topic=u-uuid-gen-command-ncs
+    title: uuid_gen Command (NCS)
+    author:
+    - org: IBM
+    date: 2023-03-23
 
 --- abstract
 
-This specification defines a Uniform Resource Name namespace for
-UUIDs (Universally Unique IDentifiers), also known as GUIDs (Globally
-Unique IDentifiers).  A UUID is 128 bits long and is intended to guarantee
+This specification defines the UUIDs (Universally Unique IDentifiers) and it's a Uniform Resource Name namespace. UUIDs are also known as GUIDs (Globally Unique IDentifiers).
+A UUID is 128 bits long and is intended to guarantee
 uniqueness across space and time.  UUIDs were originally used in the
 Apollo Network Computing System and later in the Open Software
 Foundation's (OSF) Distributed Computing Environment (DCE), and then
@@ -256,7 +273,7 @@ many cases, become exposed in many non-standard ways.
 This specification attempts to standardize that practice as openly as
 possible and in a way that attempts to benefit the entire Internet.
 The information here is meant to be a concise guide for those wishing
-to implement services using UUIDs, as URNs {{RFC8141}}, or otherwise.
+to implement services using UUIDs, UUIDs in combination with URNs {{RFC8141}}, or otherwise.
 
 There is an ITU-T Recommendation and an ISO/IEC Standard {{X667}} that are
 derived from {{RFC4122}}.  Both sets of
@@ -444,7 +461,8 @@ SHAKE
 UTC
 : Coordinated Universal Time
 
-
+OID
+: Object Identifier
 
 ## Changelog {#changelog}
 {:removeinrfc}
@@ -460,6 +478,10 @@ draft-04
 - Remove Re-randomize Until Monotonic (Method 3) from Monotonicity and Counters #92
 - Fix ambiguous text around UUIDv6 clock sequence #89
 - Move endianness statement from layout to format section #85
+- Further modified abstract to separate URN topic from UUID definition #83
+- Provided three more UUID format examples #83
+- Added text further clarifying version construct is for the variant in this doc #83
+- Provided further clarification for local/global bit vs multicast bit #83
 
 draft-03
 
@@ -610,6 +632,15 @@ urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
 ~~~~
 {: #sampleURNUUID title='Example URN UUID'}
 
+There many other ways to define a UUID format some select methods are detailed below.
+Please note that this is not an exhaustive list and is only provided for informational purposes.
+
+{: spacing="compact"}
+
+- Some UUID implementations, such as those found in {{Python}} and {{Microsoft}}, will output UUID with the string format, including dashes, enclosed in curly braces.
+- {{X667}} provides UUID format definitions for use of UUID with an OID.
+- The legacy {{IBM_NCS}} implementation produces a unique UUID format compatible with Variant 0xx of {{table1}}
+
 ## Variant Field {#variant_field}
 
 The variant field determines the layout of the UUID.  That is, the
@@ -640,7 +671,7 @@ Accordingly, all bit and field layouts avoid the use of these bits.
 The version number is in the most significant 4 bits of octet 6
 (bits 48 through 51 of the UUID).
 
-{{table2}} lists all of the versions for this UUID variant specified in this document.
+{{table2}} lists all of the versions for this UUID variant 10x specified in this document.
 
 | Msb0 | Msb1 | Msb2 | Msb3 | Version | Description                                                                   |
 |    0 |    0 |    0 |    0 |       0 | Unused                                                                        |
@@ -675,6 +706,9 @@ xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx
 ~~~~
 {: title='UUIDv4 Variant Examples'}
 
+It should be noted that the other remaining UUID variants found in {{table1}} leverage different sub-typing/versioning mechanisms.
+The recording and definition of the remaining UUID variant and sub-typing combinations are outside of the scope of this document.
+
 # UUID Layouts {#layout}
 
 To minimize confusion about bit assignments within octets and among differing versions, the UUID record definition is provided as a grouping of fields within bit layout consisting four octets to a row.
@@ -1618,7 +1652,9 @@ cards.
 
 For compatibility with earlier specifications, note that this
 document uses the unicast/multicast bit, instead of the arguably more
-correct local/global bit.
+correct local/global bit because MAC addresses with the local/global bit set or not are both possible in a network.
+This is not the case with the unicast/multicast bit.
+One node cannot have a MAC address that multicasts to multiple nodes.
 
 In addition, items such as the computer's name and the name of the
 operating system, while not strictly speaking random, will help
@@ -1706,7 +1742,7 @@ Further, at this time the authors and working group have concluded that IANA is
 # Security Considerations {#Security}
 
 Implementations SHOULD NOT assume that UUIDs are hard to guess.
-Foe example, they MUST NOT be used
+For example, they MUST NOT be used
 as security capabilities (identifiers whose mere possession grants
 access).  Discovery of predictability in a random number source will
 result in a vulnerability.