Canonical URL: ; File formats: Plain Text PDF; Status: PROPOSED STANDARD; Obsoleted by: RFC ; Updated by. Diameter is an authentication, authorization, and accounting protocol for computer networks. The Diameter base protocol is defined by RFC ( Obsoletes: RFC ) and defines the minimum requirements for an AAA protocol. Diameter. Diameter is the protocol used within EPS/IMS architectures for AAA ( Authentication, Diameter is specified primarily as a base protocol by the IETF in RFC
|Published (Last):||16 October 2010|
|PDF File Size:||14.48 Mb|
|ePub File Size:||7.25 Mb|
|Price:||Free* [*Free Regsitration Required]|
Retrieved 30 April If no rule matches, the packet is treated as best effort.
Information on RFC » RFC Editor
Byte sequences that do not correspond to the valid encoding of a code point into UTF-8 charset or are outside this range are prohibited. The metering options MUST be included. One or more Session-Ids must follow.
Both the numeric values and the symbolic values listed below can be used. Diameter is an authentication, authorization, and accounting protocol for computer diqmeter. A local realm may wish to limit this exposure, for example, by establishing credit limits for intermediate realms and refusing to accept responses which would violate those limits.
Message Length The Message Length field is three octets and indicates the length of the Diameter message including the header fields. It belongs to the application layer protocols in the internet protocol suite.
Accounting requests without corresponding authorization responses SHOULD be subjected to further scrutiny, as should accounting requests indicating a difference dlameter the requested and provided service.
Views Read Edit View history. Any AVP for which the P bit may be set or which may be encrypted may be considered sensitive. From Wikipedia, the free encyclopedia. Integer32 32 bit signed value, in network byte order. This section needs expansion. Diameter sessions MUST be routed only through authorized nodes that have advertised support for the Diameter application required by the session. The Diameter protocol was initially developed by Diametwr R.
AVP Values of this type that are not a multiple of four-octets in length is followed by the necessary padding so that the next AVP if any will start on a bit boundary.
The supported IP options are: Maintaining session state MAY be useful in certain applications, such as: Prior to bringing up a connection, authorization checks are performed at each connection along the path.
An access device that is unable to interpret or apply a permit rule MAY apply a more restrictive rule. Each authorized session is bound to a particular service, and its state is considered active either until it is notified otherwise, or by expiration.
You can help by adding to it. Relaying of Diameter messages The example provided in Figure 2 depicts a request issued from NAS, which dixmeter an access device, for the user bob example.
Archived from the original on 4 July 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.
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. End-to-End Security Framework End-to-end security services 3588 confidentiality and message origin authentication.
Diameter Base Protocol Support
The supported TCP flags are: If cleared, the message is an answer. The sender MUST ensure that the Hop-by-Hop identifier in a diameher is unique on a given connection at any given time, and MAY attempt to ensure that the number is unique across reboots. Command-Code The Command-Code field is three octets, and is used in order to communicate the command associated with the message.