Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6lo@ietf.org
Cc: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Subject: big frame support in 802.15.4G
Date: Fri, 04 Mar 2016 15:30:00 -0500	[thread overview]
Message-ID: <18168.1457123400@obiwan.sandelman.ca> (raw)
In-Reply-To: <20160304163749.GA21798@omega>

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]


Can 802.15.4g with 2048 byte frames exist in an LLN along with nodes using
802.15.4-2012 classic 127 byte frames?

There are three questions embedded here:
1) are there radios issues that would prevent this from ever being an issue?

2) assuming that 15.4g radios can communicate with 15.4 radios, is there
   something that would permit one 15.4g radio to realize it was talking
   to another 15.4g radio at the L2 (frame) level?

3) if the answer to #2 is no, then is this akin to ethernet with jumbo
   frames, where the MTU (and fraglettation method) to each destination needs
   to go into the neighbour cache?

RFC4681 section 4.6.4 specifies an MTU value for the network as a whole
        in the RA.  https://tools.ietf.org/html/rfc4861#section-4.6.4

I thought that I'd see an option to put the MTU into the NA as well, but
I don't see that specified, so how can jumbo ethernet work today?
(maybe that's why it isn't on by default more often...)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]

  parent reply	other threads:[~2016-03-04 20:30 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
2016-03-30 17:18                     ` Remi Philippe
2016-03-30 21:00                       ` Stefan Schmidt
2016-03-04 20:30           ` Michael Richardson [this message]
     [not found]             ` <56DC2A0A.6070906@htt-consult.com>
2016-03-07 16:25               ` [6lo] big frame support in 802.15.4G 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=18168.1457123400@obiwan.sandelman.ca \
    --to=mcr+ietf@sandelman.ca \
    --cc=6lo@ietf.org \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    /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