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

Shumon Huque <shuque@isc.upenn.edu> Thu, 09 September 2010 18:38 UTC

Return-Path: <shuque@isc.upenn.edu>
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 5A3763A6855; Thu, 9 Sep 2010 11:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.743
X-Spam-Level:
X-Spam-Status: No, score=-3.743 tagged_above=-999 required=5 tests=[AWL=-1.144, BAYES_00=-2.599]
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 lDUsoHQNFQDz; Thu, 9 Sep 2010 11:38:10 -0700 (PDT)
Received: from talkeetna.isc-net.upenn.edu (TALKEETNA.isc-net.upenn.edu [128.91.197.188]) by core3.amsl.com (Postfix) with ESMTP id AE3CE3A6894; Thu, 9 Sep 2010 11:38:02 -0700 (PDT)
Received: by talkeetna.isc-net.upenn.edu (Postfix, from userid 4127) id 42F0926E4; Thu, 9 Sep 2010 14:38:29 -0400 (EDT)
Date: Thu, 09 Sep 2010 14:38:29 -0400
From: Shumon Huque <shuque@isc.upenn.edu>
To: Stefan Santesson <stefan@aaa-sec.com>
Subject: Re: [certid] Review of draft-saintandre-tls-server-id-check
Message-ID: <20100909183829.GA4332@isc.upenn.edu>
References: <4C880FBB.7070309@stpeter.im> <C8ADEB52.EBBB%stefan@aaa-sec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C8ADEB52.EBBB%stefan@aaa-sec.com>
User-Agent: Mutt/1.4.2.1i
Organization: University of Pennsylvania
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: Thu, 09 Sep 2010 18:38:11 -0000

On Thu, Sep 09, 2010 at 01:39:30AM +0200, Stefan Santesson wrote:
> 
> I actually think we made an error in 4985 and that the domain name should be
> the domain that the service is authorized to represent.
> 
> RFC 4985 is ambiguous here: the definition of the name form says:
> 
>    "The DNS domain name of the domain where the specified service
>     is located."
> 
> This corresponds to #2 in your example
> While the description underneath the definition states:
> 
>    "The purpose of the SRVName is limited to authorization of service
>     provision within a domain."
> 
> Which corresponds to #1.
> 
> I think there should be an errata correcting the definition to be:
> 
>    "The DNS domain name of a domain for which the certified subject
>     is authorized to provide the identified service."
> 
> As it is now, the RFC is ambiguous.

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.

-- 
Shumon Huque
University of Pennsylvania.