node
Click on the red underlined text to get to the source
... RFC3588], which supports content lengths up to 2^24 - 9
octets. As a result, NAIs processed only by Diameter nodes can be
very long. Unfortunately, an NAI transported over Diameter ...
... username" part SHOULD be treated as
opaque data when processed by nodes that are not a part of the
authoritative domain (in the sense of Section 4) for that realm.
...
... tasks such as normalization do not typically need to be performed by
nodes that just pass NAIs around or receive them from the network.
...
... - 255 may be used in the username portion, which may be
unacceptable to nodes that only support RFC 2486(-> 4282prop). Many devices
already allow this behaviour, however.
...
... privacy) may not be acceptable to RFC 2486(-> 4282prop)-compliant
nodes. Many devices already allow this behaviour, however.
o A recommendation to support NAI length ...
... that long NAIs may not be acceptable to RFC 2486(-> 4282prop)-compliant nodes.
o The mediating network ...