DIAMETER BASE PROTOCOL RFC 3588 PDF

I knew various protocols and I immediately took on Diameter. A Diameter node knows how to connect to another Diameter node or what to do if another Diameter node wants to connect to it. And then, they speak the Diameter application language. And the beauty of the protocol is that the Diameter message the packet can be extended in many ways.

Author:Meziramar Mazujin
Country:Austria
Language:English (Spanish)
Genre:Career
Published (Last):24 March 2018
Pages:102
PDF File Size:4.65 Mb
ePub File Size:19.22 Mb
ISBN:442-2-76928-353-8
Downloads:32287
Price:Free* [*Free Regsitration Required]
Uploader:Zukora



This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications.

The Diameter base application needs to be supported by all Diameter implementations. Message length. Size of the Diameter message including the header fields.

R , Request. If set, the message is a request. Otherwise the message is an answer. P , Proxiable. If set, the message MAY be proxied, relayed or redirected.

Otherwise the message MUST be locally processed. E , Error. If set, the message contains a protocol error, and the message will not conform to the ABNF described for this command. Messages with this bit set are commonly referred to as error messages. T , Potentially retransmitted message. This flag is set after a link failover procedure, to aid the removal of duplicate requests.

It is set when resending requests not yet acknowledged, as an indication of a possible duplicate due to a link failure. Diameter agents only need to be concerned about the number of requests they send based on a single received request.

Retransmissions by other entities do not need to be tracked. 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. Application ID. Used to identify to which application the message is applicable for. The application can be an authentication application, an accounting application or a vendor specific application. Hop by Hop ID. This field aids in matching requests and replies. The sender MUST ensure that the 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.

The sender of an Answer message MUST ensure that this field contains the same value that was found in the corresponding request. The identifier is normally a monotonically increasing number, whose start value was randomly generated. An answer message that is received with an unknown identifier MUST be discarded. End to End ID. This field is used to detect duplicate messages. Upon reboot implementations MAY set the high order 12 bits to contain the low order 12 bits of current time, and the low order 20 bits to a random value.

Senders of request messages MUST insert a unique identifier on each message. The identifier MUST remain locally unique for a period of at least 4 minutes, even across reboots. The originator of an Answer message MUST ensure that the field contains the same value that was found in the corresponding request. The combination of the Origin-Host and this field is used to detect duplicates. A structure used to encapsulate protocol specific data as well as authentication, authorization and accounting information.

AVP code. When combined with the Vendor ID the attribute is uniquely identified. AVP length. Total size of the AVP header and data in bytes. Vendor ID. Diameter Agent. A Diameter node that provides either relay, proxy, redirect or translation services. Diameter Client. A device at the edge of the network that performs access control. Diameter Node. A host process that implements the Diameter protocol, and acts either as a Client, Agent or Server.

Diameter Peer. A Diameter Node to which a given Diameter Node has a direct transport connection. Diameter Security Exchange. A process through which two Diameter nodes establish end-to-end security. Diameter Server. A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm.

Home Realm. The administrative domain with which the user maintains an account relationship. Local Realm. The administrative domain providing services to a user. An administrative domain MAY act as a local realm for certain users, while being a home realm for others. Used to extract the identity and realm of a user. The string in the NAI that immediately follows the ' ' character. NAI realm names are required to be unique, and are piggybacked on the administration of the DNS namespace.

Diameter makes use of the realm, also loosely referred to as domain, to determine whether messages can be satisfied locally, or whether they must be routed or redirected. Working groups :.

G5N150UF PDF

A developer’s perspective: Why do I like Diameter protocol?

This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations. Message length. Size of the Diameter message including the header fields. R , Request. If set, the message is a request.

LES 4 ACCORDS TOLTEQUES PDF

Diameter Base Protocol

Diameter is an authentication, authorization, and accounting protocol for computer networks. It belongs to the application layer protocols in the internet protocol suite. The name is a play on words, derived from the RADIUS protocol, which is the predecessor a diameter is twice the radius. Diameter is used for many different interfaces defined by the 3GPP standards, with each interface typically defining new commands and attributes.

Related Articles