Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WNM Identifiers | UUID RFC 4122 superseeded by RFC 9562 #136

Open
unep-gwdc opened this issue Aug 28, 2024 · 1 comment
Open

WNM Identifiers | UUID RFC 4122 superseeded by RFC 9562 #136

unep-gwdc opened this issue Aug 28, 2024 · 1 comment

Comments

@unep-gwdc
Copy link

The WMN specification requires message identifiers to be UUIDs conforming to RFC 4122 (section 1.4, https://github.com/wmo-im/wis2-notification-message/blob/main/standard/sections/clause_7_normative_text.adoc) . This RFC has been superseeded by RFC 9562 recently including new UUID variants such as time-ordered UUIDv7.

Changing the requirement to RFC 9562 would allow data providers to use these new UUID versions making the specification more future proof but other introduced UUIDs like Nill UUID and Max UUID should probably excluded to ensure uniqueness.

@josusky
Copy link
Contributor

josusky commented Oct 25, 2024

As far as I see, the requirement is:

The id property SHALL be a Universally Unique Identifier (UUID).

It is true that the clause 1.4 Identifier then mentions the RFC 4122. But that can be relaxed. We (the TT-WISMD) team do not have any special preference for this type of UUID or other type, as long as it is unique. So you may even use Nill UUID (00000000-0000-0000-0000-000000000000) as long as you can guarantee that no one is ever going to use it again :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants