[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12         Standards Track
          rfc3280                                       IPR declarations
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.txt


This memo profiles the X.509 v3 certificate and X.509 v2 Certificate
Revocation List (CRL) for use in the Internet.  An overview of this
approach and model are provided as an introduction.  The X.509 v3
certificate format is described in detail, with additional information
regarding the format and semantics of Internet name forms.  Standard
certificate extensions are described and two Internet-specific
extensions are defined.  A set of required certificate extensions is
specified.  The X.509 v2 CRL format is described in detail, and
required extensions are defined.  An algorithm for X.509 certification
path validation is described.  An ASN.1 module and examples are
provided in the appendices.

This document is a product of the Internet X.509 Public Key
Infrastructure (PKIX) 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.