Re: [TLS] Collisions (Re: Nico's suggestions - Re: Consensus Call:

Nicolas Williams <Nicolas.Williams@oracle.com> Tue, 11 May 2010 19:10 UTC

Return-Path: <Nicolas.Williams@oracle.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 925753A6A0E for <tls@core3.amsl.com>; Tue, 11 May 2010 12:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.038
X-Spam-Level:
X-Spam-Status: No, score=-5.038 tagged_above=-999 required=5 tests=[AWL=1.560, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 6jZFFF4SYAcs for <tls@core3.amsl.com>; Tue, 11 May 2010 12:10:22 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 3040A3A69B1 for <tls@ietf.org>; Tue, 11 May 2010 12:10:18 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4BJA5fd007148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 May 2010 19:10:06 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4BA0MgY001199; Tue, 11 May 2010 19:10:04 GMT
Received: from abhmt001.oracle.com by acsmt355.oracle.com with ESMTP id 232554891273605004; Tue, 11 May 2010 12:10:04 -0700
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 11 May 2010 12:10:03 -0700
Date: Tue, 11 May 2010 14:09:58 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>
Message-ID: <20100511190958.GR9429@oracle.com>
References: <20100510221531.GC9429@oracle.com> <201005111339.o4BDdoYQ009725@fs4113.wdf.sap.corp> <20100511152153.GF9429@oracle.com> <201005111803.o4BI3fhO006065@stingray.missi.ncsc.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201005111803.o4BI3fhO006065@stingray.missi.ncsc.mil>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Auth-Type: Internal IP
X-Source-IP: rcsinet15.oracle.com [148.87.113.117]
X-CT-RefId: str=0001.0A090209.4BE9AB8F.0045:SCFMA4539811,ss=1,fgs=0
Cc: tls@ietf.org
Subject: Re: [TLS] Collisions (Re: Nico's suggestions - Re: Consensus Call:
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, 11 May 2010 19:10:23 -0000

On Tue, May 11, 2010 at 02:03:39PM -0400, Kemp, David P. wrote:
> This sounds like a general problem unrelated to caching.
> 
> If a non-browser app cannot recover from failures, what happens when a
> bit error gets through multiple layers of detection and correction, or a
> DSL connection dies and restarts?   "Stuff happens" all the time, and
> humans know how to hit the "retry" button.  An unattended application
> that doesn't know how to recover from unexplained errors is not ready
> for prime time.

Fatal errors are fatal.  But the error here isn't quite as fatal.  I
suppose I can agree to view as such though and then there's no real
problem.

Nico
--