[pkix] RFC 6960 on X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP

rfc-editor@rfc-editor.org Thu, 06 June 2013 20:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AFA11E8107; Thu, 6 Jun 2013 13:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.233
X-Spam-Level:
X-Spam-Status: No, score=-102.233 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 zJ1hlnJPY3sW; Thu, 6 Jun 2013 13:58:36 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 724C421E80DE; Thu, 6 Jun 2013 13:58:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5569EB1E004; Thu, 6 Jun 2013 13:57:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130606205707.5569EB1E004@rfc-editor.org>
Date: Thu, 06 Jun 2013 13:57:07 -0700
Cc: pkix@ietf.org, rfc-editor@rfc-editor.org
Subject: [pkix] RFC 6960 on X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 20:58:37 -0000

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

        
        RFC 6960

        Title:      X.509 Internet Public Key Infrastructure 
                    Online Certificate Status Protocol - OCSP 
        Author:     S. Santesson, M. Myers,
                    R. Ankney, A. Malpani,
                    S. Galperin, C. Adams
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2013
        Mailbox:    sts@aaa-sec.com, 
                    mmyers@fastq.com, 
                    none,  ambarish@gmail.com, 
                    slava.galperin@gmail.com,
                    cadams@eecs.uottawa.ca
        Pages:      41
        Characters: 82037
        Obsoletes:  RFC 2560, RFC 6277
        Updates:    RFC 5912

        I-D Tag:    draft-ietf-pkix-rfc2560bis-20.txt

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

This document specifies a protocol useful in determining the current 
status of a digital certificate without requiring Certificate Revocation 
Lists (CRLs).  Additional mechanisms addressing PKIX operational 
requirements are specified in separate documents.  This document obsoletes 
RFCs 2560 and 6277.  It also updates RFC 5912.

This document is a product of the Public-Key Infrastructure (X.509) 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