The Network Access Identifier
draft-ietf-radext-nai-01
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (radext WG)
|
|
Last updated |
|
2013-01-08
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group DeKok, Alan
INTERNET-DRAFT FreeRADIUS
Obsoletes: 4282
Category: Standards Track
<draft-ietf-radext-nai-01.txt>
8 January 2013
The Network Access Identifier
draft-ietf-radext-nai-01
Abstract
In order to provide inter-domain authentication services, it is
necessary to have a standardized method that domains can use to
identify each others users. This document defines the syntax for the
Network Access Identifier (NAI), the user identity submitted by the
client prior to accessing network resources. This document is a
revised version of RFC 4282 [RFC4282], which addresses issues with
international character sets, as well as a number of other
corrections to the previous document.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
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 July 8, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
DeKok, Alan Standards Track [Page 1]
INTERNET-DRAFT The Network Access Identifier 8 January 2013
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
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.
DeKok, Alan Standards Track [Page 2]
INTERNET-DRAFT The Network Access Identifier 8 January 2013
Table of Contents
Appendix A - Changes from RFC4282 ............................ 3
1. Introduction ............................................. 4
1.1. Terminology ......................................... 4
1.2. Requirements Language ............................... 5
1.3. Purpose ............................................. 6
1.4. Motivation .......................................... 6
2. NAI Definition ........................................... 7
2.1. UTF-8 Syntax and Normalization ...................... 7
2.2. Formal Syntax ....................................... 7
2.3. NAI Length Considerations ........................... 8
2.4. Support for Username Privacy ........................ 9
2.5. International Character Sets ........................ 9
2.6. The Normalization Process ........................... 10
2.7. Use in Other Protocols .............................. 11
2.8. Routing inside of AAA Systems ....................... 11
2.9. Compatibility with Email Usernames .................. 12
2.10. Compatibility with DNS ............................. 12
2.11. Realm Construction ................................. 13
2.11.1. Historical Practices .......................... 14
2.12. Examples ........................................... 15
3. Security Considerations .................................. 15
4. IANA Considerations ...................................... 16
Show full document text