Re: [Issue 16] Special Characters in RFC 2486bis-01

[Bernard Aboba <aboba@internaut.com>]

In RFC 2486, "jari.arkko@ericsson.com" is a valid NAI, and it would appear
that this is also true in RFC 2486bis, due to the following rules:

username = dot-string
dot-string = string
dot-string =/ dot-string "." string

Or am I missing something?

At a minimum, I think we may need additional examples of legal and illegal
NAIs.

--------------------------------------------------------------------
Issue 16: Special Characters in RFC 2486bis-01
Submitter: Paola Pappalardo
Submitter email address: misspaola@tiscali.it
Date first submitted: October 29, 2004
Reference: http://ops.ietf.org/lists/radiusext/2004/msg00804.html
Document: RFC2486bis-01
Comment type: T
Priority: S
Section: Various
Rationale/Explanation of issue:

I have to handle the Network Access Identifier (NAI) for my work. I have
read the RFC 2486 and I'm a little confused about the use of special
characters,
like  "<" / ">" / "(" / ")" / "[" / "]" / "\" / "."  / "," / ";" / ":" /
"@" / %x22  / Ctl,

in the NAI username.

Can you help me? Can you please give some examples of valid NAI containing
special characters?
[Jari Arkko]
The issue is what "special" characters, not just alphabets
and digits can appear in NAIs. The realm part rules are
according to the usual DNS, which I think allows only "-"
and ".". The user name part allows more special characters,
but disallows some others. A couple of valid examples:

    jari_arkko@ericsson.com
    user%%%%%@example.com

A couple of invalid examples:

    jari.arkko@ericsson.com
    user>luser@example.com

Nevertheless, there's an escape mechanism that allows
even special characters. Example:

    jari\.arkko@ericsson.com

If you read the new draft you will see that the ABNF syntax is hopefully
easier to read
than in RFC 2486, because the treatment of each character has
been listed on its own line, and you do not have read the
comments to find out what actual characters are allowed.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>