×
The Diameter base protocol is defined by RFC 6733 (Obsoletes: RFC 3588 and RFC 5719) and defines the minimum requirements for an AAA protocol. Diameter Applications can extend the base protocol by adding new commands, attributes, or both. Diameter security is provided by IPsec or TLS.
1. Relay Agents Relay agents are Diameter agents that accept requests and route messages to other Diameter nodes based on information found in the messages ( ...
People also ask
1. Incoming connections When a connection request is received from a Diameter peer, it is not, in the general case, possible to know the identity of that peer ...
The core of the Diameter protocol is defined in the Diameter base standard, IETF RFC 3588. This RFC specifies the minimum requirements for a Diameter ...
The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. The client (server) ...
The Diameter base protocol is intended to provide an Authentication, Authorization, and Accounting (AAA) framework for applications such as network access or IP ...
Missing: Draft | Show results with:Draft
... based on Diameter base protocol (IETF RFC 3588 [2]), NASREQ. (IETF RFC 4005 [3]) and Diameter EAP application (IETF RFC 4072 [6]). Some interfaces are based ...
specification of the Diameter Base Protocol (IETF RFC 6733 [15]). The Nt application identifier shall be included in the Auth-Application-Id AVP within the ...
RFC 7966 Diameter ... Introduction The Diameter base protocol specification [2] defines security protection between neighboring Diameter peers. ... draft-ietf-aaa- ...
... Diameter application being defined relies on the session management specified in the Diameter base protocol: o If it is, the Diameter command defined for ...