Re: [v6ops] Interest in energy consumption of IPv6 smartphones (vs. IPv4)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 02 June 2016 08:33 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 120D212B04A for <v6ops@ietfa.amsl.com>; Thu, 2 Jun 2016 01:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level:
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 b4SINX0iDGtQ for <v6ops@ietfa.amsl.com>; Thu, 2 Jun 2016 01:33:50 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B480612B038 for <v6ops@ietf.org>; Thu, 2 Jun 2016 01:33:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u528XjX8025366; Thu, 2 Jun 2016 10:33:45 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E217E205AD2; Thu, 2 Jun 2016 10:34:07 +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 D535F205AD1; Thu, 2 Jun 2016 10:34:07 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u528Xjmp003962; Thu, 2 Jun 2016 10:33:45 +0200
To: "Fred Baker (fred)" <fred@cisco.com>
References: <20160211191203.4120F180472@rfc-editor.org> <5099e169-696d-54ec-a4a7-8cc773e358c5@gmail.com> <4B8679AA-6FA4-4D9F-A7DD-C8DD6F525EC6@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5fcbf830-fc25-7394-5c8a-55dc9189b462@gmail.com>
Date: Thu, 02 Jun 2016 10:33:45 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <4B8679AA-6FA4-4D9F-A7DD-C8DD6F525EC6@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/xYzB1SKroGWhIWF536jYSm1mq6M>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Interest in energy consumption of IPv6 smartphones (vs. IPv4)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 02 Jun 2016 08:33:53 -0000

Le 01/06/2016 à 18:13, Fred Baker (fred) a écrit :
> I personally would find that interesting. As you note, we recently
> posted an RFC about managing power by managing activity. Andrew
> Yourtchenko has been interested in the chattiness of IPv6
> implementations in WiFi, the issue being that it is a shared medium
> (not unlike an Ancient yellow Ethernet cable, and very unlike a
> switched network), so every hiccup reverberates throughout the
> network. I would expect that the issue affects mobile wireless in
> interesting ways. How chatty are we, and what needs to be adjusted?

It would be interesting to look at how IPv6 link and network protocol
behaviour may consume more or less energy.  ND efficiency,
energy-efficient IP paths in access and core networks, path-energy
discovery: are topics very interesting to explore.

Other operational question may be whether the full use of IPv6 on a
smartphone (disable IPv4) draws its battery more, less, or just as when
only IPv4 is used.  It may need some measurement of application
behaviour.  Recently energy-specific APIs became available on smartphone
OSs, supposing they're working ok on IPv6.

> Do you have something to share?

Well not at this time.  We are currently exploring the
application-specific measurement part with a few people.  Maybe that can
lead to an Internet Draft.

Alex


>
>> On Jun 1, 2016, at 5:40 AM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com> wrote:
>>
>> Hi v6ops,
>>
>> I wonder whether there may be interest in evaluating the energy
>> consumption of an IPv6 application on smartphones, compared to its
>> IPv4 counterpart.
>>
>> I suspect the difference may be negligible but I am not sure.
>>
>> It would be good to avoid a situation in which the end user
>> prefers IPv4 on the smartphone because IPv6 empties the battery.
>>
>> Alex
>>
>> Le 11/02/2016 à 20:12, rfc-editor@rfc-editor.org a écrit :
>>> A new Request for Comments is now available in online RFC
>>> libraries.
>>>
>>> BCP 202 RFC 7772
>>>
>>> Title:      Reducing Energy Consumption of Router Advertisements
>>>  Author:     A. Yourtchenko, L. Colitti Status:     Best Current
>>> Practice Stream:     IETF Date:       February 2016 Mailbox:
>>> ayourtch@cisco.com, lorenzo@google.com Pages:      6 Characters:
>>> 12555 See Also:   BCP 202
>>>
>>> I-D Tag: draft-ietf-v6ops-reducing-ra-energy-consumption-03.txt
>>>
>>> URL:        https://www.rfc-editor.org/info/rfc7772
>>>
>>> DOI:        http://dx.doi.org/10.17487/RFC7772
>>>
>>> Frequent Router Advertisement messages can severely impact host
>>> power consumption.  This document recommends operational
>>> practices to avoid such impact.
>>>
>>> This document is a product of the IPv6 Operations Working Group
>>> of the IETF.
>>>
>>>
>>> BCP: This document specifies an Internet Best Current Practices
>>> for the Internet Community, and requests discussion and
>>> suggestions for improvements. Distribution of this memo is
>>> unlimited.
>>>
>>> This announcement is sent to the IETF-Announce and rfc-dist
>>> lists. To subscribe or unsubscribe, see
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>>
>>> For searching the RFC series, see
>>> https://www.rfc-editor.org/search For downloading RFCs, see
>>> https://www.rfc-editor.org/retrieve/bulk
>>>
>>> Requests for special distribution should be addressed to either
>>> the author of the RFC in question, or to
>>> rfc-editor@rfc-editor.org.  Unless specifically noted otherwise
>>> on the RFC itself, all RFCs are for unlimited distribution.
>>>
>>>
>>> The RFC Editor Team Association Management Solutions, LLC
>>>
>>>
>>
>> _______________________________________________ v6ops mailing list
>>  v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>