Re: [rtcweb] A problem with both A and B

Emil Ivov <emcho@jitsi.org> Tue, 21 May 2013 07:45 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 6E37021F90F1 for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 00:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 UF01m9NuIUl9 for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 00:45:27 -0700 (PDT)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 562F821F8519 for <rtcweb@ietf.org>; Tue, 21 May 2013 00:45:27 -0700 (PDT)
Received: by mail-bk0-f53.google.com with SMTP id mx1so154128bkb.40 for <rtcweb@ietf.org>; Tue, 21 May 2013 00:45:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=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=aJKIZFwg5XcgxMssMNSbtM81xMgakL5mqjy+4yZHjzs=; b=kludOvF+dRJ9N9+OqfaLA14JXcTBYE2obreTQai29HR/bEqJZccl2egf+bYq9z8wLf zuBwDmOcU2vUjBwTEqHiJK+Oj7FboBkQjUgUjh5CxDIE9GMA+uvzX7MgLJBUQE5xoaVZ iFqWcaEORFe1o4c+jQ9rzVVPYy6scrG/wf0h0JVKu/0WrKLvxWFS5xo56DW1ypPc2Zrv 0kAOvtuIQZecQV8nxxxEG3g6tg/f8po/bVdbfqQoLrxpOpaZAYUuC0s+zFHfFjhi4iNr X1CgegxsZDCKoJBkaRVvwwnAlSB1NCmbojibI+zeCjmrApDyH4wo8YjjrbTDP/FU1Klg eYdQ==
X-Received: by 10.205.105.196 with SMTP id dr4mr356194bkc.45.1369122326246; Tue, 21 May 2013 00:45:26 -0700 (PDT)
Received: from [192.168.1.119] ([88.203.232.9]) by mx.google.com with ESMTPSA id iy11sm219506bkb.11.2013.05.21.00.45.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 00:45:25 -0700 (PDT)
Message-ID: <519B2613.9090707@jitsi.org>
Date: Tue, 21 May 2013 10:45:23 +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: Christer Holmberg <christer.holmberg@ericsson.com>
References: <BLU403-EAS40305B2D015B786CC67EB9293AC0@phx.gbl> <CABkgnnXX3zoeKqjFxjsfMgaGGRM0JzymaeWfA13LEjUZ4tGF9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C373EF0@ESESSMB209.ericsson.se> <519A4C9A.6020501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C374F13@ESESSMB209.ericsson.se> <519B22E8.9060709@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C375034@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C375034@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQkvnGKdp5sy4Izjyat32vzTLokGrGBOu6G/PyU5OCzZuSJyWeCWQKoSUtO9Vza660QXnmGs
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Tue, 21 May 2013 07:45:32 -0000

On 21.05.13, 10:38, Christer Holmberg wrote:
> Hi,
> 
>>> If adding a new stream means adding a new SSRC, within an
>>> existing m-, then it is also an SDP O/A issue - bundle or no
>>> bundle.
>> 
>> Why is that?
> 
> Because, even WITHOUT bundle, you have to answer whether adding a new
> SSRC (or, whatever mechanism we use to identify a stream) within an
> existing m- line requires an SDP O/A transaction or not.

OK, I guess I took your statement to mean that adding and removing SSRCs
to m= lines is a matter that cannot be handled without SDP O/A which I
think it isn't (and which is what this thread started with).

I obviously agree that it is not a bundle-specific issue.

Emil

-- 
https://jitsi.org