From: Dagan Martinez <dmartinez@starry.com>
To: linux-bluetooth@vger.kernel.org
Cc: Dagan Martinez <dmartinez@starry.com>
Subject: [PATCH BlueZ v2 2/2] doc/gatt-api: Add 'X-asynchronous` permissions
Date: Wed, 29 Sep 2021 14:00:31 -0400 [thread overview]
Message-ID: <20210929180031.417090-3-dmartinez@starry.com> (raw)
In-Reply-To: <20210929180031.417090-1-dmartinez@starry.com>
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.
+
+ 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)
"secure-read" (Server only)
"secure-write" (Server only)
+ "secure-asynchronous" (Server only)
"authorize"
uint16 Handle [read-write, optional] (Server Only)
--
2.31.1
prev parent reply other threads:[~2021-09-29 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:00 [PATCH BlueZ v2 0/2] Optionally require security for notify/indicate Dagan Martinez
2021-09-29 18:00 ` [PATCH BlueZ v2 1/2] gatt: allow GATT server to dicate CCC permissions Dagan Martinez
2021-09-29 18:39 ` Optionally require security for notify/indicate bluez.test.bot
2021-09-29 18:00 ` Dagan Martinez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210929180031.417090-3-dmartinez@starry.com \
--to=dmartinez@starry.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.