Re: [Trans] [trans] #73 (rfc6962-bis): Section 3 text re logcertvalidation is ambiguous

Stephen Kent <kent@bbn.com> Mon, 06 July 2015 19:50 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 8BD4D1B313D for <trans@ietfa.amsl.com>; Mon, 6 Jul 2015 12:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 y8ebgyRDKG3v for <trans@ietfa.amsl.com>; Mon, 6 Jul 2015 12:50:15 -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 0F8061B309C for <trans@ietf.org>; Mon, 6 Jul 2015 12:50:15 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:59307 helo=COMSEC-2.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1ZCCP7-000KVZ-Iw; Mon, 06 Jul 2015 15:50:13 -0400
Message-ID: <559ADBF5.7000807@bbn.com>
Date: Mon, 06 Jul 2015 15:50:13 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Rob Stradling <rob.stradling@comodo.com>, trans@ietf.org
References: <052.b3ecc6ca8b28cc47e13443079611ce86@tools.ietf.org><067.7becba46c4f8b854834f9bb0c27374ce@tools.ietf.org><559A9977.1040808@bbn.com> <559A9B83.6040000@comodo.com> <559AA60A.1060501@bbn.com> <559AD74A.5030806@comodo.com>
In-Reply-To: <559AD74A.5030806@comodo.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/pLFnvatrR3lx0KV0Mi26hEdU7kE>
Subject: Re: [Trans] [trans] #73 (rfc6962-bis): Section 3 text re logcertvalidation is ambiguous
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 06 Jul 2015 19:50:18 -0000

Rob,

> On 06/07/15 17:00, Stephen Kent wrote:
>> Rob,
>>
>> Having a cert rejected does not tell the submitter (CA or otherwise)
>> why, and thus the submitted doesn't know how to resolve the problem.
>
> Are the folks that work for (sloppy) CAs really incapable of reading 
> RFC5280 for themselves, incapable of examining their rejected certs to 
> discover the problem(s) for themselves, and incapable of finding a 
> suitable mailing list on which to ask questions if they get stuck?
I think may have misunderstood my point. I did not request that a log 
return an error indicating
why a cert failed the logs checks. I asked that there be a deterministic 
way for a submitter
to know whether a cert will pass. That can be accomplished in (at least) 
two ways:
establish a standard set of checks that all logs perform, or establish a 
way to each log to
state what set of checks it performs.

Steve