--- 1/draft-ietf-lamps-eai-addresses-16.txt	2018-02-12 03:13:09.124427934 -0800
+++ 2/draft-ietf-lamps-eai-addresses-17.txt	2018-02-12 03:13:09.152428598 -0800
@@ -1,19 +1,19 @@
 
 LAMPS                                                   A. Melnikov, Ed.
 Internet-Draft                                                 Isode Ltd
 Updates: 5280 (if approved)                               W. Chuang, Ed.
 Intended status: Standards Track                            Google, Inc.
-Expires: July 15, 2018                                  January 11, 2018
+Expires: August 15, 2018                               February 11, 2018
 
         Internationalized Email Addresses in X.509 certificates
-                   draft-ietf-lamps-eai-addresses-16
+                   draft-ietf-lamps-eai-addresses-17
 
 Abstract
 
    This document defines a new name form for inclusion in the otherName
    field of an X.509 Subject Alternative Name and Issuer Alternative
    Name extension that allows a certificate subject to be associated
    with an Internationalized Email Address.
 
    This document updates RFC 5280.
 
@@ -25,21 +25,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on July 15, 2018.
+   This Internet-Draft will expire on August 15, 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
@@ -130,23 +130,22 @@
    restrictions as specified by Section 2.3.1 of [RFC5890] and SHALL be
    restricted to lower case letters.  NR-LDH stands for "Non-Reserved
    Letters Digits Hyphen" and is the set of LDH labels that do not have
    "--" characters in the third and forth character position, which
    excludes "tagged domain names" such as A-labels.  Consistent with the
    treatment of rfc822Name in [RFC5280], SmtpUTF8Mailbox is an envelope
    <Mailbox> and has no phrase (such as a common name) before it, has no
    comment (text surrounded in parentheses) after it, and is not
    surrounded by "<" and ">".
 
-   Due to operational reasons to be described shortly and name
-   constraint compatibility reasons described in Section 6,
-   SmtpUTF8Mailbox subjectAltName MUST only be used when the local-part
+   Due to name constraint compatibility reasons described in Section 6,
+   SmtpUTF8Mailbox subjectAltName MUST NOT be used unless the local-part
    of the email address contains non-ASCII characters.  When the local-
    part is ASCII, rfc822Name subjectAltName MUST be used instead of
    SmtpUTF8Mailbox.  This is compatible with legacy software that
    supports only rfc822Name (and not SmtpUTF8Mailbox).  The appropriate
    usage of rfc822Name and SmtpUTF8Mailbox is summarized in Table 1
    below.
 
    SmtpUTF8Mailbox is encoded as UTF8String.  The UTF8String encoding
    MUST NOT contain a Byte-Order- Mark (BOM) [RFC3629] to aid
    consistency across implementations particularly for comparison.
@@ -161,21 +160,21 @@
     +-----------------+-------------+--------------+-----------------+
 
            non-ASCII may additionally include ASCII characters.
 
                      Table 1: Email address formatting
 
 4.  IDNA2008
 
    To facilitate comparison between email addresses, all email address
    domains in X.509 certificates MUST conform to IDNA2008 [RFC5890] (and
-   avoids any "mappings" mentioned in that document).  Use of non-
+   avoid any "mappings" mentioned in that document).  Use of non-
    conforming email address domains introduces the possibility of
    conversion errors between alternate forms.  This applies to
    SmtpUTF8Mailbox and rfc822Name in subjectAltName, issuerAltName and
    anywhere else that these are used.
 
 5.  Matching of Internationalized Email Addresses in X.509 certificates
 
    In equivalence comparison with SmtpUTF8Mailbox, there may be some
    setup work on one or both inputs depending of whether the input is
    already in comparison form.  Comparing SmtpUTF8Mailboxs consists of a