Re: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking

Philipp Hancke <fippo@goodadvice.pages.de> Thu, 08 August 2013 18:31 UTC

Return-Path: <fippo@goodadvice.pages.de>
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 0E05021F9DC7 for <stox@ietfa.amsl.com>; Thu, 8 Aug 2013 11:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.256
X-Spam-Level:
X-Spam-Status: No, score=-1.256 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 AvbaNtd20bNY for <stox@ietfa.amsl.com>; Thu, 8 Aug 2013 11:31:27 -0700 (PDT)
Received: from lo.psyced.org (lost.IN.psyced.org [188.40.42.221]) by ietfa.amsl.com (Postfix) with ESMTP id A10A021F9B8D for <stox@ietf.org>; Thu, 8 Aug 2013 11:31:19 -0700 (PDT)
Received: from [192.168.2.100] (p54972629.dip0.t-ipconnect.de [84.151.38.41]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id r78IVBv9016286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 20:31:15 +0200
Message-ID: <5203E3EB.8080404@goodadvice.pages.de>
Date: Thu, 08 Aug 2013 20:31:07 +0200
From: Philipp Hancke <fippo@goodadvice.pages.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
References: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se> <8C703C0F-181C-4E36-8A59-727B45C0A1B5@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C418FAC@ESESSMB209.ericsson.se> <B7CBEFB1-2A23-4337-90DD-D8157123A1AD@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C41C17E@ESESSMB209.ericsson.se> <6E2B9398-C9C5-47F1-AC5D-2C7E23AB6E69@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C41C208@ESESSMB209.ericsson.se> <51FEA128.2060806@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C41CBAC@ESESSMB209.ericsson.se> <51FF3E7B.9000208@goodadvice.pages.de> <44B7F35B-056E-450D-B664-EE3ADAB4CA81@ag-projects.com>
In-Reply-To: <44B7F35B-056E-450D-B664-EE3ADAB4CA81@ag-projects.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: stox@ietf.org
Subject: Re: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking
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: Thu, 08 Aug 2013 18:31:32 -0000

Am 08.08.2013 00:27, schrieb Saúl Ibarra Corretgé:
>
> On Aug 5, 2013, at 7:56 AM, Philipp Hancke wrote:
>
>> Am 05.08.2013 07:12, schrieb Christer Holmberg:
>>> Hi,
>>>
>>>> The gateway would care to translate the final response. Getting more then one 180 is not causing any harm nor does those need to be translated into different events on XMPP side.
>>>
>>> If that's the case, then you should have to problem :) I would suggest to have some text about that, though.
>>>
>>> And, I assume that means that possible early media from the SIP side won't be forwarded into the XMPP network either, or?
>>
>> http://xmpp.org/extensions/xep-0269.html has some suggestions on how to do early media. It's not entirely clear to me if the details are correct (e.g. I wouldn't use a raw-udp transport when the initiator only indicated support for ice-udp) but the general plan seems ok.
>
> Can we rely on it given the fact that is deferred?

Well, it's deferred because of inactivity, i.e. nobody bothered to 
update it or push it to draft.
yate might have an implementation...

> Are there any plans to change stuff in there, in "Jingle 2.0"?

Not that I know of.