A new Request for Comments is now available in online RFC libraries.RFC 3280 Title: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Author(s): R. Housley, W. Polk, W. Ford, D. Solo Status: Standards Track Date: April 2002 Mailbox: rhousley@rsasecurity.com, wford@verisign.com, wpolk@nist.gov, dsolo@alum.mit.edu Pages: 129 Characters: 295556 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-pkix-new-part1-12.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3280.txtThis memo profiles the X.509 v3 certificate and X.509 v2 CertificateRevocation List (CRL) for use in the Internet. An overview of thisapproach and model are provided as an introduction. The X.509 v3certificate format is described in detail, with additional informationregarding the format and semantics of Internet name forms. Standardcertificate extensions are described and two Internet-specificextensions are defined. A set of required certificate extensions isspecified. The X.509 v2 CRL format is described in detail, andrequired extensions are defined. An algorithm for X.509 certificationpath validation is described. An ASN.1 module and examples areprovided in the appendices.This document is a product of the Internet X.509 Public KeyInfrastructure (PKIX) Working Group of the IETF.This is now a Proposed Standard Protocol.This document specifies an Internet standards track protocol forthe Internet community, and requests discussion and suggestionsfor improvements. Please refer to the current edition of the"Internet Official Protocol Standards" (STD 1) for thestandardization state and status of this protocol. Distributionof 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 listshould be sent to IETF-REQUEST@IETF.ORG. Requests to beadded to or deleted from the RFC-DIST distribution list shouldbe sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.Details on obtaining RFCs via FTP or EMAIL may be obtained by sendingan EMAIL message to rfc-info@RFC-EDITOR.ORG with the message bodyhelp: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcsRequests for special distribution should be addressed to either theauthor of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unlessspecifically noted otherwise on the RFC itself, all RFCs are forunlimited distribution.echoSubmissions for Requests for Comments should be sent toRFC-EDITOR@RFC-EDITOR.ORG. Please consultRFC 2223, Instructions to RFCAuthors, for further information.
Datatracker
draft-ietf-pkix-new-part1-12
This is an older version of an Internet-Draft that was ultimately published asRFC 3280.
| Document | Document type | This is an older version of an Internet-Draft that was ultimately published asRFC 3280. | |
|---|---|---|---|
| Select version | |||
| Compare versions | |||
| Authors | Russ Housley,Tim Polk,Dr. Warwick S. Ford,David Solo Email authors | ||
| RFC stream |   | ||
| Intended RFC status | Proposed Standard | ||
| Other formats | |||
| Additional resources | Mailing list discussion |