IETF Logo Mail Archive

Re: [Roll] [roll] #95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?

C Chauvenet <c.chauvenet@watteco.com> Thu, 05 April 2012 14:38 UTC

Return-Path: <c.chauvenet@watteco.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 57DB821F85CC for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 07:38:38 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fV7PTkT2rlHY for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 07:38:37 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by ietfa.amsl.com (Postfix) with ESMTP id C48F421F85C3 for <roll@ietf.org>; Thu, 5 Apr 2012 07:38:36 -0700 (PDT)
Received: from mail9-am1-R.bigfish.com (10.3.201.240) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.23; Thu, 5 Apr 2012 14:38:35 +0000
Received: from mail9-am1 (localhost [127.0.0.1]) by mail9-am1-R.bigfish.com (Postfix) with ESMTP id ECEAB2E03CA; Thu, 5 Apr 2012 14:38:35 +0000 (UTC)
X-SpamScore: -73
X-BigFish: VPS-73(z4b6Kzc89bh15caKJzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h93fhd25h)
X-Forefront-Antispam-Report: CIP:157.56.248.181; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0510HT005.eurprd05.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail9-am1 (localhost.localdomain [127.0.0.1]) by mail9-am1 (MessageSwitch) id 1333636714124172_24988; Thu, 5 Apr 2012 14:38:34 +0000 (UTC)
Received: from AM1EHSMHS012.bigfish.com (unknown [10.3.201.229]) by mail9-am1.bigfish.com (Postfix) with ESMTP id 0CB2D480063; Thu, 5 Apr 2012 14:38:34 +0000 (UTC)
Received: from AMXPRD0510HT005.eurprd05.prod.outlook.com (157.56.248.181) by AM1EHSMHS012.bigfish.com (10.3.207.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 5 Apr 2012 14:38:33 +0000
Received: from AMXPRD0510MB390.eurprd05.prod.outlook.com ([169.254.3.137]) by AMXPRD0510HT005.eurprd05.prod.outlook.com ([10.255.57.40]) with mapi id 14.16.0135.002; Thu, 5 Apr 2012 14:38:32 +0000
From: C Chauvenet <c.chauvenet@watteco.com>
To: "roll@ietf.org" <roll@ietf.org>, "mukul@UWM.EDU" <mukul@UWM.EDU>, "jpv@cisco.com" <jpv@cisco.com>
Thread-Topic: [Roll] [roll] #95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?
Thread-Index: AQHNEx32hh4lWAafiEaDmA/VlsX0qpaMTC1w
Date: Thu, 05 Apr 2012 14:38:31 +0000
Message-ID: <97B69B30E0EF244B940B65EA541E3F2D022166C5@AMXPRD0510MB390.eurprd05.prod.outlook.com>
References: <055.011df19dbc537f65d6ae0f3e832587d1@trac.tools.ietf.org>
In-Reply-To: <055.011df19dbc537f65d6ae0f3e832587d1@trac.tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.4.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
Subject: Re: [Roll] [roll] #95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?
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: Thu, 05 Apr 2012 14:38:38 -0000


-----Message d'origine-----
De : roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] De la part de roll issue tracker
Envoyé : jeudi 5 avril 2012 13:02
À : mukul@UWM.EDU; jpv@cisco.com
Cc : roll@ietf.org
Objet : [Roll] [roll] #95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?

#95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?

 Resolution: No because multiple DROs would be generated if multiple source  routes are being discovered.

 Discussion:

 p15 :  Stop (S): This flag, when set to one by a target, indicates that  the P2P-RPL route discovery is over.

 [Cedric]
 Is this bit really usefull ? My guess is that it will be always set to 1.
 If you hear a DRO, this indeed means that the RDO has reached the target,  so you could just stop processing RDO when you hear a DRO.
 Do we really need a flag to stop RDO processing or the hearing of a DRO  type message could do the job ?

 [Mukul]
 A P2P-RPL invocation might involve discovery of multiple source routes. In  that case, receipt of a DRO does not mean route discovery is over. Only  when the target sets the stop flag in the DRO, a node could be sure that  the route discovery is over.

[Cedric2]
OK fo multiple discovery.
But if I want to discover a route to a multicast group of target. I set a multicast adress in the target field of the RDO. Then, do I received as many DRO message as the number of target reached ? In that case, would the first DRO with a "S" flag stop the RDO propagation to reach all the target included in the multicast group ?
-- 
-----------------------------------+---------------------
 Reporter:  jpv@…                  |      Owner:  mukul@…
     Type:  defect                 |     Status:  new
 Priority:  major                  |  Milestone:
Component:  p2p-rpl                |    Version:
 Severity:  Submitted WG Document  |   Keywords:
-----------------------------------+---------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/95>
roll <http://tools.ietf.org/wg/roll/>

_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email