[Dime] Application Id for commands in Gq and similar applications

["Tom-PT Taylor" <taylor at nortel.com>]

I have been mulling over the use of application-ids in the new ITU-T Rs 
application, which builds on 3GPP Gq. It has introduced a stateless mode 
of operation which has caused us to reuse a couple of 3GPP Cx commands, 
Push-Notification-Request/Answer, in place of RAR/RAA when the PDF is 
running in stateless mode. That means we have a new application, not Gq.

To ensure that Rs messages are routed to the right application at the 
destination, the application-Id in the Diameter header has to be that of 
the Rs application rather than of the application (mostly base, but also 
NASREQ and Cx as I said) that originally defined the command. And the 
application-Id presented in the body of the command has to be consistent 
with the header.

My conclusion is that Gq should not have preserved the mandatory 
Auth-Application-Id AVPs of the commands it took from base and RFC 4005, 
but should instead have accepted that it was an experimental 
vendor-specific application within the context of Diameter rules and 
replaced these AVPs with Vendor-Specific-Application-Id AVPs. The Rs 
application should do the same, using its own application-id and the 
ITU-T vendor-id.

Comments?

_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime