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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E27F221F873D for <>; Fri, 13 Apr 2012 06:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iHOnS5O-cY2l for <>; Fri, 13 Apr 2012 06:33:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1376821F85F0 for <>; Fri, 13 Apr 2012 06:33:00 -0700 (PDT)
Received: from localhost ([::1] by with esmtp (Exim 4.77) (envelope-from <>) id 1SIgcO-00068V-Tj; Fri, 13 Apr 2012 09:32:52 -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:32:52 -0000
Message-ID: <>
References: <>
X-Trac-Ticket-ID: 95
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] #95: Why need stop flag? Is the receipt of DRO not sufficient to indicate completion of route discovery?
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:02 -0000

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

Changes (by jpv@…):

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



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


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

 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 ?

 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.

 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 ?

 A target cannot set the S flag to one in the DRO if the target address in
 the P2P-RDO specified a multicast address. See the following text at the
 end of page 21 in P2P-RPL-9:

 "The target MAY set the stop flag inside the DRO message to one if

 Goyal, et al.           Expires September 7, 2012              [Page 21]

 Internet-Draft         draft-ietf-roll-p2p-rpl-09             March 2012

 o  this router is the only target specified in the corresponding DIO,
    i.e., the corresponding DIO specified a unicast address of the
    router as the Target inside the P2P-RDO with no additional targets
    specified via RPL Target Options; and


 So how do you stop the RDO flooding when the target adress is mulicast ?


 Stop flag cannot be used when the target address is multicast or when
 multiple unicast targets are there. The DIO generation will stop when the
 DAG dies. In the meanwhile, trickle algorithm would hopefully avoid
 unnecessary message generation. Note that the draft recommends a very
 small value for the redundancy constant.

 So in this case, the RDO (I guess this is what you mean when you mentioned
 "DIO" in you previous message) generation to discover the route is never
 ending until the temporary DAG dies ?

 [Mukul4] Never ending wont be the correct description. The temporary DAG
 lasts for a few seconds only. Plus, the trickle algorithm would prevent
 the generation of many DIOs.

 I guess the RDO flooding would stop according to the MaxRank/NH field  of
 the P2P-RDO message.

 Yes, it would. MaxRank and other routing constraints would always limit
 the scope of route discovery. Note that there are two separate things:
 1) scope of discovery: how far the discovery message (P2P-RDO inside the
 DIO) travels. This is controlled by the routing constraints and the
 maxRank field inside the P2P-RDO.
 2) How many discovery messages are generated by the nodes that join the
 DAG: this is controlled by trickle timer and ultimately by the DAG life
 time. The stop flag in the DRO is an optimization that allows DIO
 generation to stop in the nodes that can hear the stop flag.

 But if this field is set to 0 (meaning infinity according to section 7.1),
 we should find a mechanism to stop the discovery mechanism.
 What do you think ?

 To tell the truth, MaxRank is basically a way to avoid putting a metric
 container in the DIO (when a limit on rank is the only constraint you want
 to specify). The scope of discovery is limited by both MaxRank as well as
 the routing constraints in the metric container.

 Actually, the problem for stopping the discovery process without the "S"
 flag is also present with unicast addresses, because not all nodes will
 hear the DRO (Only the nodes in the neighborhood of DRO forwarders).
 So we ended with some nodes forming and maintaining a temporary DAG even
 is they are not included in the discovered path, until the temporary DAG
 As you mentioned, the maxRank field, routing constraints, and trickle or
 DAG lifetime limit this overhead.
 The section 9.2 of this draft give useful guidelines for trickle operation
 using the P2P RPL mechanism, and limit the flooding of RDO messages.
 The only improvement we could add is to avoid the maintenance of some part
 of the temporary DAG that don't hear the DRO with the S flag.
 This nodes will still send out some DIO when the trickle timer fires.
 Though, thank's to the trickle's operation described in section 9.2, they
 won't be propagated.
 One possibility could be to state that : "if a DRO has not been heard
 within a certain period of time, then their node is not considered as a
 part of the discovered path and should leave the temporary DAG".

 Two problems:
 1) An intermediate router has no idea how long the target wants to wait
 before generating DRO.


 2) If an intermediate router leaves the DAG early (ie before the DAG's
 lifetime is over), it might end up rejoining the DAG when it hears the
 DAG's DIO again.

 Yes. So if I understand correctly, even if a mechanism enable nodes that
 are not along the discovered path to leave the temporary DAG, they will
 join it at some point due to the temporary DAG maintenance messages
 So in the end, the benefit I saw (Saving power, packets, state
 maintenance), is not there.
 Then if there is no benefit, there is no reason to change the spec.
 So if what I wrote above is correct, I'm OK to close the ticket and don't
 change anything about the "S" flag behavior.

 This "certain period of time" could be determined according to the network
 topology, the application, or the network diameter for instance and let to
 the implementation.

 It would be much easier if the origin could choose a small (yet
 reasonable) lifetime for the DAG.

 I agree that this parameters will greatly impact on the RPL P2P cost.

 I see a benefit in the case of a discovery process to a unicast target in
 a very large and sparse network. Here, a lot of nodes will maintain
 unnecessary states if they are not part of the discovered path.
 With the current spec, they will send periodic and unnessecary DIO. The
 handling of a "DRO timeout reception" could save packets, thus battery,
 bandwidth etc...

 I am not sure this will work as I explained above.
 Roll mailing list

 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 <>