One document matched: draft-ietf-pkix-ipki-part1-11.txt

Differences from draft-ietf-pkix-ipki-part1-10.txt

A new Request for Comments is now available in online RFC libraries.


        RFC 2459:

        Title:	    Internet X.509 Public Key Infrastructure
		    Certificate and CRL Profile    
	Author(s):  R. Housley, W. Ford, W. Polk, D. Solo
	Status:     Proposed Standard
	Date:       January 1999
        Mailbox:    housley@spyrus.co, wford@verisign.com,
		    wpolk@nist.gov, david.solo@citicorp.com
	Pages:      129
        Characters: 278438
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-ietf-pkix-ipki-part1-11.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2459.txt

This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use
in the Internet.  An overview of the 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 (e.g., IP addresses).  Standard certificate
extensions are described and one new Internet-specific extension is
defined.  A required set of certificate extensions is specified.  The
X.509 v2 CRL format is described and a required extension set is
defined as well.  An algorithm for X.509 certificate path validation
is described. Supplemental information is provided describing the
format of public keys and digital signatures in X.509 certificates for
common Internet public key encryption algorithms (i.e., RSA, DSA, and
Diffie-Hellman).  ASN.1 modules and examples are provided in the
appendices

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