public-webrtc@w3.org from June 2013 by author

Adam Bergkvist

• Re: Recap from WebRTC World (Friday, 28 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Thursday, 27 June)
• Re: Is DataChannel label unique? (Wednesday, 26 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 26 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 25 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Thursday, 20 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Thursday, 20 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Thursday, 20 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 19 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 19 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 18 June)
• Re: SDP wrapper? Object-oriented API? (Monday, 17 June)
• Re: How to know if a given track or media stream is being transmitted (Monday, 17 June)
• Re: New editor's draft (v20130603) (Friday, 14 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Friday, 14 June)
• Re: New editor's draft (v20130603) (Friday, 14 June)
• Re: quibbles about the spec (Thursday, 13 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Thursday, 13 June)
• Re: Our simple PeerConnection example with Futures/Promises (Monday, 10 June)
• Re: Our simple PeerConnection example with Futures/Promises (Monday, 10 June)
• Re: quibbles about the spec (Monday, 10 June)
• Re: Our simple PeerConnection example with Futures/Promises (Monday, 10 June)
• Our simple PeerConnection example with Futures/Promises (Thursday, 6 June)
• Re: New editor's draft (v20130603) (Wednesday, 5 June)
• Re: New editor's draft (v20130603) (Wednesday, 5 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 5 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 5 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 4 June)
• New editor's draft (v20130603) (Monday, 3 June)

Adam Roach

• Re: API design (Saturday, 29 June)
• Re: API design (Friday, 28 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Signaling without a server (Sunday, 9 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 4 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)

Alexandre GOUAILLARD

• Re: Recap from WebRTC World (Thursday, 27 June)

Alexey Aylarov

• Re: Mandatory vs optional codecs (Thursday, 27 June)

Anne van Kesteren

• Re: Futures in WebRTC (Tuesday, 4 June)

bugzilla@jessica.w3.org

• [Bug 22442] New: Bug in section 8.1.3 Verifying Assertions (Tuesday, 25 June)
• [Bug 22441] New: Bug in section 8.1.2 Requesting Assertions (Tuesday, 25 June)
• [Bug 20819] no priority API (Friday, 21 June)
• [Bug 20819] no priority API (Friday, 21 June)
• [Bug 20820] congestion control of data and audio/video (Thursday, 20 June)
• [Bug 20820] congestion control of data and audio/video (Wednesday, 19 June)
• [Bug 20819] no priority API (Wednesday, 19 June)
• [Bug 22347] New: RTCIceServer should have multiple URLs (Thursday, 13 June)
• [Bug 18485] Change DTMF API to be on PeerConnection (Thursday, 13 June)
• [Bug 20794] i want to connect p2p with html5 (Thursday, 13 June)

Christer Holmberg

• VS: SDP wrapper? Object-oriented API? (Wednesday, 19 June)

cowwoc

• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Saturday, 29 June)
• Re: API design (Friday, 28 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Wednesday, 19 June)
• Alternative to the offer/answer mechanism (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• Re: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• Re: SDP wrapper? Object-oriented API? (Monday, 17 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• Re: SDP wrapper? Object-oriented API? (Saturday, 15 June)
• Re: SDP wrapper? Object-oriented API? (Saturday, 15 June)
• Re: quibbles about the spec (Wednesday, 12 June)
• Re: Futures in WebRTC (Friday, 7 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: Futures in WebRTC (Monday, 3 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Saturday, 1 June)

Cullen Jennings

• Re: Signaling without a server (Wednesday, 12 June)

Cullen Jennings (fluffy)

• Re: Allowing RTCIceServer to contain multiple URLs (Wednesday, 12 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Saturday, 8 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Thursday, 6 June)

Dan Ristic

• Re: Simultaneous Peer Connections (Monday, 24 June)
• Simultaneous Peer Connections (Monday, 24 June)
• Re: Signaling without a server (Sunday, 9 June)

David Beckwith

• Re: Futures in WebRTC (Wednesday, 5 June)

Eric Rescorla

• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 18 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Futures in WebRTC (Tuesday, 4 June)

Frédéric Luart

• RE: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• RE: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• RE: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• RE: SDP wrapper? Object-oriented API? (Monday, 17 June)

Gili

• Re: API design (Thursday, 27 June)
• Re: API design (Thursday, 27 June)
• Re: Mandatory vs optional codecs (Thursday, 27 June)
• API design (Thursday, 27 June)
• Re: Mandatory vs optional codecs (Thursday, 27 June)
• Re: Mandatory vs optional codecs (Thursday, 27 June)
• Mandatory vs optional codecs (Thursday, 27 June)
• Recap from WebRTC World (Thursday, 27 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 26 June)

Harald Alvestrand

• Re: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Thursday, 13 June)
• Re: Draft text for identity-bound streams (Thursday, 13 June)
• Anycast (Re: Allowing RTCIceServer to contain multiple URLs) (Wednesday, 12 June)
• Re: quibbles about the spec (Wednesday, 12 June)
• Re: Draft text for identity-bound streams (Wednesday, 12 June)

Iñaki Baz Castillo

• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: quibble on terminology (Monday, 17 June)
• Re: SDP wrapper? Object-oriented API? (Monday, 17 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• Re: How to know if a given track or media stream is being transmitted (Friday, 14 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Monday, 3 June)

Jan-Ivar Bruaroey

• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 19 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Wednesday, 19 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Tuesday, 18 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Wednesday, 12 June)
• Re: Our simple PeerConnection example with Futures/Promises (Friday, 7 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Re: Futures in WebRTC (Monday, 3 June)

Jim Barnett

• RE: Operations in invalid states: Exceptions don't make sense. (Wednesday, 26 June)
• RE: Operations in invalid states: Exceptions don't make sense. (Monday, 24 June)
• RE: Operations in invalid states: Exceptions don't make sense. (Thursday, 20 June)
• quibble on terminology (Monday, 17 June)
• RE: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• RE: Our simple PeerConnection example with Futures/Promises (Monday, 10 June)
• RE: Our simple PeerConnection example with Futures/Promises (Monday, 10 June)
• RE: quibbles about the spec (Friday, 7 June)
• quibbles about the spec (Thursday, 6 June)
• RE: Future of Futures in Chrome (Tuesday, 4 June)

José Luis Millán

• Re: How to know if a given track or media stream is being transmitted (Monday, 17 June)
• How to know if a given track or media stream is being transmitted (Friday, 14 June)

Justin Uberti

• Re: Conclusion of RTCIceServer multiple-URI thread (Saturday, 15 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Thursday, 13 June)
• Re: Conclusion of RTCIceServer multiple-URI thread (Wednesday, 12 June)
• Conclusion of RTCIceServer multiple-URI thread (Wednesday, 12 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Wednesday, 12 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Wednesday, 12 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Friday, 7 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Thursday, 6 June)
• Future of Futures in Chrome (Tuesday, 4 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Monday, 3 June)
• Re: Operations in invalid states: Exceptions don't make sense. (Saturday, 1 June)

Keith Wansbrough

• Re: New editor's draft (v20130603) (Tuesday, 4 June)

Ken Smith

• Re: Mandatory vs optional codecs (Thursday, 27 June)
• Re: Recap from WebRTC World (Thursday, 27 June)
• Re: SDP wrapper? Object-oriented API? (Monday, 17 June)
• Re: SDP wrapper? Object-oriented API? (Saturday, 15 June)

lonce

• Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth) (Monday, 17 June)
• Audio and Opus configurability for speed and quality (at the expense of bandwidth) (Friday, 14 June)

Martin Thomson

• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Saturday, 15 June)
• Re: Draft text for identity-bound streams (Wednesday, 12 June)
• Re: Security of cross-origin audio (Monday, 3 June)
• Re: Security of cross-origin audio (Monday, 3 June)

Matthew Kaufman (SKYPE)

• RE: Simultaneous Peer Connections (Monday, 24 June)
• RE: Alternative to the offer/answer mechanism (Thursday, 20 June)
• RE: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)

