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

["roll issue tracker" <[e-mail]>]

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

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