Re: [Stox] Communication between STOX-capable and non-STOX-capable entities

Matt Ryan <mryan@getjive.com> Thu, 29 May 2014 14:48 UTC

Return-Path: <mryan@getjive.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C04541A034F for <stox@ietfa.amsl.com>; Thu, 29 May 2014 07:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 Qx0jsRbvzbyn for <stox@ietfa.amsl.com>; Thu, 29 May 2014 07:48:37 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D15851A6F04 for <stox@ietf.org>; Thu, 29 May 2014 07:48:35 -0700 (PDT)
Received: by mail-ig0-f178.google.com with SMTP id hl10so439565igb.17 for <stox@ietf.org>; Thu, 29 May 2014 07:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getjive.com; s=mail; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XriMQaDjjAYD8CjYd9hIVaXhwlM7p0nPW9VbFGfLKPw=; b=qY7Ynk0LXdsDZZZbw76GEV2QsbUt5NIsX/8Yg0x0wVmts4Zuo9coN1TxOo19fOQrL/ xoizodhBzWuRMpbr96PQP0Nh+GHvjv74lRHZuJKYzBHnytecmvtoh220A7HuNKx5Q7Fb G87U00hXtbeFrs36RoMjMT14WA+pJoxCFSqvc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XriMQaDjjAYD8CjYd9hIVaXhwlM7p0nPW9VbFGfLKPw=; b=hlywKODVmJyXbR1UKm871mR1PXY/lNDCW+q3SmSMgFfm95I+v2VaWonEJTtuVblxoU MZaS7wm7WoePiq4huCnFOyJBrDxJK7R/WlNWM9XCUw/DOg8LdRrsTJakhWd5aKQBvsBL JSTtk4fXRAr1djzOZc5rzoRI/ahKp/2sJiId3JUbForjs+dE1J8QAPypwPcOyCa0+VEt xyXDFO/0PB71j2A2XKLQilFEDTI6WQ1lU1oCnPs/UULUZIB6srZWbKh1ymIaYk264oe1 n4Pw7fPMCSBPLJ1SyGzHp1AEnwdgw5UevpY6dj2PGRD9/8e2wO9brzHf4VoB2VtPUONM c3GQ==
X-Gm-Message-State: ALoCoQlFjIuANQTGkQFh+rfeyI9XM1kBixH+HGkjPPFRmpAugy/v9/kijGtG3g0tEZKb55RbQHw5
X-Received: by 10.42.204.19 with SMTP id fk19mr8116488icb.68.1401374911641; Thu, 29 May 2014 07:48:31 -0700 (PDT)
Received: from [10.20.200.236] ([199.87.120.126]) by mx.google.com with ESMTPSA id vm1sm14634792igc.3.2014.05.29.07.48.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 May 2014 07:48:31 -0700 (PDT)
Message-ID: <538748BE.1050608@getjive.com>
Date: Thu, 29 May 2014 08:48:30 -0600
From: Matt Ryan <mryan@getjive.com>
Organization: Jive Communications, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: stox@ietf.org
References: <537ABFA1.2080606@getjive.com> <CDAE759A-8174-46E6-8610-A37E554AB3FD@ag-projects.com> <53872C3C.7000007@stpeter.im>
In-Reply-To: <53872C3C.7000007@stpeter.im>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/Mkd5VXsTnWrBfR24-fUt-XaDE7U
Cc: =?ISO-8859-1?Q?Sa=FAl_Ibarr?= =?ISO-8859-1?Q?a_Corretg=E9?= <saul@ag-projects.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] Communication between STOX-capable and non-STOX-capable entities
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 29 May 2014 14:48:39 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Saúl and Peter, thanks for your input on my question.

I agree that this is the approach we should take.  This direction is
supported by RFC 7427 (previously draft-ietf-stox-core) where the
responsibility for determining the format for communication and
translating if required is put upon the sending server and it's
accompanying gateway, and not upon the receiving server.

