Re: [certid] version -07

Peter Saint-Andre <stpeter@stpeter.im> Mon, 12 July 2010 14:52 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 0BBE93A698C for <certid@core3.amsl.com>; Mon, 12 Jul 2010 07:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.862
X-Spam-Level:
X-Spam-Status: No, score=-2.862 tagged_above=-999 required=5 tests=[AWL=-0.262, 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 Ln5XpbBrb6aU for <certid@core3.amsl.com>; Mon, 12 Jul 2010 07:52:01 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 79DAD3A6990 for <certid@ietf.org>; Mon, 12 Jul 2010 07:52:01 -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 D6A1740E44 for <certid@ietf.org>; Mon, 12 Jul 2010 08:52:08 -0600 (MDT)
Message-ID: <4C3B2C16.7000209@stpeter.im>
Date: Mon, 12 Jul 2010 08:52:06 -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.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: certid@ietf.org
References: <4C2ECEB6.7080209@KingsMountain.com>
In-Reply-To: <4C2ECEB6.7080209@KingsMountain.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
Subject: Re: [certid] version -07
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: Mon, 12 Jul 2010 14:52:03 -0000

On 7/2/10 11:46 PM, =JeffH wrote:
> As PaulH said ... finally decloaking after being off this topic for a
> while. Apologies for latency.
> 
> Peter, thanks for updating the draft!
> 
> All -- good discussion on the list, thanks for all the thoughtful
> contributions -- the spec is much better for it.
> 
> Yes, I have various bits of feedback on -07, some described below. this
> is without a careful review though, and is driven by reading through the
> recent threads on certid@ and checking -07 for how the issues were
> addressed. I concur with the decisions taken. It seems that all raised
> issues were nominally addressed in -07, so the below are
> (subtle-but-important) nits.
> 
> =JeffH
> ------
> 
> [ the below items aren't necessarily difficult to clean up, I'm just
> noting them for the record for now ]
> 
> * It seems to me coming to this new revision of the spec somewhat
> "fresh", that the concepts being addressed could build more cleanly from
> (especially) section 1.1 (intro/motivation), section 2 Names, and
> section 3 Representation of Server Identity. I can take a whack at
> making concrete suggestions by early/mid this next week.

That sounds nice but not necessary. :)

> * need to explicitly define (at least) the below terms/phrases in
> section 1.3 if we are going to use them..
> 
>    attribute-type-and-value pair
> 
>    DER encoding
> 
>    Internet application   ..or..   application service   ..or..   ?
> 
>    service provider
> 
>    subjectAltName   (this term is used in section 1.3 but isn't itself
> defined
>                      until seciton 2.2)

Added to the terminology section (along with several other terms).

> * I think we need to review the terms/phrases we use to reference cert
> components and aspects thereof. I think we're being inconsistent and at
> times ambiguous (need to do careful review). unfortunately other specs
> we depend on use non-congruent terminology it seems.
> 
> E.g. in just sections 2.2 and 3 we use these various terms/phrases wrt
> "subjectAltName"...
> 
>   subjectAltName extension
> 
>   subjectAltName extension types
> 
>   subjectAltNames
> 
>   subjectAltName entry
> 
>   SubjectAltName field
> 
>   subjectAltName identifier
> 
>   subjectAltName identifier types
> 
>   subjectAltName identifier of type
> 
>   [the GeneralName structure in] the subjectAltName
> 
> 
> ..and then including the rest of the spec we also use (in addition to
> the above)..
> 
>   application-specific subjectAltName extensions
> 
>   subjectAltName extension of type
> 
>   subjectAltName extensions of type
> 
> 
> Obviously various of the above terms/phrases are redundant and we ought
> to clean this up.

Fixed, per my previous message.

> ---
> end

I hope we're nearing the end so that we can request a Last Call soon
(several specs now have dependencies on this I-D, including one that's
already been approved by the IESG and one that will soon go into IETF
Last Call).

Peter

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