Re: [Uuidrev] Last (hopefuly) comments on rfc4122bis

["Kyzer Davis (kydavis)" <[e-mail]>]

Thanks Murray,

 

I have these 3 items on the tracker. 
I will iterate quickly and get this re-uploaded.

 

Thanks,

 

From: Murray S. Kucherawy <[e-mail]> 
Sent: Monday, October 23, 2023 12:33 PM
To: Kyzer Davis (kydavis) <[e-mail]>
Cc: [e-mail]
Subject: Re: [Uuidrev] Last (hopefuly) comments on rfc4122bis

 

On Mon, Oct 23, 2023 at 7:20 AM Kyzer Davis (kydavis) <[e-mail] <mailto:[e-mail]> > wrote:

Thanks Murray,

 

Let me comment on a few of these I can sus out what changes are needed (if any).

 

> What are the maxima for ID and Hex ID?  Are they always the same?  If so, do we need both?

 

I had originally included 0 through 15 (0x0 through 0xF) but I was lead to remove the “Reserved for future definition” entries.

This table is a delta of Table 2 in this doc which does list the full list of versions available.

As for having both: I can drop Hex column, it is a bit superfluous.

 

I think the registry creation needs to say explicitly that there's a range of valid values.  I wouldn't expect IANA to read and understand the entire document.

 

 > Are any subtypes other than "version" possible?

>Are any variants other than "OSF DCE / IETF" possible?

 

Yes, technically speaking there are two non-IETF variants each with own subtyping mechanism (“Family” and whatever Microsoft may have in use.)
There is a fourth, unused, variant that could at some point in the future be claimed by some other standards body and feature a subtyping mechanism independent of the other three.

 

I included the “subtype” > “Version” and “Variant Name” columns as a method to promote some variant agnostic extendibility of this registry. Thus, at some point the page could potentially be updated to include “all UUID subtypes from other variants” one place.

 

However, I recognize that for the purpose of this document I can only register what we have defined in this spec so I scoped the actual registration to only the OSF DCE / IETF variant and subtype. 

 

If I need to provide some text around these last few paragraphs I can do so. 

 

If the column is free-form, it should say that.  If there's a specific set of valid values, they need to be enumerated and defined.

 

 > The bullets at the end of this section don't read clearly.  It might be enough to say "On systems ..." for each of them.

Sure, that is an easy enough change. If I must modify anything for the aforementioned topics, I can sneak this in else I am not sure a whole draft-14 just for that small change is warranted.

 

I'd rather send this with that clarification, since these other things need adjustment anyway.

 

-MSK