Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

Hi, Here is my understanding... - 1. If you're sending a LOWPAN_IPHC frame without 6LoRH, it'd be better to use page-0 LOWPAN_IPHC, without paging dispatch, in case a receiver is a legacy, non-6TiSCH, node. - 2. Since a node may receive a page-1 LOWPAN_IPHC frame without 6LoRH, it'd be

Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

That would make sense and save a byte in all cases but is this compliant with RFC 8025?" " Values of the Dispatch byte defined in [RFC4944] are considered as belonging to the Page 0 parsing context, which is the default and does not need to be signaled explicitly at the beginning of a

Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

Yes, examples-02 has the exact same thing: 0xf1 directly followed by IPHC. If my understanding is correct, this is compliant but a waste of one byte. On Wed, Jul 5, 2017 at 12:05 PM, Thomas Watteyne wrote: > Simon, > > Didn't look at details, but you look at

Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

You indeed don’t need page 1 for IPHC. You need to be on page 1 once you need 6LoRH. (My proposal was to simply define 6TiSCH to start in page 1. No idea whether that removes any ever-so-remote compatibility with 6LoWPAN or if there is any other reason to start off in page 0.) Grüße, Carsten

Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

Simon, Didn't look at details, but you look at examples-00. Could you please check examples-02 and whether the issue is still there? Thomas On Wed, Jul 5, 2017 at 12:02 PM, Simon Duquennoy wrote: > In Thomas' example >

Re: [6tisch] 6TiSCH interop: 6LoRH and OSCOAP as a requirement?

In Thomas' example https://tools.ietf.org/html/draft-munoz-6tisch-examples-00#section-3.6.1 there is a page dispatch to page 1 (0xf1) followed by IPHC (no routing header). In this case, couldn't one choose to elide the page dispatch and directly include IPHC? Or is the IPHC different from a page 0