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

Qin Wang <qinwang6top@yahoo.com> Wed, 05 October 2016 15:28 UTC

Return-Path: <qinwang6top@yahoo.com>
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 464CC129523 for <6tisch@ietfa.amsl.com>; Wed, 5 Oct 2016 08:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.015
X-Spam-Level:
X-Spam-Status: No, score=-5.015 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 IzvFdCS43NYQ for <6tisch@ietfa.amsl.com>; Wed, 5 Oct 2016 08:28:04 -0700 (PDT)
Received: from nm21.bullet.mail.bf1.yahoo.com (nm21.bullet.mail.bf1.yahoo.com [98.139.212.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4786012978A for <6tisch@ietf.org>; Wed, 5 Oct 2016 08:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1475681281; bh=x8pThlKsZWdmgD7cakG4YQP/7mWA2iUQhKLcVlGjyFI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=ZhcdzcjBtSo0S37wsp+IJggpBQp1zQX4kViF2a7VV8ud4LqAE2rxBAVs82jsmhyguW/mMJ1pSVf9GW9lHNFcxUvnnvaIBBVqTF5XSktCgqL36/oLs5eOjUYIpT2YD4M6QY1XWskaYYMojAlUjUdhpy2GwM1qpzK9O0f76RYLzhYbs3XOmUQS4+fIbYG6ekmxpKbDgZhEBOhsa7CcnBKK4VfFKS4mKhOPyNlyAWRWyivjcHijsmp3aJoLExfDDQHnMIVzpQ3km0qitmHyEWRQo0YBkirqJOU1MFbIVq0VAXX4hTYBmz894Y9I0jPT7c0lfVrPiNCmR4L+rc9XGEea2Q==
Received: from [98.139.214.32] by nm21.bullet.mail.bf1.yahoo.com with NNFMP; 05 Oct 2016 15:28:01 -0000
Received: from [98.139.212.195] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 05 Oct 2016 15:28:01 -0000
Received: from [127.0.0.1] by omp1004.mail.bf1.yahoo.com with NNFMP; 05 Oct 2016 15:28:01 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 430372.91601.bm@omp1004.mail.bf1.yahoo.com
X-YMail-OSG: IYLw3hcVM1ktiIn61lsO30DuY4UFiszxgdnEtQnxkIG4jp5CAGCjqZ6lTS_5WWS 2mhJp3s19K5FLE1HGIsQbLlyFQiIichKKUfgyb0BNKHaOw6Vx.C7OPNHaB_aIpD.S.vmMxt2Jdab 06bv9MrLrIklnYp.Jy1urXQ3oXyDK2xZicWS_ba5WYQO6zye5OeYsm95FailowS8Z.F87UARHDcc k2qoHQTcyTdhpT.NqUMnd6IC2pTs5q5ubVgPiCbfJmo175IfXn.17MyqbPlYOHYwJSgCehm.SlfM Aofj79J_KH8m9pVbg2DykTkbvZgGMIW.tMF1JNSZWM4XxLFjSF16Bp1AP2UT.qaMEG5vnTMyW0K9 3tWiXKsnrRSzfnBuV1VXU0eolpNF8fOoQwJ_8_lTYI_fvg0iYyVbHG7Fu9Dn0jtnrizUKLnskUkL lXrYGeECk23JJKw7EvpDsTQ6RdQHeqfY6US15TaGDkz.yUbZsusItVa1pDjP5xS6Ty.1HW.8em_W j6Xo2ayIgCo2Efam1JFrpPxfzD2mqfRtSm4m5fYNntSlvdMuULYE-
Received: from jws106109.mail.bf1.yahoo.com by sendmailws133.mail.bf1.yahoo.com; Wed, 05 Oct 2016 15:28:00 +0000; 1475681280.995
Date: Wed, 05 Oct 2016 15:27:54 +0000
From: Qin Wang <qinwang6top@yahoo.com>
To: Tero Kivinen <kivinen@iki.fi>
Message-ID: <459643762.4806735.1475681274441@mail.yahoo.com>
In-Reply-To: <22517.5664.440871.727991@fireball.acr.fi>
References: <CAMsDxWQ0MhopcM_8rbDEsiM2=k5JpTG8x+x3LMcRH_Dw-vBw9Q@mail.gmail.com> <1294757112.10022353.1475678742266@mail.yahoo.com> <22517.5664.440871.727991@fireball.acr.fi>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_4806734_1026122237.1475681274437"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/6Z-8yJCh8M55BUFmaa4Pox3d600>
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
Reply-To: Qin Wang <qinwang6top@yahoo.com>
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:28:06 -0000

Hi Tero,
Thank you for the update. 
According to my understanding, the flag used in 6P is trying to define the communication direction of scheduled cell(s). So, I wonder if 2 bits flag is enough.
ThanksQin  

    On Wednesday, October 5, 2016 11:03 AM, Tero Kivinen <kivinen@iki.fi> wrote:
 

 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