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 ). Canonical URL: ; File formats: Plain Text PDF; Status: PROPOSED STANDARD; Obsoleted by: RFC ; Updated by. 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.
|Published (Last):||6 March 2005|
|PDF File Size:||16.39 Mb|
|ePub File Size:||13.97 Mb|
|Price:||Free* [*Free Regsitration Required]|
Diameter sessions MUST be routed only through authorized nodes that have advertised support for the Diameter application required by the session. The use of Relays is advantageous since it eliminates the need for NASes to be configured with the necessary security information they would otherwise require to communicate with Vase servers in other realms.
This is described in Section 5. Messages with the “E” bit set are commonly referred to as error messages. These services are provided by supporting AVP integrity and confidentiality between two peers, communicating through agents.
Diameter Command Naming Conventions Diameter includes support for error handling Section 7capability negotiation Section 5.
Accounting requests without corresponding authorization responses SHOULD be subjected to further scrutiny, as should accounting requests indicating a difference between the requested and provided service. Stateful Agent A stateful agent is one that maintains session state information, dimaeter keeping track of all authorized active sessions.
AVPs are used by the base Diameter protocol to support the following required features: If cleared, the message MUST be locally processed.
NAI realm names are required to be unique and are piggybacked on the administration of the DNS namespace. Message Length The Message Length field is three octets and indicates the length of the Diameter message including the header nase. If no rule matches, the packet is treated as best effort.
The Session-Id is then used in all subsequent messages to identify the user’s session see Section 8 for more information.
Since RADIUS clients and servers diamete not aware of each other’s capabilities, they may not be able to successfully negotiate a mutually acceptable service, or in some cases, even be aware of what service has been implemented. If cleared, the message is an answer. There is no relationship imposed between the two; they are set independently.
These services may happen concurrently e.
Description of the Document Set Protocoll to Extensibility The Diameter protocol is designed to be extensible, using several mechanisms, including: Application Identifier An application is identified by a vendor id and an application id. Support for server-initiated messages is mandatory in Diameter, and is described in Section 8. Internet Standards Application layer protocols Computer access rdc protocols Authentication protocols.
If the base accounting is used without any mandatory AVPs, new commands or additional mechanisms e. This requires that proxies maintain the state of their downstream peers e.
Information on RFC » RFC Editor
Please refer to Section Role of Diameter Agents To avoid potential interoperability issues, it is important to ensure that the semantics of the reused features are well understood.
This security protects the entire Diameter communications path from the originating Diameter node to the terminating Diameter node. Diameter Path Authorization As noted diametef Section 2.
Diameter clients are often implemented in devices situated at the edge of a network and provide access control services for that network.
RFC – Diameter Base Protocol
As ofthe only value supported is 1. A three-letter acronym for both the request and answer is also normally provided. Please refer to bass current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.