IETF Logo Mail Archive

Re: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)

"Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)" <rahul.jadhav@huawei.com> Mon, 13 June 2016 14:15 UTC

Return-Path: <rahul.jadhav@huawei.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0059212D7A3 for <roll@ietfa.amsl.com>; Mon, 13 Jun 2016 07:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DLY8BPP33gM for <roll@ietfa.amsl.com>; Mon, 13 Jun 2016 07:15:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34F3C12D7C7 for <roll@ietf.org>; Mon, 13 Jun 2016 07:15:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQS62381; Mon, 13 Jun 2016 14:15:03 +0000 (GMT)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 13 Jun 2016 15:15:02 +0100
Received: from BLREML510-MBS.china.huawei.com ([169.254.2.25]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0235.001; Mon, 13 Jun 2016 19:44:53 +0530
From: "Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)" <rahul.jadhav@huawei.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)
Thread-Index: AQHRwgrF/t8geBkUZ0GC5+hWTyHOMJ/mxi+A
Date: Mon, 13 Jun 2016 14:14:52 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5D031014@blreml510-mbs.china.huawei.com>
References: <12a93208-a01e-32b0-1e70-9e37eeeab8bb@earthlink.net>
In-Reply-To: <12a93208-a01e-32b0-1e70-9e37eeeab8bb@earthlink.net>
Accept-Language: en-IN, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.214.70]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.575EBFE7.01BE, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0791abac55bb21bc9ca3baf3b2615afe
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/piKo_Ag5mHOtk1UJ2J6GmeqbaIw>
Cc: Dongxin Liu <liudx@gsta.com>
Subject: Re: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2016 14:15:08 -0000

Dear Authors,

Thanks for the draft. IMO, P2P traffic in RPL is an important work and a weak-point of RPL.

One comment regarding link asymmetry and how the draft takes care of it.. 
The draft talks about sending route control messages (RREQ-instance message) from OrigNode to TargNode to enable data transmission from TargNode to OrigNode (section 4) i.e. send message downstream to identify upstream path, like the way RPL DIO msg flows downstream to identify upstream path.
Isn't this orthogonal to the requirements of asymmetric link detection? Can a node make a reachability assumption towards an upstream peer on receiving msg from that upstream peer?
In case of P2P-RPL (RFC 6997), there is a clear assumption about bidirectional reachability. To quote, "Since the links in the discovered route have bidirectional reachability (Section 7), the Target may use the discovered route to reach the Origin."
How does the draft address this problem and handle asymmetric bidirectional routes?
	
Thanks,
Rahul

-----Original Message-----
From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Charlie Perkins
Sent: 09 June 2016 AM 10:21
To: Routing Over Low power and Lossy networks
Cc: Dongxin Liu
Subject: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)


Hello folks,

We have submitted AODV-RPL for consideration in the [roll] WG. AODV-RPL borrows some ideas from AODV and also handles asymmetric bidirectional routes.  Comments and suggestions will be appreciated!

Regards,
Charlie P.

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

v2.23.0 | Report a Bug | By Email