Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Remi Philippe <remi@linqio.com>, linux-wpan@vger.kernel.org
Subject: Re: 802.15.4G support?
Date: Thu, 03 Mar 2016 09:26:54 -0500	[thread overview]
Message-ID: <28981.1457015214@obiwan.sandelman.ca> (raw)
In-Reply-To: <20160228140659.GA17980@omega>

Alexander Aring <alex.aring@gmail.com> wrote:
    > You want to run 6LoWPAN on it, current the 802.15.4 calculates a lot of
    > stuff with the IEEE802154_MTU define, in most cases when using
    > fragmentation.

    > It seems you don't need fragmentation in your case, because you reach
    > the 1280 minimum MTU for IPv6. The condition at [4] should be always
    > true then.

I believe that they do, as 15.4g PHYs can communicate with 15.4 PHYs, and
so the fragment on/off/MTU decision will need to be added to the neighbour
cache.

    > Another question would be: You can run 6LoWPAN on it, but nobody
    > specifies to run 6LoWPAN on such "SUN PHY's". I actually don't see
    > that. Everything is specified with 127 MTU.

    > I don't want to tell you cannot run 6LoWPAN on it, but does somebody
    > need to specify 6LoWPAN for 802.15.4g at first?

WiSun alliance did that, I think.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


  parent reply	other threads:[~2016-03-03 14:36 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 [this message]
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
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=28981.1457015214@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --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