RFC 6961 on The Transport Layer Security (TLS) Multiple Certificate Status Request Extension

A new Request for Comments is now available in online RFC libraries.

        RFC 6961

        Title:      The Transport Layer Security (TLS) 
                    Multiple Certificate Status Request Extension 
        Author:     Y. Pettersen
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2013
        Mailbox:    yngve@spec-work.net
        Pages:      10
        Characters: 21473
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-multiple-cert-status-extension-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6961.txt

This document defines the Transport Layer Security (TLS) Certificate
Status Version 2 Extension to allow clients to specify and support
several certificate status methods.  (The use of the Certificate
Status extension is commonly referred to as "OCSP stapling".)  Also
defined is a new method based on the Online Certificate Status
Protocol (OCSP) that servers can use to provide status information
about not only the server's own certificate but also the status of
intermediate certificates in the chain.

This document is a product of the Transport Layer Security Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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