Re: [PATCH BlueZ 2/2] doc/gatt-api: Add 'X-asynchronous` permissions
flat view
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: 2021-09-29 18:04:37
Hi Dagan, On Wed, Sep 29, 2021 at 10:42 AM Dagan Martinez [off-list ref] wrote:
quoted hunk ↗ jump to hunk
Update docs to reflect the addition of `X-asynchronous` permissions, which allow a GATT server to restrict CCC write permissions via permissions set on its associated characteristic. --- doc/gatt-api.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt index 04789c6d3..2550510ba 100644 --- a/doc/gatt-api.txt +++ b/doc/gatt-api.txt@@ -253,7 +253,13 @@ Properties string UUID [read-only] Defines how the characteristic value can be used. See Core spec "Table 3.5: Characteristic Properties bit field", and "Table 3.8: Characteristic Extended - Properties bit field". Allowed values: + Properties bit field". + + The "x-asynchronous" flags allow a characteristic to impose write + restrictions on its client characteristic configuration descriptor, + if applicable, restricting access to notifications and indications.
Don't really like the asynchronous name, it doesn't really reflect what we want to accomplish.
quoted hunk ↗ jump to hunk
+ Allowed values: "broadcast" "read"@@ -267,10 +273,13 @@ Properties string UUID [read-only] "writable-auxiliaries" "encrypt-read" "encrypt-write" + "encrypt-asynchronous" (Server only) "encrypt-authenticated-read" "encrypt-authenticated-write" + "encrypt-authenticated-asynchronous" (Server only)
I think for CCC we may just inherit the read/write permissions, or have it as encrypt-notify/encrypt-indicate, etc.
"secure-read" (Server only)
"secure-write" (Server only)
+ "secure-asynchronous" (Server only)
"authorize"
uint16 Handle [read-write, optional] (Server Only)
--
2.31.1-- Luiz Augusto von Dentz