Re: [smartobjectdir] Smart Grid and SGIP

"Richard Shockey" <richard@shockey.us> Wed, 19 September 2012 18:33 UTC

Return-Path: <richard@shockey.us>
X-Original-To: smartobjectdir@ietfa.amsl.com
Delivered-To: smartobjectdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F8121E8043 for <smartobjectdir@ietfa.amsl.com>; Wed, 19 Sep 2012 11:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.519
X-Spam-Level:
X-Spam-Status: No, score=-99.519 tagged_above=-999 required=5 tests=[AWL=0.975, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.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 jhpGA84tFQ6n for <smartobjectdir@ietfa.amsl.com>; Wed, 19 Sep 2012 11:33:09 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7.bluehost.com [IPv6:2605:dc00:100:2::a7]) by ietfa.amsl.com (Postfix) with SMTP id E39DD21E809E for <smartobjectdir@ietf.org>; Wed, 19 Sep 2012 11:33:08 -0700 (PDT)
Received: (qmail 24771 invoked by uid 0); 19 Sep 2012 18:33:03 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy7.bluehost.com with SMTP; 19 Sep 2012 18:33:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=j6c9g1m+9sqk9Mii/itXR+q3BQTPaw55r9keNpek6gE=; b=d+8wiw3HKCsr0eSseMuI9Zzgpf4BXCWOFzt+MlrkT9+ERcwKkC7x40gcvxzVTRjkjByKTmwroMZkCWFZbRLr94jxm2nGNjD+S0jJCIMMC4nkS/CVw6yGieV4Xho7IUm2;
Received: from [71.191.243.130] (port=49442 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1TEP53-0001e8-RL; Wed, 19 Sep 2012 12:33:02 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Vint Cerf'" <vint@google.com>, "'Fred Baker \(fred\)'" <fred@cisco.com>
References: <D8656EDE-1D31-4523-9657-B66AEAC23019@cisco.com> <CAHxHggeog1bcMSscj53=Nqy-5Um-DtaG9W08ituMhGj8LqOOSQ@mail.gmail.com>
In-Reply-To: <CAHxHggeog1bcMSscj53=Nqy-5Um-DtaG9W08ituMhGj8LqOOSQ@mail.gmail.com>
Date: Wed, 19 Sep 2012 14:32:58 -0400
Message-ID: <005901cd9695$32e05ab0$98a11010$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005A_01CD9673.ABCEBAB0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac2WkzIwdqYEdaCfS/y84RBJiz1zMQAAaOZA
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
Cc: 'IETF SmartObjectDir' <smartobjectdir@ietf.org>, 'Russ Housley' <housley@vigilsec.com>
Subject: Re: [smartobjectdir] Smart Grid and SGIP
X-BeenThere: smartobjectdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <smartobjectdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smartobjectdir>, <mailto:smartobjectdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartobjectdir>
List-Post: <mailto:smartobjectdir@ietf.org>
List-Help: <mailto:smartobjectdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartobjectdir>, <mailto:smartobjectdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 18:33:11 -0000

+1    

 

Do the regulators have to pay as well?  J 

 

It's a very insular industry.

 

From: smartobjectdir-bounces@ietf.org
[mailto:smartobjectdir-bounces@ietf.org] On Behalf Of Vint Cerf
Sent: Wednesday, September 19, 2012 2:19 PM
To: Fred Baker (fred)
Cc: IETF SmartObjectDir; Russ Housley
Subject: Re: [smartobjectdir] Smart Grid and SGIP

 

+1

 

 

On Wed, Sep 19, 2012 at 2:08 PM, Fred Baker (fred) <fred@cisco.com>; wrote:

I'm reporting on recent events in the Smart Grid Interoperability Panel.

SGIP continues doing what it does, which is reviewing standards from a
variety of  bodies but mostly IEC, for their place in the Smart Grid.
They're mostly happy with IETF standards and plan to use them. The past four
years have been an educational process on my part, mostly trying to ensure
that wherever they can use IPv4, they can also use IPv6. I have written one
RFC at their request, and inserted an IPv6-related comment into one IEC
specification-in-development. Communications is not their primary interest;
most specifications that deal with communications at all, such as RFC 6142,
specify it down to what is referred to as the "ISO Transport API", by which
they mean RFC 2126. For the most part, it is normalization of what we might
call MIBs and object models and working out the details of
business-to-business exchanges at the application layer.

SGIP has been funded by ARRA money - the ~$800B initiative to "get America
working" with "shovel-ready" projects in 2009. In ARRA, about $28B was set
aside for grid modernization, and about $4.5B of that specifically for
computerization of it. Four years later, that money has been allocated or
spent, and SGIP has to find other funding.

Hence, SGIP is becoming a membership organization. Anyone who wants a place
at the table has to pay a membership fee. There is a schedule of fees for
for-profit and not-for-profit institutions; if we are to be members, I think
it would be ISOC as a member, and I would expect SGIP to invoice according
to ISOC's PIR+organizational member donations revenue.

What I have told George Arnold of NIST and Paul Molitor of NEMA is that the
equation has the flow of value in the wrong direction. I am there,
representing the IETF, as a service to SGIP, but we don't derive value from
the SGIP or from SGIP participation. Hence, having us pay a fee for the
privilege of offering a service doesn't make sense. Rather, I am willing to
participate as a guest when invited, and the IETF is willing to receive
liaison notes and do work on the behalf of the industry as we have in
6lowpan, roll, and core.

If anyone disagrees with my assessment, now would be the time to say so :-)
_______________________________________________
smartobjectdir mailing list
smartobjectdir@ietf.org
https://www.ietf.org/mailman/listinfo/smartobjectdir