public-webrtc@w3.org from November 2013 by subject

[Bug 23832] New: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases

[Bug 23919] New: DataChannel.onerror callback needs an error argument specified.

[Bug 23920] New: TURN authentication failures should be surfaced as some event

[minutes] Nov 11-12 F2F

[MMUSIC] Should we put the SCTP max message size in the SDP?

ACTION-88: Remove '?' characters from all dictionaries

ACTION-95: Constraints usage in the WebRTC spec

addIceCandidate behavior

constraints vs attributes

DataChannel edits/questions from Dan

Date and time for WebRTC telconf

Doodle for WebRTC teleconf

Fwd: [rfc-dist] RFC 7064 on URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol

Fwd: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

Getting the MediaStream associated with a video element?

How to detect when TURN authentication failed?

In defense of AddStream

ISSUE-3: Should we refactor the generic guidance on error handling out of the spec

ISSUE-4: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases

No way to specify remote constraints?

RTC in Web workers

Screen sharing and application control

Should we put the SCTP max message size in the SDP?

stats for SCTP

Stats variables - some more input

TPAC Remote Participation.

Using tracks instead of streams

WebRTC spec error message review

Why does screen sharing require a browser extension?

Last message date: Saturday, 30 November 2013 04:57:25 UTC