Re: [6tsch] set DAGRank to Join Priority

Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu> Fri, 27 September 2013 18:30 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 435D421F9FC3 for <6tsch@ietfa.amsl.com>; Fri, 27 Sep 2013 11:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 NSXU7wzSbIya for <6tsch@ietfa.amsl.com>; Fri, 27 Sep 2013 11:30:24 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3075721F9CF3 for <6tsch@ietf.org>; Fri, 27 Sep 2013 11:30:23 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id y10so2931841pdj.36 for <6tsch@ietf.org>; Fri, 27 Sep 2013 11:30:23 -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=uRE9RKdIEHgwHVIG5UN9TS/4q/nYPM53aDX7b2ncJJ4=; b=fzGtaqDLSybQrheQH++o8T7irx6MMXZ7665ZT7+o4d4ObQbycHL1Lmo9DF6t/lpJBs dTq2FapHTk3tYrJQI1jeMTHL+erXAoItuFUM0oB8upWQexN8WA5Vsb/bEYht0XMAV0q8 s4lnEyqcentYca2/SHftEbKJQ+44UV9i8d7on3dgg/Qmsn5WuAf7FEtVi4GCXQSrlGYG vYK7vB7Tt8DGSP2KW5BlHZ6sXOlgalvtq9Gg6KlAFKyGk5L6GEYSx9zISdzHAbd1hb/2 hDZ3Q62tXPnppO6mTe8oZfnucH+Rbzm9jKc95sB/2Aai4laE+ihHv3ZevrelnXZn5g39 P1Pw==
X-Gm-Message-State: ALoCoQk01i7oSwZ49BB5NHQOcwcOLZYGI+u10wWNT7D31jUSMowdUax46SM3THSaUwIU70pUTULx
MIME-Version: 1.0
X-Received: by 10.68.192.195 with SMTP id hi3mr9034767pbc.18.1380306623488; Fri, 27 Sep 2013 11:30:23 -0700 (PDT)
Received: by 10.70.34.44 with HTTP; Fri, 27 Sep 2013 11:30:23 -0700 (PDT)
In-Reply-To: <CAAzoce5GiY8zsD4aSaSeWB19Se3fwcTTd8wpqRTC0rAonncUkg@mail.gmail.com>
References: <CAAzoce5GiY8zsD4aSaSeWB19Se3fwcTTd8wpqRTC0rAonncUkg@mail.gmail.com>
Date: Fri, 27 Sep 2013 11:30:23 -0700
Message-ID: <CALEMV4Zom6wW6ByhB3zMwJRt1NpqmeFbe13NuUbrFSWz=pNGhw@mail.gmail.com>
From: Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu>
To: Qin Wang <qinwang@berkeley.edu>
Content-Type: multipart/alternative; boundary=047d7ba970e6f9711f04e761ade6
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 18:30:28 -0000

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:

> 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
>
>