Re: [TLS] simplistic renego protection

Chris Newman <Chris.Newman@Sun.COM> Tue, 17 November 2009 04:05 UTC

Return-Path: <Chris.Newman@Sun.COM>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D982B3A6838 for <tls@core3.amsl.com>; Mon, 16 Nov 2009 20:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level:
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qig5cZUKRpM for <tls@core3.amsl.com>; Mon, 16 Nov 2009 20:05:33 -0800 (PST)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by core3.amsl.com (Postfix) with ESMTP id 38AF33A68FA for <tls@ietf.org>; Mon, 16 Nov 2009 20:05:33 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nAH45Wdg024644 for <tls@ietf.org>; Mon, 16 Nov 2009 20:05:32 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-type: text/plain; CHARSET="US-ASCII"; format="flowed"
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KT800J00J7DGS00@fe-sfbay-10.sun.com> for tls@ietf.org; Mon, 16 Nov 2009 20:05:32 -0800 (PST)
Received: from vpn-129-150-241-98.sfbay.sun.com ([unknown] [10.1.110.5]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KT800MOOJD50M20@fe-sfbay-10.sun.com>; Mon, 16 Nov 2009 20:05:31 -0800 (PST)
Date: Mon, 16 Nov 2009 20:05:29 -0800
From: Chris Newman <Chris.Newman@Sun.COM>
In-reply-to: <200911161725.nAGHPWaA014181@fs4113.wdf.sap.corp>
Sender: Chris.Newman@Sun.COM
To: mrex@sap.com
Message-id: <089F31C221374096B0FE619F@446E7922C82D299DB29D899F>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
References: <200911161725.nAGHPWaA014181@fs4113.wdf.sap.corp>
Cc: tls@ietf.org
Subject: Re: [TLS] simplistic renego protection
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2009 04:05:33 -0000

--On November 16, 2009 18:25:32 +0100 Martin Rex <mrex@sap.com> wrote:
> But when a proposal enters the IETF process, the IETF and the
> working group should discuss it based on its technical merits.

The IETF is about rough consensus and running code.  Technical merit is one 
aspect of that.  Time to market can be important.  Technical maturity of 
the specification can be important.  The best or perfect proposal often 
takes longer to develop than the good enough proposal and thus loses.  Just 
look at how badly HTTP is designed when it comes to authentication -- but 
it was good enough to standardize.  The HTTP Next-Generation working group 
failed because HTTP is good enough.

draft-rescorla-tls-renegotiation-00 already has lots of running code; and 
that's a traditional IETF litmus test that correctly makes alternative 
proposals far less attractive.

If you want your alternative proposal to be considered, submit an Internet 
draft and get some running code and feedback from implementations showing 
your proposal would deploy protection to more users than 
draft-rescorla-tls-renegotiation-00.  Then you may sway people to your 
viewpoint.

But time-to-market is __very__ important for this particular problem.  I 
think you have already spent too much time arguing on the list and not 
enough time writing specs and gathering implementation experience to make a 
viable alternative proposal.

		- Chris