draft-ietf-radext-nai-10.txt   draft-ietf-radext-nai-11.txt 
RADEXT Working Group DeKok, Alan RADEXT Working Group DeKok, Alan
INTERNET-DRAFT FreeRADIUS INTERNET-DRAFT FreeRADIUS
Obsoletes: 4282 Obsoletes: 4282
Category: Standards Track Category: Standards Track
<draft-ietf-radext-nai-10.txt> <draft-ietf-radext-nai-11.txt>
29 October 2014 26 November 2014
The Network Access Identifier The Network Access Identifier
draft-ietf-radext-nai-10 draft-ietf-radext-nai-11
Abstract Abstract
In order to provide inter-domain authentication services, it is In order to provide inter-domain authentication services, it is
necessary to have a standardized method that domains can use to necessary to have a standardized method that domains can use to
identify each other's users. This document defines the syntax for identify each other's users. This document defines the syntax for
the Network Access Identifier (NAI), the user identity submitted by the Network Access Identifier (NAI), the user identity submitted by
the client prior to accessing resources. This document is a revised the client prior to accessing resources. This document is a revised
version of RFC 4282, which addresses issues with international version of RFC 4282, which addresses issues with international
character sets, as well as a number of other corrections to the character sets, as well as a number of other corrections to the
skipping to change at page 1, line 45 skipping to change at page 1, line 45
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. 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 Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 12, line 42 skipping to change at page 12, line 42
matching the above ABNF are not valid NAIs. However, some realms matching the above ABNF are not valid NAIs. However, some realms
which do match the ABNF are still invalid NAIs. That is, matching which do match the ABNF are still invalid NAIs. That is, matching
the ABNF is a necessary, but not sufficient, requirement for an NAI. the ABNF is a necessary, but not sufficient, requirement for an NAI.
In general, the above requirement means following the requirements In general, the above requirement means following the requirements
specified in [RFC5891]. specified in [RFC5891].
2.6. The Normalization Process 2.6. The Normalization Process
Conversion to Unicode as well as normalization SHOULD be performed by 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 (e.g. laptops, desktops, smart phones, etc.) that take
edge systems are best suited to determine the users intent, and can "local" text as input. These edge systems are best suited to
best convert from "local" text to a normalized form. 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 Other AAA systems such as proxies do not have access to locale and
character set information that is available to edge systems. character set information that is available to edge systems.
Therefore, they may not always be able to convert local input to Therefore, they may not always be able to convert local input to
Unicode. Unicode.
That is, all processing of NAIs from "local" character sets and That is, all processing of NAIs from "local" character sets and
locales to UTF-8 SHOULD be performed by edge systems, prior to the 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 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 over the wire in their canonical form, and this canonical form is
 End of changes. 4 change blocks. 
7 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/