Re: [Trans] Precertificate format

Stephen Kent <kent@bbn.com> Wed, 10 September 2014 16:08 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 0E6911A8741 for <trans@ietfa.amsl.com>; Wed, 10 Sep 2014 09:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.852
X-Spam-Level:
X-Spam-Status: No, score=-5.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 laKWtgWOMECM for <trans@ietfa.amsl.com>; Wed, 10 Sep 2014 09:08:48 -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 E33361A8780 for <trans@ietf.org>; Wed, 10 Sep 2014 09:08:43 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:47853 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1XRkS1-000JOu-10 for trans@ietf.org; Wed, 10 Sep 2014 12:08:57 -0400
Message-ID: <54107789.1060003@bbn.com>
Date: Wed, 10 Sep 2014 12:08:41 -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><CAFewVt5kZqw0-W7PqtFHe7yJUsR9PqVJ6C74ZShgo0qs19wLjA@mail.gmail.com><544B0DD62A64C1448B2DA253C011414607D07DC251@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM><20140909011451.GW5645@hezmatt.org><CALzYgEee_=1HTBvF3MQEZeeZc9VL_rK2eRjwVjOnhZKEO+8r=w@mail.gmail.com> <540F459E.6060504@bbn.com> <5410189E.4020808@comodo.com>
In-Reply-To: <5410189E.4020808@comodo.com>
Content-Type: multipart/alternative; boundary="------------040708000109060005020606"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/5HJAo3slqNeS7F2htHRfDWPdbII
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:08:54 -0000

Rob,

> Hi Stephen. That's an interesting idea, but I see a few issues.
>
> Step 4 requires the final cert to be logged, so it's incompatible with 
> the name redaction mechanism.
Oops, an oversimplified description on my part. In step 4 I think one 
can apply the whatever redaction mechanisms that we adopt.
> Monitors want to detect misissuance (i.e. certs that have been issued 
> incorrectly). I'm not sure that it's reasonable to expect Monitors to 
> also take responsibility for detecting non-issuance of certs that 
> should have been issued.
The current I-D says
Monitors watch logs and check that they behave correctly.They also

watch for certificates of interest.


The non-issuance of an SCT after issuance of an SCT* for a "certificate 
of interest"
would seem to be within scope, given the somewhat vague description in 
the I-D.


Steve