# uuidrev - Revise Universally Unique Identifier Definitions   {#uuidrev---revise-universally-unique-identifier-definitions}

*   Tuesday, 8 November⋅16:30 – 17:30 (UK Time)

### INFO:   {#info}

info: https://datatracker.ietf.org/wg/uuidrev/meetings/

Meetecho:
https://wws.conf.meetecho.com/conference/?group=uuidrev&short=uuidrev&item=1

Notes: https://notes.ietf.org/notes-ietf-115-uuidrev

note that chat is now Zulip:  
 https://zulip.ietf.org/login/#narrow/stream/uuidrev  
but is accessible via meetecho interface.

# AGENDA   {#agenda}

## Hello, logistics, expected schedule of work.   {#hello-logistics-expected-schedule-of-work}

## NoteWell.   {#notewell}

https://www.ietf.org/about/note-well/

## Kyzer on draft-ietf-uuidrev-rfc4122bis-00 issues   {#kyzer-on-draft-ietf-uuidrev-rfc4122bis-00-issues}

    https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/
    [KD] RFC4122 + draft-peabody-dispatch-new-uuid-format -> rfc4122bis
    
    [JF] Question: are the algorithms going in as appendices or are they being removed entirely?
    [KD] Text is reused, nothing is gone, the text is updated
    [JF] Just wanted to make sure that we're not using the algorithms entirely
    [KD] They're not conventional algorithms; they are just unnumbered bulleted items
    
    [MK] Need to Update ABNF RFC reference from 4234 to 5234
    [MK] ABNF hex-octet needs definition
    [MK] Need to carry definitions forward from RFC4122 because that document is dead if we obsolete it
    [MK] Will send email to list with full details
    
    [KD] Action items
    [KD] * Issuing draft updates monthly

BM: Brendan has encountered many missing namespaces when doing SUIT.
When this has happened, he has included the relevant namespace into the
SUIT Manifest document.  
ACTION: Brendan will send this to the list.

KD: missed some notes about RNG issues.

BM: was worried about running out of true random, and this can be used
to create a side channel. ACTION BM. Maybe don't generate a new random
number for each UUID, but rather for each time increment.

KD: Need to allocate namespace template with IANA?  
MR: Do not need to register namespace, IANA already allocated  
ACTION: State that allocation is already completed in IANA
considerations section

JF: ACTION KD: Need to ask list about issue updates

JF: How do we keep UUID in step with ITU/ISO  
MK: We have liasons --- ACTION WG chairs.  
MR: Not certain about copyright issues  
MK: Need to consider paywall issues. IESG need to review

BM: was previously concerned about how to do OID->UUID. (versus UUID
used in an OID).... and there were many ways, including text, binary,
and also CBOR.

JF: Do we elevate to Internet Standard  
MK: New versions added so cannot raise to Internet Standard  
MR: Need to wait at least 2 years after Proposed Standard

MK: 4122 has no BCP14/RFC2119. There are 44 SHOULDs. There is no
guidance under what circumstances you can legitimately not follow the
SHOULD.  
MR: they're probably almost all MUSTs  
MK: If there's no guidance, they're "MAY"  
JF: Every issue in the github tracker was about SHOULD replacing MUST  
MR: ACTION: Ask for review of SHOULDs  
MK: They're not all in "Best Practices"

## AOB/Open Mike   {#aobopen-mike}

MR: Please fill out virtual interim survey!
https://rallly.co/p/M1x0A4QD5ZPD  
MR: Propose that virtual interim can process github issues to iterate
quickly