IETF Logo Mail Archive

Re: [pkix] Proposal to review and adopt CertID and KeyID proposal

Stefan Santesson <stefan@aaa-sec.com> Tue, 02 March 2010 21:46 UTC

Return-Path: <stefan@aaa-sec.com>
X-Original-To: pkix@core3.amsl.com
Delivered-To: pkix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 520133A8CD2 for <pkix@core3.amsl.com>; Tue, 2 Mar 2010 13:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 W-90R-VPB7H3 for <pkix@core3.amsl.com>; Tue, 2 Mar 2010 13:46:41 -0800 (PST)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.114]) by core3.amsl.com (Postfix) with ESMTP id 780313A8538 for <pkix@ietf.org>; Tue, 2 Mar 2010 13:46:40 -0800 (PST)
Received: from s19.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id DCEC7341014 for <pkix@ietf.org>; Tue, 2 Mar 2010 22:46:48 +0100 (CET)
Received: (qmail 60694 invoked from network); 2 Mar 2010 21:46:40 -0000
Received: from 213-64-142-247-no153.business.telia.com (HELO [192.168.1.16]) (stefan@fiddler.nu@[213.64.142.247]) (envelope-sender <stefan@aaa-sec.com>) by s19.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <dev+ietf@seantek.com>; 2 Mar 2010 21:46:40 -0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Tue, 02 Mar 2010 22:46:38 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Sean Leonard <dev+ietf@seantek.com>, pkix@ietf.org
Message-ID: <C7B345CE.8C12%stefan@aaa-sec.com>
Thread-Topic: [pkix] Proposal to review and adopt CertID and KeyID proposal
Thread-Index: Acq6UdYQp/XaKwJm3kmZlrFDaBbexg==
In-Reply-To: <4B8D78D1.2030203@seantek.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [pkix] Proposal to review and adopt CertID and KeyID proposal
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 21:46:42 -0000

Sean,

On this particular issue:


On 10-03-02 9:45 PM, "Sean Leonard" <dev+ietf@seantek.com> wrote:

> * Refocus the proposal to standardizing on a single structure for
> uniquely identifying certificates on a going-forward basis. Namely:
>    PKIXCertID ::= ESSCertIDv2


What is the point of defining PKIXCertID?
Why not just refer to ESSCertIDv2?

As we have done in RFC 3161 update. See:
http://tools.ietf.org/html/draft-ietf-pkix-rfc3161-update-09


/Stefan

v2.23.0 | Report a Bug | By Email