Re: [certid] Review of draft-saintandre-tls-server-id-check

"Richard L. Barnes" <rbarnes@bbn.com> Mon, 13 September 2010 17:00 UTC

Return-Path: <rbarnes@bbn.com>
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 263A83A6A73; Mon, 13 Sep 2010 10:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level:
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, 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 Ro3FTjK4dFsT; Mon, 13 Sep 2010 10:00:50 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 293303A6A72; Mon, 13 Sep 2010 10:00:50 -0700 (PDT)
Received: from [192.1.255.185] (port=54786 helo=col-dhcp-192-1-255-185.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OvCP5-000PoW-GT; Mon, 13 Sep 2010 13:01:15 -0400
Message-Id: <D6499A36-BCF1-4E19-AF64-9AC8F140BB5C@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4C8E4EB8.8030905@stpeter.im>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: [certid] Review of draft-saintandre-tls-server-id-check
Date: Mon, 13 Sep 2010 13:01:13 -0400
References: <C8AF03F6.EC6E%stefan@aaa-sec.com> <4C8E4EB8.8030905@stpeter.im>
X-Mailer: Apple Mail (2.936)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, IETF cert-based identity <certid@ietf.org>, 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 17:00:51 -0000

On Sep 13, 2010, at 12:18 PM, Peter Saint-Andre wrote:

> On 9/9/10 1:36 PM, Stefan Santesson wrote:
>>
>>
>>
>> On 10-09-09 8:38 PM, "Shumon Huque" <shuque@isc.upenn.edu> wrote:
>>
>>> Earlier in RFC 4985, it says:
>>>
>>>   The SRVName, if present, MUST contain a service name and a domain
>>>   name in the following form:
>>>
>>>      _Service.Name
>>>
>>>   The content of the components of this name form MUST be consistent
>>>   with the corresponding definition of these components in an SRV RR
>>>   according to RFC 2782
>>>
>>> I think this was actually clear enough. The subsequent statement  
>>> that
>>> Name is "The DNS domain name of the domain where the specified  
>>> service
>>> is located." (which could mean any of a number of things) confused  
>>> the
>>> issue, and probably should not have been in the document.
>>
>>
>> Agreed, but since it will be an errata, the text must be corrected.
>>
>> Do you agree with my proposal?
>>
>>    "The DNS domain name of a domain for which the certified subject
>>     is authorized to provide the identified service."
>
> Authorized by whom? I *think* that here the DNS domain name is one  
> that
> the certified subject has itself authorized (perhaps even  
> "established"
> is better) to provide the desired service. Therefore I suggest an
> alternative wording:
>
>     "A DNS domain name which the certified subject has
>      authorized to provide the identified service."
>
> Peter

I don't think that's right either, since it's the *issuer* of the cert  
that's making the assertion.  Maybe something like the following:
"
A DNS domain name for which the issuer authorizes the subject to  
provide the indicated service.
"