IETF Logo Mail Archive

Re: [Emu] Review of draft-clancy-emu-eap-shared-secret-01

Charles Clancy <clancy@cs.umd.edu> Sat, 15 July 2006 22:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1sdY-0001BC-G2; Sat, 15 Jul 2006 18:29:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1sdX-0001B7-Ip for emu@ietf.org; Sat, 15 Jul 2006 18:29:23 -0400
Received: from dispatch.cs.umd.edu ([128.8.128.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1sdW-0003uN-BT for emu@ietf.org; Sat, 15 Jul 2006 18:29:23 -0400
Received: from delegate.pc.cs.umd.edu (exchange.cs.umd.edu [128.8.130.248]) by dispatch.cs.umd.edu (8.12.11.20060308/8.12.5) with ESMTP id k6FMT4Io000466; Sat, 15 Jul 2006 18:29:08 -0400
Received: from [192.168.0.101] ([71.123.36.170]) by delegate.pc.cs.umd.edu with Microsoft SMTPSVC(6.0.3790.1830); Sat, 15 Jul 2006 18:29:02 -0400
Message-ID: <44B96C70.3030800@cs.umd.edu>
Date: Sat, 15 Jul 2006 18:30:08 -0400
From: Charles Clancy <clancy@cs.umd.edu>
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: [Emu] Review of draft-clancy-emu-eap-shared-secret-01
References: <7.0.1.0.2.20060711072555.043cf6c0@qualcomm.com> <20060712165015.57845.qmail@web54402.mail.yahoo.com> <7.0.1.0.2.20060712100845.0418ec58@qualcomm.com> <44B5357C.5060300@gmx.net> <7.0.1.0.2.20060712105107.06f86208@qualcomm.com> <44B539F0.6060803@gmx.net>
In-Reply-To: <44B539F0.6060803@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jul 2006 22:29:02.0193 (UTC) FILETIME=[12C4FE10:01C6A85E]
X-CSD-MailScanner-Information: Please email staff@cs.umd.edu for more information
X-CSD-MailScanner: Found to be clean
X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (score=0.374, required 5, autolearn=disabled, DNS_FROM_RFC_ABUSE 0.37)
X-MailScanner-From: clancy@cs.umd.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: emu@ietf.org
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
Errors-To: emu-bounces@ietf.org

 >> So I am drawing from the experience of IKEv2 and ESPv3.  The idea is
 >> purely based on document maintenance process.
 >
 > I am not sure whether IKEv2 or ESPv3 is a good example. Our goal was
 > to develop a simple EAP method. To have something interoperable we
 > have to define a mandatory to implement ciphersuite. I strongly
 > believe that we have to put this ciphersuite into the EAP method
 > document.

I think one document makes the most sense.

--
t. charles clancy, ph.d.  |  tcc@umd.edu  |  www.cs.umd.edu/~clancy


_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu

v2.23.0 | Report a Bug | By Email