top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

Allowed host and realm naming for a diameter node

+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.

posted Mar 15, 2015 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

The realm FQDN is always a final substring of the host name.
As you say, some vendors make further restrictions, smaller or bigger, on host and realm names.
Also, some standards specify a strict format for the host name (e.g. for an MME, see section of 3GPP TS 23.003 ).

answer Mar 26, 2015 by Berci Pécsi
Similar Questions
+1 vote

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

+3 votes

What would be the standard value for the Origin Host and realm from the MME and HSS?

My question is regarding the for roaming in the GSMA is always mention that all the configuration should contain the

But we are a little confuse with the realm configuration from both sides. If there any standard value we need to configure to comply with other carriers when we approach roaming services ?

+2 votes

Probably is bigineer question. Diameter protocol maintains two table one is peer and other is realm. My question here is what is the requirement of having two tables here. We can have only one i.e. Peer Table which will tell us which peer to be reached. Looks that I am missing some part...

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.