Re: [Roll] "Charter inclusion: Work in Routing proposals: AODV_RPL - > DAO_Projection"

Mingui Zhang <zhangmingui@huawei.com> Mon, 29 August 2016 08:44 UTC

Return-Path: <zhangmingui@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 CE0CC12D14B for <roll@ietfa.amsl.com>; Mon, 29 Aug 2016 01:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.769
X-Spam-Level:
X-Spam-Status: No, score=-4.769 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=-0.548, 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 WJnhn8uyI4jt for <roll@ietfa.amsl.com>; Mon, 29 Aug 2016 01:44:07 -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 57FD812D144 for <roll@ietf.org>; Mon, 29 Aug 2016 01:44:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQH62964; Mon, 29 Aug 2016 08:44:02 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 29 Aug 2016 09:44:01 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.6]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Mon, 29 Aug 2016 16:43:54 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] "Charter inclusion: Work in Routing proposals: AODV_RPL - > DAO_Projection"
Thread-Index: AQHR9GXAQKfqVq8KfEGSljCkUp5AHaBfn/Kw
Date: Mon, 29 Aug 2016 08:43:53 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A62ED666@NKGEML515-MBS.china.huawei.com>
References: <5ac3960df196482c01fc272d9164012a@xs4all.nl> <5795E3B9.4000802@ericsson.com> <50d0bcdd18ff300aaf1e183f6751c492@xs4all.nl> <5795F37C.1050303@ericsson.com> <7aff23749031ebe9e839e0aa9ac3c1db@xs4all.nl> <9b78090fa7c3a958fac60b5759659220@xs4all.nl>
In-Reply-To: <9b78090fa7c3a958fac60b5759659220@xs4all.nl>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.146.93]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.57C3F5D2.0130, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.6, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8228d842032b585584066b0668c151e3
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/HWwJKpK_NMCU7vricxevo3tcVtk>
Subject: Re: [Roll] "Charter inclusion: Work in Routing proposals: AODV_RPL - > DAO_Projection"
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, 29 Aug 2016 08:44:11 -0000

I support both.

For F: draft-thubert-roll-dao-projection-02

1) When I first read the Abstract, I thought the purpose of this draft is to only enable loose source routing (non-storing mode) down the DODAG. However, after I read the last 4 paragraphs of the Introduction, I realize the protocol extension specified in this draft can also benefit the storing mode.

2) page 10 last paragraph
s/the lest router in the path/the last router in the path/

3) In the paragraph underneath of Figure 5, there is a unfinished sentence.
OLD
   The process recurses till the destination which sends a DAO-ACK to
   the root.  In the example above, for target D, the list of via
   options is S, A, B and C.  The projected DAO is sent by the root to
NEW
   In the example above, the projected DAO is sent by the root to target D.  The list of via
   options is S, A, B and C.  D removes the last Via Option and passes the DAO to C.

4) The paragraph underneath of Figure 6 repeats the previous paragraph.
OLD
   The process recurses till the destination which sends a DAO-ACK to
   the root.  In the example above, for target D, the list of via
   options is S, A, B and C.  The projected DAO is sent by the root to
NEW
   The process recurses till S which sends a DAO-ACK to
   the root.

5) If changes 3) & 4) make sense, the following sentence is to be appended to the last paragraph on page 10.
The process recurses till the first router in the path; the first router sends a DAO-ACK to the root.

6) Underneath Figure 7, some concluding words are needed.

Thanks,
Mingui

> -----Original Message-----
> From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of peter van der Stok
> Sent: Friday, August 12, 2016 2:50 PM
> To: Roll
> Subject: [Roll] "Charter inclusion: Work in Routing proposals: AODV_RPL - >
> DAO_Projection"
> 
> Dear all,
> 
> Following the ROLL Meeting at IETF 96, we would like to know your opinion about
> the drafts, presented during IETF95 and IETF96. This the last set of three
> messages. The adoption of drafts as WG drafts will be asked independently
> dependent on the status of the draft.
> 
> Please, do answer to the three messages before 2 September 2016.
> 
> 
>   F: draft-thubert-roll-dao-projection-02
>       Root initiated routing state in RPL
> 
> •    Is the draft relevant to the working group.?
> •    Do you foresee to contribute to the work described in the draft ?
> •    Are you willing to review the draft ?
> •    Should the draft be rejected by the WG ?
> 
> 
>   G: draft-satish-roll-aodv-rpl-00
>         Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs)
> 
>   •    Is the draft relevant to the working group.?
>   •    Do you foresee to contribute to the work described in the draft ?
>   •    Are you willing to review the draft ?
>   •    Should the draft be rejected by the WG ?
> 
> 
> It would be nice to know the reasons why you agree or disagree with the drafts
> 
> 
> Thank you very much,
> 
> 
>   Peter and Ines
> 
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll