IETF Logo Mail Archive

Re: [Stox] stox-presence-03: a couple of comments

Peter Saint-Andre <stpeter@stpeter.im> Fri, 06 September 2013 01:12 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 92C5421E808A for <stox@ietfa.amsl.com>; Thu, 5 Sep 2013 18:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.028
X-Spam-Level:
X-Spam-Status: No, score=-102.028 tagged_above=-999 required=5 tests=[AWL=-0.299, 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 lrofISUM8nyM for <stox@ietfa.amsl.com>; Thu, 5 Sep 2013 18:12:34 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 8EADD21E8093 for <stox@ietf.org>; Thu, 5 Sep 2013 18:12:32 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 26FC7415B2; Thu, 5 Sep 2013 19:16:41 -0600 (MDT)
Message-ID: <52292BFD.7070207@stpeter.im>
Date: Thu, 05 Sep 2013 19:12:29 -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: Markus.Isomaki@nokia.com
References: <E44893DD4E290745BB608EB23FDDB7620A08FEFE@008-AM1MPN1-041.mgdnok.nokia.com> <521BDB79.9080809@stpeter.im>
In-Reply-To: <521BDB79.9080809@stpeter.im>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: stox@ietf.org
Subject: Re: [Stox] stox-presence-03: a couple of comments
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: Fri, 06 Sep 2013 01:12:39 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/26/13 4:49 PM, Peter Saint-Andre wrote:
> On 8/26/13 6:34 AM, Markus.Isomaki@nokia.com wrote:
>> Hi,
> 
> Hi Markus, thanks for the feedback.
> 
>> I have a couple of comments on the presence-03 draft:
>> 
>> * Some asymmetry between XMPP-to-SIP (3.2) and SIP-to-XMPP (3.3) 
>> directions
>> 
>> - 3.2.1 explains the DNS operations an XMPP domain uses to
>> determine that the foreign domain does not support XMPP but
>> actually supports SIP/SIMPLE. Presumably something similar is
>> needed in the reverse direction, but this is not explained in
>> 3.3.1. - The case where the subscription is rejected is covered
>> in 3.3.1 but not in 3.2.1.
> 
> Good point. We'll add something about that.

Actually, I think draft-ietf-stox-core already covers that:

   When an XMPP service receives an XMPP stanza whose 'to' address
   specifies or includes a domain other than the domain of the XMPP
   service, it needs to determine whether the destination domain offers
   an XMPP service or a SIP service.  To do so, it performs one or more
   DNS SRV lookups [RFC2782] for "_xmpp-server" records as specified in
   [RFC6120].  If the response returns a hostname, the service can
   attempt XMPP communication.  If not, the service can attempt to
   locate a SIP service for that domain using the procedures specified
   in [RFC3263].

   Similarly, when a SIP service receives a SIP message whose Request-
   URI specifies or includes a domain other than the domain of the SIP
   service, it needs to determine whether the destination domain offers
   a SIP service or an XMPP service.  To do so, it uses the procedures
   specified in [RFC3263].  If that response returns a hostname, the
   service can attempt SIP communication.  If not, the service can
   perform one or more DNS SRV lookups [RFC2782] for "_xmpp-server"
   records as specified in [RFC6120].

IIRC, we planned to remove such text from all but the core document,
since it applies to presence, im, chat, groupchat, media, etc.

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKSv8AAoJEOoGpJErxa2phm0P/jdOQH+Zev5htJ4QJDA/U3bE
LUO0yN4yXUpfoMXUTzWbwCDPx8kX566zRyhK1uqiOylUVA3hljOfWMc1Fm5mj0RS
nFVUIV8E1sk8mWKvAjsctTuoCQ2Tlk9IfCVLnhP77XX7MoHY8bfU1v20UdwV8yGj
AU92Bf6bJ/+LFPaZTIS3mxZHCPTTa91pItF0yQF0suwDUtIPJtV1Cz77R6zyqRQG
39AdFNUv0FdZ73rS3oeEeZHCcCZctiWdfXr1CRG79h706cfF08Lp3Z8sVi++4Nbp
Yac6ypzkKmJRmaYVikV6lzkMYAg1muJ5SrBnSj54cRxz/2PYftuK3duvR3CaeCxk
qx2f45vv2QL0bpZVU2JoINvTZtPB1pfm8PcdDBCbQ0iMkVhRjfy7CJgFbKHlDckW
dhi5kKda2eBiWBcscKs+t33luUi8sKxMj+/1pjCL7gNM54oBKMY/n0XXupVEiikP
YmFqnBP2LDW3dRIzpY+VdYMQGgS//omdIDPjjEyWBIvepZKrXQpAqKlBHYqEJxaE
M0laUEvfkzfY1WOkUD7D1b1guiFHQ55i6BK/+KaHk7RibJbp5uqbvAhqY9OVUuqZ
Zt/unJHBl7ONqhlPasbop9nlVRwTGfczuDBBWfiHkJSgjy+wztOcfSuuqMRNEDA8
pijKmqW3wwEIQ3237F34
=idjv
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email