IETF Logo Mail Archive

Re: [Roll] [roll] #94: Why does DRO travel by multicast.

C Chauvenet <c.chauvenet@watteco.com> Thu, 05 April 2012 14:20 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 5BE0F21F8760 for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 07:20:17 -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 7kJEnjETc8ME for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 07:20:16 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id CB9C521F8753 for <roll@ietf.org>; Thu, 5 Apr 2012 07:20:15 -0700 (PDT)
Received: from mail116-ch1-R.bigfish.com (10.43.68.229) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Thu, 5 Apr 2012 14:20:14 +0000
Received: from mail116-ch1 (localhost [127.0.0.1]) by mail116-ch1-R.bigfish.com (Postfix) with ESMTP id 5D9DC360508; Thu, 5 Apr 2012 14:20:14 +0000 (UTC)
X-SpamScore: -70
X-BigFish: VPS-70(zzc89bh15caKJzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h93fhd25h)
X-Forefront-Antispam-Report: CIP:157.56.248.181; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0510HT002.eurprd05.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail116-ch1 (localhost.localdomain [127.0.0.1]) by mail116-ch1 (MessageSwitch) id 1333635610998073_17723; Thu, 5 Apr 2012 14:20:10 +0000 (UTC)
Received: from CH1EHSMHS030.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.234]) by mail116-ch1.bigfish.com (Postfix) with ESMTP id E55174E011C; Thu, 5 Apr 2012 14:20:10 +0000 (UTC)
Received: from AMXPRD0510HT002.eurprd05.prod.outlook.com (157.56.248.181) by CH1EHSMHS030.bigfish.com (10.43.70.30) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 5 Apr 2012 14:20:09 +0000
Received: from AMXPRD0510MB390.eurprd05.prod.outlook.com ([169.254.3.137]) by AMXPRD0510HT002.eurprd05.prod.outlook.com ([10.255.57.37]) with mapi id 14.16.0135.002; Thu, 5 Apr 2012 14:20:08 +0000
From: C Chauvenet <c.chauvenet@watteco.com>
To: "mukul@UWM.EDU" <mukul@UWM.EDU>
Thread-Topic: [Roll] [roll] #94: Why does DRO travel by multicast.
Thread-Index: AQHNExuHIbYVUv+ic02NsuQ750a+6JaMR9tQ
Date: Thu, 05 Apr 2012 14:20:08 +0000
Message-ID: <97B69B30E0EF244B940B65EA541E3F2D022165B2@AMXPRD0510MB390.eurprd05.prod.outlook.com>
References: <055.5e7958cf85282c164ccf1feb557bf9dc@trac.tools.ietf.org>
In-Reply-To: <055.5e7958cf85282c164ccf1feb557bf9dc@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
Cc: "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] [roll] #94: Why does DRO travel by multicast.
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:20:17 -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] #94: Why does DRO travel by multicast.

#94: Why does DRO travel by multicast.

 Resolution: Because we want the stop flag in DRO to reach as many nodes as  possible.

 Discussion:

 p14 :  A DRO message travels from the target to the origin via link-local  multicast along the
   route specified inside the Address vector in the P2P-RDO.

 [Cedric]
 Why using multicast if you know every destinators ?
 Could we unicast packets to each destinators in the address vector ?

 [Mukul]
 DRO travels by link local multicast so that the nodes, that are on the  temporary DAG but not necessarily on a discovered route, may know that the  route discovery is over (via the stop flag) and there is no need to  generate any more DIOs. This may lead to a significant reduction in the
 (unnecessary) DIOs generated. Only the routers on the discovered route do  the multicast-based forwarding though.

[Cedric2]
Makes sense, thank's for clarification.
This ticket can be closed.

-- 
-----------------------------------+---------------------
 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/94>
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