From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, brian.gix@intel.com
Subject: [PATCH BlueZ v2 1/5] mesh: Add new required method for Key Refresh proc
Date: Wed, 22 May 2019 12:54:24 -0700 [thread overview]
Message-ID: <20190522195428.1901-2-brian.gix@intel.com> (raw)
In-Reply-To: <20190522195428.1901-1-brian.gix@intel.com>
CompleteAppKeyUpdate() - Used in conjunction with SetKeyPhase()
---
doc/mesh-api.txt | 26 +++++++++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 112990a5d..3fad2fc6f 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -434,6 +434,7 @@ Methods:
PossibleErrors:
org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.DoesNotExist
+ org.bluez.mesh.Error.Busy
void DeleteSubnet(uint16 net_index)
@@ -451,7 +452,9 @@ Methods:
void SetKeyPhase(uint16 net_index, uint8 phase)
This method is used to set the master key update phase of the
- given subnet.
+ given subnet. When finalizing the procedure, it is important
+ to CompleteAppKeyUpdate() on all app keys that have been
+ updated during the procedure prior to setting phase 3.
The net_index parameter is a 12-bit value (0x000-0xFFF)
specifying which subnet phase to set.
@@ -491,6 +494,7 @@ Methods:
PossibleErrors:
org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.AlreadyExists
+ org.bluez.mesh.Error.DoesNotExist
void ImportAppKey(uint16 net_index, uint16 app_index,
array{byte}[16] app_key)
@@ -512,6 +516,7 @@ Methods:
PossibleErrors:
org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.AlreadyExists
+ org.bluez.mesh.Error.DoesNotExist
void UpdateAppKey(uint16 app_index)
@@ -524,6 +529,25 @@ Methods:
This call affects the local bluetooth-meshd key database only.
+ PossibleErrors:
+ org.bluez.mesh.Error.InvalidArguments
+ org.bluez.mesh.Error.DoesNotExist
+ org.bluez.mesh.Error.Busy
+
+ void CompleteAppKeyUpdate(uint16 app_index)
+
+ This method is used by the application at the completion of
+ a Key Refresh Procedure. This method should be called for each
+ app key being updated during the procedure, and must be
+ performed prior to changing the phase of the bound net key
+ to phase 3. (See SetKeyPhase() method).
+
+ The app_index parameter is a 12-bit value (0x000-0xFFF)
+ specifying which app key was updated. Note that the subnet that
+ the key is bound to must exist and be in Phase 2.
+
+ This call affects the local bluetooth-meshd key database only.
+
PossibleErrors:
org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.DoesNotExist
--
2.14.5
next prev parent reply other threads:[~2019-05-22 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:54 [PATCH BlueZ v2 0/5] mesh: Add App and Net Key Refresh keyring back-end Brian Gix
2019-05-22 19:54 ` Brian Gix [this message]
2019-05-22 19:54 ` [PATCH BlueZ v2 2/5] mesh: Centralize definition of PRIMARY_NET_IDX Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 3/5] mesh: Implement Net Key keyring storage handling Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 4/5] mesh: Implement App " Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 5/5] mesh: Implement Key Refresh Phasing in keyring Brian Gix
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=20190522195428.1901-2-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).