OCSP Algorithm Agility
draft-hallambaker-ocspagility-02

Document Type Expired Internet-Draft (individual)
Author Phillip Hallam-Baker 
Last updated 2008-12-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hallambaker-ocspagility-02.txt

Abstract

The OSCP specification defined in RFC 2560 requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used leading to possible interoperability failures in contexts where multiple signature algorithms are in use. This document specifies an algorithm for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported.

Authors

Phillip Hallam-Baker (pbaker@verisign.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)