RE: : application ID and no end ...

Thomas,
 
If you are trying to reach a server that implements the new application, then any commands that form part of that application should use the new Application ID.  If the new Application ID is not used, then the messages could not be routed properly.
 
Of course, the drawback for this is, all relays and proxies would need to be updated to enable them to route messages for the new Application ID.  This is why it is not recommended to create new applications unless absolutely necessary.
 
John


________________________________

	From: [email protected] [mailto:[email protected]] On Behalf Of ext Belling, Thomas
	Sent: 29 November, 2005 13:34
	To: [email protected]
	Cc: Grosse-Rhode, Friedrich
	Subject: [AAA-WG]: application ID and no end ...
	
	

	Dear all, 

	allow me to come back to a favorite technical subject on this email exploder before the AAA WG (and email exploder?) a closed down ..

	Immagine an application, e.g. based on DCC, that adds new mandatory AVPs to the CCR and CCA and therefore has an own Diameter application ID assigned.

	The application also uses the RAR, RAA, ASR, and ASA, as defined in RFC 3588, without adding own AVPs to these commands.

	My question: Which application ID shall be used for these commands as Auth-Application-Id ? ID 0 from Diameter base, or the ID of the new application?

	My concern with ID 0 is that the application IDs is also used in Realm-based routing, and you may thus end up with the wrong client is you use diffrent application IDs for different messages within a Diameter session.

	Thanks for your help 

	BR, Th Belling 


	---------------------------------- 
	Dr. Thomas Belling 
	Siemens AG           
	Sankt-Martin-Str. 76 
	D-81541 München Germany 
	Tel     +49 89 636 75207 
	Mobile  +49 172 2974678 
	Email   Thomas.Belling (AT) siemens.com