IETF Logo Mail Archive

Re: [rtcweb] Why requiring pre-announcement of SSRCs is a problem for conferencing ( Was: New Version Notification for draft-uberti-rtcweb-plan-00.txt )

Emil Ivov <emcho@jitsi.org> Wed, 15 May 2013 23:41 UTC

Return-Path: <emil@sip-communicator.org>
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 A26EE11E80D7 for <rtcweb@ietfa.amsl.com>; Wed, 15 May 2013 16:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level:
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599]
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 wYqm3qPau6bn for <rtcweb@ietfa.amsl.com>; Wed, 15 May 2013 16:41:28 -0700 (PDT)
Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BFAAA11E80D3 for <rtcweb@ietf.org>; Wed, 15 May 2013 16:41:27 -0700 (PDT)
Received: by mail-ea0-f174.google.com with SMTP id z7so1358596eaf.5 for <rtcweb@ietf.org>; Wed, 15 May 2013 16:41:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=AMaMDu1vbf79uAIyAVYrDD/zQDdiFRB2IrInBRmiOZw=; b=E55MgZ4FfK9FFk0sG4qTzCWnsJpn27/VpqQewGbTRxzuRyd7gIOgBpYW45UGfN1lGF nQ8pSdVXi3be59GVd4ZwIOAk0h4QoT+sTyrsFxfsZx7UVfESa/7lLhgaRVpOnwH1J71p LB9QpcX+oCoj9KcrdZVww2NkPZ6PmwUHHR82FQyojx9bJyCjOa+5Wkp4HawowQpyAxBb rpgMvxb1Wng4fYeNpqFOqPvwbOmKRBJQLjpMAQphrrPBVANzNrQw7Tq7NwFV41lrKAH7 xIziOFiIFTfw5pJvmxnmlihP53p7UPLXsFv1yxZGA+4Po8H6VDxBUawX3Svof2VXzMiY VE3A==
X-Received: by 10.15.108.6 with SMTP id cc6mr48628869eeb.28.1368661286527; Wed, 15 May 2013 16:41:26 -0700 (PDT)
Received: from [10.1.1.28] (damencho.com. [78.90.89.119]) by mx.google.com with ESMTPSA id bp51sm6995097eeb.5.2013.05.15.16.41.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 May 2013 16:41:25 -0700 (PDT)
Message-ID: <51941D24.9090107@jitsi.org>
Date: Thu, 16 May 2013 02:41:24 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <20130503054601.4639.64651.idtracker@ietfa.amsl.com>, <CALe60zAi_Lx3QFCbBQ5aPNkgorJAff0E79jkpbQX1Qt3wf2bzg@mail.gmail.com>, <CAOJ7v-1Wk6u7XiYrNVmoqr5Jisu2WRvZpte7hQTOiP8YHUc6hg@mail.gmail.com>, <008701ce4b21$a0997aa0$e1cc6fe0$@gmail.com>, <BLU169-W108D56DF61B85814543873C93BA0@phx.gbl>, <518AAAF2.5000207@alum.mit.edu>, <CA+9kkMBw4+kXAv6qLCcmGLwMxAqR6P-Tk8dm-ardv_jihHx0Hw@mail.gmail.com>, <9E563BDA-C336-4FB8-B11A-A2DC40C672C1@iii.ca>, <CA+9kkMC-NnF+VugBOZNhY4-Cz1tqJA44WSF9dg45g4GCWxkh-g@mail.gmail.com>, <518D6C76.5060606@alum.mit.edu>, <CAHBDyN6xYor-XWnLEkufoQPYrDc+KurrM0m3HBTqLXqNkPtDkQ@mail.gmail.com>, <BLU169-W82D3FCC3246D6D878FA44E93A00@phx.gbl>, <5191F948.3040402@ericsson.com> <51920280.3080308@jitsi.org>, <519223A0.1040908@ericsson.com> <5192947F.90206@jitsi.org>, <CAOJ7v-0+m+gFqahAJ-eL8T=hirq9Hz8hHuoJB1fjpGG5Cu+9zw@mail.gmail.com>, <5193DB82.2030702@jitsi.org> <BLU169-W123BD628EA6BF951658F08093A20@phx.gbl>
In-Reply-To: <BLU169-W123BD628EA6BF951658F08093A20@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQlm8YuvNDlfBrWgu4xoibilsDNGCzd08eSBphmsQcU+p5QE4GiX2rNKcB7rtXLMcuf9/Pje
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Roni Even <even.roni@huawei.com>
Subject: Re: [rtcweb] Why requiring pre-announcement of SSRCs is a problem for conferencing ( Was: New Version Notification for draft-uberti-rtcweb-plan-00.txt )
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: Wed, 15 May 2013 23:41:28 -0000

On 15.05.13, 22:55, Bernard Aboba wrote:
>> Obviously, for this to work, the WebRTC APIs would need to provide means
>> of obtaining and setting this information from/to the browser.
>> Applications need to be able to start and stop specific streams, relate
>> them as layers or FEC repair flows.
> 
> [BA] I hope that you're not talking about application-specific RTCP
> packets; I would prefer to avoid that if possible.

Not at all. In this particular case I was referring to the possibility
of using application-specific signalling that two browsers (or a browser
and some other app) can use to signal such things. Such signalling could
go through websockets, clue data channels or e-mail for all it matters:
it would be up to the application.

-- 
https://jitsi.org

v2.23.0 | Report a Bug | By Email