RFC 2986 on Certification Request Syntax Specification
RFC Editor <rfc-ed@ISI.EDU> Thu, 09 November 2000 01:58 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08967; Wed, 8 Nov 2000 20:58:14 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA14108 for ietf-123-outbound.10@ietf.org; Wed, 8 Nov 2000 20:55:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA13981 for <all-ietf@loki.ietf.org>; Wed, 8 Nov 2000 20:29:10 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA01667 for <all-ietf@ietf.org>; Wed, 8 Nov 2000 20:29:08 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA22135; Wed, 8 Nov 2000 17:29:00 -0800 (PST)
Message-Id: <200011090129.RAA22135@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2986 on Certification Request Syntax Specification
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 08 Nov 2000 17:29:00 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2986
Title: PKCS #10: Certification Request Syntax
Specification Version 1.7
Author(s): M. Nystrom, B. Kaliski
Status: Informational
Date: November 2000
Mailbox: magnus@rsasecurity.com, bkaliski@rsasecurity.com
Pages: 14
Characters: 27794
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-nystrom-pkcs10-v1-7-00.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2986.txt
This memo represents a republication of PKCS #10 v1.7 from RSA
Laboratories' Public-Key Cryptography Standards (PKCS) series, and
change control is retained within the PKCS process. The body of this
document, except for the security considerations section, is taken
directly from the PKCS #9 v2.0 or the PKCS #10 v1.7 document.
This memo describes a syntax for certification requests.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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 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.