Re: [Roll] [roll] #87: Can't we split the target from the RDO ?

JP

I Agree to close for an experimental and I suggest we revisit should the work go standard track.

Cheers
Pascal

-----Original Message-----
From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of Mukul Goyal
Sent: dimanche 8 avril 2012 17:56
To: roll@ietf.org
Subject: Re: [Roll] [roll] #87: Can't we split the target from the RDO ?

Hi JP

Please mark this ticket as closed.

Thanks
Mukul

----- Original Message -----
From: "roll issue tracker" <trac+roll@trac.tools.ietf.org>
To: mukul@UWM.EDU, jpv@cisco.com
Cc: roll@ietf.org
Sent: Wednesday, April 4, 2012 8:09:56 AM
Subject: [roll] #87: Can't we split the target from the RDO ?

#87: Can't we split the target from the RDO ?

 Problem (proposed resolution)
 ------------------------------
 The RDO is a garbage option will all sorts of data in it. The advocated  reason for that is conciseness since separate options mean overhead.
 OTOH, it makes more sense to have all the targets expresses as target  options as opposed to having one target in the DRO and then all other  targets listed after. Having the target separate would allow for a DIO  with no RDO but only a target, which would be useful to poll a device on  an existing DAG. Currently the draft MUST a RDO and MAY and target  option. The suggestion is to allow for a target in DIO without a RDO.

 Proposed resolution
 -------------------------
 Keep it at that since 1) there are implementations and 2) it's  experimental . This resolution implies that the issue will be reopened  should the work go for standard track

 Discussion
 -------------

 [Pascal]" MAY carry one or more RPL Target Options to specify additional  unicast/multicast addresses for the target."
 Now here I would have a MUST carry at least one target. That is indeed  what makes is a lookup DIO...

 [Mukul]
 As I stated in the previous message, we need to include the target in  the P2P-RDO to save bytes for the common case (discover route to one  unicast/multicast target). So, we cannot make using the target option a  MUST.

 [Pascal2] Certainly. I prefer the split, in which case the MUST IMHO  goes to the target as opposed to the RDO. In a case where the RDO is not  needed, the target only message is actually shorter...

 [Mukul2] As I said before, I think a P2P mode DIO always needs to have  one P2P-RDO. I guess, in this case, we agree to disagree!

 [Pascal3] Certainly. And there's nothing blocking with that  disagreement, mostly if the draft targets experimental.
 I think it's OK to keep your response as the proposed resolution for  the issue. Still I'd like advice from others so exposing the issue as LC  will help. Let's see on which side the coin falls.

 [Mukul3] OK. I will be happy to hear additional opinions.

 [Pascal4] Fine, let's keep that as the proposed resolution

 [Mukul4] OK.
 Pascal

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

Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/87>
roll <http://tools.ietf.org/wg/roll/>

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