top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Using the string +apX for the diameter application identifiers in RFC6408

+3 votes
363 views

Can anybody tell me why use the string "apX" for the application identifiers in RFC6408? Why not use some kind of acronym for them?

E.g., Can I change 'aaaapX' in the following "(S-NAPTR) Application Service Tag" registry table 

 ---------------------------------------------- 
 | Tag | Diameter Application | 
 ---------------------------------------------- 
 | aaaap1 | NASREQ [RFC3588 [1]] | 
 | aaaap2 | Mobile IPv4 [RFC4004 [2]] | 
 ---------------------------------------------- 

as "aaaaconym" as follows: 
 ---------------------------------------------- 
 | Tag | Diameter Application | 
 ---------------------------------------------- 
 | aaanasreq | NASREQ [RFC3588 [3]] | 
 | aaamip4 | Mobile IPv4 [RFC4004 [4]] | 
 ----------------------------------------------
posted Oct 21, 2013 by Meenal Mishra

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

1 Answer

+1 vote

The "apX" directly identified the application identifier number. Therefore there is no need to maintain mapping between human readable acronyms and actual application identifier numbers.

answer Oct 21, 2013 by Sanketi Garg
Similar Questions
+2 votes
Blocking Data usage using Diameter Rx to the PCRF

Is it possible to block all Data traffic for a specific UE by sending Diameter-Rx AAR command to the PCRF?
If yes, can you indicate AVPs shall be present in the AAR?
May I suppose the following AVP list
- Subscription-Id Containing the targeted MSISDN/IMSI
- Framed-IP-Address or Framed-IPv6-Prefix (containing the IP-address allocated to the UE)
- Media-Component-description containing the following Sub AVP
- Media-Component-number Mandatory sub-AVP
- Flow-Status set to DISABLED

0 votes
DIAMETER: When does the Diameter message contains Application-ID field in Diameter header and Application-ID AVP ?

What is the use of keeping the same information in two places like Application-Id in the Diameter header and Application-Id as AVP ?

+3 votes
Diameter:Difference between Vendor-Id presents as an independent AVP and within the Vendor-Specific-Application-ID AVP ?

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.

...