Re: [Roll] Fwd: New Version Notification for draft-dt-roll-p2p-rpl-00

Just to clarify further, the route discovery mechanism described in the draft do not prescribe any use of DAOs although when you think about it, a DAO MAY serve as the Discovery Reply message. The difference is that a DAO is restricted to travel along the DAG where as we (the draft's authors) have allowed the Discovery Reply message to travel along any route if it merely carries a source-route back to the originator of route discovery.

Regards
Mukul

----- Original Message -----
From: "Mukul Goyal" <mukul@uwm.edu>
To: "JeongGil Ko (John)" <jgko@cs.jhu.edu>
Cc: "ROLL WG" <roll@ietf.org>
Sent: Thursday, April 29, 2010 2:02:55 PM GMT -06:00 US/Canada Central
Subject: Re: [Roll] Fwd: New Version Notification for draft-dt-roll-p2p-rpl-00

Hi John

>One confusion as I read through the draft is where the authors say in 4.1 and 4.7 that 'DIOs' can be used for discovery messages and suddenly, 4.3 indicates that DAOs are needed in some cases to support the Rout Stack option. Not that its impossible, it would be more than overwhelming to deal with both DAOs and DIOs for discovery :) 

No. The draft merely points out that RPL-07 allows only a DAO to carry the Route Stack option. To support the P2P mechanisms described in the draft, RPL should allow Measurement Request and Discovery messages to carry the Route Stack option as well.

>Overall it looks like a nice high level description of what 'should/could/can/may' happen (although I thought the discussion on loose source routing was over with) but we would need to tie it harder with RPL itself. Just my 2 cents ;)

Regarding loose source routing, there are good reasons to ditch it for DAG-based routing. But there are no reasons why it can not be supported for the route discovery mechanism described in the draft. Loose source routes are useful and should be supported if there are no major technical difficulties in doing so. 

Thanks
Mukul

On Apr 28, 2010, at 1:46 PM, Mukul Goyal wrote:

> Hi all
> 
> The following draft has been submitted for WG's consideration. It describes the additional mechanisms required to support P2P routing in LLNs. The draft first provides a high level description of the mechanisms and then proposes one way of realizing these mechanisms in RPL.
> 
> Regards
> Mukul
> 
> ----- Forwarded Message -----
> From: "IETF I-D Submission Tool" <idsubmission@ietf.org>
> To: mukul@uwm.edu
> Sent: Wednesday, April 28, 2010 12:40:38 PM GMT -06:00 US/Canada Central
> Subject: New Version Notification for draft-dt-roll-p2p-rpl-00 
> 
> 
> A new version of I-D, draft-dt-roll-p2p-rpl-00.txt has been successfully submitted by Mukul Goyal and posted to the IETF repository.
> 
> Filename:	 draft-dt-roll-p2p-rpl
> Revision:	 00
> Title:		 Mechanisms to Support Point-to-Point Routing in Low Power and Lossy Networks
> Creation_date:	 2010-04-28
> WG ID:		 Independent Submission
> Number_of_pages: 13
> 
> Abstract:
> This draft presents mechanisms to determine the end-to-end cost of an
> existing route and to discover/establish "on demand" one or more
> routes between two nodes in a low power and lossy network.  This
> draft also proposes functionality that would enable RPL to provide
> these P2P mechanisms.
> 
> 
> 
> The IETF Secretariat.
> 
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
> 

------
JeongGil Ko (John)
Ph.D. Student
Department of Computer Science
Johns Hopkins University
http://www.cs.jhu.edu/~jgko

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