RE: : application ID and no end ...
"Belling, Thomas" <[email protected]> Tue, 29 Nov 2005 14:01:33 +0100
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <784A66466728424D93027C59B6478B9E802D62@MCHP7I5A.ww002.siemens.net> |
Hi all, I agree that in most practical scenarios realm based routing would not be used for an ASR. However, this is nowhere stated on RFC 3558 - so we should not rule that out. Furthermore, instead of demading complicated considerations in this respect from each application designer, wouldn´t it be easier to state that as a rule the app-ID should be used for all commands within a Diameter session related to that application? Thomas > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of [email protected] > Sent: Tuesday, November 29, 2005 1:53 PM > To: [email protected] > Subject: RE: [AAA-WG]: application ID and no end ... > > > Hi, > > > ASR is a common diameter message applicable to any > > application and since the Destination-Host is used for > > routing I don't see how the message can reach the wrong > > client. So, ASR can use application id '0'IMHO. > > I think so too. > > It seems that in some cases the application-id should > be changed even if there is no changes to the command > but in other cases this is not needed. > > I think it might be difficult to find a rule that can > be applied in all cases. > > I think the main thing is that the Diameter Application > defines what app-id is used in each case taking in account > the possible error cases etc. > > > BR, > Mikko > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On Behalf Of ext STURA Marco Consultant > > Sent: 29 November, 2005 14:21 > > To: Loughney John (Nokia-NRC/Helsinki); > > [email protected]; [email protected] > > Cc: [email protected] > > Subject: RE: [AAA-WG]: application ID and no end ... > > > > John, > > > > but ASR is mainly sent by a server to a specific client using > > the Destination-Host. The server must know where the Diameter > > session to be torn down is actually running, in which client. > > > > ASR is a common diameter message applicable to any > > application and since the Destination-Host is used for > > routing I don't see how the message can reach the wrong > > client. So, ASR can use application id '0'IMHO. > > > > Regards > > Marco > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On Behalf Of [email protected] > > Sent: Tuesday, November 29, 2005 1:06 PM > > To: [email protected]; [email protected] > > Cc: [email protected] > > Subject: RE: [AAA-WG]: 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 >