Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Simon Vincent <simon.vincent@xsilon.com>,
	Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>,
	linux-wpan@vger.kernel.org
Subject: Re: [RFC] the problem of on-the-wire byte order in ieee802154
Date: Mon, 1 Jun 2015 16:01:57 +0200	[thread overview]
Message-ID: <20150601140156.GE1195@omega> (raw)
In-Reply-To: <20150601134915.GE1897@wantstofly.org>

On Mon, Jun 01, 2015 at 04:49:15PM +0300, Lennert Buytenhek wrote:
> On Fri, May 29, 2015 at 11:11:33AM +0200, Alexander Aring wrote:
> 
> > > I noticed the 802.15.4 spec has test vectors for the crypto that
> > > show the byte order of the address.
> > > See 802.15.4-2011 spec [1]
> > > Annex C, Section C.2.1.1
> > > 
> > > source address 0xacde480000000001 is represented in a packet as.
> > > 08 D0 84 21 43 01 00 00 00 00 48 DE AC || 02 05 00 00 00 || 55 CF 00 00 51
> > > 52 53 54 22 3B C1 EC 84 1A
> > > B5 53.
> > 
> > thanks for this note. That shows that the LSB "01" of
> > 0xacde480000000001 is send at the first of the packet. Then it
> > should be little endian, or? (In case of this example).
> 
> That's what this example suggests, yes -- as 01-00-00-00-00-48-DE-AC
> would not be a valid source address, as it is a group address.  Note,
> however, that Annex C is an informative annex, and not a normative
> annex.
> 
> I've reached out to the IEEE for clarification of this issue, let's
> see what they come up with.

oh, "where" did you do that exactly?

- Alex

      reply	other threads:[~2015-06-01 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 14:09 [RFC] the problem of on-the-wire byte order in ieee802154 Lennert Buytenhek
2015-05-28 14:27 ` Phoebe Buckheister
2015-05-29  4:17   ` Lennert Buytenhek
2015-05-29  7:44     ` Alexander Aring
2015-05-29  8:08       ` Lennert Buytenhek
2015-05-29  8:31         ` Alexander Aring
2015-05-29  8:53           ` Simon Vincent
2015-05-29  9:11             ` Alexander Aring
2015-06-01 13:49               ` Lennert Buytenhek
2015-06-01 14:01                 ` Alexander Aring [this message]

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=20150601140156.GE1195@omega \
    --to=alex.aring@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=phoebe.buckheister@itwm.fraunhofer.de \
    --cc=simon.vincent@xsilon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox