- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Thu, 22 Aug 2013 17:10:11 +0200
- To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>,"public-webrtc@w3.org" <public-webrtc@w3.org>
- Message-ID: <f685b85f-bb92-4475-828a-b9e3ef03e6af@email.android.com>
That seems like a compelling use case to me. It is an outcome you cannot arrive at otherwise. "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> wrote: >If in a browser to browser scenario the application does not want >bundling to take place (e.g. for QoS reasons) then somehow bundling >needs to be turned off either by the offerer or the answerer. This can >only currently be done by manipulating the SDP before calling >setLocalDescription/setRemoteDescription and hoping the browser does >the right thing. > >I think it would be much cleaner to have a constraint on >createOffer/createAnswer so that the SDP does not include the bundling >option when it is not wanted. > >Regards >Andy > > > >> -----Original Message----- >> From: Harald Alvestrand [mailto:harald@alvestrand.no] >> Sent: 22 August 2013 06:29 >> To: public-webrtc@w3.org >> Subject: Re: Transport related API need >> >> On 08/20/2013 06:46 PM, Hutton, Andrew wrote: >> > Hi Stefan, >> > >> > Sorry for the slow response it is holiday season. >> > >> > The use case is simply the case where the application does not want >> the offer to include bundling which could be for example in a case >> where interworking with anything that does not do bundling be it the >> legacy world or a conference server that does not bundle. This could >> also be because of QoS requirements etc. >> >> Andrew, >> >> do you have an use case in mind where *offering* bundling would be >> harmful? >> The normal SIP/SDP case is that non-understood extensions are >ignored, >> so you would only have a reason to turn off bundling if the other >> device >> will malfunction if you send the offer. >> >> > >> > It should I know be possible for the receiver of the offer to >ignore >> the bundle option and everything to work but I believe there should >be >> a clean API that can be used to tell the browser not to even attempt >> bundling without relying on the application to modify SDP. >> >> I'm not convinced that the case exists in the real world where >offering >> bundling is harmful. >> >> If we need it, I agree that it should be possible to just twist an >API >> knob. >> I'm just not finding the need compelling. >> >> (This is an useful case to consider; I think that if we call this one >> way or the other, it will make precedent for other items where SDP >> negotiation *should* result in things working OK, but people still >want >> to do SDP mangling of an offer). >> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Received on Thursday, 22 August 2013 15:13:52 UTC