[Trans] [trans] #76 (client-behavior): Normative client behavior specified in Section 3.4
"trans issue tracker" <trac+trans@tools.ietf.org> Fri, 20 March 2015 17:56 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 703621A1E0F for <trans@ietfa.amsl.com>; Fri, 20 Mar 2015 10:56:52 -0700 (PDT)
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=unavailable
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 LVGByBiGHzin for <trans@ietfa.amsl.com>; Fri, 20 Mar 2015 10:56:51 -0700 (PDT)
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 74F831A3B9C for <trans@ietf.org>; Fri, 20 Mar 2015 10:56:50 -0700 (PDT)
Received: from localhost ([::1]:58760 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 1YZ1AA-0005rM-4i; Fri, 20 Mar 2015 10:56:50 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: trans issue tracker <trac+trans@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-trans-rfc6962-bis@tools.ietf.org, kent@bbn.com
X-Trac-Project: trans
Date: Fri, 20 Mar 2015 17:56:50 -0000
X-URL: http://tools.ietf.org/trans/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/trans/trac/ticket/76
Message-ID: <052.0789019d9e32c9233f0440891ac5bb94@tools.ietf.org>
X-Trac-Ticket-ID: 76
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-trans-rfc6962-bis@tools.ietf.org, kent@bbn.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
Resent-To: draft-ietf-trans-rfc6962-bis@ietf.org
Resent-Message-Id: <20150320175650.74F831A3B9C@ietfa.amsl.com>
Resent-Date: Fri, 20 Mar 2015 10:56:50 -0700
Resent-From: trac+trans@tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/TUGbepVUwaPh8j70q8HKA1uee2w>
Cc: trans@ietf.org
Subject: [Trans] [trans] #76 (client-behavior): Normative client behavior specified in Section 3.4
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: <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: Fri, 20 Mar 2015 17:56:52 -0000
#76: Normative client behavior specified in Section 3.4 Section 3.4 does a much better job of explaining why there are 3 options for transmitting the SCT. However, the description of the certificate extension says that a certificate is more likely to be refused if any of the SCTs are now “invalid.” This statement cites specific TLS client behavior, which is out of scope. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-trans- kent@bbn.com | rfc6962-bis@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: client- | Version: behavior | Keywords: Severity: - | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/76> trans <http://tools.ietf.org/trans/>
- [Trans] [trans] #76 (client-behavior): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … Stephen Kent
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … Stephen Kent
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … Stephen Kent
- Re: [Trans] [trans] #76 (rfc6962-bis): Normative … trans issue tracker