IETF RFC 3588 DIAMETER BASE PROTOCOL PDF
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.
|Published (Last):||5 October 2011|
|PDF File Size:||19.69 Mb|
|ePub File Size:||6.28 Mb|
|Price:||Free* [*Free Regsitration Required]|
The Diameter protocol requires that agents maintain transaction state, which is used for failover purposes. When set the AVP Code belongs to the specific vendor profocol address space. An access device that is unable to interpret or apply a permit rule MAY apply a more restrictive rule. Diameter Relay and redirect agents must not reject messages with unrecognized AVPs. In this case, all IP numbers from 1. 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.
The ” E ” Error uetf — If set, the message contains a protocol error, and the message will not conform to the CCF described for iett command. However, they basd since they modify messages to implement policy enforcement. The definition contains a list of valid values and their interpretation and is described in the Diameter application introducing the AVP.
Since Relays do not perform any application level processing, they provide relaying services for all Diameter applications, and therefore MUST advertise the Relay Application Identifier. If cleared, the message MUST be locally processed.
However, the protocol’s failover procedures require that agents maintain a copy of pending requests. When creating a request, the End-to-End Identifier is set to a locally unique value.
An access device that is unable to interpret or apply a deny rule MUST terminate the session. Diameter is used for many different interfaces defined by the 3GPP standards, with each interface typically defining new commands and attributes. Therefore, each connection 35588 authenticated, replay and integrity protected and confidential on a per-packet basis. Each English word is delimited by a hyphen. The Diameter protocol requires that relaying and proxying agents maintain transaction diametsr, which is used for failover purposes.
The End-to-End Identifier is an unsigned bit integer field in network byte order that is used to detect duplicate messages along with the combination of the Origin-Host AVP.
This is a valid packet, but it only has one use, to try to circumvent firewalls. Match rgc the TCP header contains the comma separated list of flags specified in spec. After that the transport connection can be disconnected. An example is a message set used to terminate a session. Application-ID is used to identify for which Diameter application the message is applicable.
RFC – Diameter Base Protocol
The following format is used in the definition: Received answers that do not match a known Hop-by-Hop Identifier are ignored by the Diameter agent. Integer64 64 bit signed value, in network byte order. The keyword “any” is 0.
As noted in Section 6. Some common Diameter commands defined in the protocol base and applications are:. Diameter Applications can extend the base protocol by adding new commands, attributes, or both. The use of Relays is advantageous since it eliminates the need for NASes to prottocol configured with the necessary security information they would otherwise require to communicate with Diameter servers in other realms.
A three-letter acronym for both the request and answer is also normally provided.
Information on RFC » RFC Editor
In case of xiameter agents, the Hop-by-Hop Identifier is maintained in the header as the Diameter agent responds with an answer message. Obsolete RFCs are indicated with strikethrough text. This AVP would be encoded as follows: P roxiable – If set, the message MAY be proxied, relayed or redirected. Additionally, application specific state machines can be introduced either later or at a higher abstraction layer.
Packets may be filtered based on the following information that is associated with it: The list may be specified as any combination of ranges or individual types separated by commas. Messages with the ‘E’. The format of the header is: See Section bsse for more information on AVPs. Maintaining session state MAY be useful in certain applications, such as: The fields are transmitted in network byte order.
It is set when resending requests not yet acknowledged as an indication of a possible duplicate due to a link failure.
This allows a single server to handle policies for many services.