IETF Logo Mail Archive

Re: [Stox] core issues

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 23 August 2013 17:42 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 B007D21F9C32 for <stox@ietfa.amsl.com>; Fri, 23 Aug 2013 10:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.124
X-Spam-Level:
X-Spam-Status: No, score=0.124 tagged_above=-999 required=5 tests=[AWL=-0.309, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, 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 DUXmFuCXO7L9 for <stox@ietfa.amsl.com>; Fri, 23 Aug 2013 10:42:44 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB9B21F9C29 for <stox@ietf.org>; Fri, 23 Aug 2013 10:42:43 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta07.westchester.pa.mail.comcast.net with comcast id GCwL1m00A1ap0As57HijYf; Fri, 23 Aug 2013 17:42:43 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta22.westchester.pa.mail.comcast.net with comcast id GHii1m01M3ZTu2S3iHiin1; Fri, 23 Aug 2013 17:42:43 +0000
Message-ID: <52179F12.5040104@alum.mit.edu>
Date: Fri, 23 Aug 2013 13:42:42 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: stox@ietf.org
References: <E44893DD4E290745BB608EB23FDDB7620A07605C@008-AM1MPN1-042.mgdnok.nokia.com> <52125D9C.5080609@stpeter.im> <3816E434-747C-4E45-A713-393B4E1AAD01@edvina.net> <5213ED3D.2010709@stpeter.im> <5213F090.4000104@gmail.com> <521400CF.8020801@alum.mit.edu> <521469A0.80104@gmail.com> <52150EF5.5060401@alum.mit.edu> <D6EEBE80-183A-4921-A1CC-B7E52C9D9C24@ag-projects.com> <5216775B.6080709@alum.mit.edu> <FF6ACF04-873F-4DDF-AB7E-4F1A751D7629@ag-projects.com> <521797B1.7040900@stpeter.im>
In-Reply-To: <521797B1.7040900@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1377279763; bh=NbpDHUX3sY4ZZxA84MrCbeHUZ6LaL7xZA/UkrRlhc40=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=bZ2PHGcBYePy+nuTb2kCQJ/nU6NgglgmMu/dlIDcGamwyCAzxi2O+gUW6GwWcpHt2 5w4/Sxag7/5k2VAzGNAx3q3o2YilKeA2Pf2ghhXC3JeXrTByGtMYnaL9glOcumOAwB 8gMsy/pDtHx3APU3xGXv86jbSvt1C/UqYIkf1yDAvxO80B4rRQorXv+JScZg+hw3kb 7WqT6Hkh6Bx5kxgJGGPAWvr4m3tMqe+wBuZqvWFjdqYhL1uMkJEXTwabVBybmvQ1zF cYSFw1Au0T6mvZ86qxsqBFflfTi62RtKBtEw3Sr6kgLenqnmXxtNn+NTfXzVxSBCux 4qfbcCFbx7vOw==
Subject: Re: [Stox] core issues
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, 23 Aug 2013 17:42:54 -0000

WFM

On 8/23/13 1:11 PM, Peter Saint-Andre wrote:
> On 8/23/13 3:55 AM, Saúl Ibarra Corretgé wrote:
>>>>
>>>> I see the subject hasn't changed, so are we talking about the -core draft or the -media draft here? The early media situation is indeed tricky when RTP is being used, but if we are dealing with chat, there should be no problem in keeping a few TCP connections alive until one of the dialogs has been confirmed. Also, when chat is in use the GW effectively terminates the media.
>>>
>>> There isn't any way to have a signaling only GW for xmpp-msrp.
>>> So yes, you are right about that. Its only an issue for RTP media.
>>>
>>
>> Do, do you (or anyone) still think that any text on this regard is needed in the *core* document, or shall we just put that in the media one?
>
> I think this belongs in the -media document. Let's change the thread
> name accordingly. :-)
>
> Peter
>

v2.23.0 | Report a Bug | By Email