Hi,
this will be discussed tomorrow at the T2TRG meeting preceeding the RIOT
summit [1]. Will anyone of you who discussed this be there? The premise is
that 6LoWPAN was designed to run on even on a minimized, non-compliant IEEE
802.15.4, so the question is: other than PAN bootstrapping and MAC:
Hi Joakim,
That was what I pretty much meant before I'm sorry for not expressing
this clear enough.
Seems we reached common ground here.
Best,
Thomas
On 20 Sep 2017, at 13:51 PDT(-0700), Joakim Nohlgård wrote:
Hi again,
Perhaps it would make sense to split it in two? One low level part
Hi Joakim,
Thanks for sharing your point of view.
Personally I think it complicates MAC protocol implementations when they
somehow have to accommodate 802.15.4 functionality and deal with e.g.
starting and maintaining the PAN and I'd expect we will have to use more
#ifdefs.
In my opinion
On Wed, Sep 20, 2017 at 11:32 AM, Kaspar Schleiser wrote:
> Hi Joakim,
>
> On 09/20/2017 10:11 AM, Joakim Nohlgård wrote:
>> I have recently been digging around the gnrc_netdev code as well. I
>> think that adding support for other frame types and logic for sending
>> these
Hi Joakim,
On 09/20/2017 10:11 AM, Joakim Nohlgård wrote:
> I have recently been digging around the gnrc_netdev code as well. I
> think that adding support for other frame types and logic for sending
> these frames will definitely become a mess if the 802.15.4 code is not
> decoupled from the
Hi Oleg!
On 19 Sep 2017, at 13:24 PDT(-0700), Oleg Hahm wrote:
On Sun, Sep 17, 2017 at 02:37:39PM -0700, Thomas Eichinger wrote:
A while ago I worked on adding support for MAC commands and
procedures the
standard describes like channel scanning and automatic association of
a
device with a
Hey Thomas!
I agree with Kaspar: thanks for bringing this up and yes, we should aim for
compliance.
On Sun, Sep 17, 2017 at 02:37:39PM -0700, Thomas Eichinger wrote:
> A while ago I worked on adding support for MAC commands and procedures the
> standard describes like channel scanning and
Hi Thomas,
On 09/17/2017 11:37 PM, Thomas Eichinger wrote:
> tl;dr: Do we see the need to be IEEE 802.15.4 compliant?
Thanks for bringing this up.
The answer is pretty simple: Yes, of course!
Kaspar
___
devel mailing list
devel@riot-os.org