IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 21 May 2013 07:20 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 C710C21F95EB for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 00:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.111
X-Spam-Level:
X-Spam-Status: No, score=-6.111 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 Gnv-NaGWYq0o for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 00:20:21 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0113521F9728 for <rtcweb@ietf.org>; Tue, 21 May 2013 00:20:20 -0700 (PDT)
X-AuditID: c1b4fb30-b7f8a6d000001a2d-66-519b2033633d
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 8C.BA.06701.3302B915; Tue, 21 May 2013 09:20:19 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0328.009; Tue, 21 May 2013 09:20:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] A problem with both A and B
Thread-Index: AQHOUzwnCrd1S7QwyEqM9DOrRHv1xJkJuD4AgAPsAUCAAH7PAIABHI7Q
Date: Tue, 21 May 2013 07:20:18 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C374F13@ESESSMB209.ericsson.se>
References: <BLU403-EAS40305B2D015B786CC67EB9293AC0@phx.gbl> <CABkgnnXX3zoeKqjFxjsfMgaGGRM0JzymaeWfA13LEjUZ4tGF9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C373EF0@ESESSMB209.ericsson.se> <519A4C9A.6020501@alum.mit.edu>
In-Reply-To: <519A4C9A.6020501@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyM+Jvra6xwuxAg6er9C1WbDjAarH2Xzu7 A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVxckNNwVXhiuef1zI3MD7l72Lk5JAQMJHY NHMFI4QtJnHh3nq2LkYuDiGBw4wSq+9vY4FwljBKNP16xNTFyMHBJmAh0f1PG6RBRMBXovfy ObBmYQFDid8XTjFDxI0krq3fzwJhu0n8WLwQrIZFQFWi4+spMJsXqHfqt9NQ818ySly4cJIN ZD6ngI5E+2F5kBpGoIO+n1rDBGIzC4hL3HoynwniUAGJJXvOM0PYohIvH/9jBWmVEFCUWN4v B1GuI7Fg9yc2CFtbYtnC18wQawUlTs58wjKBUXQWkqmzkLTMQtIyC0nLAkaWVYzsuYmZOenl 5psYgXFwcMtvgx2Mm+6LHWKU5mBREuft054aKCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoEx 13rN/cdht2dkv7F+NU3yxF+PA6meiluv1+cK/HrdaZQr+rY/59v6xZ7ZK/vdKxivSrxr3LH5 HX/dtxvR0fwrE8pm/3jgXG+uIfJ33qH9h578m/+0UXKaxWU5n7MeV+Sml+kv/75pK//zzX8v PDbxSi7iNr746prlFFXWh3XRlrd3PLO6bhjLqcRSnJFoqMVcVJwIAPRU8fFRAgAA
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:20:27 -0000

Hi,

>> I don't think it's a BUNDLE issue whether adding/removing of streams require an O/A exchange or not. It's an SDP, and SDP O/A, issue.
>>
>> BUNDLE is about sharing a 5-tuple.
>
> I don't agree.
>
> RTP is already able to support multiple RTP streams sharing an RTP session (and 5-tuple).
>
> What BUNDLE is about is describing that in SDP.
> And that includes how SDP O/A works.

Multiple RTP streams can already share an RTP session today, using multiple SSRCs per m- line :)

If adding a new stream means adding a new m- line, then an SDP O/A is obviously needed - bundle or no bundle.

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.

Regards,

Christer



> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On 
> Behalf Of Martin Thomson
> Sent: 17. toukokuuta 2013 23:50
> To: Bernard Aboba
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] A problem with both A and B
>
>> "Dale R. Worley" <worley@ariadne.com> wrote:
>>     DES F11  It must be possible to add and remove one way video flows
>>        within the bundle without requiring an additional offer/answer
>>        cycle.
>
> I'm not sure why this speaks specifically about video...
>
> On 17 May 2013 13:21, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
>> It is important. In fact, I would argue it is critical for congestion control (e.g. removal of simulcast or layered streams by the sender should not require an O/A exchange).
>
> This is different I think.  Responding to congestion only requires 
> that it be possible to stop sending a given stream.  (Or maybe crank 
> down resolution or frame rate.)
>
> This item talks about addition.  That's an entirely different proposition.  As long as we assume constraints (you don't need to re-ICE a new transport for the stream, you don't use new packet types and codec profiles), this could be possible.  But to get WebRTC to support this requires API changes.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email