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

"Satish Anamalamudi (Satish Anamalamudi)" <> Wed, 15 June 2016 06:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7488A12D0CF for <>; Tue, 14 Jun 2016 23:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.647
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id d-xZlbeMvI2R for <>; Tue, 14 Jun 2016 23:46:41 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1FE5212B017 for <>; Tue, 14 Jun 2016 23:46:39 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id CQV30168; Wed, 15 Jun 2016 06:46:37 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Wed, 15 Jun 2016 07:46:34 +0100
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Wed, 15 Jun 2016 14:46:26 +0800
From: "Satish Anamalamudi (Satish Anamalamudi)" <>
To: Routing Over Low power and Lossy networks <>
Thread-Topic: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)
Thread-Index: AQHRwgqqj0P4r3lEykuKYT5MxzxPQ5/m8bUAgAMr68A=
Date: Wed, 15 Jun 2016 06:46:25 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-IN, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.5760F9CE.0007, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0791abac55bb21bc9ca3baf3b2615afe
Archived-At: <>
Cc: Dongxin Liu <>
Subject: Re: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Jun 2016 06:46:43 -0000

Hello Rahul,

Thank you for your comments. Please, see my response in "[SA]".

With Regards,
> -----Original Message-----
> From: Roll [] On Behalf Of Rahul Arvind
> Jadhav (Rahul Arvind Jadhav, 2012 Labs)
> Sent: 2016年6月13日 22:15
> To: Routing Over Low power and Lossy networks
> Cc: Dongxin Liu
> Subject: Re: [Roll] AODV-RPL (draft-satish-roll-aodv-rpl-00.txt)
> 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?

For AODV-RPL, how to exactly check the link reliability is out the scope of the document. 

Assume the link reliability (Bi-directional Symmetric or Bi-directional Asymmetric) is known, the operation of AODV-RPL at nodeB is explained below. 


             Figure.1. Sample AODV-RPL topology

Case 1: If the link from OrigNode->nodeB(Downstream) and nodeB->OrignNode(upstream) is reliable at nodeB then "S" bit is remains to 1 (Symmetric).
Case 2: If the link from OrigNode->nodeB(Downstream) is not reliable and nodeB->OrigNode(upstream) is reliable at nodeB then "S" bit is set to "0"(Asymmetric).

Case 3: If the link from OrigNode ->nodeB(Downstream) is reliable and the link from nodeB->OrignNode (upstream) is not reliable then nodeB won't multicast the control messages. With this case, data transmission for RREQ-Instance from TargNode to OrgNode is not possible.

Once the TargNode receive the RREQ-Instance with “S=1” then RREP-Instance is unicast back to OrigNode in symmetrical links. 

When the “S” bit is set to “0” by any intermediate node during RREQ-Instance then it can’t be changed to “1” by another intermediate node on the way towards Destination. Hence, TargNode will initiate another RREQ-Instance multicast towards OrgNode for S=0. 

Currently, RPL[RFC6550] use the Rank (ETX) in Objective Function Zero (OF-0) to check the bi-directional symmetric link reliability during network formation. The ETX functionality could be revised to check for both Symmetric(S=0) and Asymmetric(S=1) link reliability. Furthermore, EAR [On Accurate and Asymmetry-aware Measurement of Link Quality in Wireless Mesh Networks] metric can also be used to check for uni-directional and bi-directional link reliability. Performance of EAR is tested in both simulations (Ns-2) and Linux-based testbed.

> 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 [] 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 mailing list