Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates
draft-ietf-lamps-rfc3709bis-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-lamps-rfc3709bis@ietf.org, lamps-chairs@ietf.org, rdd@cert.org, rfc-editor@rfc-editor.org, spasm@ietf.org, tim.hollebeek@digicert.com
Subject: Protocol Action: 'Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates' to Proposed Standard (draft-ietf-lamps-rfc3709bis-10.txt)

The IESG has approved the following document:
- 'Internet X.509 Public Key Infrastructure: Logotypes in X.509
   Certificates'
  (draft-ietf-lamps-rfc3709bis-10.txt) as Proposed Standard

This document is the product of the Limited Additional Mechanisms for PKIX
and SMIME Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc3709bis/

Ballot Text

Technical Summary

   This document specifies a certificate extension for including
   logotypes in public key certificates and attribute certificates.
   This document obsoletes RFC 3709 and RFC 6170.

Working Group Summary

The document reached broad WG agreement.

Document Quality

This is an update and merge of two older documents, RFC 3709 and RFC 6170.
Historical implementations exist for both RFCs, and implementations are rapidly
becoming more common as these RFCs are fundamental to Verified Mark Certificates
which are rapidly being rolled out by Google, Apple, and others.

These experiences have shown that the two documents are in need of modernization
(e.g. SHA-1 is mandatory to implement in RFC 3709), so this merge/update is very 
timely and useful for the industry.

Personnel

Document Shepherd: Tim Hollebeek

Responsible AD: Roman Danyliw

RFC Editor Note