| Version | 1 |
| Variant | specified in RFC 4122 |
| urn | urn:uuid:597ae2f6-16a6-1027-98f4-d28b5365dc14 |
| Hexdump | 597ae2f616a6102798f4d28b5365dc14 |
| Bytes | YzΓ÷␖ª␐'ÿ⌠╥ïSe▄␔ |
| Clock ID | 6388 |
| Clock ID (hex) | 0x18f4 |
| Timestamp, RFC | 1617-08-26 06:59:41 |
| Timestamp, MS | 1635-11-13 06:59:41 |
| Timestamp, UNIX | 2004-11-12 06:59:41 |
| Raw hex timestamp | 0x2716a6597ae2f6 |
| Raw timestamp | 11002427813323510 |
| Sub-millisecond timestamp | 23510 |
| MAC Address | d28b5365dc14 |
| is_local bit | False |
| is_multicast bit | True |
| MAC Manufacturer | None |
| UUIDv1 | timestamp + clock_id + version (1) + node ID (MAC) |
| MAC Date | None |
Seen in RFC 4530
Counts : rfc4530:1
RFC 4530 LDAP entryUUID June 2006
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in BCP 14
[RFC2119].
2. UUID Schema Elements
2.1. UUID Syntax
A Universally Unique Identifier (UUID) [RFC4122] is a 16-octet (128-
bit) value that identifies an object. The ASN.1 [X.680] type UUID is
defined to represent UUIDs as follows:
UUID ::= OCTET STRING (SIZE(16))
-- constrained to an UUID [RFC4122]
In LDAP, UUID values are encoded using the [ASCII] character string
representation described in [RFC4122]. For example,
"597ae2f6-16a6-1027-98f4-d28b5365dc14".
The following is an LDAP syntax description suitable for publication
in subschema subentries.
( 1.3.6.1.1.16.1 DESC 'UUID' )
2.2. 'uuidMatch' Matching Rule
The 'uuidMatch' matching rule compares an asserted UUID with a stored
UUID for equality. Its semantics are the same as the
'octetStringMatch' [X.520][RFC4517] matching rule. The rule differs
from 'octetStringMatch' in that the assertion value is encoded using
the UUID string representation instead of the normal OCTET STRING
string representation.
The following is an LDAP matching rule description suitable for
publication in subschema subentries.
( 1.3.6.1.1.16.2 NAME 'uuidMatch'
SYNTAX 1.3.6.1.1.16.1 )
2.3. 'uuidOrderingMatch' Matching Rule
The 'uuidOrderingMatch' matching rule compares an asserted UUID with
a stored UUID for ordering. Its semantics are the same as the
'octetStringOrderingMatch' [X.520][RFC4517] matching rule. The rule
differs from 'octetStringOrderingMatch' in that the assertion value
is encoded using the UUID string representation instead of the normal
OCTET STRING string representation.
Zeilenga Standards Track [Page 3]