info: https://datatracker.ietf.org/wg/uuidrev/meetings/
Meetecho:
https://meetings.conf.meetecho.com/interim/?short=b85d9b68-3e38-43dc-83ee-1b58f9e920ec
Notes: https://notes.ietf.org/notes-ietf-interim-2023-uuidrev-04-uuidrev
note that chat is now Zulip:
https://zulip.ietf.org/login/#narrow/stream/uuidrev
but is accessible via meetecho interface.
Michael introduced the group to the use of tools.
https://www.ietf.org/about/note-well/
BCP 54 / RFC 7154
1. Treat colleagues with respect
2. Speak slowly and limit the use of slang
3. Dispute ideas by using reasoned argument
4. Use best engineering judgment
5. Find the best solution for the whole Internet
6. Contribute to the ongoing work of the group and the IETF
graph LR
classDef current fill:orange
classDef you-are-here fill:green
WG-Adopt --editing--> WGLC
WGLC --consensus--> AD-Review
AD-Review --> IETF-LC
IETF-LC --> IANA-Review
IETF-LC --> IESG-Review
IANA-Review --> IESG-Review
IESG-Review --> RFC-Editor
RFC-Editor((RFC-Editor)) --> RFC
you-are-here --> IESG-Review
class you-are-here you-are-here
class IESG-Review lastIETF
class RFC-Editor current
{: .language-mermaid}
https://github.com/ietf-wg-uuidrev/rfc4122bis/issues/144
Will not retain this registry.
We will retain this registry with Specification Required.
This has just NIL/MAX and will be removed.
Included for completeness, and will be Standards Action policy.
things back to the WG mailing list: IETF process oriented issues!
** should the WG reset back to WGLC?
** all decisions made "today" need to come back to the ML, period.
**
* ACTION: NOT going to reset to WGLC unless WG consensus is that we
need V9.