From nobody Tue Nov 6 01:42:17 2018 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A3C130E6E for ; Tue, 6 Nov 2018 01:42:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dg_zYHILy-aC for ; Tue, 6 Nov 2018 01:42:10 -0800 (PST) Received: from ns.italtel.it (ns.italtel.it [138.132.53.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09548130E5C for ; Tue, 6 Nov 2018 01:42:06 -0800 (PST) Received: from ns.italtel.it (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0383014B4B4; Tue, 6 Nov 2018 10:42:05 +0100 (CET) Received: from exconn00speak.corp.dom (unknown [138.132.89.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ns.italtel.it (Postfix) with ESMTPS id AE48B14B4B3; Tue, 6 Nov 2018 10:42:04 +0100 (CET) Received: from ITMI01VW365.corp.dom (2002:8a84:5a41::8a84:5a41) by ITMI01VW365.corp.dom (2002:8a84:5a41::8a84:5a41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 6 Nov 2018 10:42:03 +0100 Received: from ITMI01VW365.corp.dom ([fe80::d9c:90b0:d9c1:dd97]) by ITMI01VW365.corp.dom ([fe80::d9c:90b0:d9c1:dd97%17]) with mapi id 15.01.1466.003; Tue, 6 Nov 2018 10:42:03 +0100 From: Villa Silvia To: Yuval Lifshitz CC: "dime@ietf.org" Thread-Topic: R: [Dime] Mail regarding draft-ietf-dime-rfc3588bis Thread-Index: AdRtKULzgui1lYo6RmurApMnh888nwBhQ1KAAD1AVPAAUbtUAAEyRq3g Date: Tue, 6 Nov 2018 09:42:03 +0000 Message-ID: References: <9483df2e03b04080a857b3bee987f434@italtel.com> <1783796887.17665942.1540728405641@mail.yahoo.com> <20181031082048.GA12198@dhcp-0-211.tlv.redhat.com> In-Reply-To: <20181031082048.GA12198@dhcp-0-211.tlv.redhat.com> Accept-Language: it-IT, en-US Content-Language: it-IT X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [138.132.89.225] x-puremessage: [Scanned] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [Dime] R: R: Mail regarding draft-ietf-dime-rfc3588bis X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2018 09:42:15 -0000 Thank you very much Yuval. You have been very precious!!! :-) -----Messaggio originale----- Da: Yuval Lifshitz [mailto:yuvalif@yahoo.com] Inviato: mercoled=EC 31 ottobre 2018 09:21 A: Villa Silvia Cc: dime@ietf.org Oggetto: Re: R: [Dime] Mail regarding draft-ietf-dime-rfc3588bis While it may be that some servers will allow that (folowing the "Robustness= Principle"), the client should not do that. Note that even in the case that the server don't mind the change in Origin-= Host, it is most likely because it ignores it, and will not update the valu= e - either way, this is server specific implementation and not part of the = spec. If the client just reconnected to the server, than the Diameter session sho= uld just continue, using the original parameters (including Origin-Host). If the client went down, and a different client took over, than the client = is either expected to start a new session (the common case where the client= is stateless) whith a new Origin-Host, or to continue the same session (if= the client is stateful) with the old Origin-Host. Yuval On Mon, Oct 29, 2018 at 04:23:02PM +0000, Villa Silvia wrote: > Thank you very much for your answer Yuval. > > Do you think that is allowed to a Diameter Client sending a subsequent AA= R for a Session by a different Origin-Host? > What do you think server will do? > > Let me clarify... > > I have this Diameter Client that opens many Diameter Connections with dif= ferent Origin-Hosts and the same Origin-Realm. > > Suppose that the Client sends an AAR for a new Session by Diameter-Connec= tion-1 and Origin-Host-1. > Suppose that the Diameter-Connection-1 will fell and lost. > It shall be permissible for the Client to send subsequent re-auth for the= same Session-Id by a Diameter-Connection-2 and Origin-Host-2? > The Server is required to update the Destination-Host associated to the S= ession-Id (like Target Refresh Requests in SIP dialogs)? > And so all subsequent RAR or ASR will be sent by Server to the Diameter-C= onnection-2 and Destination-Host-2. > > Thank you again, Yuval. > > Silvia > > > Da: Yuval Lifshitz [mailto:yuvalif@yahoo.com] > Inviato: domenica 28 ottobre 2018 13:07 > A: dime@ietf.org; Villa Silvia > 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 se= ssion was initialized (i.e the Destination-Host of the RAR should be the sa= me as the Origin-Host of the AAR). > > There is no requirement, however, to send the RAR on the same Diameter co= nnection that was used to send the AAR. For example, if there was a connect= ivity issue with the client after the AAR was sent, that was resolved (clie= nt 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 t= he 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 us= e "realm routing" and send the RAR on any Diameter connection that may reac= h the desired realm. However, even in this case, the Destination-Host of th= e RAR must be set to the correct Destination-Host, and it is up to the Diam= eter agent(s) to route the request to the correct client. > > Hope this helps, > > Yuval > > On Friday, October 26, 2018, 3:47:26 p.m. GMT+3, Villa Silvia > 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 differ= ent 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 A= AR 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 diffe= rent 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 l= e informazioni in essa contenute e ogni documento o file allegato, e' rivol= ta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa a= utorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvi= sati che qualsiasi azione, copia, comunicazione, divulgazione o simili basa= te sul contenuto di tali informazioni e' vietata e potrebbe essere contro l= a legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Re= golamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione= per errore, vi preghiamo di darne immediata notizia al mittente e di distr= uggere 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-ma= il and its attachments are intended for the addressee(s) only and are confi= dential and/or may contain legally privileged information. If you have rece= ived this message by mistake or are not one of the addressees above, you ma= y take no action based on it, and you may not copy or show it to anyone; pl= ease 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 > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime > Internet Email Confidentiality Footer ** La presente comunicazione, con l= e informazioni in essa contenute e ogni documento o file allegato, e' rivol= ta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa a= utorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvi= sati che qualsiasi azione, copia, comunicazione, divulgazione o simili basa= te sul contenuto di tali informazioni e' vietata e potrebbe essere contro l= a legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Re= golamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione= per errore, vi preghiamo di darne immediata notizia al mittente e di distr= uggere 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-ma= il and its attachments are intended for the addressee(s) only and are confi= dential and/or may contain legally privileged information. If you have rece= ived this message by mistake or are not one of the addressees above, you ma= y take no action based on it, and you may not copy or show it to anyone; pl= ease 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/ 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 aut= orizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisa= ti 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, Rego= lamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione p= er errore, vi preghiamo di darne immediata notizia al mittente e di distrug= gere il messaggio originale e ogni file allegato senza farne copia alcuna o= riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'i= nformativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail= and its attachments are intended for the addressee(s) only and are confide= ntial and/or may contain legally privileged information. If you have receiv= ed 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; plea= se reply to this e-mail and point out the error which has occurred. Click h= ere to read your privacy notice: http://www.italtel.com/it/about/privacy/