Max Jonas Werner

• Re: Is DataChannel label unique? (Tuesday, 25 June)

piranna@gmail.com

• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Saturday, 29 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: API design (Friday, 28 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: API design (Thursday, 27 June)
• Re: Is DataChannel label unique? (Wednesday, 26 June)
• Re: Is DataChannel label unique? (Tuesday, 25 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Re: Simultaneous Peer Connections (Monday, 24 June)
• Is DataChannel label unique? (Sunday, 23 June)
• Fwd: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• RE: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• Re: SDP wrapper? Object-oriented API? (Tuesday, 18 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• Re: SDP wrapper? Object-oriented API? (Sunday, 16 June)
• SDP wrapper? Object-oriented API? (Friday, 14 June)
• Re: Signaling without a server (Wednesday, 12 June)
• Re: Signaling without a server (Sunday, 9 June)
• Re: Signaling without a server (Sunday, 9 June)
• Signaling without a server (Sunday, 9 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)

Randell Jesup

• Re: New editor's draft (v20130603) (Friday, 14 June)
• Re: New editor's draft (v20130603) (Thursday, 13 June)
• Re: New editor's draft (v20130603) (Tuesday, 4 June)

Robin Raymond

• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Saturday, 29 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Saturday, 29 June)
• Re: Recap from WebRTC World (Thursday, 27 June)

Roman Shpount

• Re: API design (Saturday, 29 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: API design (Friday, 28 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: Alternative to the offer/answer mechanism (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Thursday, 20 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)

Silvia Pfeiffer

• Re: Recap from WebRTC World (Thursday, 27 June)
• Re: SDP wrapper? Object-oriented API? (Wednesday, 19 June)

Stefan Håkansson LK

• CfC: publish FPWD of "MediaStream Image Capture"; deadline June 30 (Thursday, 20 June)
• Re: Draft text for identity-bound streams (Thursday, 13 June)
• Re: Draft text for identity-bound streams (Thursday, 13 June)
• Re: Draft text for identity-bound streams (Wednesday, 12 June)
• Documents in scope for Futures discussion (Wednesday, 5 June)
• Re: Futures in WebRTC (Tuesday, 4 June)
• Details Futures teleconf (Monday, 3 June)

Suhas Nandakumar (snandaku)

• RE: SDP wrapper? Object-oriented API? (Saturday, 15 June)

Ted Hardie

• Re: Teleco Integrators vs Web Developers vs Browser Implementers (Friday, 28 June)
• Re: Allowing RTCIceServer to contain multiple URLs (Monday, 3 June)

tim panton

• Re: SDP wrapper? Object-oriented API? (Monday, 17 June)

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