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):||21 August 2014|
|PDF File Size:||3.54 Mb|
|ePub File Size:||5.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
This AVP would be encoded as follows: The combination of the Origin-Host see Section 6. The RFC defines a core state machine for maintaining connections between peers and processing messages.
Given that the Diameter protocol introduces the concept of long-lived authorized sessions, translation agents MUST be session stateful and MUST maintain transaction state.
The AddressType is used to discriminate the content and format of the remaining octets. Internet Standards Application layer protocols Computer access control protocols Authentication protocols. Application-ID is used to identify for which Diameter application the message is applicable.
Accounting requests without corresponding authorization responses SHOULD be subjected to further scrutiny, as should accounting requests indicating a difference between the requested ffc provided service. This routing decision is performed using a list of supported realms, and known peers. Command Flags The Command Flags field is eight bits. End-to-end security policies include: The fields are transmitted in network byte order.
If cleared, the message MUST be locally processed. Application-ID Application-ID is four octets and is used to identify to which application the message is applicable for. Duplicate answer messages that are to be locally consumed see Section 6. This does not affect the selection of port numbers.
The identifier MUST remain locally unique for a period of at least 4 minutes, even across reboots. The following Command Codes are defined in the Diameter base protocol: The values are for permanent, standard commands allocated by IANA.
Diameter (protocol) – Wikipedia
Diameter Command Naming Conventions Diameter command names typically includes one or more English words followed by the verb Request or Answer. Senders of request messages MUST insert a unique identifier on each message. The absence of a particular option may be denoted with a ‘! 35888 from ” https: The default value is zero.
Therefore, each connection is authenticated, replay and integrity protected and rfx on a per-packet basis. A three-letter acronym for both the request and answer is also normally provided.
Each authorized session is bound to a particular service, and its state is considered active either until it is notified otherwise, or by expiration. The format of the Data field MUST be one of the following base data types or a data type derived from the base rcf types. The encoding example illustrates how padding is used and how length fields are calculated.
The ‘P’ bit indicates the need for encryption for end-to-end security. Retrieved 30 April Thus an administrator could change the configuration to avoid interoperability problems. Redirecting a Diameter Message Since redirect agents do not perform any application level processing, they provide relaying services for all Diameter applications, and therefore MUST advertise the Relay Application Identifier.
It is set when resending requests not yet acknowledged as an indication of a possible duplicate due to a link failure. Role of Diameter Agents In addition to client and servers, the Diameter protocol introduces relay, proxy, redirect, and translation agents, each of which is defined in Section 1.
This page was last edited on 19 Octoberat