Re: [Dime] R: Mail regarding draft-ietf-dime-rfc3588bis

[Yuval Lifshitz <[e-mail]>]

inline
On Mon, Oct 29, 2018 at 04:40:37PM +0000, Villa Silvia wrote:
> A new request in line
> 
> Da: Yuval Lifshitz [mailto:[e-mail]]
> Inviato: domenica 28 ottobre 2018 13:07
> A: [e-mail]; Villa Silvia <[e-mail]>
> Oggetto: Re: [Dime] Mail regarding draft-ietf-dime-rfc3588bis
> 
> Hello Silvia,
> The server is expected to send the RAR to the same host from which the session was initialized (i.e the Destination-Host of the RAR should be the same as the Origin-Host of the AAR).
> 
> There is no requirement, however, to send the RAR on the same Diameter connection that was used to send the AAR. For example, if there was a connectivity issue with the client after the AAR was sent, that was resolved (client reconnected wit the same Diameter identity), and then the server want to send the RAR, it should be allowed to send it over the new connection to the same client (with the correct Destination-Host).
> 
> Another case is where the client is not directly connected to the server (i.e. a Diameter agent sits between them). In such a case the server may use "realm routing" and send the RAR on any Diameter connection that may reach the desired realm. However, even in this case, the Destination-Host of the RAR must be set to the correct Destination-Host, and it is up to the Diameter agent(s) to route the request to the correct client.
> 
> [SILVIA] I would like to check if I understood this last sentence well.
> In this last case where there is an agent between server and client..
> The server can select a different routing street by “realm routing” so that server can send the RAR or ASR to a different diameter agent peer (compared to that used for the AAR).
> However, server must anyway insert in this RAR the specific Destination-Host-AVP that must be the same as the Origin-Host of the AAR.
> So that the new diameter agent peer will deliver the RAR always to the same “Client Origin-Host and Connection”.
> It is correct?
> I'm sorry if I ask you again but I do not know if I understood the second case correctly
> Thank you very much.
> Silvia
> 

[yuval] yes, your understanding is correct

> 
> 
> Hope this helps,
> 
> Yuval
> 
> On Friday, October 26, 2018, 3:47:26 p.m. GMT+3, Villa Silvia <[e-mail]<mailto:[e-mail]>> wrote:
> 
> 
> 
> Hello Diameter experts and funs,
> 
> 
> 
> I have a question on the interpretation of RFC 6733.
> 
> 
> 
> I have a Client Diameter that opens many Diameter Connections with different Origin-Hosts and the same Origin-Realm.
> 
> The Client need to send AAR in session with maintained state to a Server.
> 
> 
> 
> Where a Diameter Server will send requests in session such as RAR or ASR?
> 
> 
> 
> The Destination-Host-AVP must be valued with the Origin-Host-AVP of the AAR sent by the client or a different Destination-Host-AVP can be chosen by realm?
> 
> 
> 
> What would happen if the diameter connection will fell and lost?
> 
> The Diameter Server must/can/cannot choose to send the request to a different Destination-Host-AVP of the same Client Realm?
> 
> 
> 
> I cannot understand where is the limit between protocol rules and custom policy local develop solution.
> 
> 
> 
> Thank you.
> 
> 
> 
> Silvia
> 
> 
> Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/
> _______________________________________________
> DiME mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/dime
> Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/