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.

[Marcel Mulder]

I can only agree that the change of generating a random 128-bit UUID in BTLE world causing issues is virtually zero. But,... There is a specification. The reason for creating a specification is that we can talk the same language in BTLE world. Nordic complies to the BTLE specification with its softdevice because Nordic used that specification and have been qualified. Why make an exception for generating UUID's? I don't see no reason for not complying to standards.