Subject: Fwd: RFC 2560 on PKIX OCSP

From: Paul Hoffman / IMC <[email-masked]>
Date: Mon, 14 Jun 1999 12:59:41 -0700

I think the IETF-Announce folks still have the wrong address for this list, 
so let me be the first to pass this message along.

>To: IETF-Announce: ;
>Subject: RFC 2560 on PKIX OCSP
>Cc: [email-masked]
>Date: Mon, 14 Jun 1999 11:08:33 -0700
>From: RFC Editor <[email-masked]>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 2560:
>
>         Title:      X.509 Internet Public Key Infrastructure
>                     Online Certificate Status Protocol - OCSP
>         Author(s):  M. Myers, R. Ankney, A. Malpani, S. Galperin,
>                     C. Adams
>         Status:     Proposed Standard
>         Date:       June 1999
>         Mailbox:    [email-masked], [email-masked],
>                     [email-masked], [email-masked],
>                     [email-masked],
>         Pages:      23
>         Characters: 43243
>         Updates/Obsoletes/See Also: None
>         I-D Tag:    draft-ietf-pkix-ocsp-08.txt
>
>
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2560.txt
>
>
>This document specifies a protocol useful in determining the current
>status of a digital certificate without requiring CRLs. Additional
>mechanisms addressing PKIX operational requirements are specified in
>separate documents.
>
>This document is a product of the Public-Key Infrastructure (X.509)
>Working Group of the IETF.
>
>This document 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 [email-masked].  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to [email-masked].
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to [email-masked] with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: [email-masked]
>         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 [email-masked].  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>[email-masked].  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Alegre Ramos
>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.
>Content-Type: text/plain
>Content-ID: <[email-masked]>
>
>RETRIEVE: rfc
>DOC-ID: rfc2560
>
><ftp://ftp.isi.edu/in-notes/rfc2560.txt>