Re: TLS requirements (Last Call: draft-ietf-atompub-protocol to Proposed Standard)

Julian Reschke <julian.reschke@gmx.de> Tue, 05 June 2007 08:18 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvUEv-0006EI-J2; Tue, 05 Jun 2007 04:18:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvUEu-0006Da-7D for ietf@ietf.org; Tue, 05 Jun 2007 04:18:04 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvUEs-0005TA-QP for ietf@ietf.org; Tue, 05 Jun 2007 04:18:04 -0400
Received: (qmail invoked by alias); 05 Jun 2007 08:18:01 -0000
Received: from p508F9DF1.dip0.t-ipconnect.de (EHLO [192.168.178.22]) [80.143.157.241] by mail.gmx.net (mp005) with SMTP; 05 Jun 2007 10:18:01 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18PgcFLLPgP9UA/XwCalwIsW7DVslhdTanojYPAwU ++Iky/J5Ppcpqf
Message-ID: <46651C30.2040304@gmx.de>
Date: Tue, 05 Jun 2007 10:17:52 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Eric Rescorla <ekr@networkresonance.com>
References: <45F6CE12.8020703@mozilla.com> <tsllki1rpyc.fsf@cz.mit.edu> <45F6EF91.7030008@mozilla.com> <tslk5xlq8ul.fsf@cz.mit.edu> <45F6FA2A.4060409@mozilla.com> <1C0F121E56ADA47B5683D263@caldav.corp.apple.com> <45F7EC16.1030904@zurich.ibm.com> <45F7F3FC.6020306@gmx.de> <86lkhzc22x.fsf@delta.rtfm.com> <68fba5c50705181605p66298f1fh31f119185f67d8e8@mail.gmail.com> <517bf110705192034s6e4e5656r596a6f11883e6a9a@mail.gmail.com> <20070520204129.9E0AE33C23@delta.rtfm.com>
In-Reply-To: <20070520204129.9E0AE33C23@delta.rtfm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Cyrus Daboo <cyrus@daboo.name>, Sam Hartman <hartmans-ietf@mit.edu>, Tim Bray <tbray@textuality.com>, ietf@ietf.org, iesg@ietf.org
Subject: Re: TLS requirements (Last Call: draft-ietf-atompub-protocol to Proposed Standard)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Eric Rescorla wrote:
> I agree that these specs should explicitly specify which TLS version
> to support. As a practical matter, this is either 1.0 or 1.1, since
> 1.2 is not yet finished. Unfortunately, which one to require isn't
> really something that can be decided on technical grounds: the
> protocols are very slightly different and (at least in theory)
> backward compatible. TLS 1.1 is slightly more secure and TLS 1.0 is
> quite a bit more widely deployed. 
> 
> On balance, I think this probably turns into a MUST for 1.0 and a
> SHOULD for 1.1, but I could certainly see this argued another way.

I noticed that atompub is on next Thursday's IESG agenda. Any news on 
how this issue will be resolved?

Best regards, Julian


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