From: James Prestwood <prestwoj@gmail.com>
To: Jesse Lentz <jesse@twosheds.org>, iwd@lists.linux.dev
Subject: Re: [PATCH 2/2] doc: Add State and Role properties to DPP API
Date: Wed, 22 Jun 2022 13:35:38 -0700 [thread overview]
Message-ID: <312b2cd5fdede0d7fdd7f45aeda5919e9b22950f.camel@gmail.com> (raw)
In-Reply-To: <20220622194142.213135-2-jesse@twosheds.org>
Hi Jesse,
On Wed, 2022-06-22 at 15:41 -0400, Jesse Lentz wrote:
> Document the State and Role properties of the DeviceProvisioning API.
> ---
> doc/device-provisioning-api.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/doc/device-provisioning-api.txt b/doc/device-
> provisioning-api.txt
> index 0aba2557..c1d706ec 100644
> --- a/doc/device-provisioning-api.txt
> +++ b/doc/device-provisioning-api.txt
> @@ -56,3 +56,13 @@ Methods string StartEnrollee()
> net.connman.iwd.NotCo
> nfigured
> net.connman.iwd.NotSu
> pported
> net.connman.iwd.Busy
> +
> +Properties string State [readonly, optional]
> +
> + Reflects the DPP state. Possible values are
> "presence",
> + "authenticating", and "configuring".
I think a "stopped" state would also be needed.
> +
> + string Role [readonly, optional]
> +
> + Reflects the DPP role. Possible values are
> "enrollee"
> + and "configurator"
I don't think you actually need this one. The role should be implied by
however you started DPP:
StartEnrollee() -> enrollee
StartConfigurator() -> configurator
ConfigureEnrollee() -> configurator
Thanks,
James
next prev parent reply other threads:[~2022-06-22 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 19:41 [PATCH 1/2] dpp: Add State and Role properties to dbus API Jesse Lentz
2022-06-22 19:41 ` [PATCH 2/2] doc: Add State and Role properties to DPP API Jesse Lentz
2022-06-22 20:35 ` James Prestwood [this message]
2022-06-23 16:30 ` Jesse Lentz
2022-06-23 16:47 ` James Prestwood
2022-06-23 17:24 ` Jesse Lentz
2022-06-23 18:00 ` Denis Kenzior
2022-06-23 19:07 ` Jesse Lentz
2022-06-23 19:58 ` Denis Kenzior
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=312b2cd5fdede0d7fdd7f45aeda5919e9b22950f.camel@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=jesse@twosheds.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