public-webrtc@w3.org from February 2012 by author

Adam Bergkvist

• Re: Data API (Tuesday, 28 February)
• Re: Data API Proposal aligned to WebSocket (Monday, 27 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Data API Proposal aligned to WebSocket (Wednesday, 22 February)
• Re: Proposal how to map JSEP to the existing API (Monday, 13 February)
• Re: New JSEP draft posted (Monday, 13 February)
• Re: New JSEP draft posted (Friday, 10 February)
• Proposal how to map JSEP to the existing API (Friday, 10 February)
• Re: Use of .iceState and .sdpState (Wednesday, 8 February)

Alex Russell

• Re: Numeric constants vs enumerated strings (Thursday, 16 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)

Anne van Kesteren

• Re: Numeric constants vs enumerated strings (Thursday, 16 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)

bugzilla@jessica.w3.org

• [Bug 15861] New: API for JS interaction with congestion control (Friday, 3 February)

caryfitz

• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)

Chen, Miaobo

• Default video control behavior? (Monday, 6 February)

Christer Holmberg

• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 27 February)
• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Wednesday, 22 February)
• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• RE: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• RE: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Friday, 17 February)
• RE: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• RE: [rtcweb] JSEP-02: Associating ICE candidates with m- lines (Friday, 17 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Thursday, 16 February)
• RE: [rtcweb] Joint JSEP draft posted (Thursday, 16 February)
• RE: [rtcweb] JSEP-01: Release of non-needed ICE candidates (Wednesday, 15 February)
• JSEP-01: Release of non-needed ICE candidates (Wednesday, 15 February)
• JSEP-01: Associating ICE candidates with m- lines (Wednesday, 15 February)
• JSEP-01: SDP_PRANSWER and FEDEX use-case (Wednesday, 15 February)

Cullen Jennings

• Re: Minimizing the protocol (Re: Data API) (Wednesday, 29 February)
• Re: Minimizing the protocol (Re: Data API) (Wednesday, 29 February)
• Data API (Monday, 27 February)
• Re: Constraints structure and Capabilities API (Monday, 27 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Friday, 17 February)
• Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Thursday, 16 February)
• Re: [rtcweb] JSEP-01: Associating ICE candidates with m- lines (Thursday, 16 February)
• Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Thursday, 16 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Wednesday, 15 February)
• Re: Data API: what is agreed, what is open - buffering (Wednesday, 15 February)
• Re: Next Telco (Tuesday, 14 February)
• Re: Next Telco (Tuesday, 14 February)
• Re: Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Tuesday, 14 February)
• Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Monday, 13 February)
• Re: Data API: what is agreed, what is open - buffering (Monday, 13 February)
• Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Monday, 13 February)
• Re: Use of .iceState and .sdpState (Monday, 13 February)
• Re: [rtcweb] JS app interaction with congestion control (Monday, 13 February)
• Re: Data API: what is agreed, what is open (Friday, 10 February)

Dan Burnett

• Re: Constraints structure and Capabilities API (Friday, 24 February)
• Constraints structure and Capabilities API (Thursday, 23 February)

Dominique Hazael-Massieux

• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Tuesday, 14 February)
• Re: [minutes] F2F meeting Feb 1st (Monday, 13 February)
• New public WD (Thursday, 9 February)
• [minutes] F2F meeting Feb 1st (Wednesday, 8 February)
• Use of .iceState and .sdpState (Wednesday, 8 February)
• API scope (Monday, 6 February)
• API scope (Monday, 6 February)
• New "startup level" fee for W3C Membership (Monday, 6 February)

Ejzak, Richard P (Richard)

• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Tuesday, 21 February)
• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Tuesday, 21 February)

Eric Rescorla

• Re: [minutes] F2F meeting Feb 1st (Friday, 10 February)

Harald Alvestrand

