Diameter is an authentication, authorization, and accounting protocol for computer networks. The Diameter base protocol is defined by RFC ( Obsoletes: RFC ) and .. RFC , Diameter Network Access Server Application. RFC (part 1 of 4): Diameter Network Access Server Application. Diameter Network Access Server Application (NASREQ, RFC ). • Diameter Base Accounting (RFC ). • Diameter Extensible Authentication Protocol.
|Published (Last):||14 June 2010|
|PDF File Size:||10.67 Mb|
|ePub File Size:||14.93 Mb|
|Price:||Free* [*Free Regsitration Required]|
Distribution of this memo is unlimited. Current information, if any, about IPR issues: A Command Code is used to determine the action that is to be taken for a particular message.
Call and Session Information. Retrieved 12 October Information about the call, the identity of the dia,eter, and the user’s authentication information are packaged into a Diameter AA-Request AAR message and sent to a server.
When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements. When set the AVP Code belongs to the specific vendor code address space.
The packet consists of a Diameter header and a variable number of Attribute-Value Pairs, or AVPs, for encapsulating information relevant to the Diameter message.
Diameter (protocol) – Wikipedia
Additionally, application specific state machines can be introduced either later or at a higher abstraction layer. It belongs to the application layer rff in the internet protocol suite. The Diameter protocol requires that relaying and proxying agents maintain transaction state, which is used for failover purposes. Internet Standards Application layer protocols Computer access control protocols Authentication protocols.
ITU-T work programme
VPN Virtual Private Network – In this document, this term is used to describe access services that use tunneling methods. Then it defines the Diameter message Command-Codes.
It is possible for a single session to be authorized first and then for an authentication request to follow. All RFCs always remain available on-line.
Retrieved 30 April Application-ID is used to identify for which Diameter application the message is applicable. If 400, the message MUST be locally processed. Diameter Applications can extend the base protocol by adding new commands, attributes, or both.
Diameter is used for many different 4005 defined by the 3GPP standards, with each interface typically defining new commands and attributes. The authorization AVPs are further broken down by service type.
First, this document describes the operation of a Diameter NAS application. You can help by adding to it. Messages with the “E” bit set are commonly referred to as error messages. If authorization was requested, a successful response will include the authorization AVPs appropriate for the service being provided, as defined in section 6. Justification for the specific reference: The degree of stability or maturity of the document: Any explicit references within that referenced document should also be listed: This is part of the basic protocol functionality and all stacks should support it and as such abstract from the connectivity related operations.
Other useful information describing the “Quality” of the document:. This capability goes beyond the Call Check capabilities described in section 5. For example, for pre-paid services, the Diameter server that originally authorized a session may need some confirmation that the user is still using the services.
ITU-T A.5 reference justification
When creating a request, the End-to-End Identifier is set to a locally unique value. It is set when resending rfcc not yet acknowledged as an indication of a possible duplicate due to a link failure. Some common Diameter commands defined in the protocol base and applications are:.