RFC 3709: Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9399.
Current document in this lineage: RFC 9399 — Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates
In plain English — editorial summary, not part of the RFC
This document specifies a certificate extension for including logotypes in public key certificates and attribute certificates. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3709
- Published
- February 2004
- Authors
- S. Santesson; R. Housley; T. Freeman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 21
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3709 (2004)
- RFC 6170 (2011)
- RFC 9399 (2023) ✓
Read the full history of Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3820Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate ProfileCurrent
June 2004
- RFC 3739Internet X.509 Public Key Infrastructure: Qualified Certificates ProfileCurrent
March 2004
- RFC 3779X.509 Extensions for IP Addresses and AS IdentifiersCurrent
June 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 2560X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPObsoleted
June 1999
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?