Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H0kxI-0000El-BT; Sat, 30 Dec 2006 15:37:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H0kxG-0000Eg-WF for tls@ietf.org; Sat, 30 Dec 2006 15:37:23 -0500 Received: from bay0-omc1-s35.bay0.hotmail.com ([65.54.246.107]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H0kxF-00006Y-Lr for tls@ietf.org; Sat, 30 Dec 2006 15:37:22 -0500 Received: from hotmail.com ([65.54.174.86]) by bay0-omc1-s35.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sat, 30 Dec 2006 12:37:21 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 30 Dec 2006 12:37:20 -0800 Message-ID: Received: from 69.227.152.254 by BAY103-DAV14.phx.gbl with DAV; Sat, 30 Dec 2006 20:37:16 +0000 X-Originating-IP: [69.227.152.254] X-Originating-Email: [home_pw@msn.com] X-Sender: home_pw@msn.com From: To: Date: Sat, 30 Dec 2006 12:37:31 -0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Live Mail desktop 8.0.1223 X-MimeOLE: Produced By Microsoft MimeOLE V8.0.1223 X-OriginalArrivalTime: 30 Dec 2006 20:37:20.0994 (UTC) FILETIME=[4DF12C20:01C72C52] X-Spam-Score: 0.3 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: Subject: [TLS] update for tls- psk-null? X-BeenThere: tls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1274589774==" Errors-To: tls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============1274589774== Content-Type: multipart/alternative; boundary="----=_NextPart_000_020F_01C72C0F.45D6B8E0" This is a multi-part message in MIME format. ------=_NextPart_000_020F_01C72C0F.45D6B8E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Procedurally, I don't support = http://www.ietf.org/internet-drafts/draft-ietf-tls-psk-null-03.txt. I think it should be slightly rewritten, declared to be a retrospective = "update" to [TLS-PSK]. This would=20 properly contextualize the material in the I-D, while achieving the = stated goal of the current I-D ("augment"). Consider this, and consider withdrawing it from the RFC Editor queue. = The adequacy of the augmented ciphersuites (how many implementations, etc) can then be = evaluated as=20 the TLS-PSK gets evaluated in its own standards track progress. ------=_NextPart_000_020F_01C72C0F.45D6B8E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Procedurally, I don=92t support http://www.ietf.org/internet-drafts/draft-ietf-tls-psk-null-03.txt=
 
I think it should be slightly rewritten, declared to be a = retrospective=20 "update" to [TLS-PSK]. This would
properly contextualize the material in the I-D, while achieving the = stated=20 goal of the current I-D ("augment").
 
Consider this, and consider withdrawing it from the RFC Editor = queue. The=20 adequacy of
the augmented ciphersuites (how many implementations,  etc) = can then=20 be evaluated as
the TLS-PSK gets evaluated in its own standards track=20 progress.
------=_NextPart_000_020F_01C72C0F.45D6B8E0-- --===============1274589774== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls --===============1274589774==--