from June 2013 by subject

[Bug 18485] Change DTMF API to be on PeerConnection

[Bug 20794] i want to connect p2p with html5

[Bug 20819] no priority API

[Bug 20820] congestion control of data and audio/video

[Bug 22347] New: RTCIceServer should have multiple URLs

[Bug 22441] New: Bug in section 8.1.2 Requesting Assertions

[Bug 22442] New: Bug in section 8.1.3 Verifying Assertions

Allowing RTCIceServer to contain multiple URLs

Alternative to the offer/answer mechanism

Anycast (Re: Allowing RTCIceServer to contain multiple URLs)

API design

Audio and Opus configurability for speed and quality (at the expense of bandwidth)

CfC: publish FPWD of "MediaStream Image Capture"; deadline June 30

Conclusion of RTCIceServer multiple-URI thread

Details Futures teleconf

Documents in scope for Futures discussion

Draft text for identity-bound streams

Future of Futures in Chrome

Futures in WebRTC

Fwd: Alternative to the offer/answer mechanism

How to know if a given track or media stream is being transmitted

Is DataChannel label unique?

Mandatory vs optional codecs

New editor's draft (v20130603)

Operations in invalid states: Exceptions don't make sense.

Our simple PeerConnection example with Futures/Promises

quibble on terminology

quibbles about the spec

Recap from WebRTC World

SDP wrapper? Object-oriented API?

Security of cross-origin audio

Signaling without a server

Simultaneous Peer Connections

Teleco Integrators vs Web Developers vs Browser Implementers

VS: SDP wrapper? Object-oriented API?

Last message date: Saturday, 29 June 2013 07:16:14 UTC