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. 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 ).
|Published (Last):||7 January 2004|
|PDF File Size:||16.10 Mb|
|ePub File Size:||14.88 Mb|
|Price:||Free* [*Free Regsitration Required]|
An access device that is unable to interpret or apply a deny rule MUST terminate the session. Upstream Upstream is used to identify the direction of a particular Diameter message from the access device towards the home server. Diameter Server A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. This is known as the Realm Routing Table, as is defined further in Section 2. A given Diameter instance of the peer state machine MUST NOT use more than one transport connection to communicate with a given peer, unless multiple instances exist on the peer in which case a separate connection per process is allowed.
Roaming Relationships Roaming relationships include relationships between companies and ISPs, orotocol among peer ISPs within a roaming consortium, and relationships between an ISP and a roaming consortium. In that sense, Diameter is a peer- to-peer protocol.
The RFC defines an authorization and an accounting state machine. The Proxy-Info AVP allows rff agents to add local state to a Diameter request, with the guarantee that the same state will be present in the answer.
Each new definition must be either defined or listed with a reference to the RFC that defines the format. The AVP can ; appear anywhere in the message. If cleared, the message is an answer. The metering options MUST be included.
NAI realm names are required to be unique, and are piggybacked on the administration of protkcol DNS namespace. Each of these AVPs follows – in the order in which they are specified – including their headers and padding. Diameter Applications can extend the base protocol by adding new commands, attributes, or both.
Agents do not need to support all modes of operation in order to conform with the protocol specification, but MUST follow 33588 protocol compliance guidelines in Section 2. Happy to help you again. Multi-sessions are tracked by using the Acct-Multi-Session-Id.
Translation of messages can only occur if the agent recognizes the application of a particular request, and therefore translation agents MUST only advertise their locally supported applications. Hope it suffice your query.
For more information please refer https: To test for a particular IP version, the bits part can be set to zero. The base protocol also defines certain rules that apply to all exchanges of messages between Diameter nodes. LOCAL – Diameter messages that resolve to a route entry with the Local Action set to Local dfc be satisfied locally, and do not need to be routed to another server. The absence of a particular option may be denoted with a ‘!
A home realm may also wish to check that each accounting request message corresponds to a Diameter response authorizing the session.
Diameter Base Protocol Support
In addition, they MUST fully support each Diameter application that is needed to implement the intended service, e. By providing explicit support for inter-domain roaming and message routing Sections 2.
This MAY require that new AVP values be assigned to represent the new authentication transform, or any other scheme that produces similar results. This is typically accomplished by tracking the diameeter of NAS devices.
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. Please refer to Section If no doameter matches, the packet is treated as best effort.
Chinmoy March 20, at 8: Dinesh Kumar September 6, at 4: The ” E ” Error bit — If set, the message contains a protocol error, and the diametre will not conform to the CCF described for this command.
The End-to-End Identifier is an unsigned bit prptocol field in network byte order that is used to detect duplicate messages along with the combination of the Origin-Host AVP. When relays or proxy are involved, this hop-by-hop security does not protect the entire Diameter user session. Diameter relay and proxy agents are responsible for finding an upstream server that supports the application of a particular message.
Newer Post Older Post Home. Integer32 32 bit signed value, in network byte order. Prior to issuing the request, NAS performs a Diameter route lookup, using “example. Local Action The Local Action field is used to identify how a rff should be treated. Relay Agent or Relay Relays forward requests and responses based on routing-related AVPs and realm routing table entries.