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> Mon, 20 May 2013 09:36 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 D41AF21F9307 for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 02:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 Cvdc4BZXtXL5 for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 02:36:27 -0700 (PDT)
Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A463A21F9298 for <rtcweb@ietf.org>; Mon, 20 May 2013 02:36:26 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jk14so1767927bkc.31 for <rtcweb@ietf.org>; Mon, 20 May 2013 02:36:25 -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=NH8yjaDoejvEetkWUptyhZjYlxYB/xUL/yUbU0HS7lI=; b=DIHq89zd7uDBDS7DOWZvel1Gih1jdvo52O8iDqQiWY6jLGJL2NYatX0mQMnaMrUgd8 B992jCTIQPVtxWvKnycUU/9YjhF6pionZTik0R7Toe40iRWrZGkEVMgVigHp1x/mZxjd JrG69E6fmx+xRNzGcXgtZwxW8QjFeIVT7KnTgt5yJ593p5Dys36k5nhHTFT2we56uN1x wMN780IUUoP+rSmy6yjCRdDB1D/q1dKKoBdGuI+CCNoddYb3I8X7PwFz3xoALMIjZWzy WDs5LYHVzcIpxXdYqltx74bAGDu4dUiWQtDpJ9+0rLYP1gGMekcjvOZdpiPn8jXGLlK0 mHqA==
X-Received: by 10.205.115.196 with SMTP id ff4mr19129980bkc.111.1369042585142; Mon, 20 May 2013 02:36:25 -0700 (PDT)
Received: from camionet.local (77-85-165-231.btc-net.bg. [77.85.165.231]) by mx.google.com with ESMTPSA id v6sm5530440bko.3.2013.05.20.02.36.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 02:36:24 -0700 (PDT)
Message-ID: <5199EE93.9000904@jitsi.org>
Date: Mon, 20 May 2013 12:36:19 +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/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.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> <1447FA0C20ED5147A1AA0EF02890A64B1C2CCE9A@ESESSMB209.ericsson.se> <519531F6.1010201@jitsi.org> <1447FA0C20ED5147A1AA0EF02890A64B1C2CDEE8@ESESSMB209.ericsson.se>
In-Reply-To: <1447FA0C20ED5147A1AA0EF02890A64B1C2CDEE8@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmBstseO+YuN8lbWOw8o3Pw/w/ZVE62RLaa+d/+ue/FfUWh+T/jKuxn0LPOMEG0ldAvYtfo
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Mon, 20 May 2013 09:36:28 -0000

Hey Stefan,

On 19.05.13, 14:35, Stefan Håkansson LK wrote:
> I'm no expert, but how do you handle things like congestion management 
> with translators? IIUC the RMCAT group has decided to handle the simple 
> point-point case only. (I'm not trying to remove translators from the 
> topologies we cover - I just want to bring all the pieces to the table).

I believe 3551 recommends use of RTCP and monitoring packet loss.
Additional means can also be implemented over out-of-band signalling
between the translator and a controlling entity.

I already mentioned this in my response to Harald: note that my use of
the term RTP translator did not apply solely to the
"Topo-Trn-Translators" described in 5117. The problems (i.e. heavy
signalling constraints) apply to pretty much any entity that is not
mixing content and behaving like a complete single-stream B2BUA.

Emil

-- 
https://jitsi.org

v2.23.0 | Report a Bug | By Email