- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Thu, 26 May 2011 14:17:20 +0200
- To: Francois Daoust <fd@w3.org>, Göran Eriksson AP <goran.ap.eriksson@ericsson.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Francois, thanks for reading so carefully. Those reqs where removed late in the editing as it was decided to just focus on media stream stuff at the time. They read: F20 Support for DTMF signaling F21 Short messages (game state data) with short latency must be supported (The browser shall support datagram peer-to-peer.) with A16 being an API to send/receive DTMF and A17 an API to send/receive data. Stefan -----Original Message----- From: public-webrtc-request@w3.org [mailto:public-webrtc-request@w3.org] On Behalf Of Francois Daoust Sent: den 23 maj 2011 17:41 To: Göran Eriksson AP Cc: public-webrtc@w3.org Subject: Re: Use cases draft Thanks Göran, On 05/19/2011 08:01 PM, Göran Eriksson AP wrote: > Here is a link to the 'use case' document mentioned in the call today... > > https://tools.ietf.org/html/draft-holmberg-rtcweb-ucreqs-01 There are a couple of use cases which map to non existing requirements: - 4.4.2 links to F21 and A17. - 4.7.2 links to F20 and A16. I suppose the mapping is incorrect. Or are there missing requirements? Francois.
Received on Thursday, 26 May 2011 12:17:46 UTC