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

Yoav Nir <> Fri, 27 September 2013 17:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 138B021F91BF for <>; Fri, 27 Sep 2013 10:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.372
X-Spam-Status: No, score=-10.372 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jogKM7dipTdL for <>; Fri, 27 Sep 2013 10:19:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2DC7D21F91F2 for <>; Fri, 27 Sep 2013 10:19:10 -0700 (PDT)
Received: from ([]) by (8.13.8/8.13.8) with ESMTP id r8RHInux013484; Fri, 27 Sep 2013 20:18:49 +0300
X-CheckPoint: {5245BDF9-C-1B221DC2-1FFFF}
Received: from ([]) by ([]) with mapi id 14.02.0347.000; Fri, 27 Sep 2013 20:18:49 +0300
From: Yoav Nir <>
To: Herb Falk <>, "Sean P. Turner" <>
Thread-Topic: [MSEC] Key Management protocol (GDOI - 6407) forward
Thread-Index: Ac67FJGyoGPYHJStQ3mYygEDVBEZfAAEfu0gABl+LQA=
Date: Fri, 27 Sep 2013 17:18:49 +0000
Message-ID: <>
References: <> <418E74FA535F654FAB3CAAE12902E2940156AA80@SISCO-SBS.sisconet.local>
In-Reply-To: <418E74FA535F654FAB3CAAE12902E2940156AA80@SISCO-SBS.sisconet.local>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: multipart/alternative; boundary="_000_7417090A55F142EDB0511EB197DAAB52checkpointcom_"
MIME-Version: 1.0
Cc: "" <>, Jeff Gooding/SCE/EIX <>, "Maik Seewald \(maseewal\)" <>, "" <>, "Madani, Vahid" <>, "Adamiak, Mark \(GE Energy Management\)" <>, "Novosel, Damir" <>, "Thanos, Daniel \(GE Energy Management\)" <>, "Alex Apostolov \(\)" <>
Subject: Re: [MSEC] Key Management protocol (GDOI - 6407) forward
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Security List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Sep 2013 17:19:36 -0000


Just to be clear, there is no such thing as a "draft RFC". Drafts become RFCs, at which point they're done. You may be referring to the fact that RFC 6407 is labeled "proposed standard". This is a label that the IETF attaches to documents for which there is relatively little implementation experience. The label is not automatically changed after a while. Even things that are widely implemented and used by millions such as IKEv2 (RFC 5996), IPsec (RFC 4301), TLS (RFC 5246), and HTTP (RFC 2616), without a doubt the most popular protocol on the Internet) is at "draft standard" - a classification that does not exist any more, but was below "full standard".

I'm adding Sean Turner, the Security Area Director, because he's been handling many similar requests recently.

Hope this helps


On Sep 27, 2013, at 5:15 AM, Herb Falk <<>> <<>> wrote:

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.

MSEC mailing list<>