RE: [MSEC] Changes to ECC Draft
"Fries, Steffen" <steffen.fries@siemens.com> Wed, 18 April 2007 06:54 UTC
Return-path: <msec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1He43w-0000Yt-8v; Wed, 18 Apr 2007 02:54:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1He43u-0000Yc-TZ for MSEC@ietf.org; Wed, 18 Apr 2007 02:54:42 -0400
Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1He43t-0005b6-C9 for MSEC@ietf.org; Wed, 18 Apr 2007 02:54:42 -0400
Received: from mail2.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id l3I6sd6F020780; Wed, 18 Apr 2007 08:54:39 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail2.sbs.de (8.12.6/8.12.6) with ESMTP id l3I6scME002966; Wed, 18 Apr 2007 08:54:39 +0200
Received: from MCHP7I6A.ww002.siemens.net ([139.25.131.137]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Apr 2007 08:54:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MSEC] Changes to ECC Draft
Date: Wed, 18 Apr 2007 08:54:33 +0200
Message-ID: <6A18D243963B7447AC1A36583F78EEDA01CAC852@MCHP7I6A.ww002.siemens.net>
In-Reply-To: <8ba53040704172011y1065ae1xa6bf3c70b0299306@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MSEC] Changes to ECC Draft
Thread-Index: AceBZ0pbMCDhRW6ZSVKSfhylpW+CcgAHta1A
References: <8ba53040704172011y1065ae1xa6bf3c70b0299306@mail.gmail.com>
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Eugene Chin <eugene.chin@gmail.com>, MSEC@ietf.org
X-OriginalArrivalTime: 18 Apr 2007 06:54:38.0727 (UTC) FILETIME=[6EC3B970:01C78186]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc:
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1323605505=="
Errors-To: msec-bounces@ietf.org
Hi Eugene,
will this involve changes to the general call flow and parameter send in
the MIKEY messages? I'm just asking because the ECC approach is also
described in the MIKEY applicability draft, which I'm going to submit as
an updated version end of this week. I included the call flows from your
draft.
Ciao
Steffen
________________________________
From: Eugene Chin [mailto:eugene.chin@gmail.com]
Sent: Wednesday, April 18, 2007 5:11 AM
To: MSEC@ietf.org
Subject: [MSEC] Changes to ECC Draft
Hi all,
With respect to
http://www.ietf.org/internet-drafts/draft-ietf-msec-mikey-ecc-02.txt,
upon further review, we have discovered some issues in the way
MIKEY-ECIES and MIKEY-ECMQV methods have been defined. Corrections are
being made now, and I will submit a new draft as soon as it's ready.
If anyone else has read it and has any comments, those are
always welcome.
Thanks,
Eugene.
_______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec
- [MSEC] Changes to ECC Draft Eugene Chin
- RE: [MSEC] Changes to ECC Draft Fries, Steffen