Re: [Roll] Loop free local DODAG repair solution

Philip Levis <pal@cs.stanford.edu> Tue, 23 October 2012 16:34 UTC

Return-Path: <pal@cs.stanford.edu>
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 ECACC21F84B1 for <roll@ietfa.amsl.com>; Tue, 23 Oct 2012 09:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lQNCVIeqlppj for <roll@ietfa.amsl.com>; Tue, 23 Oct 2012 09:34:04 -0700 (PDT)
Received: from cs-smtp-2.Stanford.EDU (cs-smtp-2.Stanford.EDU [171.64.64.26]) by ietfa.amsl.com (Postfix) with ESMTP id EF2C511E80A5 for <roll@ietf.org>; Tue, 23 Oct 2012 09:34:00 -0700 (PDT)
Received: from dn0a2101f9.sunet ([10.33.1.249]) by cs-smtp-2.Stanford.EDU with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <pal@cs.stanford.edu>) id 1TQhQW-0002Ie-FO; Tue, 23 Oct 2012 09:34:00 -0700
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Philip Levis <pal@cs.stanford.edu>
In-Reply-To: <5086C308.5010601@merl.com>
Date: Tue, 23 Oct 2012 09:34:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5F32780-909B-445C-B9EE-F2A0705ED5E4@cs.stanford.edu>
References: <50194329.3040003@merl.com> <501945CC.5040801@merl.com> <5086A598.7030508@merl.com> <8F2798CD-B406-4D56-B1AB-2E6F3A4B15A9@cs.stanford.edu> <5086C308.5010601@merl.com>
To: Jianlin Guo <guo@merl.com>
X-Mailer: Apple Mail (2.1278)
X-Scan-Signature: 127ff6e1eac6b45a32dc112250ed777d
Cc: roll@ietf.org, Philip Orlik <porlik@merl.com>, Kieran Parsons <parsons@merl.com>
Subject: Re: [Roll] Loop free local DODAG repair solution
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, 23 Oct 2012 16:34:05 -0000

The original observation behind loop detection and repair is that it is often much simpler and less expensive than loop prevention. This is not always true; I wouldn't to use it on core routers. But the tradeoffs that LLNs introduce make it an attractive option. 

Phil

On Oct 23, 2012, at 9:17 AM, Jianlin Guo wrote:

> Hi Phil,
> 
> Thank you for your comment. Goal of our local repair method is to prevent loop from occurring and therefore, loop detection is unnecessary.
> 
> Jianlin
> On 10/23/2012 11:39 AM, Philip Levis wrote:
>> I thought the hop-by-hop header detects loops and triggered DIOs repair them?
>> 
>> Phil
>> 
>> On Oct 23, 2012, at 7:11 AM, Jianlin Guo wrote:
>> 
>>> Dear ROLL WG members,
>>> 
>>> As we all know that loop is an open issue in RPL. Experiment shows that loop occurs quite often. We have proposed a loop free local DODAG repair solution. The proposed repair method does not increase rank, and therefore, it does not create any loop. Also, the proposed repair method does not require any modification to RPL and works for both storing mode and non-storing mode of RPL. It provides benefits to RPL.
>>> 
>>> The detailed solution is specified in draft-guo-roll-loop-free-dodag-repair-00. Please review the draft. Your comments and feedback are welcome.
>>> 
>>> Best regards,
>>> Jianlin Guo
>>> Senior Principal Member Research Staff
>>> Mitsubishi Electric Research Laboratories
>>> 201 Broadway, Cambridge, MA, USA
>>> 
>>> _______________________________________________
>>> Roll mailing list
>>> Roll@ietf.org
>>> https://www.ietf.org/mailman/listinfo/roll
> 
>