Re: [6tsch] set DAGRank to Join Priority

Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu> Fri, 27 September 2013 21:31 UTC

Return-Path: <xvilajosana@berkeley.edu>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5691C21F8F6D for <6tsch@ietfa.amsl.com>; Fri, 27 Sep 2013 14:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level:
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.543, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7c7YLjh2MhG for <6tsch@ietfa.amsl.com>; Fri, 27 Sep 2013 14:31:54 -0700 (PDT)
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id 183BC21F9A2D for <6tsch@ietf.org>; Fri, 27 Sep 2013 14:31:44 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so3087360pbb.0 for <6tsch@ietf.org>; Fri, 27 Sep 2013 14:31:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=FnZGOJE0fyrXv5rGxHjV8ggQMPragST2vm5wGtrwZsg=; b=EfeelyJOpJgRNesqnhwngQE0nqIq9Cm1oI6bWtmfschwLYRB1bamk4OdQsmlm9U9cW ak3Wd8rAqvXGqCIjFeaUOjJoYNa5D/NmrCYH7Evy+p0UtDk870JtIEp4l8aWZ/cRhu11 oUWzKwl4mmA7uOX/+hd4jjxwmQxNf5GEDn09tPEnDbLnDWSqwrPtkmaLlQkHuDhHW0D+ MVwA/HFVYgOMHaKEA2FkIFcZvMN3wnd5rDvv2Kl+8IjfK+bDITdgCzidkHEEc9FQ7ws3 8K9wwyEbSLmXsUt6957FUD/+Hc1Tmjsm+zkNIov9KyBbLcc4zAgwYoXW70v7csqeF9Mn v7QA==
X-Gm-Message-State: ALoCoQlEGTI6LGuRy4g3/G16MGGGdsqkD7rRI4YkhFLnY7pEBiHSbUn44zpKKAhCHNHfpKqT2+NK
MIME-Version: 1.0
X-Received: by 10.67.4.227 with SMTP id ch3mr14235806pad.74.1380317503690; Fri, 27 Sep 2013 14:31:43 -0700 (PDT)
Received: by 10.70.34.44 with HTTP; Fri, 27 Sep 2013 14:31:43 -0700 (PDT)
In-Reply-To: <CAAzoce5sWeo6+58jjX6Jax_c=JWiBMEFZR=qJA-oX9MWmqjKSQ@mail.gmail.com>
References: <CAAzoce5GiY8zsD4aSaSeWB19Se3fwcTTd8wpqRTC0rAonncUkg@mail.gmail.com> <CALEMV4Zom6wW6ByhB3zMwJRt1NpqmeFbe13NuUbrFSWz=pNGhw@mail.gmail.com> <CAAzoce4zvg0_igrE=U-afgf1iOsGmSUo78kjL-z7tmLVnWRBwg@mail.gmail.com> <CALEMV4Zbc8xy=yQzE7K=RChEWBdC80ommMwqhRxYwfZNt6XypA@mail.gmail.com> <CAAzoce5sWeo6+58jjX6Jax_c=JWiBMEFZR=qJA-oX9MWmqjKSQ@mail.gmail.com>
Date: Fri, 27 Sep 2013 14:31:43 -0700
Message-ID: <CALEMV4YExLAh_7Guv9ak5t4j-g-e=Lu3QHDrfr_DiwSKFkgQ_g@mail.gmail.com>
From: Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu>
To: Qin Wang <qinwang@berkeley.edu>
Content-Type: multipart/alternative; boundary=047d7b16018d7c276004e76436b1
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
Subject: Re: [6tsch] set DAGRank to Join Priority
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: xvilajosana@eecs.berkeley.edu
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" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 21:31:58 -0000

Hi Qin,

well the rank is 2Byte, what i suggest is to divide it by 256 and take this
number as Join Priority (1Byte). If this number is bigger than 0x3F then
the Join Priority becomes 0x3F. Of course this if 0x3F is a strict
requirement.

regards,
Xavi


On Fri, Sep 27, 2013 at 2:20 PM, Qin Wang <qinwang@berkeley.edu> wrote:

