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. 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 ). RFC Diameter Base Protocol, September Canonical URL: Discuss this RFC: Send questions or comments to [email protected] Other actions: View.

Author: Goltishura Gushura
Country: Japan
Language: English (Spanish)
Genre: Love
Published (Last): 23 May 2016
Pages: 321
PDF File Size: 2.84 Mb
ePub File Size: 20.91 Mb
ISBN: 837-6-31057-391-8
Downloads: 6314
Price: Free* [*Free Regsitration Required]
Uploader: Kazrabei

The name is a play on words, derived from the RADIUS protocol, which is the predecessor a diameter is twice the radius. For example, a Diameter peer may be authentic, but that does not mean that it is authorized to act as a Diameter Server advertising a set of Diameter applications.

Translation of messages can only occur if the agent recognizes the application of a particular request, and therefore translation agents MUST only advertise their locally supported applications.

An access device that is unable to interpret or apply a deny rule MUST terminate the session. Here there are two: This field is only present if the respective bit-flag is enabled.

The use of Relays is advantageous since it eliminates the need for NASes to be configured with the necessary security information they diamete otherwise require to communicate with Diameter servers in other realms.

Diameter (protocol)

The Diameter protocol defines a policy protocol used by clients to perform policy, AAA, and resource control. Both the request and the answer for a given command share the same command code.

This AVP would be encoded as follows: Transaction state implies that upon forwarding a request, its Hop-by-Hop Identifier is saved; the field is replaced with a locally unique identifier, which is restored to its original value when the corresponding answer is received.


If cleared, the message is an answer. At diamete step, forwarding of an authorization response is considered evidence of a willingness to take on financial risk relative to the session.

Diameter Header A summary diameteg the Diameter header format is shown oetf. This field indicates the version of the Diameter Base Protocol. In this case, all IP numbers from 1. The Diameter protocol requires that relaying and proxying agents maintain transaction state, which is used for failover purposes. See Section 4 for more information on AVPs. Translation agents are likely to be used as aggregation servers to communicate with a Diameter infrastructure, while allowing for the embedded systems to be migrated at a djameter pace.

The supported ICMP types are: Match if the TCP header contains the comma separated list of flags specified in spec. Prior to bringing up a connection, authorization checks are performed at each connection along the path.

By using this site, you agree to rfv Terms of Use and Privacy Policy. Since additional code points are added by amendments to the standard from time to time, implementations MUST be prepared to encounter any code point from 0x to 0x7fffffff. Translation Agents A translation agent is a device that provides translation between two protocols e. This section needs expansion.

Diameter (protocol) – Wikipedia

The dimaeter consists of a Diameter header and rfcc variable number of Attribute-Value Pairs, or AVPs, for encapsulating information relevant to the Diameter message.

The ” R ” Request bit — If set, the message is a request. A three-letter acronym for both the request and answer is also normally provided. The sender MUST ensure that the Hop-by-Hop identifier in a request is unique on a given connection at any given time, and MAY attempt to ensure that the number is unique across reboots. Further, since redirect agents never relay requests, they are not required to maintain transaction state.


A Diameter implementation MAY act as one type of agent for some requests, and as another type of agent for others. The identifier MUST remain locally unique for a period of at least 4 minutes, even across reboots.

Diameter Relay and redirect agents must not reject messages with unrecognized AVPs. For example, administrators hase the home realm may not wish to honor requests that have been routed through an untrusted realm.

RFC – part 2 of 5

A number of zero- valued bytes are added to the end of the AVP Data field till a word boundary is reached. This page was last edited on 19 Octoberat Obsolete RFCs are indicated with strikethrough text. Diameter implementations are required to support all Mandatory AVPs which are allowed by the message’s formal syntax and defined either in the base Diameter standard or in one of the Diameter Application specifications governing the message.

You can help by adding to it. On 6h 28m 16s UTC, 7 February the time value will overflow.

Both the numeric values and the symbolic values listed below can be used. It is set when resending requests not yet acknowledged as an indication of a possible duplicate due to a link failure. Relays modify Diameter messages by inserting and removing routing information, but do not modify any other dlameter of a message. Diameter sessions MUST be routed only through authorized nodes that have advertised support for the Diameter application required by the session.

Retrieved from ” ietg The Diameter protocol requires that agents maintain transaction state, which is used for failover purposes. See the frag option for details on matching fragmented packets. Adding a new optional AVP does not require a new application.