All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: 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: Fri, 29 May 2015 09:44:20 +0200	[thread overview]
Message-ID: <20150529074419.GA2557@omega> (raw)
In-Reply-To: <20150529041723.GN11340@wantstofly.org>

On Fri, May 29, 2015 at 07:17:23AM +0300, Lennert Buytenhek wrote:
...
> 
> Also, every other 802 link layer I know of transmits the OUI bytes
> of the EUI first, and at least for 802.3 ("Ethernet"), the point of
> transmitting the least significant bit first is so that the first
> transmitted header bit is the group address bit of the destination
> ethernet address, see e.g. this section from 802.3-2012 3.2.3:
> 
> 	http://i.imgur.com/YfaWVwT.png
> 
> (And note how the I/G and U/L bits are on the very left, even though
> when we write out an EUI-48, the I/G bit is 01:00:00:00:00:00, and
> the U/L bit is 02:00:00:00:00:00.)
> 
> I don't know of any EUI-{48,64} users that transmit the OUI bytes
> including the I/G bit and the U/L bit as the very last bytes of the
> address, but this is what you are arguing for, and I'm really not
> sure why you think it should be like this -- the references you
> quoted all seem to contradict the conclusion you're drawing from
> them, in my humble opinion.

Maybe this helps a little bit to clarifing this [0].

8. MAC addresses
8.6 Bit-ordering and different MACs

"Throughout this subclause, considerations relating to the order of bit
and/or octet transmission refer to the basic bit-serial model of
transmission that applies to the representation of MAC frames at the
boundary between the MAC and the PHY."

"...octet transmission that applies to the representation of MAC frames..."
which is little endian.



Also I note that several documents [0] and [1] talks about, what Phoebe
already said: EUI-64 is a number representation and each payload in PSDU
should send in little endian byte order.


That the PSDU should send in little endian is specified in section:
10.2.3 Bit-to-symbol mapping

"Each octet of the PPDU is processed through the modulation and spreading
functions, as illustrated in Figure 69, sequentially, beginning with the
Preamble field and ending with the last octet of the PSDU. Within each octet,
the least significant symbol (b0,b1,b2,b3) is processed first and the most
significant symbol (b4,b5,b6,b7) is processed second."


- Alex

[0] http://standards.ieee.org/getieee802/download/802-2014.pdf
[1] http://www.silabs.com/Support%20Documents/TechnicalDocs/UG100.pdf (Section 2.1)
[2] http://datasheet.octopart.com/SN260QT-STMicroelectronics-datasheet-516599.pdf (Section 7.1)

  reply	other threads:[~2015-05-29  7:44 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 [this message]
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

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=20150529074419.GA2557@omega \
    --to=alex.aring@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=phoebe.buckheister@itwm.fraunhofer.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.