IETF Logo Mail Archive

Re: [Stox] core issues

Daniel-Constantin Mierla <miconda@gmail.com> Tue, 20 August 2013 22:41 UTC

Return-Path: <miconda@gmail.com>
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 81CA611E82FC for <stox@ietfa.amsl.com>; Tue, 20 Aug 2013 15:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.729
X-Spam-Level:
X-Spam-Status: No, score=-1.729 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SARE_MLH_Stock1=0.87]
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 KZVMIvUgNTx5 for <stox@ietfa.amsl.com>; Tue, 20 Aug 2013 15:41:24 -0700 (PDT)
Received: from mail-ee0-x22f.google.com (mail-ee0-x22f.google.com [IPv6:2a00:1450:4013:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8B67811E82F5 for <stox@ietf.org>; Tue, 20 Aug 2013 15:41:23 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id d49so471399eek.20 for <stox@ietf.org>; Tue, 20 Aug 2013 15:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nKBEE/Nu716ESYOPRp8msgehwFQeU4ITOZgAa9zUxls=; b=pz80W94dbuezDQDta/EUyQ0gsHlWri6+euwD0kew7Lk5VMZ2R71BxOJnnu8FK6YxAH k01XWSTxdR6hCV72DrOZW7QO3Q9voaKU69cgEZ8On9vGA7u0VAGoH1GyIMTwks4lTItD B1DJX72n3zcb8olp2kmY+QcPoBLO03D7FCjSrZ7RuUF80IQs23SfRHgb1X/ev7T69USq +fHizrmaawgVnKWVyKGf0qPMPX1NEF/zWdcNX8yAje1DA5kdDyQwdnUAvC6tI7kqs6YQ EJlte2YxJ7UQfguI5usA+AjYxRr8z5n6MmoURPcjH36s/zAAgmXCtNcO7neHvlZfpTDl qEMQ==
X-Received: by 10.15.45.8 with SMTP id a8mr5011519eew.1.1377038482697; Tue, 20 Aug 2013 15:41:22 -0700 (PDT)
Received: from [127.0.0.1] (ns.asipto.com. [213.133.111.169]) by mx.google.com with ESMTPSA id f49sm5260742eec.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 20 Aug 2013 15:41:21 -0700 (PDT)
Message-ID: <5213F090.4000104@gmail.com>
Date: Wed, 21 Aug 2013 00:41:20 +0200
From: Daniel-Constantin Mierla <miconda@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>, "Olle E. Johansson" <oej@edvina.net>
References: <E44893DD4E290745BB608EB23FDDB7620A07605C@008-AM1MPN1-042.mgdnok.nokia.com> <52125D9C.5080609@stpeter.im> <3816E434-747C-4E45-A713-393B4E1AAD01@edvina.net> <5213ED3D.2010709@stpeter.im>
In-Reply-To: <5213ED3D.2010709@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: stox@ietf.org, Markus.Isomaki@nokia.com
Subject: Re: [Stox] core issues
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: miconda@gmail.com
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 Aug 2013 22:41:24 -0000

On 8/21/13 12:27 AM, Peter Saint-Andre wrote:
> On 8/20/13 12:32 AM, Olle E. Johansson wrote:
>> 19 aug 2013 kl. 20:02 skrev Peter Saint-Andre <stpeter@stpeter.im>:
>>
>>> On 8/14/13 1:19 PM, Markus.Isomaki@nokia.com wrote:
>>>
>>>> * Core
>>>>
>>>> - Issue: Should something general about forking be defined here
>>>> or is it purely a -media issue?
>>> I think this is best left for the stox-media spec.
>> Do remember to handle the case where one sip INVITE can get multiple
>> 200 OK. It's a corner case, but it does happen. And it's signalling.
> That sounds like fun.
This should be caught by the gateway, handled locally, like any SIP 
endpoint UA (and how is happening for PSTN gateways). Only one 200ok 
should be propagated to xmpp/jingle side. Which one? A matter of the 
implementation, most I have seen they go with the first response 
received, for the others they send ACK followed quickly by BYE (I mean, 
the good SIP UA implementations, some just crash in such cases :-) ).
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

v2.23.0 | Report a Bug | By Email