Re: [Trans] Precertificate format

Stephen Kent <kent@bbn.com> Wed, 10 September 2014 16:09 UTC

Return-Path: <kent@bbn.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA3D1A8786 for <trans@ietfa.amsl.com>; Wed, 10 Sep 2014 09:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.853
X-Spam-Level:
X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2fEWOPB6BX5t for <trans@ietfa.amsl.com>; Wed, 10 Sep 2014 09:09:08 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1F9D1A8787 for <trans@ietf.org>; Wed, 10 Sep 2014 09:09:00 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:59995 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1XRkS3-000Jcg-Ov for trans@ietf.org; Wed, 10 Sep 2014 12:08:59 -0400
Message-ID: <5410779A.20209@bbn.com>
Date: Wed, 10 Sep 2014 12:08:58 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: trans@ietf.org
References: <540DFA75.2040000@gmail.com> <540E0E90.1070208@bbn.com> <540E28FD.7050809@gmail.com> <540ECD3A.4040704@primekey.se> <540F4598.5010505@bbn.com> <CABrd9SSg5=wuierLoqAU00pMHxgGx+=ai5mHv4u5t6zm43yDWg@mail.gmail.com>
In-Reply-To: <CABrd9SSg5=wuierLoqAU00pMHxgGx+=ai5mHv4u5t6zm43yDWg@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/OY6z-Mnetj6xwXt4CBfSrOLzXoU
Subject: Re: [Trans] Precertificate format
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 16:09:12 -0000

Ben,

> On 9 September 2014 19:23, Stephen Kent<kent@bbn.com>  wrote:
>> I agree that using a redefined (to include the serial number) cert template
>> from CRMF would avoid the 5280 issue, but it still requires the CA to assign
>> the serial number before
>> the cert is issued. That is my biggest concern, i.e., it imposes a new
>> requirement on
>> CAs, one that may have adverse security implication for some. Nonetheless, I
>> like your suggestion (minus the serial number) as a starting point. See my
>> next message.
> I have a suggestion: let the RFC say that any certificate which the
> log knows can be revoked without knowing its serial number can omit
> the serial number.
because, as you noted, we have no IETF-standard way to revoke a single
cert w/o knowing its serial number, I don't think this is a good fix.

Nonetheless, I do appreciate your willingness to explore alternative 
approaches
to address the concern I raised.

Steve