[recipe] Energy reduction / static management / dynamic management

Stuart Cheshire <cheshire@apple.com> Thu, 26 March 2009 07:48 UTC

Return-Path: <cheshire@apple.com>
X-Original-To: recipe@core3.amsl.com
Delivered-To: recipe@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 206F03A68EC for <recipe@core3.amsl.com>; Thu, 26 Mar 2009 00:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id I-eo9pu0yYxk for <recipe@core3.amsl.com>; Thu, 26 Mar 2009 00:48:37 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com []) by core3.amsl.com (Postfix) with ESMTP id 44EF53A680C for <recipe@ietf.org>; Thu, 26 Mar 2009 00:48:37 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com []) by mail-out3.apple.com (Postfix) with ESMTP id 8B09158F9AE2 for <recipe@ietf.org>; Thu, 26 Mar 2009 00:49:30 -0700 (PDT)
Received: from relay11.apple.com (unknown []) by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 75B64280AB for <recipe@ietf.org>; Thu, 26 Mar 2009 00:49:30 -0700 (PDT)
X-AuditID: 11807130-ac098bb000000fcd-32-49cb338ae4c5
Received: from elliott.apple.com (elliott.apple.com []) by relay11.apple.com (Apple SCV relay) with ESMTP id 518D028092 for <recipe@ietf.org>; Thu, 26 Mar 2009 00:49:30 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from dhcp-42c9.meeting.ietf.org (dhcp-42c9.meeting.ietf.org []) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KH300H5JSEHWB00@elliott.apple.com> for recipe@ietf.org; Thu, 26 Mar 2009 00:49:30 -0700 (PDT)
Message-id: <F6B5B6E7-8DBE-4473-9592-433430988914@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
To: recipe@ietf.org
Date: Thu, 26 Mar 2009 00:49:29 -0700
X-Mailer: Apple Mail (2.930.3)
X-Brightmail-Tracker: AAAAAA==
Subject: [recipe] Energy reduction / static management / dynamic management
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/recipe>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 07:48:38 -0000

Some quick thoughts after tonight's dinner:

Here are three (certainly not the only three) broad themes we might  
want to think about.

1. Simple reduction of absolute energy usage. There are two aspects to  
this, measurement and control.

1a. Measurement -- allowing people to determine where energy is going  
in their homes. This alone is an important part of enabling people to  
save energy, by knowing where they're using energy. The first step to  
replacing your refrigerator with a more efficient one is discovering  
that your current refrigerator is using too much energy. I'd like to  
see a world where every power outlet or light switch includes a power  
meter, which can be interrogated over the network to find out how much  
power is being drawn from it at any moment.

1b. Control. For example, using less energy by automatically turning  
off lights in unoccupied rooms. Here the theme is not more efficient  
devices, but less use of the devices you have.

2. Time-sensitive use of energy. When the electricity company charges  
more for peak-time usage, signaling refrigerator compressors, air  
conditioning, hot tub heating, electric car charging, and similar high- 
load devices to try to limit their consumption during peak time can  
reduce the peak load on the electricity grid, and reduce the  
customer's electricity bill, even though the total energy consumption  
may be the same. The difference here is that you're not trying to  
reduce your hot tub heater's total energy consumption, you're trying  
to control *when* it consumes that energy.

3. Dynamic adaptation to current spot pricing. This is an extension of  
(2). Whereas in (2) the peak and off-peak hours for each day of the  
week are published well in advance, with spot pricing the  
instantaneous price of one kWh is not published in advance, but  
instead is announced in an hour-by-hour or even minute-by-minute  
basis, according to current demand. The difference between this and  
case (2) is that case (2) can be handled entirely within the home, by  
simply entering the peak/off-peak hours manually into some controller,  
but case (3) would require active communication with the electricity  
company to determine the current price, which is a larger challenge.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* Internet Architecture Board
* www.stuartcheshire.org