Re: [rtcweb] A problem with both A and B
Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 20 May 2013 16:47 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7AE21F967D for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 09:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.267
X-Spam-Level:
X-Spam-Status: No, score=0.267 tagged_above=-999 required=5 tests=[AWL=-0.496, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_17=0.6, J_CHICKENPOX_55=0.6, RDNS_NONE=0.1]
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 ORb5hlFpyouF for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 09:46:54 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2EB21F95FC for <rtcweb@ietf.org>; Mon, 20 May 2013 09:46:54 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by QMTA11.westchester.pa.mail.comcast.net with comcast id eB6o1l0031YDfWL5BGmt2h; Mon, 20 May 2013 16:46:53 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id eGmt1l00d3ZTu2S3gGmtwm; Mon, 20 May 2013 16:46:53 +0000
Message-ID: <519A537C.30908@alum.mit.edu>
Date: Mon, 20 May 2013 12:46:52 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <51965506.7050008@jitsi.org> <CAMvTgccSpdAa2F26eeRg61mLQg+ThWfHNU5xXHwz0Ap7bePxBQ@mail.gmail.com>
In-Reply-To: <CAMvTgccSpdAa2F26eeRg61mLQg+ThWfHNU5xXHwz0Ap7bePxBQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369068413; bh=2RzN0sfydmyYEoqSof1OWTVK2RqOr2sNehjygKqDcdI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Pz8rpl62ZtfMtJ2dCUfuQHf3Mjkd3O7Y4cMh0kV8ormQFywgQnzO04wKr0H4Vp8Nq PeICnCdfDkZSqyvbsJj7J2ND2K0fDrlbOQmRlDRg3H+vh4jlDQzkvTzMlCdUtuZhiK I1/8D1PHOuSQqLw1vNCMJc3LbJllxx6MpwgYZvPiCjoBQifhOuHUv30eKLHYDpzXhS KCRpCQvmm0ltuzGHY9lwtXzl+uAst47VgORXRHok5XAW528eh64G5IGtChuqBQYA7G OiY1xPhdr2SfkxfowArwSqU9SKZ30Q8WuwgwXOQ3ZYAf5dgQp4KuoGgNNwEDS+uFqj npR5Rn3G4vAzQ==
Subject: Re: [rtcweb] A problem with both A and B
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 16:47:08 -0000
On 5/20/13 4:53 AM, Kevin Dempsey wrote: > I would say that at present only the sending application knows what a > stream is for. The receiving side needs to determine the purpose by > matching the RTP packets to the signalling the applications have done. ISTM that the legacy cases have depended upon doing this in a simplistic way. E.g., the app only supports one audio media stream to be played out over one audio device. So it refuses anything other than a single audio m-line and then maps all the audio packets it receives, regardless of SSRC, to that one device. So it needs minimal signaling. This has gradually evolved to slightly more complex cases, such as audio+video using similar logic. The a=content attribute was added to cover simple cases of multiple media of the same type, but still assuming a separate m-line for each device. All of this assumes that there is a very small range of fundamentally different applications, so signaling is not used much to distinguish them. But clearly this is beginning to break down. ISTM the current plan is to require that the two ends of a session be running the same logical application, and that they then define how to sort out the use of multiple media in an application-specific way. This is what both CLUE and RTCWEB seem to be doing. In the CLUE case the assumption is that initial SIP session setup verifies if the assumption is true, and then defines different actions if it is or isn't. In the case of RTCWEB, I guess the assumption is that it is probably a single web server application controlling both ends. But in cases where that is not true - gatewaying to the sip world - I guess this is left for the web server to figure out. I don't know how this is going to work when a Google+ with no Facebook account wants to interact with a Facebook user that has no Google+ account. ISTM in that case you need separate but equivalent web applications on both providers, and somehow they still need to have a consistent signaling mechanism between them. Thanks, Paul
- [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Dale R. Worley
- Re: [rtcweb] A problem with both A and B Bernard Aboba
- Re: [rtcweb] A problem with both A and B Martin Thomson
- Re: [rtcweb] A problem with both A and B Roni Even
- Re: [rtcweb] A problem with both A and B Stefan Håkansson LK
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Sergio Garcia Murillo
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Paul Kyzivat
- Re: [rtcweb] A problem with both A and B Paul Kyzivat
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Paul Kyzivat
- Re: [rtcweb] A problem with both A and B Martin Thomson
- Re: [rtcweb] A problem with both A and B Stefan Håkansson LK
- Re: [rtcweb] A problem with both A and B Paul Kyzivat
- Re: [rtcweb] A problem with both A and B Paul Kyzivat
- Re: [rtcweb] A problem with both A and B Stefan Håkansson LK
- Re: [rtcweb] A problem with both A and B Suhas Nandakumar
- Re: [rtcweb] A problem with both A and B Kevin Dempsey
- Re: [rtcweb] A problem with both A and B Suhas Nandakumar
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Sergio Garcia Murillo
- Re: [rtcweb] A problem with both A and B Emil Ivov
- Re: [rtcweb] A problem with both A and B Christer Holmberg
- Re: [rtcweb] A problem with both A and B Cullen Jennings (fluffy)
- Re: [rtcweb] A problem with both A and B Richard Barnes