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):||7 June 2010|
|PDF File Size:||9.78 Mb|
|ePub File Size:||4.85 Mb|
|Price:||Free* [*Free Regsitration Required]|
Each English word is delimited by a hyphen. As ofthe only value supported is 1. 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. One or more Session-Ids must follow. 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. The Message Length field indicates the length of the Diameter message in bytes, including the header fields and the padded AVPs.
End-to-End Identifier The End-to-End Identifier is an unsigned bit integer field in network byte order and is used to detect duplicate messages.
Retrieved from ” https: However, they differ since they modify messages to implement policy enforcement. P roxiable – If set, the message MAY be proxied, relayed or redirected.
Prottocol field is only present if the respective bit-flag is enabled.
An access device that is unable to interpret or apply a permit rule MAY apply a more restrictive rule. 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 slower pace. The ” R ” Request bit — If set, the message is diamrter request. Here there are two: The supported IP options are: Received answers that do not match a known Hop-by-Hop Identifier are ignored by the Diameter agent.
The encoding example illustrates how padding is used and how length fields are calculated. A stateful agent is one that maintains session state information; by keeping track of all authorized active sessions. The supported ICMP types are: Both the request and the protoclo for a given command share the same command code. The AddressType is used to discriminate the content and format of the remaining octets.
Which AVPs are sensitive is determined by service provider policy. The list may be specified as any combination of ranges diametef individual types separated by commas. By issuing an accounting request corresponding to the authorization response, the local realm implicitly indicates its agreement to provide the service indicated in the authorization response.
RFC – Diameter Base Protocol
T Potentially re-transmitted message – This flag is set after a link failover procedure, to aid the removal of duplicate requests. Direction in or out Source and destination IP address possibly masked Protocol Source and destination port lists or ranges DSCP values no mask or range Rules for the appropriate direction are evaluated in order, with the first matched rule terminating the evaluation.
The “ip” keyword means any protocol will match. It is important to note that although proxies MAY provide a value-add function for NASes, they do not allow access devices to use end-to- end security, since modifying messages breaks authentication. All proxies MUST potocol transaction state. On 6h 28m 16s UTC, 7 February the time value will overflow. Proxies MAY be used in call control centers or access ISPs that provide outsourced connections, they can monitor the number and types of ports in use, and make allocation and bass decisions according to their configuration.
Diameter (protocol) – Wikipedia
An access device that is diameeter to interpret or apply a deny rule MUST terminate the session. Each new definition must be either defined or listed with a reference to the RFC that defines the format. Since enforcing policies requires an understanding of the service being provided, Proxies MUST only advertise the Diameter applications they support.
If no rule matches, the packet is dropped if the last rule evaluated was idameter permit, and passed if the last rule was a deny.
Each authorized session is bound to a particular service, and its state is considered active either until it is notified otherwise, or by expiration. Diameter Header A summary of the Diameter header format is shown below.
The format of diametfr header is: Unsigned32 32 bit unsigned value, in network byte order.