Re: [smartpowerdir] Vint Cerf joins the Smart Power Directorate

Russ Housley <housley@vigilsec.com> Thu, 04 February 2010 17:35 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: smartpowerdir@core3.amsl.com
Delivered-To: smartpowerdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C41ED3A6A27; Thu, 4 Feb 2010 09:35:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.64
X-Spam-Level:
X-Spam-Status: No, score=-102.64 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4Nk4TMiUnIM; Thu, 4 Feb 2010 09:35:02 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 9A6BB3A68E3; Thu, 4 Feb 2010 09:35:02 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id CED869A4730; Thu, 4 Feb 2010 12:35:55 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id WZ-IR5J5pCWa; Thu, 4 Feb 2010 12:35:48 -0500 (EST)
Received: from [192.168.2.101] (pool-96-255-37-236.washdc.fios.verizon.net [96.255.37.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1497C9A4724; Thu, 4 Feb 2010 12:35:55 -0500 (EST)
Message-ID: <4B6B0574.9010604@vigilsec.com>
Date: Thu, 04 Feb 2010 12:35:48 -0500
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: Adrian Farrel <Adrian.Farrel@huawei.com>
References: <4B6AF481.8010303@vigilsec.com> <209DE19220C6487B99F547C34116789B@your029b8cecfe>
In-Reply-To: <209DE19220C6487B99F547C34116789B@your029b8cecfe>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, IETF SmartPower Directorate <smartpowerdir@ietf.org>
Subject: Re: [smartpowerdir] Vint Cerf joins the Smart Power Directorate
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpowerdir>
List-Post: <mailto:smartpowerdir@ietf.org>
List-Help: <mailto:smartpowerdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 17:35:03 -0000

Thanks.  I fixed the mail list entry.

Russ

On 2/4/2010 11:32 AM, Adrian Farrel wrote:
> Russ,
>
> John Drake is now jdrake@juniper.net
>
> A
> ----- Original Message ----- From: "Russ Housley" <housley@vigilsec.com>
> To: "IETF SmartPower Directorate" <smartpowerdir@ietf.org>
> Cc: "The IESG" <iesg@ietf.org>
> Sent: Thursday, February 04, 2010 4:23 PM
> Subject: Vint Cerf joins the Smart Power Directorate
>
>
>> I asked Vint Cerf to join the smart power directorate, and he agreed
>> to do it.
>>
>> As you know, this directorate reports to the General Area Director
>> (currently the IETF Chair), and it provides coordination between the
>> IETF and others working on Smart Power.
>>
>> Below is the whole membership of the directorate and its charter.
>>
>> Russ
>>
>>
>> ---- Directorate Members -----
>>
>> Loosely representing an IETF Area:
>> John Drake <John.E.Drake2@boeing.com> -- Routing
>> Sam Hartman <hartmans@painless-security.com> -- Security
>> Wes Eddy <Wesley.M.Eddy@nasa.gov> -- Transport
>> Andy Bierman <andyb@iwl.com> -- Management
>> Zack Shelby <zach@sensinode.com> -- Internet
>> Ted Hardie <ted.ietf@gmail.com> -- Applications
>> Henning Schulzrinne <hgs@cs.columbia.edu> -- RAI
>> Geoff Mulligan <geoff@proto6.com> -- General
>> Pierre Lin <pierre.lin@team.telstra.com> -- OPS
>>
>> Liaisons with an interest:
>> Fred Baker <fred@cisco.com> -- Liaison to SGIP
>> JP Vasseur <jvasseur@cisco.com> -- Liaison to ZigBee
>>
>> Providing broader perspective:
>> Ed Juskevicius <edj.etc@gmail.com> -- Canadian perspective
>> Zack Shelby <zach@sensinode.com> -- CENELEC/ETSI efforts in Europe
>> Vint Cerf <vint@google.com> -- SGIP Governing Board
>>
>> Area Directors with an interest:
>> Russ Housley <housley@vigilsec.com> -- General Area
>> Dan Romascanu <dromasca@avaya.com> -- O&M Area
>> Ralph Droms <rdroms@cisco.com> -- Internet Area
>> Jari Arkko <jari.arkko@piuha.net> -- Internet Area
>>
>>
>> ---- Directorate Charter -----
>>
>> There are many initiatives to couple delivery of electricity with the
>> data communications used to control and monitor the electricity
>> generation, delivery infrastructure, and consuming devices. The U.S.
>> Smart Grid is one such initiative. A smart grid includes an intelligent
>> monitoring system that keeps track of all electricity flowing in the
>> system, and it employs two-way communications to reduce cost, improve
>> reliability, and increase transparency.
>>
>> Recognizing that a smart grid has many similarities to the "Internet of
>> Things", developments associated with the use of Internet protocols to
>> connect many devices without human users can be applied without
>> enhancement to a smart grid.
>>
>> The Smart Power Directorate provides review and coordination on the use
>> of Internet protocols to provide smart grid communications. The goal is
>> to point other organizations to relevant IETF documents and provide
>> review of documents from other organizations that depend upon Internet
>> protocols. If the directorate identifies a gap that requires new work
>> in the IETF, the directorate will raise the issue with the IESG. The
>> directorate will not develop new protocols or enhance existing ones.
>> This review and coordination will require expertise from all of the
>> Areas in the IETF.
>>
>