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

"Heatley, Nick" <nick.heatley@ee.co.uk> Thu, 02 June 2016 11:02 UTC

Return-Path: <nick.heatley@ee.co.uk>
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 9AAF712D68C for <v6ops@ietfa.amsl.com>; Thu, 2 Jun 2016 04:02:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.245
X-Spam-Level:
X-Spam-Status: No, score=-1.245 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no 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 UG3D9Nxywmfy for <v6ops@ietfa.amsl.com>; Thu, 2 Jun 2016 04:02:29 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6934712D153 for <v6ops@ietf.org>; Thu, 2 Jun 2016 04:02:08 -0700 (PDT)
Received: from [85.158.137.67] by server-12.bemta-3.messagelabs.com id CD/D8-21858-E2210575; Thu, 02 Jun 2016 11:02:06 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHKsWRWlGSWpSXmKPExsUy9d9HH11doYB wg6mbzSxOnnnCZvF+ViOrxc3/01gsTh/by+zA4nFt0w9mj52z7rJ7LFnykymAOYo1My8pvyKB NeP9gTtsBXdeMVY8n/6UuYHxxHPGLkYuDiGBTYwS33csYYJwDjBKzHixHCpzklFi8Z5lQA4nB 5uArkT7rFXMIAkRgRZGiZNbl7N1MXJwMAuoSsz+ww9SIywQLPGv6xo7iC0iECIx69JkRgjbSW LLo5ksIOUsAioSuxfJg4R5BUIl1nXfYIHYdZhJ4v7OSWC9nALWEtvXfWUFsRkFZCW+NK5mBrG ZBcQlbj2ZzwRiSwgISCzZc54ZwhaVePn4HyuErSBxaVEXK0R9nsSDF9vYIZYJSpyc+YRlAqPI LCSjZiEpm4WkbBbYZ5oS63fpQ5QoSkzpfsgOYWtItM6Zy44svoCRfRWjRnFqUVlqka6hiV5SU WZ6RkluYmaOrqGBsV5uanFxYnpqTmJSsV5yfu4mRmBcMgDBDsYV2z0PMUpyMCmJ8q4s8w8X4k vKT6nMSCzOiC8qzUktPsQow8GhJMErJhgQLiRYlJqeWpGWmQNMEDBpCQ4eJRHeqQJAad7igsT c4sx0iNQpRl2OHx331zIJseTl56VKifOqgMwQACnKKM2DGwFLVpcYZaWEeRmBjhLiKUgtys0s QZV/xSjOwagkzGsAMoUnM68EbtMroCOYgI4oeOQPckRJIkJKqoFxX8isiwvifq2NdrinqeSw9 bbQ3RptuX+/zNrui3PbXrtaey5TRDLl/rSJLlFBB76cY1WeEjAxvnrGJ83tqSH/ml+fj2y3P/ ib/9Cp2RnzH0xXnc7Aknii7+u59yrNnMWv5gncrQr/IDl538tzpR/fCD7J6L1oyFn0UHtvUL7 Ggelt5/nPvr7QoMRSnJFoqMVcVJwIAC2SKrVRAwAA
X-Env-Sender: nick.heatley@ee.co.uk
X-Msg-Ref: server-8.tower-139.messagelabs.com!1464865324!22030264!1
X-Originating-IP: [149.254.241.76]
X-StarScan-Received:
X-StarScan-Version: 8.34; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9258 invoked from network); 2 Jun 2016 11:02:05 -0000
Received: from unknown (HELO smtpml01.ee.co.uk) (149.254.241.76) by server-8.tower-139.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jun 2016 11:02:05 -0000
Received: from EEUKWV0940.EEAD.EEINT.CO.UK (Not Verified[10.246.209.217]) by smtpml01.ee.co.uk with MailMarshal (v7, 2, 3, 6978) id <B575012250000>; Thu, 02 Jun 2016 12:01:57 +0100
Received: from UK31S005EXS02.EEAD.EEINT.CO.UK (Not Verified[10.246.208.27]) by EEUKWV0940.EEAD.EEINT.CO.UK with Trustwave SEG (v7, 3, 6, 7949) id <B575012290006>; Thu, 02 Jun 2016 12:02:01 +0100
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK31S005EXS02.EEAD.EEINT.CO.UK ([2002:1ef6:d01b::1ef6:d01b]) with mapi id 14.03.0195.001; Thu, 2 Jun 2016 12:01:43 +0100
From: "Heatley, Nick" <nick.heatley@ee.co.uk>
To: Olivier MJ Crepin-Leblond <ocl@gih.com>, Nabil Benamar <benamar73@gmail.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
Thread-Topic: [v6ops] Interest in energy consumption of IPv6 smartphones (vs. IPv4)
Thread-Index: AQHRvKmNmZCWV24cdEKeI3apVfQaQp/V2pkAgAAMj4CAABoVQA==
Date: Thu, 02 Jun 2016 11:01:42 +0000
Message-ID: <6536E263028723489CCD5B6821D4B2131714501A@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <20160211191203.4120F180472@rfc-editor.org> <5099e169-696d-54ec-a4a7-8cc773e358c5@gmail.com> <4B8679AA-6FA4-4D9F-A7DD-C8DD6F525EC6@cisco.com> <5fcbf830-fc25-7394-5c8a-55dc9189b462@gmail.com> <CAMugd_V-=2woJZPQUSzDYacxZVSW-9H5S8x5Qx=VxNc5_iGerQ@mail.gmail.com> <093d3a00-a2cc-c6d9-8939-56114eb4a461@gih.com>
In-Reply-To: <093d3a00-a2cc-c6d9-8939-56114eb4a461@gih.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.246.208.5]
Content-Type: multipart/alternative; boundary="_000_6536E263028723489CCD5B6821D4B2131714501AUK30S005EXS06EE_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/H_NzW1g9DbLib12wzEV52k75eJE>
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 11:02:33 -0000

