RFC 4055 on Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

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

        RFC 4055

        Title:      Additional Algorithms and Identifiers for RSA
                    Cryptography for use in the Internet X.509 Public
                    Key Infrastructure Certificate and Certificate
                    Revocation List (CRL) Profile
        Author(s):  J. Schaad, B. Kaliski, R. Housley
        Status:     Standards Track
        Date:       June 2005
        Mailbox:    jimsch@exmsft.com, bkaliski@rsasecurity.com,
                    housley@vigilsec.com
        Pages:      25
        Characters: 57479
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pkix-rsa-pkalgs-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4055.txt

This document supplements RFC 3279.  It describes the conventions for
using the RSA Probabilistic Signature Scheme (RSASSA-PSS) signature
algorithm, the RSA Encryption Scheme - Optimal Asymmetric Encryption
Padding (RSAES-OAEP) key transport algorithm and additional one-way
hash functions with the Public-Key Cryptography Standards (PKCS) #1
version 1.5 signature algorithm in the Internet X.509 Public Key
Infrastructure (PKI).  Encoding formats, algorithm identifiers, and
parameter formats are specified.

This document is a product of the Public-Key Infrastructure (X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.