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

Matt Ryan <mryan@getjive.com> Tue, 20 May 2014 02:36 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 898DF1A047A for <stox@ietfa.amsl.com>; Mon, 19 May 2014 19:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KeYhgvkS5CSd for <stox@ietfa.amsl.com>; Mon, 19 May 2014 19:36:19 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B21C91A0469 for <stox@ietf.org>; Mon, 19 May 2014 19:36:19 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id lx4so3224927iec.32 for <stox@ietf.org>; Mon, 19 May 2014 19:36:19 -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 :subject:content-type:content-transfer-encoding; bh=/HwCoZnoG+h9gpIGY0e+4XzS9ZybCF2BMm0O5gWSVLU=; b=TrEh8JmluNlAzxNEeB90vSMwjTEB7JzaMhPC6ewblVcE6pGNWl0RRpgK5F4NxhHhqB IDx+QyPkmlgfVHGbWTVrF0eECj00s87dnddu4/ZG3IRvX9jKTXqV8RRaWEiza/qkF1Ds yTMJkL8Al5lZM/efN90/j9lnVcNiPEzK7rrOo=
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:subject:content-type:content-transfer-encoding; bh=/HwCoZnoG+h9gpIGY0e+4XzS9ZybCF2BMm0O5gWSVLU=; b=bBWxzPd0woR//vhl8xPB5XPOuSMi2F9ud2mVaVtOO5oloaHKnGg+Jh049KFZ3+mQZi rCAqdWZb3trJbZlpunKjGlCLjuzt/76JvvSvZCyrbWNQ7qET9w4ZswsS3xUj7veq2niu raXsDwjfM7Bb3ePiWbOjRqfW1iDzkPdmeHk10xXY7yX1rmNBOryEDoRnnO5TOG2Q5ycp zp6I+s2XXkUrh2F3huS9XbMxzL0yBDsfUKRHHtIeuh21CEiAcyJQsEXeJadKRDNly3i0 097hDBWfICL8kX3SaWL0PpqJCB1EyqQZwjxj7kniovjvwNx6s2JarMDEG3cZcJNvzfb8 FQWw==
X-Gm-Message-State: ALoCoQlDS6hvAwgT2BSw3Lr7tipcII0d2srbVVsknlL20kLyc/fAKY2OO2NU2FDIXkCflOowVBc+
X-Received: by with SMTP id u6mr36473459icy.41.1400553378961; Mon, 19 May 2014 19:36:18 -0700 (PDT)
Received: from [] (32.251.sfcn.org. []) by mx.google.com with ESMTPSA id rt10sm25502102igb.15.2014. for <stox@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 May 2014 19:36:18 -0700 (PDT)
Message-ID: <537ABFA1.2080606@getjive.com>
Date: Mon, 19 May 2014 20:36:17 -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.4.0
MIME-Version: 1.0
To: stox@ietf.org
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/JEDs2wqL8tlxkYEsgK1kCNKKwsU
Subject: [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: Tue, 20 May 2014 02:36:21 -0000

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.

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