1 - 2 - 3 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
interoperabilit
Click on the red underlined text to get to the source
... Diameter applications are
strongly recommended. Reuse simplifies standardization and
implementation and avoids potential interoperability issues. It is
expected that command codes are reused; new command codes can only be
created ...
... bit MUST be set according to the rules defined for the AVP
containing it. In order to preserve interoperability, a Diameter
implementation MUST be able to exclude from a Diameter ...
... AVPs to be sent. Thus an administrator could change
the configuration to avoid interoperability problems.
Diameter ...
... authenticated only, authorized only or both.
Note any value other than both MAY cause RADIUS interoperability
issues. The following values are defined:
...
... vendor's implementation of Diameter,
where no interoperability is deemed useful. Where a Vendor-Specific
AVP ...
... only for experimental and testing purposes, no guarantee is made for
interoperability between Diameter peers using experimental commands,
...
... detection, it can choose to make use of the T flag or not, in order
to optimize duplicate detection. Since the T flag does not affect
interoperability, and may not be needed by some servers, generation
of the T flag is REQUIRED for Diameter clients ...