- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Sun, 28 Oct 2012 07:29:17 -0700
- To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
- Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 28 October 2012 04:47, Hutton, Andrew <andrew.hutton@siemens-enterprise.com> wrote: > The constraint to indicate that the application only wants to receive video surely applies to the answer as much as it applies to the offer the problem is that the name and the text in the draft implies to that it only relates to the offer. I think that the question is whether it should be possible using constraints to reject incoming streams. That would provide the symmetry that we are looking for here. InboundAudio: true and InboundVideo: true as constraints would work, I should think. They could apply to offers (in that they would trigger the creation of an appropriate m= section. And in answers, they would shape the characteristics of the response: a=sendonly or m=audio 0. That's not perfectly symmetrical in the latter instance, you could always create the streams and use a=inactive, but that seems a little wasteful, especially if we aren't bundling. --Martin
Received on Sunday, 28 October 2012 14:29:46 UTC