Username
Click on the red underlined text to get to the source
... ABNF) as documented in [RFC4234]. The grammar for
the username is based on [RFC0821], and the grammar for the realm is
an updated version ...
... username "@" realm
username = dot-string
dot-string = string
dot-string =/ dot-string "." string
...
... Support for Username Privacy ...
...
Interpretation of the username part of the NAI depends on the realm
in question. Therefore, the "username ...
... username part of the NAI depends on the realm
in question. Therefore, the "username" part SHOULD be treated as
opaque data when processed by nodes ...
... NAIs are used together with a separate
authentication method that can transfer the username part in a more
secure manner to increase privacy ...
... privacy. In this case, NAIs MAY be
provided in an abbreviated form by omitting the username part.
Omitting the username part is RECOMMENDED over using a fixed username ...
... provided in an abbreviated form by omitting the username part.
Omitting the username part is RECOMMENDED over using a fixed username
part, such as "anonymous", since it provides an unambiguous way to
...
... username part.
Omitting the username part is RECOMMENDED over using a fixed username
part, such as "anonymous", since it provides an unambiguous way to
determine whether the username ...
... username
part, such as "anonymous", since it provides an unambiguous way to
determine whether the username is intended to uniquely identify a
single user.
...
...
This specification allows both international usernames and realms.
International usernames are based on the use of Unicode characters ...
... This specification allows both international usernames and realms.
International usernames are based on the use of Unicode characters,
encoded as UTF-8 ...
... In order to ensure a canonical representation, characters of the
username portion in an NAI MUST fulfill the ABNF in this
...
... Compatibility with E-Mail Usernames ...
... internationalization support as well as for purposes of Section 2.7,
and is not necessarily compatible with the usernames used in e-mail.
Note also that the internationalization requirements ...
... The conversion process may apply also recursively. That is, after
the conversion, the result may still have one or more '!' characters
in the username. For instance, the NAI
...
... Note that the syntax described in this section is optional and is not
a part of the ABNF. The '!' character may appear in the username
portion of an NAI for other purposes as well, and in those cases, the
...
... portion of an NAI for other purposes as well, and in those cases, the
rules outlined here do not apply; the interpretation of the username
is up to an agreement between the identified user and the realm given
...
... NAI reveals the home affiliation of a user, it may assist an
attacker in further probing the username space. Typically, this
problem is of most concern in protocols that transmit the username in
...
... attacker in further probing the username space. Typically, this
problem is of most concern in protocols that transmit the username in
clear-text across the Internet, such as in RADIUS ...
... RFC2866]. In order to prevent snooping of the
username, protocols may use confidentiality services provided by
...
... RFC3588].
This specification adds the possibility of hiding the username part
in the NAI, by omitting it. As discussed in Section 2.3, this is
...
... NAIs are used together with a separate
authentication method that can transfer the username in a secure
manner. In some cases, application-specific privacy mechanism ...
... transport protection is that privacy of the username is protected,
even through intermediate nodes such as NASes ...
... o International character set support has been added for both
usernames and realms. Note that this implies character codes 128
- 255 may be used in the username portion, which may be
...
... usernames and realms. Note that this implies character codes 128
- 255 may be used in the username portion, which may be
unacceptable to nodes that only support RFC 2486(-> 4282prop) ...
... already allow this behaviour, however.
o Username privacy support has been added. Note that NAIs without a
username ...
... Username privacy support has been added. Note that NAIs without a
username (for privacy) may not be acceptable to RFC 2486(-> 4282prop)-compliant
...