[PATCH BlueZ 1/4] doc/mesh-api: Add notion of Device UUID compliance
flat view
STALE2066d
From: Inga Stotland <hidden>
Date: 2021-02-11 22:23:21
Subsystem:
the rest · Maintainer:
Linus Torvalds
Add requirement that the value of Device UUID supplied in CreateNetwork/Join/Import methods should be compliant with RFC 4122. --- doc/mesh-api.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 254ccbd7f..f2c6b9e5c 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt@@ -27,7 +27,8 @@ Methods: The uuid parameter is a 16-byte array that contains Device UUID. This UUID must be unique (at least from the daemon perspective), therefore attempting to call this function using already - registered UUID results in an error. + registered UUID results in an error. The composition of the UUID + octets must be in compliance with RFC 4122. When provisioning finishes, the daemon will call either JoinComplete or JoinFailed method on object implementing
@@ -149,7 +150,8 @@ Methods: The uuid parameter is a 16-byte array that contains Device UUID. This UUID must be unique (at least from the daemon perspective), therefore attempting to call this function using already - registered UUID results in an error. + registered UUID results in an error. The composition of the UUID + octets must be in compliance with RFC 4122. The other information the bluetooth-meshd daemon will preserve about the initial node, is to give it the initial primary
@@ -179,7 +181,8 @@ Methods: The uuid parameter is a 16-byte array that contains Device UUID. This UUID must be unique (at least from the daemon perspective), therefore attempting to call this function using already - registered UUID results in an error. + registered UUID results in an error. The composition of the UUID + octets must be in compliance with RFC 4122. The dev_key parameter is the 16-byte value of the dev key of the imported mesh node.
--
2.26.2