RFC 2510 on PKI Certificate Management Protocols
RFC Editor <rfc-ed@ISI.EDU> Thu, 04 March 1999 23:55 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17429 for ietf-123-outbound.10@ietf.org; Thu, 4 Mar 1999 18:55:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17364 for <all-ietf@ietf.org>; Thu, 4 Mar 1999 18:53:07 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA08425; Thu, 4 Mar 1999 15:53:01 -0800 (PST)
Message-Id: <199903042353.PAA08425@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2510 on PKI Certificate Management Protocols
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 04 Mar 1999 15:53:00 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2510: Title: Internet X.509 Public Key Infrastructure Certificate Management Protocols Author(s): C. Adams, S. Farrell Status: Proposed Standard Date: March 1999 Mailbox: cadams@entrust.com, stephen.farrell@sse.ie Pages: 72 Characters: 158178 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-pkix-ipki3cmp-09.txt URL: ftp://ftp.isi.edu/in-notes/rfc2510.txt This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols. Protocol messages are defined for all relevant aspects of certificate creation and management. 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.echo 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 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.