Internationalization Updates to RFC 5280
RFC 8399

Document Type RFC - Proposed Standard (May 2018; No errata)
Updates RFC 5280
Last updated 2018-05-23
Replaces draft-housley-rfc5280-i18n-update
Stream IETF
Formats plain text pdf html bibtex
Reviews GENART will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Phillip Hallam-Baker
Shepherd write-up Show (last changed 2017-06-23)
IESG IESG state RFC 8399 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to Phillip Hallam-Baker <phill@hallambaker.com>, Russ Housley <housley@vigilsec.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                        R. Housley
Request for Comments: 8399                                Vigil Security
Updates: 5280                                                   May 2018
Category: Standards Track
ISSN: 2070-1721

                Internationalization Updates to RFC 5280

Abstract

   The updates to RFC 5280 described in this document provide alignment
   with the 2008 specification for Internationalized Domain Names (IDNs)
   and add support for internationalized email addresses in X.509
   certificates.

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 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8399.

Housley                      Standards Track                    [Page 1]
RFC 8399                I18n Updates to RFC 5280                May 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction ....................................................3
      1.1. Terminology ................................................3
   2. Updates to RFC 5280 .............................................3
      2.1. Update in the Introduction (Section 1) .....................4
      2.2. Update in Name Constraints (Section 4.2.1.10) ..............4
      2.3. Update in IDNs in GeneralName (Section 7.2) ................5
      2.4. Update in IDNs in Distinguished Names (Section 7.3) ........6
      2.5. Update in Internationalized Electronic Mail
           Addresses (Section 7.5) ....................................6
   3. Security Considerations .........................................7
   4. IANA Considerations .............................................8
   5. References ......................................................8
      5.1. Normative References .......................................8
      5.2. Informative References .....................................9
   Acknowledgements ...................................................9
   Author's Address ...................................................9

Housley                      Standards Track                    [Page 2]
RFC 8399                I18n Updates to RFC 5280                May 2018

1.  Introduction

   This document updates the Introduction in Section 1, the Name
   Constraints certificate extension discussion in Section 4.2.1.10, and
   the Processing Rules for Internationalized Names in Section 7 of RFC
   5280 [RFC5280] to provide alignment with the 2008 specification for
   Internationalized Domain Names (IDNs) and add support for
   internationalized email addresses in X.509 certificates.

   An IDN in Unicode (native character) form contains at least one
   U-label [RFC5890].  With one exception, IDNs are carried in
   certificates in ACE-encoded form.  That is, all U-labels within an
   IDN are converted to A-labels.  Conversion of a U-label to an A-label
   is described in [RFC5891].

   The GeneralName structure supports many different name forms,
   including otherName for extensibility.  RFC 8398 [RFC8398] specifies
   the SmtpUTF8Mailbox for internationalized email addresses, which
   includes IDNs with U-labels.
Show full document text