Are the UUID's generated with nRFgo valid?

[Marcel Mulder]

Hi,

I just took a look to nRFgo to see how it generates vendor specific UUID's. It looks if they are generated completely random including the version number. According to RFC4122 the UUID string had the format of:

xxxxxxxx-xxxx-Vxxx-xxxx-xxxxxxxxxxxx

where V is the version number of the UUID. For random generated UUID this should be 4. If i look to the generated base uuid's in nRFgo than the V part is also random. I think you end up with an invalid UUID or am I wrong?

[David Edwin]

You are correct, the UUID generated does not appear to be a Version 4 UUID. However this does not mean that the number generated is incorrect , it however does not conform to the Version 4 UUID convention. You can edit the number created to match the Version 4 UUID. i.e. using the nRGgo studio as a random number generator.

[David Edwin]

I must clarify. The impact of the a fully random 128bit number used as a UUID in the BTLE world is not a major issue simply because it is used only for vendor specific UUIDs and these are usually used in systems where the vendor controls both ends of the link that looks at this UUID. At this point I do not see any part of the BTLE UUID ecosystem that discriminates based on type of UUID, thereby reducing the impact of this issue. Let me know if there is a specific impact that you see. [Edited response to clarify]