IETF Logo Mail Archive

Re: [Roll] Loop Free DODAG Repair Solution

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 01 August 2012 17:05 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 3851411E8155 for <roll@ietfa.amsl.com>; Wed, 1 Aug 2012 10:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level:
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599]
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 DFfxQe53u+Jy for <roll@ietfa.amsl.com>; Wed, 1 Aug 2012 10:05:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 943B811E8117 for <roll@ietf.org>; Wed, 1 Aug 2012 10:05:58 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id 9EE302016A for <roll@ietf.org>; Wed, 1 Aug 2012 13:18:21 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org
In-Reply-To: <501945CC.5040801@merl.com>
References: <50194329.3040003@merl.com> <501945CC.5040801@merl.com>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 01 Aug 2012 13:05:54 -0400
Message-ID: <19309.1343840754@obiwan.sandelman.ca>
Subject: Re: [Roll] Loop Free 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: Wed, 01 Aug 2012 17:05:59 -0000

>>>>> "Jianlin" == Jianlin Guo <guo@merl.com> writes:
    Jianlin> To repair DODAG, a node multicast a repair request (REQ)
    Jianlin> message. Upon receiving a REQ message, a neighboring node
    Jianlin> generates a repair response (REP) message if it has a

In a P2MP situation, I think that an end-node won't generate any
traffic, so it won't know that the DODAG is broken.  

How can the end-node know that it should effect repair?


-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works 
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/

v2.29.0 | Report a Bug | By Email | System Status