
From housley@vigilsec.com  Mon Aug  1 13:37:14 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: smartpowerdir@ietfa.amsl.com
Delivered-To: smartpowerdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDCA01F0C42 for <smartpowerdir@ietfa.amsl.com>; Mon,  1 Aug 2011 13:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vd04u82U80fC for <smartpowerdir@ietfa.amsl.com>; Mon,  1 Aug 2011 13:37:14 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 569471F0C41 for <smartpowerdir@ietf.org>; Mon,  1 Aug 2011 13:37:14 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 78A22F24165 for <smartpowerdir@ietf.org>; Mon,  1 Aug 2011 16:37:37 -0400 (EDT)
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 VyDpG9LlgGoP for <smartpowerdir@ietf.org>; Mon,  1 Aug 2011 16:37:11 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 17828F24131 for <smartpowerdir@ietf.org>; Mon,  1 Aug 2011 16:37:37 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4B7F0935.5060706@vigilsec.com>
Date: Mon, 1 Aug 2011 16:37:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7B88378-B139-448C-ACBA-CA80FF7C2FA4@vigilsec.com>
References: <4B7F0935.5060706@vigilsec.com>
To: IETF SmartPowerDir <smartpowerdir@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: [smartpowerdir] Renaming mail list: smartpowerdir to smartobjectdir
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 01 Aug 2011 20:37:14 -0000

Based on the discussions at IETF 81, I have asked the IETF Secretariat =
to rename this mail list and the directorate itself.  I hope that I have =
given sufficient warning for everyone to update their filters and =
various other mail-bots to deal wit the new name.

Enjoy,
Russ=

