From: Alexander Aring <alex.aring@gmail.com>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>
Cc: Don Sturek <d.sturek@att.net>,
Michael Richardson <mcr+ietf@sandelman.ca>,
linux-wpan@vger.kernel.org, 6lo@ietf.org
Subject: Re: [6lo] big frame support in 802.15.4G
Date: Tue, 8 Mar 2016 09:22:08 +0100 [thread overview]
Message-ID: <20160308082207.GA790@omega> (raw)
In-Reply-To: <56DDED58.5060500@htt-consult.com>
Hi,
On Mon, Mar 07, 2016 at 04:06:32PM -0500, Robert Moskowitz wrote:
> I was thinking that there is also some difference in the physical header to
> support the larger PPU?
>
I copy&paste here some parts which I already wrote in another mailing
thread:
---
Looking again into 802.15.4g-2012 there stands on page (not pdf page)
95:
"For the 780 MHz, 915 MHz, and 2450 MHz frequency bands, the MR-O-QPSK
PHY supports communication with legacy devices according to the
specifications in Clause 10, as described in 18.3.3."
so somewhat with "Clause 10" and at 18.3.3 the standard says:
"18.3.3 Support of legacy devices of the 780 MHz, 915 MHz, and 2450 MHz
O-QPSK PHYs" ... the lot of copy&pasting witht the same sentences but
different frequencies. :-)
Then looking into 802.15.4-2011 for Clause 10, the standard says:
"10. O-QPSK PHY"
so Clause 10, they mean all other PHYs. For me it looks like it is
possible to communicate with "legacy device according to the
specifications in Clause 10".
---
That means for me:
MR-O-QPSK is compatible with O-QPSK.
The question which follows is:
How 6LoWPAN for 802.15.4g devices deals with 802.15.4g and 802.15.4-2011
(legacy devices) in one 6LoWPAN network, if this handling is supported
somehow?
Is there some mechanism on for getting the capabilities "MTU" and
Modulation for each neighbor?
Then you could start always with a O-QPSK modulation and 127 bytes MTU,
if you know your 6LoWPAN network is a complete 802.15.4g only network,
then simple use 802.15.4g features.
If not: exist there some mechanism (Option-Field in NA) to see, this
neighbor is a SUN Phy and I could change the MTU/modulation for this
neighbor.
btw: for broadcast frames you should need then 127 bytes and O-QPSK
only.
- Alex
next prev parent reply other threads:[~2016-03-08 8:22 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 [this message]
[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=20160308082207.GA790@omega \
--to=alex.aring@gmail.com \
--cc=6lo@ietf.org \
--cc=d.sturek@att.net \
--cc=linux-wpan@vger.kernel.org \
--cc=mcr+ietf@sandelman.ca \
--cc=rgm-ietf@htt-consult.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.