Re: [certid] draft slides for IETF 77

Peter Saint-Andre <stpeter@stpeter.im> Fri, 19 March 2010 19:50 UTC

Return-Path: <stpeter@stpeter.im>
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 677ED3A68CF for <certid@core3.amsl.com>; Fri, 19 Mar 2010 12:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level:
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 essTXYnQ2bOg for <certid@core3.amsl.com>; Fri, 19 Mar 2010 12:50:31 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 7D8163A681F for <certid@ietf.org>; Fri, 19 Mar 2010 12:50:31 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 19EB540D3A; Fri, 19 Mar 2010 13:50:43 -0600 (MDT)
Message-ID: <4BA3D592.6050606@stpeter.im>
Date: Fri, 19 Mar 2010 13:50:42 -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.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Paul Hoffman <phoffman@imc.org>
References: <4BA27EE4.80307@stpeter.im> <p0624085cc7c83b52391b@[10.20.30.158]> <20100318212053.GA7755@isc.upenn.edu> <4BA301EE.6070601@stpeter.im> <p0624086ec7c94944464a@[10.20.30.158]>
In-Reply-To: <p0624086ec7c94944464a@[10.20.30.158]>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060407020809070305050607"
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 19:50:32 -0000

On 3/19/10 9:32 AM, Paul Hoffman wrote:
> 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.

Paul, I agree that this needs to be clearer in the I-D. I've added a
slide on this point and will discuss it at the PKIX session, then fix up
the I-D as soon as possible after Anaheim.

Peter

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