From: Stefan Schmidt <stefan@osg.samsung.com>
To: Michael Richardson <mcr@sandelman.ca>,
Alexander Aring <alex.aring@gmail.com>
Cc: Remi Philippe <remi@linqio.com>, linux-wpan@vger.kernel.org
Subject: Re: 802.15.4G support?
Date: Mon, 14 Mar 2016 16:34:14 +0100 [thread overview]
Message-ID: <56E6D9F6.70308@osg.samsung.com> (raw)
In-Reply-To: <15462.1457122604@obiwan.sandelman.ca>
Hello.
Having read through the mail threads on linux-wpan and ietf 6lo now.
On 04/03/16 21:16, Michael Richardson wrote:
> Alexander Aring <alex.aring@gmail.com> wrote:
> > Okay. I think at first normal 127-bytes frames need to be send. After
> > if you are sure that your "neighbor" uses a "SUN Phy" then you need to
> > change the MTU (during runtime) for this special neighbor so a
> > different handling can be done.
>
> Exactly... ND messages fit nicely in 127 bytes, and so the reply could
> say something.
>
That would be a way to tackle this mid term, agreed.
From my sidem and with my linux hat on, this loks like the following.
1) 802.15.4 nodes can talk to 802.15.4g nodes on a physical level (it
needs selection of the right modulation, frequency range, overlapping
channels, etc) but it can happen and thus we need to be prepared for it.
2) If the 802.15.4g node uses a SUN PHY with a 2047 byte MTU we can run
into trouble with normal nodes only able to handle 127. So far there is
nothing specified to handle this case. Michael is proposing to use 6lo
ND for this and record the MTU value for this neighbour in the l2 nd
cache. Something that would certainly work but would need specing and
implementing. I see this as a mid term goal we want to have. Anyone
going to work on this?
3) Until 2) is done I would suggest we add a config option "802.15.4g
with SUN PHY" which will change the hardcoded MTU from 127 to 2047 and
will thus only work for a 15.g with SUN PHY only network. No interop as
we have no way of knowing. The option would be disabled by default and
the help text needs to mention the drawbacks. Once we have 2) in place
we can remove this.
Remis, Alex, Michael how does this sound. It would allow Remi to go
ahead and do the work needed to get his driver and things for 15.4g
mainline while the interop problem can get further discussed, speced and
implemented. Whats your folks opinion on this?
regards
Stefan Schmidt
next prev parent reply other threads:[~2016-03-14 15:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 18:22 802.15.4G support? Remi Philippe
2016-02-28 14:07 ` Alexander Aring
2016-03-01 9:17 ` Stefan Schmidt
2016-03-03 14:26 ` Michael Richardson
2016-03-04 8:35 ` Alexander Aring
2016-03-04 15:52 ` Michael Richardson
2016-03-04 16:37 ` Alexander Aring
2016-03-04 20:16 ` Michael Richardson
2016-03-14 15:34 ` Stefan Schmidt [this message]
2016-03-14 23:11 ` Michael Richardson
2016-03-15 5:19 ` Remi Philippe
2016-03-30 8:54 ` Stefan Schmidt
2016-03-30 17:18 ` Remi Philippe
2016-03-30 21:00 ` Stefan Schmidt
2016-03-04 20:30 ` big frame support in 802.15.4G Michael Richardson
[not found] ` <56DC2A0A.6070906@htt-consult.com>
2016-03-07 16:25 ` [6lo] " Michael Richardson
2016-03-07 16:53 ` Don Sturek
2016-03-07 21:06 ` Robert Moskowitz
2016-03-08 8:22 ` Alexander Aring
[not found] ` <CADrU+dKHiNd2xW0Nd=ZWJCAZQ_PbWXwNFo_V2u4nd7A_ccfwCw@mail.gmail.com>
2016-03-08 14:13 ` Michael Richardson
2016-03-08 14:17 ` Michael Richardson
2016-03-08 14:09 ` Michael Richardson
[not found] ` <CAH+RWqFmxcNxtzTjkcR+Z3dmCdkB5HU-=668rmXMiVaDVZUymg@mail.gmail.com>
2016-03-06 10:17 ` 802.15.4G support? Alexander Aring
2016-03-01 9:15 ` 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=56E6D9F6.70308@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcr@sandelman.ca \
--cc=remi@linqio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.