idnits 2.17.1 draft-ietf-pkix-new-part1-12.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3280 5 Title: Internet X.509 Public Key Infrastructure 6 Certificate and Certificate Revocation List (CRL) 7 Profile 8 Author(s): R. Housley, W. Polk, W. Ford, D. Solo 9 Status: Standards Track 10 Date: April 2002 11 Mailbox: rhousley@rsasecurity.com, wford@verisign.com, 12 wpolk@nist.gov, dsolo@alum.mit.edu 13 Pages: 129 14 Characters: 295556 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-pkix-new-part1-12.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3280.txt 21 This memo profiles the X.509 v3 certificate and X.509 v2 Certificate 22 Revocation List (CRL) for use in the Internet. An overview of this 23 approach and model are provided as an introduction. The X.509 v3 24 certificate format is described in detail, with additional information 25 regarding the format and semantics of Internet name forms. Standard 26 certificate extensions are described and two Internet-specific 27 extensions are defined. A set of required certificate extensions is 28 specified. The X.509 v2 CRL format is described in detail, and 29 required extensions are defined. An algorithm for X.509 certification 30 path validation is described. An ASN.1 module and examples are 31 provided in the appendices. 33 This document is a product of the Internet X.509 Public Key 34 Infrastructure (PKIX) Working Group of the IETF. 36 This is now a Proposed Standard Protocol. 38 This document specifies an Internet standards track protocol for 39 the Internet community, and requests discussion and suggestions 40 for improvements. Please refer to the current edition of the 41 "Internet Official Protocol Standards" (STD 1) for the 42 standardization state and status of this protocol. Distribution 43 of this memo is unlimited. 45 This announcement is sent to the IETF list and the RFC-DIST list. 46 Requests to be added to or deleted from the IETF distribution list 47 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 48 added to or deleted from the RFC-DIST distribution list should 49 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 51 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 52 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 53 help: ways_to_get_rfcs. For example: 55 To: rfc-info@RFC-EDITOR.ORG 56 Subject: getting rfcs 58 help: ways_to_get_rfcs 60 Requests for special distribution should be addressed to either the 61 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 62 specifically noted otherwise on the RFC itself, all RFCs are for 63 unlimited distribution.echo 64 Submissions for Requests for Comments should be sent to 65 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 66 Authors, for further information.