From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan - ML <linux-wpan@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Network Development <netdev@vger.kernel.org>,
David Girault <david.girault@qorvo.com>,
Romuald Despres <romuald.despres@qorvo.com>,
Frederic Blain <frederic.blain@qorvo.com>,
Nicolas Schodet <nico@ni.fr.eu.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH wpan-next 1/6] net: ieee802154: Drop coordinator interface type
Date: Thu, 9 Jun 2022 17:43:53 +0200 [thread overview]
Message-ID: <20220609174353.177daddb@xps-13> (raw)
In-Reply-To: <CAK-6q+gBCakX8Vm1SHuLfex5jBqLKySUiaZKg3So+zjeJaSehw@mail.gmail.com>
Hi Alex,
> > >
> > > - How is chosen the beacon order? Should we have a default value?
> > > Should we default to 15 (not on a beacon enabled PAN)? Should we be
> > > able to update this value during the lifetime of the PAN?
> > >
> >
> > Is there no mib default value for this?
I didn't find anything. I suppose we can ask for that parameter at PAN
creation, but otherwise I'll keep a backward compatible value: 15,
which means that the PAN is not beacon enabled (like today, basically).
> >
> > > - The spec talks about the cluster topology, where a coordinator that
> > > just associated to a PAN starts emitting beacons, which may enable
> > > other devices in its range to ask to join the PAN (increased area
> > > coverage). But then, there is no information about how the newly
> > > added device should do to join the PAN coordinator which is anyway
> > > out of range to require the association, transmit data, etc. Any
> > > idea how this is supposed to work?
> > >
> >
> > I think we should maybe add a feature for this later if we don't know
> > how it is supposed to work or there are still open questions and first
> > introduce the manual setup. After that, maybe things will become
> > clearer and we can add support for this part. Is this okay?
>
> *I also think that this can be done in user space by a daemon by
> triggering netlink commands for scan/assoc/etc. (manual setup) and
> providing such functionality as mentioned by the spec (auto creation
> of pan, assoc with pan). Things which are unclear here are then moved
> to the user as the operations for scan/assoc/etc. will not be
> different or at least parameterized. The point here is that providing
> the minimum basic functionality should be done at first, then we can
> look at how to realize such handling (either in kernel or user space).
Actually this is none of the 802.15.4 MAC layer business. I believe
this is the upper layer duty to make this interoperability work,
namely, 6lowpan?
Thanks,
Miquèl
next prev parent reply other threads:[~2022-06-09 15:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 18:21 [PATCH wpan-next 0/6] net: ieee802154: PAN management Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 1/6] net: ieee802154: Drop coordinator interface type Miquel Raynal
2022-06-04 2:01 ` Alexander Aring
2022-06-06 15:43 ` Miquel Raynal
2022-06-07 3:04 ` Alexander Aring
2022-06-07 16:16 ` Miquel Raynal
2022-06-08 13:47 ` Miquel Raynal
2022-06-08 14:37 ` Miquel Raynal
2022-06-09 2:06 ` Alexander Aring
2022-06-09 2:23 ` Alexander Aring
2022-06-09 15:43 ` Miquel Raynal [this message]
2022-06-11 12:05 ` Alexander Aring
2022-06-15 9:15 ` Miquel Raynal
2022-06-09 1:56 ` Alexander Aring
2022-06-09 15:52 ` Miquel Raynal
[not found] ` <CAK-6q+jchHcge2_hMznO6fwx=xoUEpmoZTFYLAUwqM2Ue4Lx-A@mail.gmail.com>
2022-06-17 15:12 ` Miquel Raynal
2022-06-20 0:13 ` Alexander Aring
2022-06-20 9:19 ` Miquel Raynal
2022-06-21 1:54 ` Alexander Aring
2022-06-21 6:27 ` Miquel Raynal
2022-06-26 1:36 ` Alexander Aring
2022-06-27 8:17 ` Miquel Raynal
2022-06-09 1:42 ` Alexander Aring
2022-06-09 14:42 ` Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 2/6] net: ieee802154: Add support for internal PAN management Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 3/6] net: ieee802154: Create a node type Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 4/6] net: ieee802154: Add the PAN coordinator information Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 5/6] net: ieee802154: Full PAN management Miquel Raynal
2022-06-03 18:21 ` [PATCH wpan-next 6/6] net: ieee802154: Trace the registration of new PANs Miquel Raynal
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=20220609174353.177daddb@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aahringo@redhat.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=frederic.blain@qorvo.com \
--cc=kuba@kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--cc=pabeni@redhat.com \
--cc=romuald.despres@qorvo.com \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.com \
/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).