RFC 3588:Diameter Base Protocol
RFC-Ref

end-to-end security


Click on the red underlined text to get to the source

... Security Exchange is a process through which two Diameter nodes establish end-to-end security. Diameter Server ...
... home server towards the access device. End-to-End Security TLS and IPsec ...
... Diameter user session. End-to-end security is security between two Diameter nodes, possibly communicating through Diameter ...


... End-to-End Security Framework ...
... End-to-end security services include confidentiality and message origin authentication ...
... agents. End-to-end security is provided via the End-to-End security extension, described in [AAACMS ...
... End-to-end security is provided via the End-to-End security extension, described in [AAACMS]. The circumstances requiring the ...
... extension, described in [AAACMS]. The circumstances requiring the use of end-to-end security are determined by policy on each of the peers. Security policies, which are not the subject ...
... IPsec transmission- level security is sufficient, there may be no need for end-to-end security. End-to-end security ...
... end-to-end security. End-to-end security policies include: - Never use end-to-end security ...
... End-to-end security policies include: - Never use end-to-end security. - Use end-to-end security ...
... end-to-end security. - Use end-to-end security on messages containing sensitive AVPs. Which AVPs ...
... sensitive. - Always use end-to-end security. It is strongly RECOMMENDED that all Diameter ...
... It is strongly RECOMMENDED that all Diameter implementations support end-to-end security. ...


... bit indicates the need for encryption for end-to-end security. The 'M' Bit ...
... agent (proxy, redirect or relay) then the message MUST NOT be sent unless there is end-to-end security between the originator and the recipient and integrity / ...
... AVP OR the originator has locally trusted configuration that indicates that end-to-end security is not needed. Similarly, for the originator of a Diameter message, a "P" in the "MAY" column means that if a message containing ...
... agent (proxy, redirect or relay) then the message MUST NOT be sent unless there is end-to-end security between the originator and the recipient or the originator has locally trusted configuration that indicates that end-to-end security is not needed. ...
... relay) then the message MUST NOT be sent unless there is end-to-end security between the originator and the recipient or the originator has locally trusted configuration that indicates that end-to-end security is not needed. Due to space constraints ...


... Diameter messages are processed by agents, and therefore MUST NOT be protected by end-to-end security. ...


... end-to-end fashion. If the Accounting- Request was protected by end-to-end security, then the corresponding ACA message MUST be protected by end-to-end security ...
... end-to-end security, then the corresponding ACA message MUST be protected by end-to-end security. Only the target ...


... third party agent. In other situations, end-to-end security is needed. Diameter ...



Google
Web
RFC-Ref