classification
Title: UUIDv1 is not RFC 4122 compliant
Type: Stage:
Components: Library (Lib) Versions: Python 3.11, Python 3.10, Python 3.9, Python 3.8, Python 3.7, Python 3.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: contact2
Priority: normal Keywords:

Created on 2021-07-13 11:15 by contact2, last changed 2021-07-13 11:15 by contact2.

Messages (1)
msg397392 - (view) Author: László Görög (contact2) Date: 2021-07-13 11:14
Section 4.1.5 of RFC 4122 says the following about Clock Sequence:

   If the clock is set backwards, or might have been set backwards
   (e.g., while the system was powered off), and the UUID generator can
   not be sure that no UUIDs were generated with timestamps larger than
   the value to which the clock was set, then the clock sequence has to
   be changed.  If the previous value of the clock sequence is known, it
   can just be incremented; otherwise it should be set to a random or
   high-quality pseudo-random value.

However, the current implementation increments the timestamp and not the clock sequence. Ref: https://github.com/python/cpython/blob/bb3e0c240bc60fe08d332ff5955d54197f79751c/Lib/uuid.py#L689-L690
History
Date User Action Args
2021-07-13 11:15:00contact2create