Re: [v6ops] draft-ietf-v6ops-reducing-ra-energy-consumption WGLC

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 28 August 2015 14:57 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67AA71A86FF for <v6ops@ietfa.amsl.com>; Fri, 28 Aug 2015 07:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 0O2EpydueFtZ for <v6ops@ietfa.amsl.com>; Fri, 28 Aug 2015 07:57:47 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D7C51A92F6 for <v6ops@ietf.org>; Fri, 28 Aug 2015 07:57:47 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t7SEvjrq026258 for <v6ops@ietf.org>; Fri, 28 Aug 2015 16:57:45 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5DCB4200E41 for <v6ops@ietf.org>; Fri, 28 Aug 2015 17:02:10 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5606E200D99 for <v6ops@ietf.org>; Fri, 28 Aug 2015 17:02:10 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t7SEvhrw017754 for <v6ops@ietf.org>; Fri, 28 Aug 2015 16:57:45 +0200
To: v6ops@ietf.org
References: <201508231800.t7NI011E029031@irp-lnx1.cisco.com> <55DF0CEB.5040500@globis.net> <55DF12E0.6040603@gmail.com> <CAPi140NBoatOEdhxtxm1PsWVb5gQSWqauC+Rx7aW6k+6=HdESg@mail.gmail.com> <55DF32C1.6000504@gmail.com>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <55E076E7.5040305@gmail.com>
Date: Fri, 28 Aug 2015 16:57:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55DF32C1.6000504@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/UYKT5sA5PBXjCyi96sdiMp-WGr0>
Subject: Re: [v6ops] draft-ietf-v6ops-reducing-ra-energy-consumption WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2015 14:57:50 -0000


Le 27/08/2015 17:54, Alejandro Acosta a écrit :
> Hello Andrew, Inline:
>
> El 8/27/2015 a las 11:01 AM, Andrew 👽 Yourtchenko escribió:
>> Hello Alejandro,
>>
>> On 8/27/15, Alejandro Acosta <alejandroacostaalamo@gmail.com>
>> wrote:
>>> Hello, I fully support this draft, in fact, I believe that all
>>> draft should have a mandatory "Eco-friendly" section.
>>>
>>> My comments:
>>>
>>> In section 3 - Consequences
>>>
>>>
>>> o  Some hosts simply experience bad battery life on these
>>> networks and otherwise operate normally.  This is frustrating for
>>> users of these networks.
>>>
>>>
>>> The sentence: "This is frustrating for users of   these
>>> networks." does not convince me. The impact of a bad battery life
>>> is quite big, to say it's just "frustrating" IMHO is not enough.
>>> I think it should be remove or create a stronger sentence.
>> If Lorenzo agrees, I'd opt for removing the sentence about the
>> frustrated users.
>
> Perfect
>
>>
>>>
>>> In section 4.2:
>>>
>>>
>>> 2.  Networks that serve large numbers (tens or hundreds) of
>>> battery- powered devices SHOULD enable this behaviour.
>>>
>>>
>>> This might be a dummy question but I wonder if this is automatic
>>> or something that will be adjusted by the administrator (or
>>> both). Probably we could be more specific in this section, I
>>> mean, just to be more clear.
>> Yeah, looks like this text needs tweaking - both you and Ray has
>> commented on it, copypasting from my reply to him, so to check
>> with you:
>>
>> How about a small tweak as below:
>>
>> "2) Administrators of networks that serve large numbers (tens or
>> hundreds) of battery- powered devices SHOULD enable this
>> behaviour."
>
> It sounds ok to me. In the future (and not that far away) another
> draft could be written about making routers smarter..,

The link-layers should be smarter, not the Routers.  The link-layers
should have link-layer messages about expressing interest in joining
link-layer multicast groups (have mssages, not just API primitives).

Alex

  I mean, they can recognize the number of
> devices in the network (in your example tens or hundreds) and change
> the behavior automatically to your draft. It looks feasible to me.
>
> Regards,
>
>
>>
>> --a
>>
>>
>>>
>>> Regards,
>>>
>>> Alejandro,
>>>
>>> El 8/27/2015 a las 8:43 AM, Ray Hunter (v6ops) escribió:
>>>>
>>>> fred@cisco.com wrote:
>>>>> This is to initiate a two week working group last call of
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-reducing-ra-energy-consumption.
>>>>>
>>>>>
>>>>>
Please read it now. If you find nits (spelling errors, minor suggested
>>>>> wording changes, etc), comment to the authors; if you find
>>>>> greater issues, such as disagreeing with a statement or
>>>>> finding additional issues that need to be addressed, please
>>>>> post your comments to the list.
>>>>>
>>>>> We are looking specifically for comments on the importance of
>>>>> the document as well as its content. If you have read the
>>>>> document and believe it to be of operational utility, that is
>>>>> also an important comment to make.
>>>>>
>>>>>
>>>> I have read this draft. I understand the motivation, it is
>>>> clearly written, and I support it.
>>>>
>>>> Minor Suggestions:
>>>>
>>>> I'd reference 4861 in the first sentence of the intro.
>>>> s/Routing information is communicated to IPv6 hosts by Router
>>>> Advertisement messages. /Routing information is communicated to
>>>> IPv6 hosts by Router Advertisement messages [RFC4861]/
>>>>
>>>> Recommendation 2 is redundant IMHO. THere's no way a router
>>>> manufacturer can really know if the devices it is serving are
>>>> battery powered devices or not (perhaps the subject of another
>>>> draft e.g. perhaps extension to 4620 to discover this via NI on
>>>> creating a new ND cache entry?)
>>>>
>>>> For recommendation 3: the timing recommendations should be
>>>> more concrete, provided rough consensus can be achieved. In
>>>> order to maximize the benefit I'd suggest specifying the upper
>>>> end of the suggested ranges.
>>>>
>>>> s/Networks that serve battery-powered devices /Routers with
>>>> network interfaces that are known to serve battery-powered
>>>> devices/
>>>>
>>>>
>>>>
>>>> -- regards, RayH
>>>> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>>>>
>>>>
>>>>
>>>>
_______________________________________________
>>>> v6ops mailing list v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>