IETF Logo Mail Archive

Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed

"trans issue tracker" <trac+trans@tools.ietf.org> Tue, 03 November 2015 01:11 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 5D7EA1ACD37 for <trans@ietfa.amsl.com>; Mon, 2 Nov 2015 17:11:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 vGEKtuo8LCin for <trans@ietfa.amsl.com>; Mon, 2 Nov 2015 17:11:37 -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 48EB81ACD2E for <trans@ietf.org>; Mon, 2 Nov 2015 17:11:37 -0800 (PST)
Received: from localhost ([::1]:42169 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 1ZtQ8O-0002iS-Tr; Mon, 02 Nov 2015 17:11:36 -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: eranm@google.com
X-Trac-Project: trans
Date: Tue, 03 Nov 2015 01:11:36 -0000
X-URL: http://tools.ietf.org/trans/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/trans/trac/ticket/99#comment:2
Message-ID: <071.c4438e8732b810844a1b1d63f6516b38@tools.ietf.org>
References: <056.44d8e1af7d476e6c42f98a5d494bb486@tools.ietf.org>
X-Trac-Ticket-ID: 99
In-Reply-To: <056.44d8e1af7d476e6c42f98a5d494bb486@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: eranm@google.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/vCCt2GNp25CazwAmoIanDbh5ICM>
Cc: trans@ietf.org
Subject: Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
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: Tue, 03 Nov 2015 01:11:38 -0000

#99: Clearer definition of when a certificate is CT-compliant needed

Changes (by eranm@google.com):

 * status:  closed => reopened
 * resolution:  needs-review =>


-- 
------------------------------+-------------------------------
 Reporter:  eranm@google.com  |       Owner:  eranm@google.com
     Type:  defect            |      Status:  reopened
 Priority:  major             |   Milestone:
Component:  rfc6962-bis       |     Version:
 Severity:  -                 |  Resolution:
 Keywords:                    |
------------------------------+-------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/99#comment:2>
trans <http://tools.ietf.org/trans/>

v2.23.0 | Report a Bug | By Email