RFC 4282:The Network Access Identifier
RFC-Ref

AAA


Click on the red underlined text to get to the source

... client and the Authentication, Authorization, and Accounting (AAA) server. NAIs are sent over the wire in their canonical form ...
... network access clients and AAA servers. Similarly, we expect domain name comparisons, matching, resolution, and AAA routing ...
... AAA servers. Similarly, we expect domain name comparisons, matching, resolution, and AAA routing to be performed on the ASCII versions ...
... provides a canonical representation, ensures that intermediate systems such as AAA proxies do not need to perform translations, and can be expected to work through systems that are unaware of ...
... NAIs are used, among other purposes, for routing AAA transactions to the user's home realm. Usually, the home realm ...
... "user@homerealm.example.net" when passing the NAI forward, as well as applying appropriate AAA routing for the transaction. ...


... compatibility considerations among NAI lengths in this specification and various AAA protocols are discussed. Note that long NAIs may not be acceptable to RFC 2486(-> 4282prop) ...



Google
Web
RFC-Ref