Are the UUID's generated with nRFgo valid?

RE: Are the UUID's generated with nRFgo valid?

David Edwin — Wed, 21 Jan 2015 14:24:10 GMT

We will have a fix the issue in the next release of the nRFgo studio. Thanks for the input. This has been acknowledged and fixed and will be part of the next release of nRFgo Studio

RE: Are the UUID's generated with nRFgo valid?

Marcel Mulder — Tue, 13 Jan 2015 15:33:57 GMT

Your are absolutely right that this is up to the user and has nothing to do with the softdevice. I was not suggesting otherwise. But if you provide tools, than those tools should behave correct in my opinion. Thank you for making an effort to make things better :-)

RE: Are the UUID's generated with nRFgo valid?

David Edwin — Tue, 13 Jan 2015 15:28:16 GMT

Remember vendor specific UUIDs are generated by the user and not by the softdevice, the nRFgo studio is an optional tool to do so and there are many other ways the user can use to generate UUIDs but this is really in user space. In any case I will request a fix in nRFgo studio.

RE: Are the UUID's generated with nRFgo valid?

Marcel Mulder — Tue, 13 Jan 2015 15:22:14 GMT

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.

RE: Are the UUID's generated with nRFgo valid?

David Edwin — Tue, 13 Jan 2015 15:05:16 GMT

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]

RE: Are the UUID's generated with nRFgo valid?

Marcel Mulder — Tue, 13 Jan 2015 13:55:36 GMT

The UUID must comply to ITU-T Rec. X.667 | ISO/IEC 9834-8 (technical equivalent to RFC4122) according to Bluetooth specification. Therefore I think it is incorrect to assume that the UUID generated by nRFgo are correct.

RE: Are the UUID's generated with nRFgo valid?

David Edwin — Tue, 13 Jan 2015 13:34:44 GMT

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.