• Summary of advice, numeric constants vs enumerated strings (Wednesday, 29 February)
• Re: Minimizing the protocol (Re: Data API) (Tuesday, 28 February)
• Minimizing the protocol (Re: Data API) (Tuesday, 28 February)
• Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Next Telco (Wednesday, 15 February)
• Re: [rtcweb] ICE Candidate Gathering - Basic Thought (Tuesday, 14 February)
• Re: ICE Candidate Gathering - Basic Thought (Tuesday, 14 February)
• Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Tuesday, 14 February)
• Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Monday, 13 February)
• Re: API scope (Monday, 13 February)
• Unidirectional vs bidriectional (Re: Data API: what is agreed, what is open) (Saturday, 11 February)
• Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Saturday, 11 February)
• Re: [rtcweb] New JSEP draft posted (Thursday, 9 February)
• Re: Data API: what is agreed, what is open (Wednesday, 8 February)
• Re: API scope (Tuesday, 7 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)
• Re: SCTP mapping to data channels (Monday, 6 February)
• Re: Fwd: Re: SCTP mapping to data channels (Saturday, 4 February)
• Re: Updated data stream API draft (Friday, 3 February)

Hutton, Andrew

• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Sunday, 19 February)
• RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Thursday, 16 February)

Iñaki Baz Castillo

• Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)

Jim Barnett

• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Tuesday, 21 February)
• RE: [rtcweb] Joint JSEP draft posted (Friday, 17 February)
• RE: [rtcweb] JSEP-01: Release of non-needed ICE candidates (Wednesday, 15 February)
• RE: [rtcweb] New JSEP draft posted (Thursday, 9 February)
• RE: [rtcweb] New JSEP draft posted (Thursday, 9 February)

Justin Uberti

• Re: Minimizing the protocol (Re: Data API) (Wednesday, 29 February)
• Re: Minimizing the protocol (Re: Data API) (Wednesday, 29 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Tuesday, 21 February)
• Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Friday, 17 February)
• Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• Re: [rtcweb] JSEP-01: Release of non-needed ICE candidates (Friday, 17 February)
• Re: [rtcweb] Joint JSEP draft posted (Friday, 17 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Friday, 17 February)
• Re: [rtcweb] JSEP-01: Associating ICE candidates with m- lines (Friday, 17 February)
• Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case (Friday, 17 February)
• Joint JSEP draft posted (Thursday, 16 February)
• Re: Next Telco (Tuesday, 14 February)
• Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted] (Tuesday, 14 February)
• Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted] (Tuesday, 14 February)
• Re: Mute and MediaStream repointing (Tuesday, 14 February)
• Re: [rtcweb] ICE Candidate Gathering - Basic Thought (Tuesday, 14 February)
• Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted] (Tuesday, 14 February)
• Re: [rtcweb] ICE Candidate Gathering - Basic Thought (Tuesday, 14 February)
• Re: API scope (Monday, 13 February)
• Re: API scope (Friday, 10 February)
• Re: New JSEP draft posted (Friday, 10 February)
• Re: Proposal how to map JSEP to the existing API (Friday, 10 February)
• Re: New JSEP draft posted (Friday, 10 February)
• Re: [rtcweb] New JSEP draft posted (Thursday, 9 February)
• Re: [rtcweb] New JSEP draft posted (Thursday, 9 February)
• New JSEP draft posted (Wednesday, 8 February)
• Re: Data API: what is agreed, what is open (Tuesday, 7 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)

Khan, Sohel

• RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Wednesday, 22 February)

Marcos Caceres

• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)

Martin Thomson

• Re: Constraints structure and Capabilities API (Friday, 24 February)
• Re: Constraints structure and Capabilities API (Thursday, 23 February)

Michael Tuexen

• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Unidirectional vs bidriectional (Re: Data API: what is agreed, what is open) (Sunday, 12 February)
• Re: Data API: what is agreed, what is open (Sunday, 12 February)

Philip Jägenstedt

• Re: Numeric constants vs enumerated strings (Thursday, 16 February)
• Re: Numeric constants vs enumerated strings (Thursday, 16 February)

Randall Stewart

• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: SCTP mapping to data channels (Saturday, 4 February)

Randell Jesup

