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
security mechanism
Click on the red underlined text to get to the source
... Auditability
RADIUS does not define data-object security mechanisms, and as a
result, untrusted proxies may modify attributes or even packet
headers ...
... IPsec. The Diameter protocol
MUST NOT be used without any security mechanism (TLS or IPsec).
...
... receiver of a Capabilities-Exchange-Req (CER) message
that does not have any security mechanisms in common with the sender
MUST return a Capabilities-Exchange-Answer (CEA) with the Result-Code ...
...
- A Diameter message that uses a security mechanism that makes use
of a pre-established session key shared between the source and the
...
... This error is returned when a CER message is received, and there
are no common security mechanisms supported between the peers. A
Capabilities-Exchange-Answer (CEA) MUST be returned with the
Result-Code ...
... either IPSec or TLS. This security mechanism is acceptable in
environments where there is no untrusted third party agent ...
... intra-domain
usage when pre-shared keys are used as a security mechanism.
When pre-shared key authentication ...
...
It is recommended that a Diameter peer implement the same security
mechanism (IPsec or TLS) across all its peer-to-peer ...
... peer-to-peer connections.
Inconsistent use of security mechanisms can result in redundant
security mechanisms being used (e.g., TLS ...
... Inconsistent use of security mechanisms can result in redundant
security mechanisms being used (e.g., TLS over IPsec) or worse,
...
