[MSEC] Key Management protocol (GDOI - 6407) forward

"Herb Falk <herb@sisconet.com>" <Herb@sisconet.com> Fri, 27 September 2013 02:15 UTC

Return-Path: <Herb@sisconet.com>
X-Original-To: msec@ietfa.amsl.com
Delivered-To: msec@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8E1B321F999B for <msec@ietfa.amsl.com>; Thu, 26 Sep 2013 19:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.261
X-Spam-Status: No, score=0.261 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id eouLVLZoglNE for <msec@ietfa.amsl.com>; Thu, 26 Sep 2013 19:15:16 -0700 (PDT)
Received: from mail.sisconet.com (mail.sisconet.com []) by ietfa.amsl.com (Postfix) with ESMTP id 5BCA421F9EAE for <msec@ietf.org>; Thu, 26 Sep 2013 19:15:16 -0700 (PDT)
Received: from SISCO-SBS.sisconet.local ([fe80::2459:3d41:7314:dc1b]) by SISCO-SBS.sisconet.local ([fe80::2459:3d41:7314:dc1b%10]) with mapi id 14.03.0123.003; Thu, 26 Sep 2013 22:15:07 -0400
From: "Herb Falk <herb@sisconet.com>" <Herb@sisconet.com>
To: "msec@ietf.org" <msec@ietf.org>
Thread-Topic: Key Management protocol (GDOI - 6407) forward
Thread-Index: Ac67FJGyoGPYHJStQ3mYygEDVBEZfAAEfu0g
Date: Fri, 27 Sep 2013 02:15:06 +0000
Message-ID: <418E74FA535F654FAB3CAAE12902E2940156AA80@SISCO-SBS.sisconet.local>
References: <CB6C229361B2E34190B3BF9F6EC922224DCCB760@EXCHMBSF323.Utility.pge.com>
In-Reply-To: <CB6C229361B2E34190B3BF9F6EC922224DCCB760@EXCHMBSF323.Utility.pge.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_418E74FA535F654FAB3CAAE12902E2940156AA80SISCOSBSsiscone_"; type="multipart/alternative"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 27 Sep 2013 09:16:07 -0700
Cc: "Thanos, Daniel \(GE Energy Management\)" <Daniel.Thanos@ge.com>, Jeff Gooding/SCE/EIX <Jeff.Gooding@sce.com>, "Maik Seewald \(maseewal\)" <maseewal@cisco.com>, "Andrew.Free@sce.com" <Andrew.Free@sce.com>, "Madani, Vahid" <VxM6@pge.com>, "Adamiak, Mark \(GE Energy Management\)" <mark.adamiak@ge.com>, "Novosel, Damir" <DNovosel@Quanta-Technology.com>, "Alex Apostolov \(alex.apostolov@omicronusa.com\)" <alex.apostolov@omicronusa.com>
Subject: [MSEC] Key Management protocol (GDOI - 6407) forward
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 02:39:40 -0000

IEC TC57 WG10 (61850) and IEC TC57 WG15 (Security) has been developing a technology/standard for use as a secure multicast for its use in power grid applications using synchrophasors and other technologies relevant to smartgrid deployments globally.

As part of the effort, some extensions to GDOI were identified.  The 6407 draft incorporates and improves some of the enhancements already identified.  IEC TC57 WG15 is waiting for the draft RFC to transition to an RFC so it can be referenced as a normative standard in IEC 62351-9.

There are several utility vendors and utilities, in particular SCE (Southern California Edison), that are awaiting this transition so that their cyber security frameworks can be updated.  Delays in the transition from draft to RFC will delay implementation of several projects and implementations.

Herbert Falk
Solutions Architect
6605 19 ½ Mile Rd.
Sterling Heights, MI 48314
(586) 254-0020 x-105

"In matters of style, swim with the current;   in matters of principle, stand like a rock." [Thomas Jefferson]

NOTICE: This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you have  received this communication in error, please do not print, copy, retransmit,  disseminate, or otherwise use the information. Also,  please indicate to the sender that you have received this communication in error, and delete the copy you received. Thank you.