• Re: Minimizing the protocol (Re: Data API) (Tuesday, 28 February)
• Re: Minimizing the protocol (Re: Data API) (Tuesday, 28 February)
• Re: Data API (Monday, 27 February)
• Re: Data API (Monday, 27 February)
• Re: Constraints structure and Capabilities API (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Constraints structure and Capabilities API (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Thursday, 23 February)
• Re: Data API Proposal aligned to WebSocket (Wednesday, 22 February)
• Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• Re: Mute and MediaStream repointing (Monday, 13 February)
• Re: Data API: what is agreed, what is open - buffering (Monday, 13 February)
• Re: Mute and MediaStream repointing (Monday, 13 February)
• Mute and MediaStream repointing (Monday, 13 February)
• Re: Data API: what is agreed, what is open (Saturday, 11 February)
• Re: API scope (Friday, 10 February)
• Re: Data API: what is agreed, what is open (Friday, 10 February)
• Re: Data API: what is agreed, what is open (Wednesday, 8 February)
• Re: Data API: what is agreed, what is open (Tuesday, 7 February)
• Re: Fwd: Re: SCTP mapping to data channels (Tuesday, 7 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)
• Re: Fwd: Re: SCTP mapping to data channels (Sunday, 5 February)
• Fwd: Re: SCTP mapping to data channels (Saturday, 4 February)
• SCTP mapping to data channels (Friday, 3 February)
• Re: [rtcweb] JS app interaction with congestion control (Wednesday, 1 February)

Rich Tibbett

• Re: Constraints structure and Capabilities API (Friday, 24 February)
• Re: Constraints structure and Capabilities API (Friday, 24 February)

Robert O'Callahan

• Re: Mute and MediaStream repointing (Monday, 13 February)

Roman Shpount

• Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case (Monday, 20 February)
• Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case] (Monday, 20 February)
• Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted] (Friday, 17 February)

Salvatore Loreto

• Re: Data API Proposal aligned to WebSocket (Monday, 27 February)
• Re: Data API Proposal aligned to WebSocket (Monday, 27 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)

Soo-Hyun Choi

• Re: Next Telco (Tuesday, 14 February)

Stefan Hakansson LK

• Concluding the CfC regarding publishing a FPWD of the Media Cap TF scenario doc (Wednesday, 22 February)
• Next Telco: March 13 (Monday, 20 February)
• Concluding "Data API: what is agreed, what is open" (Friday, 17 February)
• Re: Next Telco (Thursday, 16 February)
• Re: Data API: what is agreed, what is open (Tuesday, 14 February)
• Re: Next Telco (Tuesday, 14 February)
• Next Telco (Tuesday, 14 February)
• Re: Mute and MediaStream repointing (Monday, 13 February)
• Re: Mute and MediaStream repointing (Monday, 13 February)
• Re: Mute and MediaStream repointing (Monday, 13 February)
• Enabling JSEP (Monday, 13 February)
• Re: Data API: what is agreed, what is open (Monday, 13 February)
• Re: Data API: what is agreed, what is open (Monday, 13 February)
• Re: API scope (Monday, 13 February)
• Re: API scope (Monday, 13 February)
• Re: API scope (Sunday, 12 February)
• Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012 (Sunday, 12 February)
• Re: Proposal how to map JSEP to the existing API (Friday, 10 February)
• Re: Data API: what is agreed, what is open (Wednesday, 8 February)
• Re: Data API: what is agreed, what is open (Wednesday, 8 February)
• Data API: what is agreed, what is open (Tuesday, 7 February)
• Re: API scope (Tuesday, 7 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)
• Re: SCTP mapping to data channels (Saturday, 4 February)
• Re: Updated data stream API draft (Friday, 3 February)
• Re: Updated data stream API draft (Friday, 3 February)

Suhas Nandakumar (snandaku)

• ICE Candidate Gathering - Basic Thought (Monday, 13 February)

Tab Atkins Jr.

• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)

Ted Hardie

• Re: Data API: what is agreed, what is open (Monday, 13 February)

Tim Panton

• Re: Next Telco (Wednesday, 15 February)
• Re: Proposal how to map JSEP to the existing API (Friday, 10 February)

Timothy B. Terriberry

• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Data API Proposal aligned to WebSocket (Friday, 24 February)
• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)
• Re: Data API: what is agreed, what is open (Monday, 13 February)
• Re: Data API: what is agreed, what is open (Friday, 10 February)
• Re: API scope (Friday, 10 February)
• Re: Use of .iceState and .sdpState (Friday, 10 February)
• Re: Data API: what is agreed, what is open (Friday, 10 February)
• Re: API scope (Friday, 10 February)
• Re: API scope (Monday, 6 February)
• Re: Fwd: Re: SCTP mapping to data channels (Monday, 6 February)
• Re: SCTP mapping to data channels (Friday, 3 February)

Tobie Langel

• Re: Numeric constants vs enumerated strings (Wednesday, 15 February)

Travis Leithead

• RE: Numeric constants vs enumerated strings (Wednesday, 15 February)

Last message date: Wednesday, 29 February 2012 23:37:48 UTC