[Roll] No path DAO problem stmt draft

"Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)" <rahul.jadhav@huawei.com> Wed, 02 March 2016 14:10 UTC

Return-Path: <rahul.jadhav@huawei.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872341B2AF6 for <roll@ietfa.amsl.com>; Wed, 2 Mar 2016 06:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=unavailable
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 3wp-fAr-hr5C for <roll@ietfa.amsl.com>; Wed, 2 Mar 2016 06:10:45 -0800 (PST)
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 88E501B2AB5 for <roll@ietf.org>; Wed, 2 Mar 2016 06:04:18 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CJL01445; Wed, 02 Mar 2016 14:04:16 +0000 (GMT)
Received: from BLREML406-HUB.china.huawei.com (10.20.4.43) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 2 Mar 2016 14:04:14 +0000
Received: from BLREML510-MBS.china.huawei.com ([169.254.2.93]) by BLREML406-HUB.china.huawei.com ([10.20.4.43]) with mapi id 14.03.0235.001; Wed, 2 Mar 2016 19:34:05 +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: No path DAO problem stmt draft
Thread-Index: AdF0jF/v4O3xW+LCQPupRYViUwm4pA==
Date: Wed, 2 Mar 2016 14:04:05 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5CEC8E5C@blreml510-mbs.china.huawei.com>
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: multipart/alternative; boundary="_000_982B626E107E334DBE601D979F31785C5CEC8E5Cblreml510mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.56D6F2E0.01CA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.93, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 91c355a912352b81f15fb14001993e3d
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/SxtcGQ5Ypme35uLOVHdvum2Uuj0>
Subject: [Roll] No path DAO problem stmt draft
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Mar 2016 14:10:46 -0000

Dear All,

We recently submitted a draft (https://tools.ietf.org/html/draft-jadhav-roll-no-path-dao-ps-00) stating problem statements pertaining to No Path DAO messaging in RPL spec.

The primary pain point that is highlighted is that the No-Path DAO messaging takes a path which has a higher probability of not been available. For e.g. when the node switches its parent, a No-Path DAO is usually generated along the path through the previous parent and the No-Path DAO traverses upwards always along that path. A path which is no longer a preferred path is used for No-Path DAO messaging and thus the probability of No-Path DAO messaging failure is high, resulting in stale routing entries.

Also there are other negative implications mentioned in the document because of this messaging mode.

The work drafts the problem statement and explains requirements from solution point of view.

Kindly feedback if the problem statement impacts you.

Thanks,
Rahul


***************************************************************************************
This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!