[Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA
"trans issue tracker" <trac+trans@tools.ietf.org> Fri, 12 February 2016 10:57 UTC
Return-Path: <trac+trans@tools.ietf.org>
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 4980E1B4354 for <trans@ietfa.amsl.com>; Fri, 12 Feb 2016 02:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 n4iMzvuapwnI for <trans@ietfa.amsl.com>; Fri, 12 Feb 2016 02:57:25 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B28B1B4353 for <trans@ietf.org>; Fri, 12 Feb 2016 02:57:25 -0800 (PST)
Received: from localhost ([::1]:35680 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+trans@tools.ietf.org>) id 1aUBPd-0005Du-Gt; Fri, 12 Feb 2016 02:57:21 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: trans issue tracker <trac+trans@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: rob.stradling@comodo.com
X-Trac-Project: trans
Date: Fri, 12 Feb 2016 10:57:21 -0000
X-URL: https://tools.ietf.org/trans/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/trans/trac/ticket/154
Message-ID: <065.c4b15e6c4f869845c93207c4640d700b@tools.ietf.org>
X-Trac-Ticket-ID: 154
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: rob.stradling@comodo.com, trans@ietf.org
X-SA-Exim-Mail-From: trac+trans@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/uXqtVIDMKocaaatGl0jcc3AbnGc>
Cc: trans@ietf.org
Subject: [Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Feb 2016 10:57:27 -0000
#154: CSR extension to convey a certificate subscriber's CT preferences to the CA Some certificate subscribers might want to communicate various CT-related things to the CA. For example... - Please generate a Precertificate and then embed SCTs in the certificate. - I'm using OCSP Stapling; please embed SCTs in OCSP Responses for this certificate. - Please embed inclusion proofs (rather than SCTs) in the certificate; I accept that this will delay issuance of the certificate. - Please embed SCTs from as many logs as possible. - Please embed SCTs from logs X, Y and Z, and not from logs A, B or C. - Please do _not_ log this certificate to any logs; I accept that some TLS clients may reject the certificate due to CT non-compliance. Some CAs might permit these sorts of details to be specified in a <form> on a webpage when the subscriber requests the certificate. That's great, but it probably won't work for everyone. In particular, putting this information in a CSR extension would make it possible to tunnel it through ACME or via a certificate reseller. (I'm assigning this ticket to the rfc6962-bis component for now, but I see no particular reason why it couldn't be punted to some other document. I don't want this ticket to delay WGLC for 6962-bis). -- -------------------------------------+------------------------------------- Reporter: | Owner: rob.stradling@comodo.com | rob.stradling@comodo.com Type: enhancement | Status: new Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Keywords: -------------------------------------+------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/154> trans <https://tools.ietf.org/trans/>
- [Trans] [trans] #154 (rfc6962-bis): CSR extension… trans issue tracker
- Re: [Trans] [trans] #154 (rfc6962-bis): CSR exten… trans issue tracker
- Re: [Trans] [trans] #154 (rfc6962-bis): CSR exten… trans issue tracker
- Re: [Trans] [trans] #154 (rfc6962-bis): CSR exten… trans issue tracker
- Re: [Trans] [trans] #154 (to-be-decided): CSR ext… trans issue tracker