Because of this, I have further concerns with draft-ietf-stox-chat-06
as well as with draft-ietf-stox-groupchat-04.  I will enumerate these
each separately in their own review emails.  But in summary, the
concerns are that the examples given in these drafts show the gateways
on both sides of communication as being involved in exchanges where
they should not be required, and that showing the involvement of both
gateways gives the impression that both ARE required.

In other words, it does not emphasize the point that STOX-capable
servers must be able to communicate effectively with non-STOX-capable
servers, which it seems we agree is important.


On 5/29/14, 6:46 AM, Peter Saint-Andre wrote:
> On 5/28/14, 6:37 AM, Saúl Ibarra Corretgé wrote:
>> Hi Matt,
>> 
>> On May 20, 2014, at 4:36 AM, Matt Ryan wrote:
>> 
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
>>> 
>>> Should a STOX-capable server be able to communicate with a 
>>> non-STOX-capable server, so long as the communication is 
>>> started by the STOX-capable server?  Is this among the current
>>>  goals of the WG?
>>> 
>>> Sorry if this has been covered - but this particular point 
>>> remains unclear to me despite numerous readings through 
>>> draft-ietf-stox-core and some of the other supporting drafts.
>>> 
>>> 
>>> Let me provide a simple example to explain what I mean.
>>> 
>>> Suppose an XMPP client initiates a chat to a user that happens
>>>  to be a SIP client user.  Per draft-ietf-stox-chat, this 
>>> request flows through the XMPP Server which determines that the
>>> message is targeted to a SIP user, and then invokes its own
>>> XMPP-to-SIP Gateway to translate the request to a SIP request
>>> and send that request on to the appropriate SIP server.
>>> 
>>> So far, the XMPP Server knows that the target user is a SIP 
>>> user, but does not know anything about the SIP Server 
>>> capabilities other than that it is (presumably) a SIP server. 
>>> Importantly, the XMPP Server does not know whether the SIP 
>>> Server also supports a SIP-to-XMPP gateway.
>>> 
>>> 
>>> This is where my question comes.  Given the described XMPP 
>>> Server with a corresponding XMPP-to-SIP gateway, is it meant to
>>> be the case that this XMPP Server should be able to communicate
>>> with any valid SIP server, so long as the conversation is
>>> initiated by the XMPP Server?
>>> 
>>> 
>>> This is an important point because it has direct impact on 
>>> several of our current drafts.
>>> 
>> 
>> The idea is that a STOX capable infrastructure is transparent to 
>> others. To the eyes of the world,  given domain, say example.com
>> has SRV records for SIP and XMPP. The fact that there is an
>> actual gateway handling the traffic and doing some translations
>> is a detail of that infrastructure. So a non-STOX server should
>> be able to communicate with a STOX server just fine.
> 
> +1
> 
> Peter
> 
> 

- -- 
Matt Ryan
Code Slinger  |  Jive Communications, Inc.
Jive.com  |  mryan@getjive.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTh0i5AAoJEPyFiw1u4O0cEKEIAIwOqkOX1Rv2OmYkPlaR1+iY
aX6I8FNVifLvLH8ejei0hSTZoPqLFIbuZwkrJCnNyBo2bV4xMFoL91nQnKNe4dFX
xbKzLEPuV++A2YswEA6kklpJOlxHvqJEaAaiixci4Z24ZYR1deyW0ZQzXGKvE8Kr
Fycvqyz/eGPEM+FuY4UQSRnqnjVVHXAGvUvl86C+XEqNdxY68EYBDSHf6VTxGczI
MdVRErTmgYgGB2vQvouALrq6DB6JccWEz8cVf1QAFkXwYe4yH/Z7Rz1l/dkgUXrb
5Mfn7MCIKFAFHNGJQPPNLp1wJziGZonMMYpaDC/dFiHVy+qRSD5dNLFajtgbzUE=
=fi5u
-----END PGP SIGNATURE-----