Re: Reducing the battery impact of ND

"cb.list6" <> Sat, 11 January 2014 17:47 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C9FF81AE097 for <>; Sat, 11 Jan 2014 09:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id s0-KFS0n-5zF for <>; Sat, 11 Jan 2014 09:47:27 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c00::22f]) by (Postfix) with ESMTP id 279DA1AE070 for <>; Sat, 11 Jan 2014 09:47:26 -0800 (PST)
Received: by with SMTP id m15so2241780wgh.26 for <>; Sat, 11 Jan 2014 09:47:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R7mN1zCUhYsfuT891lEBwF/FOnJGjORwdlqjU5EXDtQ=; b=iXpCjbKl2DOUKGr7qQtYDVFsIdLL/gOOusARamFV+ZkBekXMiofpok2DFlse5s7ED1 oUX3+9cJYE2Jtr0261LJUazpTP9jmA9LaXMmYtPag+pAzWiPZiQb3JbtvlVlYzw2Ekod WNNlQn2odFaozpE2Vo/mW6SngqBCDK7s+PY0GJXKYSBUp7dBlla7jc4ezh/7gvCTopKq 7dwntI3FZ3C/63jgV62K1dGL77QfUQuIknbzE7bTASClnKjSTCbtpitHYtrIU7tb/4qB VdQMNY0QH44QHe9pahCO3WK2Ji2ypbj3cCGFgedalkYPeEuJ1v4ur6IyEwuqLYBwHX1W KnsA==
MIME-Version: 1.0
X-Received: by with SMTP id g7mr14187916wjr.37.1389462436444; Sat, 11 Jan 2014 09:47:16 -0800 (PST)
Received: by with HTTP; Sat, 11 Jan 2014 09:47:16 -0800 (PST)
Received: by with HTTP; Sat, 11 Jan 2014 09:47:16 -0800 (PST)
In-Reply-To: <EMEW3|2a5cad910dfa2e68d1809f030d2e9d5aq0AHNH03tjc||>
References: <> <> <EMEW3|2a5cad910dfa2e68d1809f030d2e9d5aq0AHNH03tjc||>
Date: Sat, 11 Jan 2014 09:47:16 -0800
Message-ID: <>
Subject: Re: Reducing the battery impact of ND
From: "cb.list6" <>
To: Tim Chown <>
Content-Type: multipart/alternative; boundary="047d7b86cfbcf401c804efb56e9c"
Cc: 6man Chairs <>, 6man WG <>, Andrew 👽 Yourtchenko <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 11 Jan 2014 17:47:29 -0000

I don't have much to offer this thread yet from a technical solution
perspective, but i can share that Samsung and others deactivate ipv6 when
the smartphone screen is off due to battery issues with ipv6 and wifi.

This is not for anyone to judge, this is a problem statement and the
current solution deployed on 10s (100s) of millions of hosts that go from
dual-stack to single stack when the screen is off. We do do quantitative
battery drain studies, and the ipv6-off configuration is meaningful better.

These phones do a fair amount of background traffic to major ipv6 enabled
clouds (google , facebook, yahoo ...) when the screen is of, so that is an
ipv6 opportunity missed ... we need a better solution to take to the
smartphone oems so they can keep ipv6 on and still meet the battery drain

We already know home routers dont get upgraded ever, so a client based
solution would be nice.  Said another way, i can help drive deployment of a
client based solution.