Re: [Stox] review: stox-im-03

Peter Saint-Andre <stpeter@stpeter.im> Tue, 24 September 2013 12:40 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B57A711E812E for <stox@ietfa.amsl.com>; Tue, 24 Sep 2013 05:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.834
X-Spam-Level:
X-Spam-Status: No, score=-101.834 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AceuEkaELq3D for <stox@ietfa.amsl.com>; Tue, 24 Sep 2013 05:40:13 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1420F11E8121 for <stox@ietf.org>; Tue, 24 Sep 2013 05:40:11 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0D1CD415DF; Tue, 24 Sep 2013 06:45:21 -0600 (MDT)
Message-ID: <5241882B.6000203@stpeter.im>
Date: Tue, 24 Sep 2013 06:40:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <2B9B48179856DC4FA00C93C79EB7E64A2A443A@ESESSMB109.ericsson.se>
In-Reply-To: <2B9B48179856DC4FA00C93C79EB7E64A2A443A@ESESSMB109.ericsson.se>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "stox@ietf.org" <stox@ietf.org>
Subject: Re: [Stox] review: stox-im-03
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2013 12:40:17 -0000

Oh, and this text probably belongs in the -core document, I think...

On 9/24/13 6:37 AM, Salvatore Loreto wrote:
> 
> Thanks Peter
> 
> 
> --Original message---
> Sender: "Peter Saint-Andre" <stpeter@stpeter.im>
> Time: Tue Sep 24 15:35:00 EEST 2013
> Cc: stox@ietf.org, 
> Subject: Re: [Stox] review: stox-im-03
> 
> On 9/24/13 12:02 AM, Salvatore Loreto wrote:
>> On 9/24/13 2:45 AM, Peter Saint-Andre wrote: Hi Sal, thanks for the
>> review.
> 
>> On 9/20/13 4:42 AM, Salvatore Loreto wrote:
> 
>>>>> my only comments is about the fact that section 3. XMPP to
>>>>> SIP implies that the MESSAGE is always (and maybe can only
>>>>> be) delivered over a TCP connection; RFC3428 states
>>>>>
>>>>> Whenever possible, MESSAGE requests SHOULD be sent over
>>>>> transports that implement end-to-end congestion control, such
>>>>> as TCP or SCTP. However, SIP does not provide a mechanism to
>>>>> prevent a downstream hop from sending a request over UDP.
>>>>>
>>>>> so you can delivery it over UDP as well and that has also
>>>>> being raised in a previous thread while talking on the
>>>>> Call-ID mapping to <thread/>. Actually you will be forced to
>>>>> deliver over UDP if the SIMPLE server only supports UDP.
>> It's not clear to me why the XMPP-to-SIP gateway couldn't
>> communicate with the SIMPLE server over UDP. Which text in Section
>> 3 do you think implies that only TCP connections are supported?
>>> there is not text at all, and that is the problem. When I read
>>> the Section 3 and the example I got the impression that I can
>>> only use TCP to forward the message on the SIP side but maybe it
>>> is only me!
> 
> I doubt it is only you. :-)
> 
> Because there is no such thing as XMPP over UDP, the gateway from SIP
> to XMPP will need to communicate over TCP. However, I see no reason
> why the gateway from XMPP to SIP could not be "smart" and send SIP
> messages over TCP or UDP depending on what the far SIP server
> supports. I'll work to add some clarifying text on these points.
> 
> Peter
> 
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox
> 

-- 
Peter Saint-Andre
https://stpeter.im/