Re: Review of draft-saintandre-tls-server-id-check

Peter Saint-Andre <stpeter@stpeter.im> Mon, 13 September 2010 19:21 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B572F3A69F9; Mon, 13 Sep 2010 12:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level:
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Cmw1uv2rf+Se; Mon, 13 Sep 2010 12:21:35 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 710E03A69A1; Mon, 13 Sep 2010 12:21:35 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0C1A8400EE; Mon, 13 Sep 2010 13:26:06 -0600 (MDT)
Message-ID: <4C8E79D7.3080507@stpeter.im>
Date: Mon, 13 Sep 2010 13:21:59 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Review of draft-saintandre-tls-server-id-check
References: <20100908195349.GA4292@isc.upenn.edu> <C8ADC7ED.EBA4%stefan@aaa-sec.com> <20100909182253.GB3460@isc.upenn.edu> <4C8E4C6B.3040803@stpeter.im> <20100913165259.GA9709@isc.upenn.edu> <8252.1284397511.595153@puncture> <4C8E7218.6010204@stpeter.im> <8252.1284405493.018713@puncture>
In-Reply-To: <8252.1284405493.018713@puncture>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, IETF cert-based identity <certid@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 19:21:36 -0000

On 9/13/10 1:18 PM, Dave Cridland wrote:
> On Mon Sep 13 19:48:56 2010, Peter Saint-Andre wrote:
>> On 9/13/10 11:05 AM, Dave Cridland wrote:
>> > Looking at the draft, it seems to read that I should check dNSName
>> > first, and then, only if this matches, check xmppAddr or sRVName. This
>> > seems odd - sRVName and xmppAddr (and URI) all contain a superset of
>> the
>> > data contained, so why look at dNSName if a more specific match exists?
>>
>> Earlier versions of this draft had somewhat elaborate rules about
>> ordering of reference identifiers. Those rules were removed in -09
>> because folks on the certid@ietf.org list argued persuasively that they
>> were not necessary because "first match wins" is good enough. Naturally,
>> an implementation might have a preference order of reference
>> identifiers, but such an order is not mandated by this I-D.
> 
> Ah, I see my confusion. §4.4 says:
> 
> 4.4. Verifying a Domain Name
> 
>   The client MUST match the source domain of a reference identifier
>   according to the following rules
> 
> And §4.5 says:
> 
> 4.5. Verifying an Application Type
> 
>   A client SHOULD check not only the domain name but also the service
>   type of the service to which it connects.
> 
> Now, I misconstrued that to mean "MUST use dNSName, SHOULD use sRVName",
> which is purely me misreading.
> 
> Up to you whether you think other people will be as silly as me, and
> what to do about it if so.

A forward reference seem appropriate:

   The client MUST match the source domain of a reference identifier
   according to the following rules (and SHOULD also check the service
   type as described under Section 4.5).

Peter

-- 
Peter Saint-Andre
https://stpeter.im/