One document matched: draft-ietf-pkix-ipki-part4-03.txt

Differences from draft-ietf-pkix-ipki-part4-02.txt

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


        RFC 2527: 

        Title:	    Internet X.509 Public Key Infrastructure
                    Certificate Policy and Certification Practices
		    Framework
	Author(s):  S. Chokhani, W. Ford
	Status:     Informational
	Date:       March 1999
        Mailbox:    chokhani@cygnacom.com, wford@verisign.com
	Pages:      45
        Characters: 91860
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-ietf-pkix-ipki-part4-03.txt

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


This document presents a framework to assist the writers of
certificate policies or certification practice statements for
certification authorities and public key infrastructures.  In
particular, the framework provides a comprehensive list of topics that
potentially (at the writer's discretion) need to be covered in a
certificate policy definition or a certification practice statement.

This document is a product of the Public-Key Infrastructure (X.509)
Working Group of the IETF.

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 Alegre Ramos
USC/Information Sciences Institute