Note also that pre- and post-processing of media are not covered by this proposal, those concepts are in the domain of MediaStream (and post-processing is possible today through various methods). In fact, I think the primary novel features of this proposal are: - SessionDescriptions are true objects, instead of wrappers around SDP - Additional control over the ICE Agent However, no use cases have yet been outlined that require this functionality. On Mon, Aug 6, 2012 at 10:00 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>wrote: > > On Aug 6, 2012, at 1:27 PM, Rohit Puri wrote: > > > Based on our experiences at TenHands Inc. where we are trying to build a > RT video-centric collaboration service, the goal cited in MSFT proposal ( > http://html5labs.com/cu-rtc-web/cu-rtc-web.htm), namely: > > > > "Flexibility in its support of popular media formats and codecs as well > as openness to future innovation—A successful standard cannot be tied to > individual codecs, data formats or scenarios. They may soon be supplanted > by newer versions, which would make such a tightly coupled standard > obsolete just as quickly. The right approach is instead to to support > multiple media formats and to bring the bulk of the logic to the > application layer, enabling developers to innovate. " > > > > sounds like a great idea. > > and every proposal from any company or individual that I can recall being > sent to theses WGs has had exactly that property. So it is sort of > disappointing to see Microsoft present it as if their proposal was somehow > different in this regards. > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
Received on Monday, 6 August 2012 20:20:35 UTC