search

rtcweb-wg / rtcweb-transport

draft-ietf-rtcweb-transport
2 stars 2 forks source link

Note non-support for marking streams as interactive #19

Closed alvestrand closed 7 years ago

alvestrand commented 8 years ago

From discussion with DSCP folks:

Subject: RE: WebRTC Transports draft - proposed "interactive" changes

Add a new paragraph:

All media flows in WebRTC are assumed to be interactive [RFC4594] [G.1010]; there is no browser API support for non-interactive media, aside from sending non-interactive media content via the data channel [W3C.WD-webrtc-20120209].

Actually there is a way to generate it, but it's convoluted (pipe the media from file to a hidden

That'll be fine - please upload revised draft.

alvestrand commented 8 years ago

after

the following existing text:

For media, a "media flow", which can be an "audio flow" or a "video flow", is what [RFC7656] calls a "media source", which results in a "source RTP stream" and one or more "redundancy RTP streams". This specification does not describe prioritization between the RTP streams that come from a single "media source".

alvestrand commented 8 years ago

Discussion people: Cc: draft-ietf-tsvwg-rtcweb-qos@ietf.org; tsvwg-chairs@ietf.org; rtcweb-chairs@ietf.org; spencerdawkins.ietf@gmail.com; Black, David

alvestrand commented 8 years ago

I chose to integrate this minus the G.1010 reference, since I did not know how to get that reference in using XML2RFC markup, and the reference to 4594 already covers it.

alvestrand commented 7 years ago

Fixed in #20 (version -14)