Re: [certid] draft slides for IETF 77

Paul Hoffman <phoffman@imc.org> Fri, 19 March 2010 15:32 UTC

Return-Path: <phoffman@imc.org>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93A7C3A6A89 for <certid@core3.amsl.com>; Fri, 19 Mar 2010 08:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.237
X-Spam-Level:
X-Spam-Status: No, score=-5.237 tagged_above=-999 required=5 tests=[AWL=-0.321, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 4dNoXFi2YU5a for <certid@core3.amsl.com>; Fri, 19 Mar 2010 08:32:39 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 595CA3A6A64 for <certid@ietf.org>; Fri, 19 Mar 2010 08:32:39 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o2JFWnM8051756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Mar 2010 08:32:51 -0700 (MST) (envelope-from phoffman@imc.org)
Mime-Version: 1.0
Message-Id: <p0624086ec7c94944464a@[10.20.30.158]>
In-Reply-To: <4BA301EE.6070601@stpeter.im>
References: <4BA27EE4.80307@stpeter.im> <p0624085cc7c83b52391b@[10.20.30.158]> <20100318212053.GA7755@isc.upenn.edu> <4BA301EE.6070601@stpeter.im>
Date: Fri, 19 Mar 2010 08:32:49 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>, Shumon Huque <shuque@isc.upenn.edu>
From: Paul Hoffman <phoffman@imc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: certid@ietf.org
Subject: Re: [certid] draft slides for IETF 77
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 15:32:40 -0000

At 10:47 PM -0600 3/18/10, Peter Saint-Andre wrote:
>On 3/18/10 3:20 PM, Shumon Huque wrote:
>> On Thu, Mar 18, 2010 at 02:05:15PM -0700, Paul Hoffman wrote:
>>> At 1:28 PM -0600 3/18/10, Peter Saint-Andre wrote:
>>>> Content-Type: multipart/signed;
>>>> protocol="application/pkcs7-signature"; micalg=sha1;
>>>> boundary="------------ms080304070605060202080805"
>>>>
>>>> I've been asked to make a presentation about our work to the PKIX
>>>> WG session on Monday at 15:20 Pacific. Draft slides are attached
>>>> and feedback is welcome -- this is mostly just an overview to get
>>>> people interested in reviewing the I-D and providing feedback.
>>>
>>> In slide 3: s/PKI/PKIX. OpenPGP has its own (unspecified) PKI.
>>>
>>> But, more importantly in slide 3: Bullets 2, 3, and 5 disagree with
>>> each other. A server is a machine; it is not a domain or a URI. A
>>> domain name is not a URI. And so on. Consider adding a bullet
>>> saying "this is known to be unclear".
>>>
>>
>> I think "server" here refers not to a machine or set of machines, but
>> to an "application service" (application server?), ie. the server
>> side component of a client-server protocol.
>
>Correct.

A public key listed in a certificate is associated with *something* that has access to the associated private key. The machine has access to that private key, as does the server application/daemon. If you want to make this distinction, you need to do so much more clearly in the draft.