IETF Logo Mail Archive

Re: [TLS] Summarizing identity change discussion so far

Nasko Oskov <noskov@microsoft.com> Fri, 18 December 2009 21:31 UTC

Return-Path: <noskov@microsoft.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 18E4328C10C for <tls@core3.amsl.com>; Fri, 18 Dec 2009 13:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Ggz+rwRVy134 for <tls@core3.amsl.com>; Fri, 18 Dec 2009 13:31:21 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 321393A68C2 for <tls@ietf.org>; Fri, 18 Dec 2009 13:31:21 -0800 (PST)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 18 Dec 2009 13:31:37 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server (TLS) id 14.0.639.20; Fri, 18 Dec 2009 13:31:04 -0800
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.138]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Fri, 18 Dec 2009 13:31:05 -0800
From: Nasko Oskov <noskov@microsoft.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Michael Gray <mickgray@au1.ibm.com>
Thread-Topic: [TLS] Summarizing identity change discussion so far
Thread-Index: AQHKf2bXeOABEFFowEGB9UF9BHMAopFqWuCAgABGHQCAALI1AA==
Date: Fri, 18 Dec 2009 21:30:32 +0000
Deferred-Delivery: Fri, 18 Dec 2009 21:31:00 +0000
Message-ID: <B197003731D4874CA41DE7B446BBA3E84B6F07C7@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <OF8FF151E8.A53BE95F-ON4A25768F.007B3729-4A25768F.007C7597@au1.ibm.com> <4B2AEDEE.30007@stpeter.im>
In-Reply-To: <4B2AEDEE.30007@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "tls@ietf.org" <tls@ietf.org>, Kyle Hamilton <aerowolf@gmail.com>
Subject: Re: [TLS] Summarizing identity change discussion so far
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: Fri, 18 Dec 2009 21:31:24 -0000

Peter Saint-Andre wrote:
>On 12/17/09 3:39 PM, Michael Gray wrote:
>> mrex@sap.com wrote:
>> 
>> Yes the problem is defining what an identity change is precisely.  We 
>> know that CA's load all sorts of stuff in to certificates as part of 
>> the DN etc and the same identify could have multiple certificates, and 
>> could be identified by multiple CAs.  If we say that in TLS we are 
>> going to check identity then it has to be very precisely defined, or 
>> extremely vaguely defined so that the implementation can not be 
>> accused of non compliance or invalid/suspect identity matching.  
>> Perhaps it needs to be a vague as possible so that TLS implementation 
>> can simply push it back to the application layer in practice
>
>As previously expressed, I think this belongs at the application layer.

I also agree that identity should be handled by the application layer, as it
is not something TLS is best positioned to handle.

Nasko

v2.23.0 | Report a Bug | By Email