From: Michael Richardson <mcr@sandelman.ca>
To: robert.cragie@gridmerge.com
Cc: Alexander Aring <alex.aring@gmail.com>,
Robert Moskowitz <rgm-ietf@htt-consult.com>,
linux-wpan@vger.kernel.org, Don Sturek <d.sturek@att.net>,
"6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6lo] big frame support in 802.15.4G
Date: Tue, 08 Mar 2016 09:13:47 -0500 [thread overview]
Message-ID: <24172.1457446427@obiwan.sandelman.ca> (raw)
In-Reply-To: <CADrU+dKHiNd2xW0Nd=ZWJCAZQ_PbWXwNFo_V2u4nd7A_ccfwCw@mail.gmail.com>
Robert Cragie <robert.cragie@gridmerge.com> wrote:
> I don't know the word "fraglettation"; I assume this is the same as
> "fragmentation"? The device would need to invoke 6LoWPAN fragmentation
> if the target device is a legacy device and the IPv6 frame is too large
> to fit into the MSDU.
I thought that 6lowpan adopted the term "fraglet" to mean fragmentation below
IPv6, such that the term "fragment" could continue to refer to what happens
above IPv6 using the Fragmentation Header.
I see that I've mis-reremembered, and the term became "link fragment".
--
] 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 [
next prev parent reply other threads:[~2016-03-08 14:13 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 ` 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 [this message]
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=24172.1457446427@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=6lo@ietf.org \
--cc=alex.aring@gmail.com \
--cc=d.sturek@att.net \
--cc=linux-wpan@vger.kernel.org \
--cc=rgm-ietf@htt-consult.com \
--cc=robert.cragie@gridmerge.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.