DIAMETER BASE PROTOCOL RFC 3588 PDF
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):||5 April 2005|
|PDF File Size:||18.53 Mb|
|ePub File Size:||17.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
Received answers that do not match a known Hop-by-Hop Identifier are ignored by the Diameter agent. To test for a particular IP version, the bits part can be set to zero. Diameter defines agent behavior explicitly; this is diametwr in Section 2.
It MAY do this in one of the following ways: A session is a logical concept at the application layer, and is shared between an access device and a server, and is identified via the Session-Id AVP.
While proxies typically do not respond to client Requests prior to receiving a Response from the server, they may originate Reject messages in cases where policies are violated. Since hase agents do not sit in the forwarding path, they do not alter any AVPs transiting between client and server. In addition, they MUST fully support each Diameter application that is bawe to implement the intended service, e.
The Transport Profile document [ RFC ] discusses transport layer issues that arise with AAA protocols and recommendations on how to overcome these issues.
Typically, it is implemented in order to provide for partial accounting of a user’s session in case pdotocol device reboot or other network problem prevents the delivery of a session summary message or session record. Since the expected behavior is not defined, it varies between implementations.
A Diameter client generates Diameter messages to request authentication, authorization, and accounting services for the user. Each authorized session is bound to a particular service, and its state bawe considered active either until it is notified otherwise or until expiration.
The following actions are supported: Downstream Downstream is used to identify diametter direction of a particular Diameter message from the home server towards the Diameter client. This requires that proxies maintain the state of their downstream peers e.
RFC – Diameter Base Protocol
The following Command Codes are defined in the Diameter base protocol: Additionally, application specific state machines can be introduced either later or at a higher abstraction layer. Capabilities exchange in the open state has been re-introduced in a separate specification [ RFC ], which clearly defines new commands for this feature. All Diameter packets with the same Session-Id are considered to be part of the same session.
Accounting The act of collecting information 33588 resource usage for the purpose of peotocol planning, auditing, billing, or cost allocation. Transmission-level security [ RADIUS ] defines an application-layer authentication and integrity scheme that is doameter only for use with Response packets. The receiver of a Capabilities Exchange message advertising Relay service MUST assume that the sender supports all current and future applications. Translation Agents A translation agent is a device that provides translation between two protocols e.
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.
The “ip” keyword means any protocol will match.
Once accepted by the server, both the client and the server are aware of the session. Expiration time Specifies the time which a dynamically discovered route table entry expires. Please refer to Section Some of these AVP values are used by the Diameter protocol itself, while others deliver data associated with particular applications that employ Diameter.
The supported ICMP types are: Multi-session A multi-session represents a logical linking of several sessions. Diameter Protocol The Diameter base protocol provides the following facilities: A rule for the prioritization of redirect routing criteria when multiple route entries are found via redirects has also been added see Section 6. However, just because a new authentication application id is required, does not 35888 that a new accounting application id is required.