top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

e2e and h2h identifier in diameter

+2 votes

What is the significance of "Hop-by-Hop identifier" & "End-to-End identifier" in Diameter ? As per RFC3588, "Hop-by-Hop id" helps in matching requests & replies and "End-to-End" helps in detecting duplicate packets... However, I couldn't understand why a single identifier can't be used to handle both detecting duplicate packets & matching request and replies. As per the identifier names, I thought "Hop-by-Hop" helps when there are agents involved during diameter routing... Does it matter when there is only Client & Server and there is no Agent/Relay in between the diameter client and server ?

posted Aug 27, 2013 by Deepankar Dubey

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

+1 vote
Best answer

It is true that in case of a client-to-server single-hop deployment, e2eid can server the purpose, but since Diameter protocol supports multi-hop scenario, it uses hop-by-hop id to uniquely associate an answer to the request. A peer stamps a unique (for that peer) hop-id while sending the request, and when the answer comes back (carrying the same hop-id), it is able to extract the required information like the source of the request as well as its 'original' hop-id.
The protocol has to support the general deployment (which would involve relays between agent and server). It can't do separate processing for the special case of single hop deployment. Note that e2eid is required to be unique only for that 'originating host', so at the server (and at relays) there could be multiple requests with the same e2eid from different clients.

In your own case, even though today you have a single hop deployment, as the network grows, you may need a relay in between. With the right implementation, you can achieve that without any change to the application or protocol implementation, just by a configuration change.

answer Aug 27, 2013 by Rathnakumar Kayyar
Similar Questions
+1 vote

Can someone please explain why few "request" message contains Destination-Host and Destination-Realm AVPs and few of them not ?

+1 vote

According to the specs 5001 and 5002 occurs when IMSI and session ID are not found in the database, in what circumstances IMSI and session ID could not be found or recognized by the database?

+3 votes

I want some reference how to determine the max and min length for Standard Diameter AVPs and 3GPP Diameter AVPs based on Seagull dictionary which is open source. How I can determine max and min length for different data types let say UTF8 String, Octet String, Unsigned32,String,Address etc. Any reference highly appreciated.

+3 votes

I am trying to clarify the allowed naming convention for the host and realm of a diameter node. This relates to the values used in the Origin-Host AVP (AVP Code 264) and Origin-Realm AVP (AVP Code 296). I have reviewed the Diameter RFCs and cannot find a definitive answer to this issue.

The reason for asking this question is that I am in discussion with a vendor of a Diameter Routing Agent (DRA) which claims that the host of a diameter node has to be in the format host.realm.
(1) Example of the only allowed format according to the vendor:Origin-Realm:
I want to clarify if multiple subdomains are allowed to be added in the host without being present in the realm.(2) Example:Origin-Realm:

According to the vendor, the example 2 is not allowed. To have the host as in example 2, the realm will have to be
Could someone please clarify this naming issue or point me to the standard where this is defined.

Useful Links with Similar Problem
Contact Us
+91 9880187415
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.