IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@stpeter.im> Mon, 13 September 2010 16:17 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 BC85C3A6A1D; Mon, 13 Sep 2010 09:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level:
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 SfQlhZzTvtWo; Mon, 13 Sep 2010 09:17:41 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 3239C3A6A11; Mon, 13 Sep 2010 09:17:36 -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 E7F72400EE; Mon, 13 Sep 2010 10:22:06 -0600 (MDT)
Message-ID: <4C8E4EB8.8030905@stpeter.im>
Date: Mon, 13 Sep 2010 10:18:00 -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: Stefan Santesson <stefan@aaa-sec.com>
Subject: Re: [certid] Review of draft-saintandre-tls-server-id-check
References: <C8AF03F6.EC6E%stefan@aaa-sec.com>
In-Reply-To: <C8AF03F6.EC6E%stefan@aaa-sec.com>
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: 7bit
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 16:17:52 -0000

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

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

v2.23.0 | Report a Bug | By Email