Index: ossp-pkg/uuid/uuid.pod
RCS File: /v/ossp/cvs/ossp-pkg/uuid/Attic/uuid.pod,v
rcsdiff -q -kk '-r1.26' '-r1.27' -u '/v/ossp/cvs/ossp-pkg/uuid/Attic/uuid.pod,v' 2>/dev/null
--- uuid.pod	2005/08/30 20:34:35	1.26
+++ uuid.pod	2005/08/31 07:28:00	1.27
@@ -58,9 +58,9 @@
 
 =head2 UUID Binary Representation
 
-According to the DCE 1.1 and ISO/IEC 11578:1996 standards, a DCE 1.1
-variant UUID is a 128 bit number defined out of 7 fields, each field a
-multiple of an octet in size and stored in network byte order:
+According to the DCE 1.1, ISO/IEC 11578:1996 and RFC 4122 standards, a
+DCE 1.1 variant UUID is a 128 bit number defined out of 7 fields, each
+field a multiple of an octet in size and stored in network byte order:
 
   0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -82,12 +82,12 @@
 
 =head2 UUID ASCII String Representation
 
-According to the DCE 1.1 and ISO/IEC 11578:1996 standards, a DCE
-1.1 variant UUID is represented as an ASCII string consisting
-of 8 hexadecimal digits followed by a hyphen, then three groups
-of 4 hexadecimal digits each followed by a hyphen, then 12
-hexadecimal digits. Formally, the string representation is defined by
-the following grammar:
+According to the DCE 1.1, ISO/IEC 11578:1996 and RFC 4122 standards,
+a DCE 1.1 variant UUID is represented as an ASCII string consisting
+of 8 hexadecimal digits followed by a hyphen, then three groups of
+4 hexadecimal digits each followed by a hyphen, then 12 hexadecimal
+digits. Formally, the string representation is defined by the following
+grammar:
 
  uuid                   = <time_low> "-" <time_mid> "-"
                           <time_high_and_version> "-"