From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 1/5] doc/advertising-api: Add Flags property
Date: Tue, 08 May 2018 09:26:21 +0000 [thread overview]
Message-ID: <CABBYNZJK9nHb1HQFEVgiC5roPRtcU59JWV+Q2gVgbZcfwUtfUw@mail.gmail.com> (raw)
In-Reply-To: <EF92087E-6EF8-403F-803C-A912DCF50A07@holtmann.org>
Hi Marcel,
On Tue, May 8, 2018 at 10:53 AM Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Luiz,
> > This adds Flags which the application can use in case it want to set
> > it own flags.
> >
> > Note: This would allow for example an application to advertise as
> > discoverable even if the adapter is not discoverable which may be
> > required by dual-mode as it may not require BR/EDR to be discoverable.
> > ---
> > doc/advertising-api.txt | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/doc/advertising-api.txt b/doc/advertising-api.txt
> > index eef98ad91..4e015f282 100644
> > --- a/doc/advertising-api.txt
> > +++ b/doc/advertising-api.txt
> > @@ -78,6 +78,21 @@ Properties string Type
> > <Transport Discovery> <Organization
Flags...>
> > 0x26 0x01
0x01...
> >
> > + array{byte} Flags [Experimental]
> > +
> > + Advertising Flags to include. When present this
will
> > + override existing flags such as Discoverable.
> > +
> > + Note: This property shall not be set when Type is
set
> > + to broadcast.
> > +
> > + Possible value:
> > + bit 0 - LE Limited Discoverable Mode
> > + bit 1 - LE General Discoverable Mode
> > + bit 2 - BR/EDR Not Supported
> > + bit 3 - Simultaneous LE and BR/EDR
(Controller)
> > + bit 4 - Simultaneous LE and BR/EDR (Host)
> > +
> I think this is the wrong approach. Exposing this low-level part is just
giving an API to circumvent and violate the Bluetooth spec. You are
inviting apps to create bad advertising data. So NAK.
Then we should find some alternative, perhaps only allow certain flags to
be set this way or change the property to just Discoverable.
> Regards
> Marcel
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2018-05-08 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 16:13 [PATCH BlueZ 1/5] doc/advertising-api: Add Flags property Luiz Augusto von Dentz
2018-05-07 16:14 ` [PATCH BlueZ 2/5] shared/ad: Add bt_ad_add_flags and bt_ad_clear_flags Luiz Augusto von Dentz
2018-05-07 16:14 ` [PATCH BlueZ 3/5] advertising: Add implementation of Flags property Luiz Augusto von Dentz
2018-05-07 16:14 ` [PATCH BlueZ 4/5] client: Add advertise.flags command Luiz Augusto von Dentz
2018-05-07 16:14 ` [PATCH BlueZ 5/5] client: Print AD Data and Flags once registered Luiz Augusto von Dentz
2018-05-08 7:40 ` [PATCH BlueZ 1/5] doc/advertising-api: Add Flags property Luiz Augusto von Dentz
2018-05-08 8:49 ` David Llewellyn-Jones
2018-05-08 7:53 ` Marcel Holtmann
2018-05-08 9:26 ` Luiz Augusto von Dentz [this message]
2018-05-08 11:17 ` Marcel Holtmann
2018-05-11 11:12 ` Luiz Augusto von Dentz
2018-05-11 11:21 ` David Llewellyn-Jones
2018-05-11 15:34 ` Marcel Holtmann
2018-05-11 19:11 ` David Llewellyn-Jones
2018-05-11 15:32 ` Marcel Holtmann
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=CABBYNZJK9nHb1HQFEVgiC5roPRtcU59JWV+Q2gVgbZcfwUtfUw@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).