From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from box.christofferholmstedt.se ([188.166.68.52]:49162 "EHLO box.christofferholmstedt.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414AbbFYJXF (ORCPT ); Thu, 25 Jun 2015 05:23:05 -0400 Received: from authenticated-user (unknown [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by box.christofferholmstedt.se (Postfix) with ESMTPSA id 56B04140D84 for ; Thu, 25 Jun 2015 05:23:02 -0400 (EDT) Date: Thu, 25 Jun 2015 11:22:55 +0200 From: Christoffer Holmstedt Subject: 802.15.4 bit- and byte-order Message-ID: <20150625092255.GA3682@arazu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-wpan-owner@vger.kernel.org List-ID: To: linux-wpan@vger.kernel.org I remember there were a discussion a few weeks back concerning bit and byte ordering. I'm not sure if there were any conclusion there but a similiar discussion just took place on the 6tisch IETF mailing list where they seem to have come to a conclusion. I will not copy and paste and try to explain the final conclusion they came to, that would probably just introduce more questions ;) ...instead I leave you with a link to the first email in the thread. https://mailarchive.ietf.org/arch/search/?email_list=6tisch&gbt=1&index=0cQxU9tOmxf5CkPtrULOFyIJbzo Hope this can help anyone that isn't following that mailing list. Regards -- Christoffer Holmstedt