RFC 3820: Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile
In plain English — editorial summary, not part of the RFC
This document forms a certificate profile for Proxy Certificates, based on X.509 Public Key Infrastructure (PKI) certificates as defined in RFC 3280, for use in the Internet. The term Proxy Certificate is used to describe a certificate that is derived from, and signed by, a normal X.509 Public Key End Entity Certificate or by another Proxy Certificate for the purpose of providing restricted proxying and delegation within a PKI based authentication system. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3820
- Published
- June 2004
- Authors
- S. Tuecke; V. Welch; D. Engert; L. Pearlman; M. Thompson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3709Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesObsoleted
February 2004
- RFC 3280Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileObsoleted
May 2002
- RFC 3279Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileUpdated
May 2002
- RFC 3029Internet X.509 Public Key Infrastructure Data Validation and Certification Server ProtocolsCurrent
February 2001
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 3779X.509 Extensions for IP Addresses and AS IdentifiersCurrent
June 2004
- RFC 3739Internet X.509 Public Key Infrastructure: Qualified Certificates ProfileCurrent
March 2004
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?