Delegated Path Validation and Delegated Path Discovery Protocol Requirements
draft-ietf-pkix-dpv-dpd-req-05

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3379.
Authors Russ Housley , Denis Pinkas
Last updated 2015-10-14 (Latest revision 2002-05-15)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3379 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Jeffrey I. Schiller
IESG note ** No value found for 'doc.notedoc.note' **
Send notices to <wpolk@nist.gov>
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-pkix-dpv-dpd-req-05 
A new Request for Comments is now available in online RFC libraries.

        RFC 3379

        Title:      Delegated Path Validation and Delegated Path
                    Discovery Protocol Requirements
        Author(s):  D. Pinkas, R. Housley
        Status:     Informational
        Date:       September 2002
        Mailbox:    Denis.Pinkas@bull.net, rhousley@rsasecurity.com
        Pages:      15
        Characters: 32455
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-pkix-dpv-dpd-req-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3379.txt

This document specifies the requirements for Delegated Path Validation
(DPV) and Delegated Path Discovery (DPD) for Public Key Certificates.
It also specifies the requirements for DPV and DPD policy management.

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.