Re: [6tisch] Link Options bitmap in 6P Cell format

Tero Kivinen <kivinen@iki.fi> Wed, 05 October 2016 15:03 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1DEA129765 for <6tisch@ietfa.amsl.com>; Wed, 5 Oct 2016 08:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d_17alfP7FM5 for <6tisch@ietfa.amsl.com>; Wed, 5 Oct 2016 08:03:44 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A188129785 for <6tisch@ietf.org>; Wed, 5 Oct 2016 08:03:09 -0700 (PDT)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.2/8.15.2) with ESMTPS id u95F2uEs014456 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Oct 2016 18:02:56 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.2/8.14.8/Submit) id u95F2uMm011932; Wed, 5 Oct 2016 18:02:56 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <22517.5664.440871.727991@fireball.acr.fi>
Date: Wed, 05 Oct 2016 18:02:56 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Qin Wang <qinwang6top@yahoo.com>
In-Reply-To: <1294757112.10022353.1475678742266@mail.yahoo.com>
References: <CAMsDxWQ0MhopcM_8rbDEsiM2=k5JpTG8x+x3LMcRH_Dw-vBw9Q@mail.gmail.com> <1294757112.10022353.1475678742266@mail.yahoo.com>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
X-Edit-Time: 11 min
X-Total-Time: 11 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/RTfRfIiJfA8nh7CJUx48LQv2uGg>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>
Subject: Re: [6tisch] Link Options bitmap in 6P Cell format
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 15:03:49 -0000

Qin Wang writes:
> In IEEE802.15.4e, LinkOptions is defined as follows.

This was changed in the 802.15.4-2015, i.e., the MLME and he PIB no
longer specify bit numbers for those infrmation, they provide the same
information in separate parameters (TxLink, RxLink, SharedLink,
TimekeepngLink, PriorityLink), or spearate PIB entries (macTxType,
macRxType, macLinkTimekeeping and macPriorityType).

The TSCH Slotframe and Link IE do define field called Link Options and
splits it to bits as follows:

+---------+---------+-------------+-------------+----------+----------+
| Bits: 0 |     1   |      2      |      3      |     4    |   5-7    |
+---------+---------+-------------+-------------+----------+----------+
| TX Link | RX Link | Shared Link | Timekeeping | Priority | Reserved |
+---------+---------+-------------+-------------+----------+----------+
		Figure 7-54 --Link Options field format

Note, that there is new bit for Priority in there too. And as normally
this is LSB first so care should be taken when written to the IETF
draft... 

> Is it what you are going to use? Then, another way is to use two bits to
> express TX/RX/Share. I'm not sure which way is better than another.

Two bits is not enough to define all different link types. The text in
802.15.4-2015 defining the bits is:

	The TX Link field shall be set to one if it is a TX link and
	shall be set to zero otherwise.

	TX Shared links, indicated by the TX link field and Shared
	Link field both set to one, may be used by a joining device to
	send an Association Request command or higher layer message to
	the advertising device.

	The RX Link field shall be set to one if the link is an RX
	link and shall be set to zero otherwise. RX links are used by
	a joining device to receive an Association Response command or
	higher layer message from an advertising device.

	The Shared Link field shall be set to one if the link is a
	shared link and shall be set to zero otherwise. A shared link
	is one that uses contention to access the medium.

	A link may be used as both a TX shared link and RX link.

	The Timekeeping field shall be set to one if the link is to be
	used for clock synchronization and shall be set to zero
	otherwise. RX links shall have the Timekeeping field set to
	one.

	The Priority field shall be set to one if the link is a
	priority channel access, as defined in 6.2.5.2, and shall be
	set to zero otherwise.
-- 
kivinen@iki.fi