> Xavi,
>
> You mean:
> if rank <= 0x3f then JoinPriority=rank else JoinPriority=0x3f
>
> Correct? I think it could be a solution.
>
> Thanks
> Qin
>
>
> On Sat, Sep 28, 2013 at 5:07 AM, Xavier Vilajosana Guillen <
> xvilajosana@eecs.berkeley.edu> wrote:
>
>> Hi Qin,
>>
>> my suggestion is to use JoinPriority[5:0] = (rank[15:8]&0x3F) or 0x3F if
>> bigger -- having a 0x3F would be like having INFINITE Join Priority as in
>> the case of RPL with ranks>65535.
>>
>> would that not work?
>> X
>>
>>
>> On Fri, Sep 27, 2013 at 1:44 PM, Qin Wang <qinwang@berkeley.edu> wrote:
>>
>>> Xavi,
>>>
>>> Let's take the example in your draft to see what the problem is. Please
>>> point out if I'm wrong.
>>> +-------+
>>>      |   0   | R(0)=0
>>>      |       | DAGRank(R(0)) = 0
>>>      +-------+
>>>          |
>>>          |
>>>      +-------+
>>>      |   1   | R(1)=R(0)+683=683
>>>      |       | DAGRank(R(1)) = 2
>>>      +-------+
>>>          |
>>>          |
>>>      +-------+
>>>      |   2   | R(2)=R(1)+683=1366
>>>      |       | DAGRank(R(2)) = 5
>>>      +-------+
>>>          |
>>>          |
>>>      +-------+
>>>      |   3   | R(3)=R(2)+683=2049
>>>      |       | DAGRank(R(3)) = 8
>>>      +-------+
>>>          |
>>>          |
>>>      +-------+
>>>      |   4   | R(4)=R(3)+683=2732
>>>      |       | DAGRank(R(4)) = 10
>>>      +-------+
>>>          |
>>>          |
>>>      +-------+
>>>      |   5   | R(5)=R(4)+683=3415
>>>      |       | DAGRank(R(5)) = 13
>>>      +-------+
>>>
>>> From the example, you can see R(n) is a 2-byte integer, and DAGRank is
>>> always the higher byte of the 2byte integer, because minHopRankIncrease =
>>> 256.
>>>
>>> If set JoinPriority = DAGRank, then it is possible JoinPriority> 0x3f
>>> (although it unlikely happens often), out of its range.
>>> If set JoinPriority[5:0] = DAGRank[7:2], (Is it your suggestion?), a new
>>> node may found many existing nodes with same JoinPriority in received EB.
>>> In another word, the JoinPriority can not provide information about
>>> preferring joining. Right?
>>>
>>> I haven't had good solution for it. So, I hope the range 0x00~0x3f is
>>> not a "MUST" in IEEE802.15.4e.
>>>
>>> What  do you think?
>>> Qin
>>>
>>>
>>>
>>>
>>> On Sat, Sep 28, 2013 at 2:30 AM, Xavier Vilajosana Guillen <
>>> xvilajosana@eecs.berkeley.edu> wrote:
>>>
>>>> Hi Qin,
>>>>
>>>> after thinking a little bit on that maybe we can use the higher byte of
>>>> the rank for that. that is  rank>>8, the higher byte is a monotonically
>>>> increasing counter. As each hop is <<8 (due to minhopRankIncrease) we can
>>>> have the sense of higher join priority as higher the rank.
>>>>
>>>> In addition having if we have the limitation of 0x3F, this means that
>>>> we will support Join priorities up to 0x3F that translated to ranks are
>>>> 0x3F<<8 (big number) ..
>>>>
>>>> just thoughts...
>>>> X
>>>>
>>>>
>>>> On Fri, Sep 27, 2013 at 10:30 AM, Qin Wang <qinwang@berkeley.edu>wrote;wrote:
>>>>
>>>>> Hi Thomas,
>>>>>
>>>>> I think with OF0 the DAGRank is uint8. But, in the Table 52b of
>>>>> IEEE802.15.4e, the range of Join Priority is 0x00~0x3f. If the range is a
>>>>> "MUST", we have to have a function mapping a DAGRank in 0x00~0xff to a
>>>>> JoinPriority in 0x00~0x3f. Correct?
>>>>>
>>>>> Would you please confirm with some expertise in IEEE802.15.4e if the
>>>>> range 0x00~0x3f is a MUST or not?
>>>>>
>>>>> Thanks
>>>>> Qin
>>>>>
>>>>> _______________________________________________
>>>>> 6tsch mailing list
>>>>> 6tsch@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/6tsch
>>>>>
>>>>>
>>>>
>>>
>>
>