Internet X.509 Public Key Infrastructure -- Certificate Image
RFC 6170
| Document | Type |
RFC - Proposed Standard
(May 2011; No errata)
Updates RFC 3709
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6170 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Tim Polk | ||
| IESG note | Steve Kent is the document shepherd <kent@bbn.com> | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) S. Santesson
Request for Comments: 6170 3xA Security
Updates: 3709 R. Housley
Category: Standards Track Vigil Security
ISSN: 2070-1721 S. Bajaj
Symantec Corp.
L. Rosenthol
Adobe
May 2011
Internet X.509 Public Key Infrastructure -- Certificate Image
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6170.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Santesson, et al. Standards Track [Page 1]
RFC 6170 Certificate Image May 2011
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................3
2. Certificate Image ...............................................3
3. LogotypeImageInfo ...............................................4
4. Embedded Images .................................................5
5. Certificate Image Formats .......................................6
5.1. PDF ........................................................6
5.2. SVG ........................................................6
5.3. PNG ........................................................7
6. Security Considerations .........................................7
7. Acknowledgements ................................................8
8. References ......................................................9
8.1. Normative References .......................................9
8.2. Informative References .....................................9
Appendix A. ASN.1 Module .........................................10
Appendix B. Example ..............................................11
1. Introduction
This standard specifies how to bind a certificate image to a
certificate (defined in [RFC5280]), providing a visual representation
of that certificate using the Logotype extension defined in [RFC3709]
and specifying the certificate image as a new "otherLogos" type.
The purpose of the certificate image is to aid human interpretation
of a certificate by providing meaningful visual information to the
user interface (UI).
Typical situations when a human needs to examine the visual
representation of a certificate are:
- A person establishes a secured channel with an authenticated
service. The person needs to determine the identity of the
service based on the authenticated credentials.
- A person validates the signature on critical information, such as
signed executable code, and needs to determine the identity of the
signer based on the signer's certificate.
- A person is required to select an appropriate certificate to be
used when authenticating to a service or Identity Management
infrastructure. The person needs to see the available
certificates in order to distinguish between them in the selection
Show full document text