RFC 3379: Delegated Path Validation and Delegated Path Discovery Protocol Requirements
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3379
- Published
- September 2002
- Authors
- D. Pinkas; R. Housley
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3278Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Obsoleted
May 2002
- RFC 3706A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) PeersCurrent
February 2004
- RFC 3709Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesObsoleted
February 2004
- RFC 4252The Secure Shell (SSH) Authentication ProtocolUpdated
January 2006
- RFC 5408Identity-Based Encryption Architecture and Supporting Data StructuresCurrent
January 2009
- RFC 5753Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Current
January 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?