IETF Logo Mail Archive

Re: [TLS] Summarizing identity change discussion so far

Martin Rex <mrex@sap.com> Thu, 17 December 2009 21:45 UTC

Return-Path: <mrex@sap.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 D69E93A68D9 for <tls@core3.amsl.com>; Thu, 17 Dec 2009 13:45:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level:
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 tIHG23WlULm6 for <tls@core3.amsl.com>; Thu, 17 Dec 2009 13:45:30 -0800 (PST)
Received: from smtpde03.sap-ag.de (smtpde03.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id C93A03A6820 for <tls@ietf.org>; Thu, 17 Dec 2009 13:45:29 -0800 (PST)
Received: from mail.sap.corp by smtpde03.sap-ag.de (26) with ESMTP id nBHLjE3B004904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Dec 2009 22:45:14 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <200912172145.nBHLjDUT018568@fs4113.wdf.sap.corp>
To: Pasi.Eronen@nokia.com
Date: Thu, 17 Dec 2009 22:45:13 +0100
In-Reply-To: <808FD6E27AD4884E94820BC333B2DB774F31F77BBB@NOK-EUMSG-01.mgdnok.nokia.com> from "Pasi.Eronen@nokia.com" at Dec 17, 9 10:28:47 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal05
X-SAP: out
Cc: tls@ietf.org
Subject: Re: [TLS] Summarizing identity change discussion so far
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mrex@sap.com
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: Thu, 17 Dec 2009 21:45:31 -0000

Pasi.Eronen@nokia.com wrote:
> 
> Comments (and especially concrete proposals for improving the text)
> are welcome.

Sounds good to me.  (I leave two typos I think to have noticed to
the native speakers).

Maybe we should at least mention one valid reason for why a certificate
may change in the Security Considerations: certificate update/renewal.

There were two scenarios mentioned where this seems to be a
regular use case IIRC.  Was it gaming where they were using quite
short-lived certificates and then XMPP, where they were using
quite long-lived connections?

-Martin

v2.23.0 | Report a Bug | By Email