Hi, (other than avoiding RA time issues) do the real benefits come when apps are changed, less session keepalives in a nat-free environment?
It is all about the apps opportunity. They need to behave differently when IPv6-only.
Nick

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Olivier MJ Crepin-Leblond
Sent: 02 June 2016 11:22
To: Nabil Benamar; Alexandre Petrescu
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Interest in energy consumption of IPv6 smartphones (vs. IPv4)

Hello all,

it is also worth noting that 3G & 4G in particular appears to drain battery more than 2G. Results could be flawed because due to novelty, in most places 4G signal strength is not yet at the level of 2G or 3G signal strength. A study under controlled environment would be somehow interesting indeed although I fail to see the end goal for performing such a study? Do we want to prove that longer addresses mean more power requirements? I would have thought the end point really relates to chipset architecture, not bits transmitted.
Kindest regards,

Olivier
On 02/06/2016 11:37, Nabil Benamar wrote:
Hi All,

Since there is no dual stack on 3g/4g in my side, I can only test with wifi. Create a tunnel with HE.net for example and then connect a smartphone on IPv6 only..make the measurements and then switch to IPv4 only repeat the steps.....energy measurements are application specific!

I would like to ask the members of the list which is the best application to use for energy consumption on Android ?

It would also be interesting to measure with different mobile OS !

Best regards
Nabil Benamar
-------------------
نبيل بنعمرو

http://nabilbenamar.ipv6-lab.net/

On Thu, Jun 2, 2016 at 9:33 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>> wrote:
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<mailto: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<mailto: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<mailto:ayourtch@cisco.com>, lorenzo@google.com<mailto: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<mailto: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<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops


_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops





_______________________________________________

v6ops mailing list

v6ops@ietf.org<mailto:v6ops@ietf.org>

https://www.ietf.org/mailman/listinfo/v6ops



--

Olivier MJ Crépin-Leblond, PhD

http://www.gih.com/ocl.html

NOTICE AND DISCLAIMER
This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. 
If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. 
If you've received this email in error, please let me know immediately on the email address above. Thank you.

We monitor our email system, and may record your emails.

EE Limited 
Registered office:Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW
Registered in England no: 02382161

EE Limited is a wholly owned subsidiary of:

British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000