Re: [Trans] Prior knowledge of certificate serial number

Stephen Kent <kent@bbn.com> Thu, 25 September 2014 15:19 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 AF9991A7006 for <trans@ietfa.amsl.com>; Thu, 25 Sep 2014 08:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level:
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, 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 97_PLK_dX8MU for <trans@ietfa.amsl.com>; Thu, 25 Sep 2014 08:19:10 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D0141A0174 for <trans@ietf.org>; Thu, 25 Sep 2014 08:19:10 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:55357 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1XXApI-000FGH-10 for trans@ietf.org; Thu, 25 Sep 2014 11:19:24 -0400
Message-ID: <5424326A.1080502@bbn.com>
Date: Thu, 25 Sep 2014 11:19:06 -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: <54219AF0.6040901@gmail.com>
In-Reply-To: <54219AF0.6040901@gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/0DB7-WxG6Dn65zFOZ_8RFs3GwMo
Subject: Re: [Trans] Prior knowledge of certificate serial number
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: Thu, 25 Sep 2014 15:19:13 -0000

Melinda,

> One of the questions that's come up is whether or not it's reasonable
> to expect that CAs will (or can) have knowledge of a certificate's
> serial number prior to issuance - it's one of the basic questions that
> needs to be considered in the context of the precertificate discussions.
> We'd be grateful if any CAs (particularly ones with a CT implementation
> either in the works or planned) could give some feedback on that.
I've expressed concern that many of the Web PKI CAs may not be
tracking the CT work. I suggest you contact someone at the CABF and
ask them to conduct a poll of their members. I propose two questions:

1. Is anyone from your organization tracking the IETF TRANS WG?

2. Would your (Web PKI) certificate issuance process be adversely
affected if you
- generated a TBScertificate, including all the fields normally present 
in certs you issue
- submit this TBScert structure to two or more third parties (over the 
Internet)
- wait to receive a (newly-defined) extension value from each of these 
parties
- insert the extension values into the cert and sign it, without 
changing any of the
cert fields in the TBScert from step 1

Steve