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 -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
