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@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
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>,
Guilhem Imberton <guilhem.imberton@qorvo.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH wpan-next v2 0/3] IEEE 802.15.4: Add coordinator interfaces
Date: Wed, 2 Nov 2022 15:52:40 +0100 [thread overview]
Message-ID: <20221102155240.71a1d205@xps-13> (raw)
In-Reply-To: <CAK-6q+jXPyruvdtS3jgzkuH=f599EiPk7vWTWLhREFCMj5ayNg@mail.gmail.com>
Hi Alexander,
aahringo@redhat.com wrote on Sun, 30 Oct 2022 22:20:03 -0400:
> Hi,
>
> On Wed, Oct 26, 2022 at 5:35 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > Hello,
> > These three patches allow the creation of coordinator interfaces, which
> > were already defined without being usable. The idea behind is to use
> > them advertizing PANs through the beaconing feature.
> >
>
> I still don't know how exactly those "leaves" and "non-leaves" are
> acting here regarding the coordinator interfaces. If this is just a
> bit here to set in the interface I am fine with it. But yea,
> "relaying" feature is a project on its own, as we said previously.
>
> Another mail I was asking myself what a node interface is then,
> currently it is a mesh interface with none of those 802.15.4 PAN
> management functionality?
Not "none", because I would expect a NODE to be able to perform minimal
management operations, such as:
- scanning
- requesting an association
But in no case it is supposed to:
- send beacons
- manage associations
- be the PAN coordinator
- act as a relay
> Or can it act also as a "leave"
> coordinator... I am not sure about that.
>
> However I think we can think about something scheduled later as we can
> still decide later if we really want that "node" can do that.
> Regarding to 6LoWPAN I think the current type what "node" interface is
> as a just a node in a mesh is required, it might depends on if you
> want routing on IP or "relaying" on MAC (mesh-over vs mesh-under), but
> I never saw mesh-under in 6LoWPAN.
Yes.
>
> Acked-by: Alexander Aring <aahringo@redhat.com>
Thanks!
Miquèl
next prev parent reply other threads:[~2022-11-02 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 9:34 [PATCH wpan-next v2 0/3] IEEE 802.15.4: Add coordinator interfaces Miquel Raynal
2022-10-26 9:35 ` [PATCH wpan-next v2 1/3] mac802154: Move an skb free within the rx path Miquel Raynal
2022-10-26 9:35 ` [PATCH wpan-next v2 2/3] mac802154: Clarify an expression Miquel Raynal
2022-10-26 9:35 ` [PATCH wpan-next v2 3/3] mac802154: Allow the creation of coordinator interfaces Miquel Raynal
2022-10-31 2:20 ` [PATCH wpan-next v2 0/3] IEEE 802.15.4: Add " Alexander Aring
2022-10-31 22:07 ` Alexander Aring
2022-11-02 14:52 ` Miquel Raynal [this message]
2022-11-04 0:55 ` Alexander Aring
2022-11-04 18:17 ` Miquel Raynal
2022-11-07 1:30 ` Alexander Aring
2022-11-07 8:43 ` Miquel Raynal
2022-11-01 10:27 ` Stefan Schmidt
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=20221102155240.71a1d205@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=edumazet@google.com \
--cc=frederic.blain@qorvo.com \
--cc=guilhem.imberton@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).