top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Diameter : How much diameter protocol flexible to introduce vendor specific application as well as AVPs ?

+6 votes
667 views

I have a requirement for diameter protocol extension. Please explain in details.

posted Feb 7, 2014 by Vimal Kumar Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
Not sure what is your requirement but in Diameter you can have a vendor specific AVP vendor specific Application.

Check http://www.ietf.org/rfc/rfc3588.txt section 6.11
Thanks to share your comment.

1 Answer

+2 votes

Diameter is designed to be extensible. 3GPP has used this extensibility to defined may 'interfaces' (Diameter applications) which are widely deployed now. (e.g., Gx - TS 29.212)

There are proprietary extensions too. But idea is to use existing commands and AVPs to the maximum possible extent, add new 'optional' AVPs as needed. But if existing commands can't serve the purpose, you will end up defining new application.

There are tools that make this easy - and we have one :) Can explain more if you have specific questions.

answer Feb 7, 2014 by Rathnakumar Kayyar
Thank you to provide your valuable comment on this topic.
Similar Questions
+3 votes

I saw Capabilities-Exchange-Request and Capabilities-Exchange-Answer messages. In CER message there are two places where Vendor-Id AVP is present, one as an independent AVP and the other one as part of Vendor-Specific-Application-Id AVP. If both of them are present in request message then both will be having same value or can hold different values.

+5 votes

Also what are the rules for populating those AVPs (in the RFC it is not clear when to use each one of the option)?

...