--- 1/draft-ietf-lamps-rfc5280-i18n-update-01.txt	2017-06-23 12:13:18.238262153 -0700
+++ 2/draft-ietf-lamps-rfc5280-i18n-update-02.txt	2017-06-23 12:13:18.258262634 -0700
@@ -1,19 +1,19 @@
 
 INTERNET-DRAFT
 Internet Engineering Task Force                               R. Housley
 Intended Status: Proposed Standard                        Vigil Security
-Updates: RFC 5280 (once approved)
-Expires: 14 December 2017                                   14 June 2017
+Updates: 5280 (once approved)
+Expires: 23 December 2017                                   23 June 2017
 
                 Internationalization Updates to RFC 5280
-                draft-ietf-lamps-rfc5280-i18n-update-01
+                draft-ietf-lamps-rfc5280-i18n-update-02
 
 Abstract
 
    These updates to RFC 5280 provide clarity on the handling of
    Internationalized Domain Names (IDNs) and Internationalized Email
    Addresses in X.509 Certificates.
 
 Status of this Memo
 
    This Internet-Draft is submitted to IETF in full conformance with the
@@ -43,20 +43,32 @@
    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.
 
+   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.
+
 1.  Introduction
 
    This document updates RFC 5280 [RFC5280].  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 are updated to provide clarity on the handling of
    Internationalized Domain Names (IDNs) and Internationalized Email
    Addresses in X.509 Certificates.
 
    An IDN in Unicode (native character) form contains at least one
@@ -65,21 +77,21 @@
    IDN are converted to A-labels.  Conversion of an U-label to an
    A-label is described in [RFC5891].
 
    The GeneralName structure supports many different names forms,
    including otherName for extensibility.  [ID.lamps-eai-addresses]
    specifies the SmtpUTF8Name for Internationalized Email addresses,
    which include IDNs with U-labels.
 
    Note that Internationalized Domain Names in Applications
    specifications published in 2003 (IDNA2003) [RFC3490] and 2008
-   (IDNA2008) [RFC5980] both refer to the Punycode Algorithm for
+   (IDNA2008) [RFC5890] both refer to the Punycode Algorithm for
    conversion [RFC3492].
 
 1.1.  Terminology
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
    document are to be interpreted as described in RFC 2119 [RFC2119].
 
 2.  Updates
 
@@ -323,31 +336,36 @@
 
    [CABF]     CA/Browser Forum, "Internal Server Names and IP Address
               Requirements for SSL", Version 1.0, June 2012,
               <https://cabforum.org/internal-names/>
 
    [RFC3490]  Faltstrom, P., Hoffman, P., and A.  Costello,
               "Internationalizing Domain Names in Applications (IDNA)",
               RFC 3490, DOI 10.17487/RFC3490, March 2003,
               <http://www.rfc-editor.org/info/rfc3490>.
 
-   [RFC3639]  St. Johns, M., Ed., Huston, G., Ed., and IAB,
-              "Considerations on the use of a Service Identifier in
-              Packet Headers", RFC 3639, DOI 10.17487/RFC3639, October
-              2003, <http://www.rfc-editor.org/info/rfc3639>.
+   [RFC3492]  Costello, A., "Punycode: A Bootstring encoding of Unicode
+              for Internationalized Domain Names in Applications
+              (IDNA)", RFC 3492, DOI 10.17487/RFC3492, March 2003,
+              <http://www.rfc-editor.org/info/rfc3492>.
+
+   [RFC3629]  Yergeau, F., "UTF-8, a transformation format of ISO
+              10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
+              2003, <http://www.rfc-editor.org/info/rfc3629>.
 
 Acknowledgements
 
    Thanks to Alexey Melnikov for the encouragement to write this update.
    Thanks to John Klensin and Patrik Falstrom for confirming many of the
-   details in this update.  Thanks to Wei Chuang, Alexey Melnikov, Tim
-   Ruehsen, and Sean Turner for their careful review and comments.
+   details in this update.  Thanks to Wei Chuang, Phillip Hallam-Baker,
+   Alexey Melnikov, Tim Ruehsen, and Sean Turner for their careful
+   review and comments.
 
 Authors' Address
 
    Russ Housley
    Vigil Security, LLC
    918 Spring Knoll Drive
    Herndon, VA 20170
    USA
 
    EMail: housley@vigilsec.com