Wednesday, 29 February 2012
- Re: Minimizing the protocol (Re: Data API)
- Re: Minimizing the protocol (Re: Data API)
- Re: Minimizing the protocol (Re: Data API)
- Re: Minimizing the protocol (Re: Data API)
- Summary of advice, numeric constants vs enumerated strings
Tuesday, 28 February 2012
- Re: Minimizing the protocol (Re: Data API)
- Re: Minimizing the protocol (Re: Data API)
- Re: Minimizing the protocol (Re: Data API)
- Minimizing the protocol (Re: Data API)
- Re: Data API
Monday, 27 February 2012
- Re: Data API
- Re: Data API
- Re: Data API Proposal aligned to WebSocket
- Data API
- Re: Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
Friday, 24 February 2012
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Constraints structure and Capabilities API
- Re: Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Constraints structure and Capabilities API
Thursday, 23 February 2012
Friday, 24 February 2012
Thursday, 23 February 2012
Friday, 24 February 2012
- Re: Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
Thursday, 23 February 2012
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Constraints structure and Capabilities API
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
- Re: Data API Proposal aligned to WebSocket
Wednesday, 22 February 2012
Tuesday, 21 February 2012
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
Thursday, 23 February 2012
Wednesday, 22 February 2012
- Re: Data API Proposal aligned to WebSocket
- Concluding the CfC regarding publishing a FPWD of the Media Cap TF scenario doc
- Data API Proposal aligned to WebSocket
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
Tuesday, 21 February 2012
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
Monday, 20 February 2012
- Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- Re: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- RE: [rtcweb] JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- JSEP-02: New offer and answer to previous offer [was: JSEP-02: SDP_PRANSWER and FEDEX use-case]
- Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Next Telco: March 13
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
Sunday, 19 February 2012
Friday, 17 February 2012
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- RE: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
- Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] Joint JSEP draft posted
- Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
- Concluding "Data API: what is agreed, what is open"
- RE: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] JSEP-02: Associating ICE candidates with m- lines
- Re: [rtcweb] JSEP-01: Release of non-needed ICE candidates
- Re: [rtcweb] Joint JSEP draft posted
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: [rtcweb] JSEP-01: Associating ICE candidates with m- lines
- Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
Thursday, 16 February 2012
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Re: Numeric constants vs enumerated strings
- Re: Next Telco
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- RE: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case
- Re: Numeric constants vs enumerated strings
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: [rtcweb] JSEP-01: Associating ICE candidates with m- lines
- Re: [rtcweb] JSEP-01: SDP_PRANSWER and FEDEX use-case
- RE: [rtcweb] Joint JSEP draft posted
- Joint JSEP draft posted
Wednesday, 15 February 2012
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- RE: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- RE: [rtcweb] JSEP-01: Release of non-needed ICE candidates
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- RE: [rtcweb] JSEP-01: Release of non-needed ICE candidates
- Re: Numeric constants vs enumerated strings
- Re: Numeric constants vs enumerated strings
- JSEP-01: Release of non-needed ICE candidates
- Re: Numeric constants vs enumerated strings
- Numeric constants vs enumerated strings
- Re: Next Telco
- JSEP-01: Associating ICE candidates with m- lines
- JSEP-01: SDP_PRANSWER and FEDEX use-case
- Re: [rtcweb] Single offer with multiple answer handling in JSEP [was RE: New JSEP draft posted]
- Re: Data API: what is agreed, what is open - buffering
- Re: Next Telco
Tuesday, 14 February 2012
- Re: Next Telco
- Re: Next Telco
- Re: Next Telco
- Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted]
- Re: Data API: what is agreed, what is open
- Re: Next Telco
- Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted]
- Re: Next Telco
- Re: Mute and MediaStream repointing
- Re: [rtcweb] ICE Candidate Gathering - Basic Thought
- Next Telco
- Re: [rtcweb] ICE Candidate Gathering - Basic Thought
- Re: Single offer with multiple answer handling in JSEP [was RE: [rtcweb] New JSEP draft posted]
- Re: [rtcweb] ICE Candidate Gathering - Basic Thought
- Re: Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
- Re: Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
- Re: ICE Candidate Gathering - Basic Thought
- Membership management (Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
Monday, 13 February 2012
- Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
- Re: Mute and MediaStream repointing
- Re: Mute and MediaStream repointing
- ICE Candidate Gathering - Basic Thought
- Re: Data API: what is agreed, what is open
- Re: Data API: what is agreed, what is open - buffering
- Re: Mute and MediaStream repointing
- Re: Mute and MediaStream repointing
- Re: Data API: what is agreed, what is open
- Re: Proposal how to map JSEP to the existing API
- Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
- Re: Data API: what is agreed, what is open - buffering
- Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
- Re: Use of .iceState and .sdpState
- Re: [rtcweb] JS app interaction with congestion control
- Re: Mute and MediaStream repointing
- Re: Mute and MediaStream repointing
- Enabling JSEP
- Mute and MediaStream repointing
- Re: New JSEP draft posted
- Re: [minutes] F2F meeting Feb 1st
- Re: Data API: what is agreed, what is open
- Re: Data API: what is agreed, what is open
- Re: API scope
Sunday, 12 February 2012
- Re: Unidirectional vs bidriectional (Re: Data API: what is agreed, what is open)
- Re: Data API: what is agreed, what is open
Monday, 13 February 2012
Sunday, 12 February 2012
- Re: API scope
- Re: Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
Saturday, 11 February 2012
- Unidirectional vs bidriectional (Re: Data API: what is agreed, what is open)
- Re: Data API: what is agreed, what is open
- Call for Consensus to publish a First Public Working Draft of "Media Stream Capture Scenarios", deadline 20 Feb 2012
Friday, 10 February 2012
- Re: Data API: what is agreed, what is open
- Re: [minutes] F2F meeting Feb 1st
- Re: API scope
- Re: Data API: what is agreed, what is open
- Re: Data API: what is agreed, what is open
- Re: API scope
- Re: Use of .iceState and .sdpState
- Re: API scope
- Re: Data API: what is agreed, what is open
- Re: API scope
- Re: Proposal how to map JSEP to the existing API
- Re: New JSEP draft posted
- Re: Proposal how to map JSEP to the existing API
- Re: Proposal how to map JSEP to the existing API
- Re: New JSEP draft posted
- Re: New JSEP draft posted
- Proposal how to map JSEP to the existing API
Thursday, 9 February 2012
- Re: [rtcweb] New JSEP draft posted
- RE: [rtcweb] New JSEP draft posted
- Re: [rtcweb] New JSEP draft posted
- Re: [rtcweb] New JSEP draft posted
- RE: [rtcweb] New JSEP draft posted
- New public WD
Wednesday, 8 February 2012
- New JSEP draft posted
- Re: Data API: what is agreed, what is open
- Re: Use of .iceState and .sdpState
- [minutes] F2F meeting Feb 1st
- Re: Data API: what is agreed, what is open
- Use of .iceState and .sdpState
- Re: Data API: what is agreed, what is open
- Re: Data API: what is agreed, what is open
Tuesday, 7 February 2012
- Re: Data API: what is agreed, what is open
- Re: Data API: what is agreed, what is open
- Data API: what is agreed, what is open
- Re: Fwd: Re: SCTP mapping to data channels
- Re: API scope
- Re: API scope
Monday, 6 February 2012
- Re: API scope
- Re: Fwd: Re: SCTP mapping to data channels
- API scope
- Re: Fwd: Re: SCTP mapping to data channels
- API scope
- New "startup level" fee for W3C Membership
- Re: Fwd: Re: SCTP mapping to data channels
- Re: Fwd: Re: SCTP mapping to data channels
- Re: Fwd: Re: SCTP mapping to data channels
- Re: Fwd: Re: SCTP mapping to data channels
- Default video control behavior?
- Re: SCTP mapping to data channels
Saturday, 4 February 2012
Sunday, 5 February 2012
Saturday, 4 February 2012
- Re: Fwd: Re: SCTP mapping to data channels
- Fwd: Re: SCTP mapping to data channels
- Re: SCTP mapping to data channels
Friday, 3 February 2012
- Re: SCTP mapping to data channels
- SCTP mapping to data channels
- Re: Updated data stream API draft
- Re: Updated data stream API draft
- Re: Updated data stream API draft
- [Bug 15861] New: API for JS interaction with congestion control