Martin, On Thu, Jul 24, 2014 at 11:17:48AM +0100, Martin Townsend wrote: > It's doesn't specifically say you can, but then again it doesn't specifically > say you can't, it's just my interpretation :) > It makes sense that you would only send uncompressed if the packet is small > anyway so I'll park this one unless we find a 6lowpan implementation that > does this. >
you said that it's also possible that we send uncompressed header WHILE fragmentation. But I don't see this, where do you read this in rfc4944? Maybe I don't see it. What I mean there exist a way in non fragmented packet and a uncompressed header. My last mail describes about the dispatch value "IPv6", see [0]. If we get a "FRAG1" dispatch value then it can't be a "IPv6" dispatch value, because this value is "FRAG1". It's really necessary to know that, we should not handle this in the sending part, but very IMPORTANT is to handle it at RECEIVING part, otherwise we are not RFC complaint. For me it looks like that 6lowpan packets which have "FRAG1" as dispatch value are always compressed. I mean in my last mail is that we handle uncompressed NOT fragmented 6lowpan packets only at receiving part to be rfc complaint. We don't do this at sending side and this is part of design (too see what is better or make it user accessible to decide if we do that or not) but only on sending part. At receiving part we MUST handle it. - Alex [0] http://tools.ietf.org/html/rfc4944#section-5.1 ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
