Re: [Roll] Clarification on SenderRank in RPL HbH option

Dario Tedeschi <dat@exegin.com> Tue, 16 October 2012 16:29 UTC

Return-Path: <dat@exegin.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D80C21F880D for <roll@ietfa.amsl.com>; Tue, 16 Oct 2012 09:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7sxwWQ7HA1d for <roll@ietfa.amsl.com>; Tue, 16 Oct 2012 09:29:01 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDF121F87EF for <roll@ietf.org>; Tue, 16 Oct 2012 09:29:01 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so6001704pad.31 for <roll@ietf.org>; Tue, 16 Oct 2012 09:29:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=C5HfA+lrzCcQtvIaViiZvmXFuO0pZ8PBy+gvcVPCwUA=; b=m4HNz8S1BLHWQ38HmUsr+aG49BZJVrMJMDzv8bl0WGq1Zk0/7PJPuzPegoj/ogW25d Du8QZKpHKeIk+yM49uhy0Qfz2+JZ/VVPVz1lbIyCwk283YqbJgf8YptSVRTDMD3o/p0R zSXxTbCWnWW393l6IEpGLJAyuaX5Z2FzJtEnVWsbhQps2TG8pN5V+B/SKhNG+qoAWVwM 5LW+DLqexiAY+RzDy7TGzTuspJcqKU9poED8hotxOVwqsFFD76KAiC6nFB/SD/Td+0W8 tRcmH0fhgpDe7AwgpItS1I6hbyjtoJqWUg3u7SyytNvywPWDlQSJDECh+c61q3Pbt9nk v/xg==
Received: by 10.68.222.37 with SMTP id qj5mr47638740pbc.132.1350404941024; Tue, 16 Oct 2012 09:29:01 -0700 (PDT)
Received: from [172.16.1.52] ([184.71.143.130]) by mx.google.com with ESMTPS id a10sm6324726paz.35.2012.10.16.09.28.59 (version=SSLv3 cipher=OTHER); Tue, 16 Oct 2012 09:28:59 -0700 (PDT)
Message-ID: <507D8B43.9000008@exegin.com>
Date: Tue, 16 Oct 2012 09:28:51 -0700
From: Dario Tedeschi <dat@exegin.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: "roll@ietf.org" <roll@ietf.org>
References: <50747202.8020702@exegin.com>
In-Reply-To: <50747202.8020702@exegin.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnyzRtwvasWAYFZp86P0WTUNOHRJQs/mrqSDWBPxdlEI/smt35xUfN+w8GAb1i0mSpzhOwT
Subject: Re: [Roll] Clarification on SenderRank in RPL HbH option
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2012 16:29:03 -0000

Can anyone clarify this for me or at least indicate if it has already 
been discussed some time in the past.

- Dario

On 09/10/2012 11:50 AM, Dario Tedeschi wrote:
>
> While writing ZigBee-IP test procedures for RPL and discussing with 
> other ZigBee-IP members, it appears there may be an error in RFC 6550.
>
> RFC 6550 says:
>
>   SenderRank: 16-bit field set to zero by the source and to
>          DAGRank(rank) by a router that forwards inside the RPL network.
>
> Firstly, it seems wrong that the source of a datagram would set its 
> SenderRank to zero. If this packet were moving up the DAG the first 
> forwarder would set the Rank-Error bit to 1, because the SenderRank 
> field in the HbH option would be lower than its own rank. Similarly, 
> if the datagram were mistakenly moving down the DAG, where the 
> source's real rank was higher than the forwarder's rank a potential 
> routing loop could be missed.
>
> Secondly, why is DAGRank(rank) used to set SenderRank, when SenderRank 
> is a 16bit field. Wouldn't doing this allow for potential routing 
> loops to be missed?
>
> Could someone (preferably one of the RPL authors) please clarify.
>
> - Dario
>