From fred@cisco.com  Mon Aug  1 13:57:23 2011
Return-Path: <fred@cisco.com>
X-Original-To: smartpowerdir@ietfa.amsl.com
Delivered-To: smartpowerdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B925D1F0C3E for <smartpowerdir@ietfa.amsl.com>; Mon,  1 Aug 2011 13:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.981
X-Spam-Level: 
X-Spam-Status: No, score=-102.981 tagged_above=-999 required=5 tests=[AWL=-0.382, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wUDyBSCdQEX1 for <smartpowerdir@ietfa.amsl.com>; Mon,  1 Aug 2011 13:57:23 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF771F0C39 for <smartpowerdir@ietf.org>; Mon,  1 Aug 2011 13:57:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2859; q=dns/txt; s=iport; t=1312232250; x=1313441850; h=mime-version:subject:from:date:cc:message-id:references: to:content-transfer-encoding; bh=hEHX3ezZ9hjfDUubuwH2i/0Sy7kIV1cThXIbMw0SszU=; b=AQ1FYXqucF/9X/t4vnEOM+T/xh+Q28/MRhMiVghXEItDWq98aWYpeF0i J9dwf45nT7i2B0/pQL3g7jvybFAPmpogPmZvP8ckv+XPA9Zlfn4PmfVE4 CIHvrl60wV6gBWJQ/6rrPspit3In5l56r56+YSGp8YCI7rQicsvifn+JD U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABYSN06rRDoI/2dsb2JhbABBp193gUABAQEBAgESAScxDgULHAMBAi9NAggGEyKHSqIQAZ5vhWNfBIdaiyGFB4t9
X-IronPort-AV: E=Sophos;i="4.67,302,1309737600";  d="scan'208";a="8569642"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-5.cisco.com with ESMTP; 01 Aug 2011 20:57:29 +0000
Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p71KvStb016428; Mon, 1 Aug 2011 20:57:28 GMT
Received: from [127.0.0.1] by stealth-10-32-244-221.cisco.com (PGP Universal service); Mon, 01 Aug 2011 13:57:28 -0700
X-PGP-Universal: processed; by stealth-10-32-244-221.cisco.com on Mon, 01 Aug 2011 13:57:28 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
Date: Mon, 1 Aug 2011 13:57:19 -0700
Message-Id: <89E4F790-A096-4441-9AAD-1D0201F403F9@cisco.com>
References: <118B375C-0CC8-4014-A494-2703A86D9A21@vigilsec.com>
To: IETF SmartPower Directorate <smartpowerdir@ietf.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [smartpowerdir] Fwd: Smart Object Directorate
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 01 Aug 2011 20:57:23 -0000

Folks: we had a discussion at breakfast Thursday morning about the =
future of the Smart Power Directorate and -interest activities. The =
sense at the table was that "Smart Power" is about a use of the =
technology, but the IETF should be more concerned about sensor network =
technology. This was discussed among the IESG, and this is what has come =
back.

In short, let's declare the objectives of "Smart Power" met, and meld =
them into the larger topic of IoT, Sensors, or whatever, and call it =
"Smart Objects".

Your opinions? For my money, it makes sense.

Begin forwarded message:

> From: Russ Housley <housley@vigilsec.com>
> Date: August 1, 2011 1:43:59 PM PDT
> To: Fred Baker <fred@cisco.com>
> Subject: Smart Object Directorate
>=20
> Fred:
>=20
> Please lead a discussion with the directorate on an update to the =
charter to match the name change.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D
>=20
> Smart Object Directorate
>=20
> (This Directorate was previously named the Smart Power Directorate.)
>=20
> Advice and coordination:
>=20
> Reports to the General Area Director (currently the IETF Chair),
> and provides coordination between the IETF and others working on
> Smart Objects.
>=20
> Charter:
>=20
> 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.
>=20
> 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.
>=20
> The Smart Object 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.
>=20
> Mail list:
>=20
> The Smart Object Directorate can be reached at =
smartobjectdir@ietf.org.=20
>=20
> The smartobject-interest@ietf.org mail list is available for open
> discussion of topics related to Smart Objects.
>=20


From richard@shockey.us  Tue Aug  2 07:27:01 2011
Return-Path: <richard@shockey.us>
X-Original-To: smartpowerdir@ietfa.amsl.com
Delivered-To: smartpowerdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8F85E8003 for <smartpowerdir@ietfa.amsl.com>; Tue,  2 Aug 2011 07:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.514
X-Spam-Level: 
X-Spam-Status: No, score=-101.514 tagged_above=-999 required=5 tests=[AWL=0.751, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzylMVzQoU6M for <smartpowerdir@ietfa.amsl.com>; Tue,  2 Aug 2011 07:27:00 -0700 (PDT)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by ietfa.amsl.com (Postfix) with SMTP id 44F1721F84F9 for <smartpowerdir@ietf.org>; Tue,  2 Aug 2011 07:27:00 -0700 (PDT)
Received: (qmail 3696 invoked by uid 0); 2 Aug 2011 14:27:09 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 2 Aug 2011 14:27:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=yb7kRDuidY1hlp0Qq9e+8ksGT3wmd4dZ0ArkbVhUVHI=;  b=Q1Gi5432z+S79sRenFdeF9fcJzxXSd0TYPZ9gcd9A48c5FiWMdy7gqz6zD+/mZ5xd2Rj2kFp58qJ7uJAkkzmxQRMmRGF5D/tQH6vpb/fMgIJR0t1uWwl/17ohAvRIe+A;
Received: from pool-71-178-24-118.washdc.fios.verizon.net ([71.178.24.118] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1QoFw5-0002qK-2A; Tue, 02 Aug 2011 08:27:09 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Fred Baker'" <fred@cisco.com>, "'IETF SmartPower Directorate'" <smartpowerdir@ietf.org>
References: <118B375C-0CC8-4014-A494-2703A86D9A21@vigilsec.com> <89E4F790-A096-4441-9AAD-1D0201F403F9@cisco.com>
In-Reply-To: <89E4F790-A096-4441-9AAD-1D0201F403F9@cisco.com>
Date: Tue, 2 Aug 2011 10:27:06 -0400
Message-ID: <000101cc5120$41e51fc0$c5af5f40$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxQjaEUB9A0Bu1NRqadI7F/ocjY0gAkezoQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.178.24.118 authed with richard@shockey.us}
Subject: Re: [smartpowerdir] Fwd: Smart Object Directorate
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 02 Aug 2011 14:27:01 -0000

+1  as we discussed Smart Power is an application of Smart Objects. 

One of the most important things we can do is update a list of the various
drafts that touch on this topic. I don't know who wants to own that document
( not me ) but It would be a big help to the whole community and the public
at large.  

-----Original Message-----
From: smartpowerdir-bounces@ietf.org [mailto:smartpowerdir-bounces@ietf.org]
On Behalf Of Fred Baker
Sent: Monday, August 01, 2011 4:57 PM
To: IETF SmartPower Directorate
Subject: [smartpowerdir] Fwd: Smart Object Directorate

Folks: we had a discussion at breakfast Thursday morning about the future of
the Smart Power Directorate and -interest activities. The sense at the table
was that "Smart Power" is about a use of the technology, but the IETF should
be more concerned about sensor network technology. This was discussed among
the IESG, and this is what has come back.

In short, let's declare the objectives of "Smart Power" met, and meld them
into the larger topic of IoT, Sensors, or whatever, and call it "Smart
Objects".

Your opinions? For my money, it makes sense.

Begin forwarded message:

> From: Russ Housley <housley@vigilsec.com>
> Date: August 1, 2011 1:43:59 PM PDT
> To: Fred Baker <fred@cisco.com>
> Subject: Smart Object Directorate
> 
> Fred:
> 
> Please lead a discussion with the directorate on an update to the charter
to match the name change.
> 
> Russ
> 
> = = = = = =
> 
> Smart Object Directorate
> 
> (This Directorate was previously named the Smart Power Directorate.)
> 
> Advice and coordination:
> 
> Reports to the General Area Director (currently the IETF Chair),
> and provides coordination between the IETF and others working on
> Smart Objects.
> 
> 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 Object 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.
> 
> Mail list:
> 
> The Smart Object Directorate can be reached at smartobjectdir@ietf.org. 
> 
> The smartobject-interest@ietf.org mail list is available for open
> discussion of topics related to Smart Objects.
> 


From dromasca@avaya.com  Tue Aug  2 07:29:05 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: smartpowerdir@ietfa.amsl.com
Delivered-To: smartpowerdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1275211E8080 for <smartpowerdir@ietfa.amsl.com>; Tue,  2 Aug 2011 07:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.421
X-Spam-Level: 
X-Spam-Status: No, score=-103.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghk4fsm42w5f for <smartpowerdir@ietfa.amsl.com>; Tue,  2 Aug 2011 07:29:04 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4230211E807C for <smartpowerdir@ietf.org>; Tue,  2 Aug 2011 07:29:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuwAANoIOE7GmAcF/2dsb2JhbABCmA2PVXeBQAEBAQEDEh4KMRoEAgEIDQQDAQEBCwYMCwEGAUUJCAEBBAESCAwOrDQCnDOFY18EmCCLQQ
X-IronPort-AV: E=Sophos;i="4.67,306,1309752000"; d="scan'208";a="294564142"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Aug 2011 10:29:12 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Aug 2011 10:26:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Aug 2011 16:29:11 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040371B167@307622ANEX5.global.avaya.com>
In-Reply-To: <000101cc5120$41e51fc0$c5af5f40$@us>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [smartpowerdir] Fwd: Smart Object Directorate
Thread-Index: AcxQjaEUB9A0Bu1NRqadI7F/ocjY0gAkezoQAAA0ltA=
References: <118B375C-0CC8-4014-A494-2703A86D9A21@vigilsec.com><89E4F790-A096-4441-9AAD-1D0201F403F9@cisco.com> <000101cc5120$41e51fc0$c5af5f40$@us>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Richard Shockey" <richard@shockey.us>, "Fred Baker" <fred@cisco.com>, "IETF SmartPower Directorate" <smartpowerdir@ietf.org>
Subject: Re: [smartpowerdir] Fwd: Smart Object Directorate
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 02 Aug 2011 14:29:05 -0000

Hi,=20

Can this list be maintained on a wiki? Thus it would be a collaborative
effort that people from the directorate can update and things happen. =20

Thanks and Regards,

Dan=20

> -----Original Message-----
> From: smartpowerdir-bounces@ietf.org [mailto:smartpowerdir-
> bounces@ietf.org] On Behalf Of Richard Shockey
> Sent: Tuesday, August 02, 2011 5:27 PM
> To: 'Fred Baker'; 'IETF SmartPower Directorate'
> Subject: Re: [smartpowerdir] Fwd: Smart Object Directorate
>=20
> +1  as we discussed Smart Power is an application of Smart Objects.
>=20
> One of the most important things we can do is update a list of the
> various
> drafts that touch on this topic. I don't know who wants to own that
> document
> ( not me ) but It would be a big help to the whole community and the
> public
> at large.
>=20
> -----Original Message-----
> From: smartpowerdir-bounces@ietf.org [mailto:smartpowerdir-
> bounces@ietf.org]
> On Behalf Of Fred Baker
> Sent: Monday, August 01, 2011 4:57 PM
> To: IETF SmartPower Directorate
> Subject: [smartpowerdir] Fwd: Smart Object Directorate
>=20
> Folks: we had a discussion at breakfast Thursday morning about the
> future of
> the Smart Power Directorate and -interest activities. The sense at the
> table
> was that "Smart Power" is about a use of the technology, but the IETF
> should
> be more concerned about sensor network technology. This was discussed
> among
> the IESG, and this is what has come back.
>=20
> In short, let's declare the objectives of "Smart Power" met, and meld
> them
> into the larger topic of IoT, Sensors, or whatever, and call it "Smart
> Objects".
>=20
> Your opinions? For my money, it makes sense.
>=20
> Begin forwarded message:
>=20
> > From: Russ Housley <housley@vigilsec.com>
> > Date: August 1, 2011 1:43:59 PM PDT
> > To: Fred Baker <fred@cisco.com>
> > Subject: Smart Object Directorate
> >
> > Fred:
> >
> > Please lead a discussion with the directorate on an update to the
> charter
> to match the name change.
> >
> > Russ
> >
> > =3D =3D =3D =3D =3D =3D
> >
> > Smart Object Directorate
> >
> > (This Directorate was previously named the Smart Power Directorate.)
> >
> > Advice and coordination:
> >
> > Reports to the General Area Director (currently the IETF Chair),
> > and provides coordination between the IETF and others working on
> > Smart Objects.
> >
> > 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 Object 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.
> >
> > Mail list:
> >
> > The Smart Object Directorate can be reached at
> smartobjectdir@ietf.org.
> >
> > The smartobject-interest@ietf.org mail list is available for open
> > discussion of topics related to Smart Objects.
> >

