Re: [manet] review of draft-dearlove-manet-olsrv2-rmpr-optimization-00

Jiazi Yi <yi.jiazi@gmail.com> Mon, 11 November 2013 11:15 UTC

Return-Path: <yi.jiazi@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AE211E8149 for <manet@ietfa.amsl.com>; Mon, 11 Nov 2013 03:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyqsW42cnb9Q for <manet@ietfa.amsl.com>; Mon, 11 Nov 2013 03:15:13 -0800 (PST)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 243C611E812F for <manet@ietf.org>; Mon, 11 Nov 2013 03:15:12 -0800 (PST)
Received: by mail-wg0-f52.google.com with SMTP id z12so3336315wgg.7 for <manet@ietf.org>; Mon, 11 Nov 2013 03:15:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=bVH5Jf3a0t+kEZOKFGj1sHKCuJGinQiiEJHRgtnTSpo=; b=i0O8IakUG3RZaMe89XzEHywxafLPAYubZDtpArHA9JlvAY0/GIcgoWZFG/Ty0MFBuE rfCaCwFXCfltRngdzx1nA2eYv6TH3YEiyKgy6J1KdLxkA19LA4fZ3/v3mVUyoqp40KoJ oWWXtYWDjcQZBlXwWoZVYRY0jMX/ho9xDUuVQU2FIKUKePyovzlEo3ddpKVqIjTjHSlF Hxb3uxBKG+tCIr2iVTQ6YeVPZb5gVYhD3r+m9YgvHmcTB6xMwN7cEbRxte2SDZFSNahu wnJ1um/u13jMbkmKbAWQtlScINZNwuNUmI3xkvczyEaS2ZzwUAyP5/8G4Ihi3+5h/fj8 1tpA==
X-Received: by 10.181.13.20 with SMTP id eu20mr11891918wid.29.1384168512352; Mon, 11 Nov 2013 03:15:12 -0800 (PST)
Received: from jy-mac-pro.home (128-79-35-43.hfc.dyn.abo.bbox.fr. [128.79.35.43]) by mx.google.com with ESMTPSA id gg20sm34161895wic.1.2013.11.11.03.15.11 for <manet@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Nov 2013 03:15:11 -0800 (PST)
Message-ID: <5280BC3E.7000101@gmail.com>
Date: Mon, 11 Nov 2013 12:15:10 +0100
From: Jiazi Yi <yi.jiazi@gmail.com>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: MANET IETF <manet@ietf.org>
References: <5280BB8E.6000906@gmail.com>
In-Reply-To: <5280BB8E.6000906@gmail.com>
Content-Type: multipart/alternative; boundary="------------000205070804020600040605"
Subject: Re: [manet] review of draft-dearlove-manet-olsrv2-rmpr-optimization-00
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2013 11:15:14 -0000

And one nit:

In the reference, we have

    [RFC6966-to-be]
               Clausen, T., Dearlove, C., and P. Jacquet, "Rationale for
               the Use of Link Metrics in the Optimized Link State
               Routing Protocol Version 2 (OLSRv2)", RFC 6966, TBD 2013.

I suppose the name of the draft is

   Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol 
OLSRv2 - Rationale

http://tools.ietf.org/html/draft-ietf-manet-olsrv2-metrics-rationale-04 ?

Jiazi

> Jiazi Yi <mailto:yi.jiazi@gmail.com>
> 11 Nov 2013 12:12
> Hi,
>
> I had a review of draft-dearlove-manet-olsrv2-rmpr-optimization-00. 
> Here are some comments (or some of them, I would rather call questions :)
>
> 1. In Section 4: Routing MPR Selection
> ...
> then x_1 to x_n may be removed from the set of routing MPRs, if selected.
> ...
>
> The first note: I think we should use RFC2119 term "MAY" here?
> In fact, this is the part that confuses me most. As the only "action" 
> described in the draft, the use of "may" without further explanation 
> when this action should be taken or not is too vague. In the end of 
> the section, another "RECOMMENDED" is used. Therefore, if I put them 
> together, it is something like "It is RECOMMENDED that one MAY do foo, 
> bar..."
>
> 2.  If x_1, x_2 ... x_n are the largest set with corresponding y_1, 
> y_2, ... y_n. Should we check all the subsets {x_i} of x_1, ... x_n 
> with the criteria
>
> d1(x_0) + d2(x_0,y_1) + ... + d2(x_m-1,y_m) < d1(x_m) for m belong to 
> subset of x_1, ... x_n?
>
> If so, we probably will have a lot combinations to check in a dense 
> network. If not, the criteria seems to be too harsh to be actually 
> "triggered"?
>
>
> 3. Should this be applied to all types of metrics? A potential affects 
> of this draft is that, we can probably have more "hops" around the 
> neighborhood of the original router, i.e., there is higher possibility 
> of interference. In some of metrics, the interference is not much 
> considered (because it is hard to measure). Will it be a problem if we 
> introduce more transmission in some scenarios?
>
> 4. We have a "Willingness" value to "represents the router's 
> willingness to be selected as an MPR." Should this need to be 
> considered also? What about if x_0 has low willingness, while the 
> others x_1, ... x_n have higher willingness?
>
> 5. In some scenarios, we probably want to have certain redundancy in 
> MPR in some lossy scenarios?
>
> sincerely
>
> Jiazi
>
>
>