MIME-Version: 1.0
In-Reply-To: <4F71982B.4010208@alvestrand.no>
References: <FA86515700364A16B4EDF69E88E3FA1A@devbox>
 <4F71982B.4010208@alvestrand.no>
Date: Thu, 29 Mar 2012 15:05:37 +0300
Message-ID: <CAFX5qAphvfePbCJDz95wDr-nbfoGsohukudo98z2WfEZa=BcOg@mail.gmail.com>
From: Antony Meyn <ajrmeyn@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=f46d043bde66c8a18e04bc608a47
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Query regarding rtcweb use cases and requirements.
Precedence: list

--f46d043bde66c8a18e04bc608a47
Content-Type: text/plain; charset=ISO-8859-1

@Herald: thanks.

>>For communications that did not need low latency, the WG felt that the
RTCWEB requirements were not different from the requirements of any other
application, so those could be fulfilled with other types of interfaces,
including server-mediated file transfers.

What about use cases of static(non-live) video streaming from browser to
browser, this would require low latency and servers-mediated file transfers
would only add up to the latency, right?. A user would like to share his
video without actually having to upload the content to a server.

>> The purpose of the "use cases and requirements" is to find a minimum set
of things that the protocol suite has to be able to do in order to be "good
enough", not to delineate everything the protocol can be used for.

Agree, but the use cases for the data API, does look promising, and it
didn't seem to have much attention in comparison to live video streaming
use cases.

--f46d043bde66c8a18e04bc608a47
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>@Herald: thanks.</div><div><br></div><div>&gt;&gt;For communications t=
hat did not need low latency, the WG felt that the RTCWEB requirements were=
 not different from the requirements of any other application, so those cou=
ld be fulfilled with other types of interfaces, including server-mediated f=
ile transfers.<br>

</div><div><br></div>What about use cases of static(non-live) video streami=
ng from browser to browser, this would require low latency and servers-medi=
ated file transfers would only add up to the latency, right?. A user would =
like to share his video without actually having to upload the content to a =
server.<div>
<br>
</div><div>&gt;&gt;
The purpose of the &quot;use cases and requirements&quot; is to find a mini=
mum set of things that the protocol suite has to be able to do in order to =
be &quot;good enough&quot;, not to delineate everything the protocol can be=
 used for.=A0</div>
<div><br></div><div>Agree, but the use cases for the data API, does look pr=
omising, and it didn&#39;t seem to have much attention in=A0comparison=A0to=
 live video streaming use cases.</div><div><br></div><div><br></div><div><b=
r>
</div><div><br></div>
<div><br></div><div><br><br>
</div><div><br></div>

--f46d043bde66c8a18e04bc608a47--