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

"roll issue tracker" <> Fri, 13 April 2012 13:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 10CDB21F878A for <>; Fri, 13 Apr 2012 06:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jnxUWN51o0+e for <>; Fri, 13 Apr 2012 06:33:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7BFE221F8787 for <>; Fri, 13 Apr 2012 06:33:25 -0700 (PDT)
Received: from localhost ([::1] by with esmtp (Exim 4.77) (envelope-from <>) id 1SIgcu-00076F-Ny; Fri, 13 Apr 2012 09:33:24 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: roll issue tracker <>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: mukul@UWM.EDU,
X-Trac-Project: roll
Date: Fri, 13 Apr 2012 13:33:24 -0000
Message-ID: <>
References: <>
X-Trac-Ticket-ID: 94
In-Reply-To: <>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mukul@UWM.EDU,,
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Subject: Re: [Roll] [roll] #94: Why does DRO travel by multicast.
X-Mailman-Version: 2.1.12
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Apr 2012 13:33:26 -0000

#94: Why does DRO travel by multicast.

Changes (by jpv@…):

 * status:  new => closed
 * resolution:   => fixed


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


 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.

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

 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.

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

 Reporter:  jpv@…                  |       Owner:  mukul@…
     Type:  defect                 |      Status:  closed
 Priority:  major                  |   Milestone:
Component:  p2p-rpl                |     Version:
 Severity:  Submitted WG Document  |  Resolution:  fixed
 Keywords:                         |

Ticket URL: <>
roll <>