RFC 6170: Internet X.509 Public Key Infrastructure -- Certificate Image
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 method to bind a visual representation of a certificate in the form of a certificate image to a public key certificate as defined in RFC 5280, by defining a new "otherLogos" image type according to RFC 3709. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6170
- Published
- May 2011
- Authors
- S. Santesson; R. Housley; S. Bajaj; L. Rosenthol
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 12
- 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
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6176Prohibiting Secure Sockets Layer (SSL) Version 2.0Updated
March 2011
- RFC 6158RADIUS Design GuidelinesUpdated
March 2011
- RFC 6113A Generalized Framework for Kerberos Pre-AuthenticationCurrent
April 2011
- RFC 6112Anonymity Support for KerberosObsoleted
April 2011
- RFC 6111Additional Kerberos Naming ConstraintsCurrent
April 2011
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6066Transport Layer Security (TLS) Extensions: Extension DefinitionsUpdated
January 2011
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?