Diameter is an authentication, authorization, and accounting protocol for computer networks. It evolved from the earlier RADIUS protocol. It belongs to the application layer protocols in the internet protocol suite. Diameter Applications extend the base protocol by adding new commands The Diameter base protocol is defined by RFC (Obsoletes: RFC ). Canonical URL: ; File formats: Plain Text PDF; Status: PROPOSED STANDARD; Obsoleted by: RFC ; Updated by. Diameter is specified primarily as a base protocol by the IETF in RFC and then DIAMETER base protocol must be used in conjunction with DIAMETER.
|Published (Last):||3 December 2007|
|PDF File Size:||2.99 Mb|
|ePub File Size:||17.89 Mb|
|Price:||Free* [*Free Regsitration Required]|
The application can be an authentication application, an accounting application, or a vendor-specific application. Pritocol A multi-session represents a logical linking of several sessions. The supported IP options are: Reuse simplifies standardization and implementation and avoids potential interoperability issues.
Broker A broker is a business term commonly used in AAA infrastructures. However, as described in Section A Diameter node MAY act as an agent for certain requests while acting as a server for others.
Diameter defines agent behavior explicitly; this is described in Section 2. This is a valid packet, but it only has one use, to try to circumvent firewalls.
This includes fixes to the Diameter extensibility description Section 1. As a result, proxies need to understand the semantics of the messages passing through idameter, and may not support all Diameter applications. The packet consists of a Diameter header and a variable number of Attribute-Value Pairs, or AVPs, for encapsulating information relevant to the Diameter message.
The bit value is transmitted in network byte order. It MAY do this in one of diiameter following ways: The following bits are assigned: When set the AVP Code belongs to the specific vendor code address space.
Diameter Base Protocol Support
The definition contains a list of valid values protocpl their interpretation and is described in the Diameter application introducing the AVP. An access device that is unable to interpret or apply a deny rule MUST terminate the session. Daimeter redirect agents do not receive answer messages, they cannot maintain session state.
Since the expected behavior is not defined, it varies between implementations. Examples are removal of obsolete types, fixes to the state machine, clarification of the election process, message validation, fixes to Failed-AVP and Result-Code AVP values, etc.
A rule that contains a tcpflags specification can never match a fragmented packet that has a non-zero offset. As a result, relays never originate messages, do not need to understand the semantics of messages or non-routing AVPs, and are capable of handling any Diameter application or message type.
LOCAL – Diameter messages that resolve to a route entry with the Local Action set to Local can be satisfied locally, and do not need to be routed to another server. Translation Agents A translation agent is a device that provides translation between two protocols e. Each “user” of a service causes prrotocol auth request to be sent, with baase unique session identifier. Multi-sessions are tracked by using the Acct-Multi-Session-Id. The request’s state is released upon receipt of the answer.
Here there are two: Arkko Ericsson September Diameter Base Protocol Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
These changes in sessions are tracked dameter the Accounting-Sub-Session-Id. Once accepted by the server, both the client and the server are aware of the session. The base protocol does diametrr require an Application Identifier since its support is mandatory.
Please refer to Section If cleared, the message MUST be locally processed. Sessions This section attempts to provide the reader with an understanding of the difference between connection and session, which are terms used extensively throughout this document. Protlcol field indicates the version of the Diameter Base Protocol.
It can be set only in cases where no answer has been received from the server for a request and the request is sent again. The request’s state is released upon receipt of the answer. Local Action The Local Action field is used to identify how a message should be treated.