RFC 6277 on Online Certificate Status Protocol Algorithm Agility
rfc-editor@rfc-editor.org Fri, 10 June 2011 17:27 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 190D511E80CC; Fri, 10 Jun 2011 10:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level:
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VzEB-1d4776G; Fri, 10 Jun 2011 10:27:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8990C11E8077; Fri, 10 Jun 2011 10:27:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7591598C512; Fri, 10 Jun 2011 10:27:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6277 on Online Certificate Status Protocol Algorithm Agility
From: rfc-editor@rfc-editor.org
Message-Id: <20110610172713.7591598C512@rfc-editor.org>
Date: Fri, 10 Jun 2011 10:27:13 -0700
Cc: pkix@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 17:27:15 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6277
Title: Online Certificate Status Protocol Algorithm
Agility
Author: S. Santesson, P. Hallam-Baker
Status: Standards Track
Stream: IETF
Date: June 2011
Mailbox: sts@aaa-sec.com,
hallam@gmail.com
Pages: 11
Characters: 21682
Updates: RFC2560
I-D Tag: draft-ietf-pkix-ocspagility-10.txt
URL: http://www.rfc-editor.org/rfc/rfc6277.txt
The Online Certificate Status Protocol (OCSP) requires
server responses to be signed but does not specify a mechanism for
selecting the signature algorithm to be used. This may lead to
avoidable interoperability failures in contexts where multiple
signature algorithms are in use. This document specifies rules for
server signature algorithm selection and an extension that allows a
client to advise a server that specific signature algorithms are
supported. [STANDARDS-TRACK]
This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
This is now a Proposed Standard Protocol.
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