Re: Iotdir early review of draft-ietf-lwig-energy-efficient-07

Zhen Cao <zhencao.ietf@gmail.com> Tue, 29 August 2017 04:00 UTC

Return-Path: <zhencao.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0225132732; Mon, 28 Aug 2017 21:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 o8OYKc9wBHVd; Mon, 28 Aug 2017 21:00:42 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77EA31326F4; Mon, 28 Aug 2017 21:00:41 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id 104so7036257uas.1; Mon, 28 Aug 2017 21:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yJgiNE2BEFFs+yXcH+0Y1Sp0YYNrDg16E95h8FMlWgE=; b=FQ3+CxKRcoX/TqjbVrtXKlI3K7KgfOghEpUk5epLnrDNoS8pFcL862jZo11N6d343y pRIrtisiR1PrNeISe9VwCC+srNz8B9w1g8hQMoWDZvZmCnr9SoDPKvD5v9fVYAERJ1w6 Q/tIgh6LWs8HGB7YChKf1RER+DRaMRkozdkteDkurm7j4sWnVY0eCykIKieWRhFWxz5H 4yeSW4TVR7HSnkzlMh6m0ZvsI5EWRzlB5bJ+INNix3H9wS7OGIfDR6RkOHmi/LRalLmD u02FvR2/W1mUJPb11KdEAr3emAn91CdkvWndv0tTXZbCid8ypDwvuvnRb/S0Ab9K2fCv CY2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yJgiNE2BEFFs+yXcH+0Y1Sp0YYNrDg16E95h8FMlWgE=; b=n9W0JvBJ3T6iUFcIPeTe98z0jjlOYyq1FKJC3NXyU0af7Un2la4baMwc/znjCImWyh /sAsr7RhjZpVEtTM4R5GPw/gaIE/PtqZE4bgBeJGIOXY7CiLuSXR6QNhXvC+8VPYuJFZ 6Ml7wkes1b2bGH12D4uoRmCmkf09gJgb7crf456e4Qbw+jOHlh2rzN3+jLGI2qJvrhkt W2MeqYdinxaRtXlc5AmY8AQd44fynjfNJw+BBHvA9tk2MTbGBLcUwqgAPQx7HOBSe+FA +lk9cTrk95qoCbPnJMpZoWjeQZ0g46zY5ruxFpygVmpeIoVu12akjyg0Nvex8VhY2M9H t9IQ==
X-Gm-Message-State: AHYfb5hKws3wCFDPk7xBELqggC7VbDmQMQ7qzSD09xouE2S2QnhpXWlh HuCi8Vktr6KQSIM+gGrmXXk0oE2I08FWtj0=
X-Received: by 10.176.82.78 with SMTP id j14mr1804901uaa.158.1503979240599; Mon, 28 Aug 2017 21:00:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.41.161 with HTTP; Mon, 28 Aug 2017 21:00:40 -0700 (PDT)
In-Reply-To: <150116690760.11487.2065170484353080456@ietfa.amsl.com>
References: <150116690760.11487.2065170484353080456@ietfa.amsl.com>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Tue, 29 Aug 2017 12:00:40 +0800
Message-ID: <CAFxP68w_Qf5Q3=uJ50wOeGGk-WP5ca15iK1AUVHM6xcLVx4=9Q@mail.gmail.com>
Subject: Re: Iotdir early review of draft-ietf-lwig-energy-efficient-07
To: Charles Perkins <charlie.perkins@huawei.com>
Cc: Iot-dir@ietf.org, lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-energy-efficient.all@ietf.org, charliep@computer.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JHrtipQSxclGnY11ZfrWoFiqAQM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Aug 2017 04:00:44 -0000

Thank you so much, Charlies, for the review, and the valuable comments
for us to improve the draft.

We will come up with wording proposals shortly.

Many thanks,
Zhen

On Thu, Jul 27, 2017 at 10:48 PM, Charles Perkins
<charlie.perkins@huawei.com> wrote:
> Reviewer: Charles Perkins
> Review result: On the Right Track
>
> [Please excuse if this is a duplicate.  I got an error from datatracker on my first attempt.]
>
> Overall comments:
>
> I think that some important techniques for energy efficiency deserve mention
> or significant enlargement:
>
> - Packet bundling
> - Data aggregation
> - Power management / range reduction
> - Fragmentation is more energy-efficient at lower layers than at higher layers
> - Compression, on the other hand, is more efficient at higher layers,
>   particularly before encryption.
>
> The document needs a concise statement of purpose.  Maybe insert the
> following after the first paragraph of the Introduction:
>
>    In this document we describe techniques that are in common use at Layer 2
>    and at Layer 3, and we indicate the need for higher-layer awareness of
>    lower-layer features.
>
> Also in the introduction, some discussion is needed about cross-layer design.
> Is cross-layer design in scope for the [lwig] Working Group?
>
> In figure 1 and elsewhere, it should not be assumed that RPL is the only
> choice for routing in energy-efficient networks.  So, for instance,
> "RPL" could be replaced by "RTG" in Figure 1.
>
> Shouldn't there be an entry for synchronized reception in Figure 2?  Isn't
> Figure 2 actually a table, and thus should be labeled Table 1?
>
> Section 3.3 (Throughput) does not seem to add much if anything to the
> discussion.  The conclusion about the trade-off is quite obvious.
>
> Particularly in section 3.5.2, but also elsewhere, some examples would
> be very helpful.
>
> Section 6.3 (CoAP timers) seems to be only about one timer.
> Are there more?  What about interactions with TCP timers, etc.?
>
> Section 7 should be entitled "Summary and Conclusions".
> In section 7, it would be nice to offer cross references for each
> conclusion, referring the reader to the relevant section of the document.
> Each conclusion should follow from some previous section of the document.
> Unfortunately that currently isn't quite the case.
>
> The citation [Announcementlayer] does not appear in the body of the article.
>
> There are weird line breaks appearing at certain random points in the
> document.
>
> I have editorial suggestions and corrections which I will
> supply as an rfcdiff file under separate email.
>
> Regards,
> Charlie P.
>