--- 1/draft-ietf-radext-nai-10.txt	2014-11-26 08:14:54.257230940 -0800
+++ 2/draft-ietf-radext-nai-11.txt	2014-11-26 08:14:54.305232119 -0800
@@ -1,20 +1,20 @@
 
 RADEXT Working Group                                         DeKok, Alan
 INTERNET-DRAFT                                                FreeRADIUS
 Obsoletes: 4282
 Category: Standards Track
-<draft-ietf-radext-nai-10.txt>
-29 October 2014
+<draft-ietf-radext-nai-11.txt>
+26 November 2014
 
                      The Network Access Identifier
-                        draft-ietf-radext-nai-10
+                        draft-ietf-radext-nai-11
 
 Abstract
 
    In order to provide inter-domain authentication services, it is
    necessary to have a standardized method that domains can use to
    identify each other's users.  This document defines the syntax for
    the Network Access Identifier (NAI), the user identity submitted by
    the client prior to accessing resources. This document is a revised
    version of RFC 4282, which addresses issues with international
    character sets, as well as a number of other corrections to the
@@ -34,21 +34,21 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on April 29, 2015.
+   This Internet-Draft will expire on May 29, 2015.
 
 Copyright Notice
 
    Copyright (c) 2014 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
@@ -506,23 +506,24 @@
    matching the above ABNF are not valid NAIs.  However, some realms
    which do match the ABNF are still invalid NAIs.  That is, matching
    the ABNF is a necessary, but not sufficient, requirement for an NAI.
 
    In general, the above requirement means following the requirements
    specified in [RFC5891].
 
 2.6.  The Normalization Process
 
    Conversion to Unicode as well as normalization SHOULD be performed by
-   edge systems such as laptops that take "local" text as input.  These
-   edge systems are best suited to determine the users intent, and can
-   best convert from "local" text to a normalized form.
+   edge systems (e.g. laptops, desktops, smart phones, etc.) that take
+   "local" text as input.  These edge systems are best suited to
+   determine the users intent, and can best convert from "local" text to
+   a normalized form.
 
    Other AAA systems such as proxies do not have access to locale and
    character set information that is available to edge systems.
    Therefore, they may not always be able to convert local input to
    Unicode.
 
    That is, all processing of NAIs from "local" character sets and
    locales to UTF-8 SHOULD be performed by edge systems, prior to the
    NAIs entering the AAA system.  Inside of an AAA system, NAIs are sent
    over the wire in their canonical form, and this canonical form is