From stephen.farrell@cs.tcd.ie Fri Jun 7 05:04:00 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379FD21F86B2 for ; Fri, 7 Jun 2013 05:04:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xeSb6CXF9pqE for ; Fri, 7 Jun 2013 05:03:51 -0700 (PDT) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5938D21F89FF for ; Fri, 7 Jun 2013 05:03:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4C30BBE87 for ; Fri, 7 Jun 2013 13:03:28 +0100 (IST) Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxADr+0vGv8o for ; Fri, 7 Jun 2013 13:03:28 +0100 (IST) Received: from [IPv6:2001:770:10:203:80ef:4ae:b4e0:a4c4] (unknown [IPv6:2001:770:10:203:80ef:4ae:b4e0:a4c4]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2CD4CBE73 for ; Fri, 7 Jun 2013 13:03:28 +0100 (IST) Message-ID: <51B1CC11.60706@cs.tcd.ie> Date: Fri, 07 Jun 2013 13:03:29 +0100 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "therightkey@ietf.org" References: <20130606205725.E4B4DB1E003@rfc-editor.org> In-Reply-To: <20130606205725.E4B4DB1E003@rfc-editor.org> X-Enigmail-Version: 1.5.1 X-Forwarded-Message-Id: <20130606205725.E4B4DB1E003@rfc-editor.org> Content-Type: multipart/mixed; boundary="------------030505070209060102080902" Subject: [therightkey] Fwd: RFC 6962 on Certificate Transparency X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 12:04:00 -0000 This is a multi-part message in MIME format. --------------030505070209060102080902 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit FYI. Well done all. Be interesting to see how this works out in the wild. Cheers, S. -------- Original Message -------- Subject: RFC 6962 on Certificate Transparency Date: Thu, 6 Jun 2013 13:57:25 -0700 (PDT) From: rfc-editor@rfc-editor.org Reply-To: ietf@ietf.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 6962 Title: Certificate Transparency Author: B. Laurie, A. Langley, E. Kasper Status: Experimental Stream: IETF Date: June 2013 Mailbox: benl@google.com, agl@google.com, ekasper@google.com Pages: 27 Characters: 55048 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-laurie-pki-sunlight-12.txt URL: http://www.rfc-editor.org/rfc/rfc6962.txt This document describes an experimental protocol for publicly logging the existence of Transport Layer Security (TLS) certificates as they are issued or observed, in a manner that allows anyone to audit certificate authority (CA) activity and notice the issuance of suspect certificates as well as to audit the certificate logs themselves. The intent is that eventually clients would refuse to honor certificates that do not appear in a log, effectively forcing CAs to add all issued certificates to the logs. Logs are network services that implement the protocol operations for submissions and queries that are defined in this document. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC --------------030505070209060102080902 Content-Type: text/plain; charset=UTF-8; name="Attached Message Part" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Attached Message Part" --------------030505070209060102080902--