Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Remi Philippe <remi@linqio.com>, Michael Richardson <mcr@sandelman.ca>
Cc: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: 802.15.4G support?
Date: Wed, 30 Mar 2016 10:54:19 +0200	[thread overview]
Message-ID: <56FB943B.3030105@osg.samsung.com> (raw)
In-Reply-To: <CAH+RWqHFKj1joOtNVpP2WR=VO_mOekfek6E9EcEtFnsDj5PHCQ@mail.gmail.com>

Hello.

On 15/03/16 06:19, Remi Philippe wrote:
> On Tue, Mar 15, 2016 at 3:11 AM, Michael Richardson <mcr@sandelman.ca> wrote:
>> Stefan Schmidt <stefan@osg.samsung.com> wrote:
>>      > 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?
>>
>> It's not even clear to me that ND can do this.
>> I still propose that we want to have a space in the l2 or l3 ND cache for
>> this info.  It could well go in the L3 cache because it is really a statement
>> about how the 6lowpan layer should fragment.
>>
>>      > 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.
>>
>> Couldn't we use "ifconfig blah0 mtu 2047"?
> Maybe we should do both, have a flag to specify the PHY type as the
> PHY header is slightly different in15.4g MR-FSK to support for mode
> switch, data whitening... it needs to support 2 octets header (page 52
> of the 802.15.4g-2012 spec) it can also lock the max MTU supported for
> the media. And allow to change the MTU from command line.
>

Did you move on with this? If you ahve any patches let us know. We are 
happily going to review them.

regards
Stefan Schmidt

  reply	other threads:[~2016-03-30  8:54 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
2016-03-14 23:11               ` Michael Richardson
2016-03-15  5:19                 ` Remi Philippe
2016-03-30  8:54                   ` Stefan Schmidt [this message]
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=56FB943B.3030105@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox