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

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 28 May 2014 12:37 UTC

Return-Path: <saul@ag-projects.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 CF0B01A00EA for <stox@ietfa.amsl.com>; Wed, 28 May 2014 05:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level:
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3] autolearn=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 x2nStxpJakZ1 for <stox@ietfa.amsl.com>; Wed, 28 May 2014 05:37:42 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) by ietfa.amsl.com (Postfix) with ESMTP id AEEA71A0064 for <stox@ietf.org>; Wed, 28 May 2014 05:37:42 -0700 (PDT)
Received: from imac.saghul.lan (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id E547614AC001; Wed, 28 May 2014 14:37:37 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
In-Reply-To: <537ABFA1.2080606@getjive.com>
Date: Wed, 28 May 2014 14:37:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDAE759A-8174-46E6-8610-A37E554AB3FD@ag-projects.com>
References: <537ABFA1.2080606@getjive.com>
To: Matt Ryan <mryan@getjive.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/q-APs80A3Uroxq_EUhCtt8rSn2g
Cc: stox@ietf.org
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: Wed, 28 May 2014 12:37:43 -0000

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.


Regards,

--
Saúl Ibarra Corretgé
AG Projects