Message-ID: <4F79859D.1050208@ericsson.com>
Date: Mon, 2 Apr 2012 13:55:25 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <FA86515700364A16B4EDF69E88E3FA1A@devbox>
 <4F71982B.4010208@alvestrand.no>
In-Reply-To: <4F71982B.4010208@alvestrand.no>
Content-Type: multipart/alternative;
 boundary="------------090800020007060104070806"
Subject: Re: [rtcweb] Query regarding rtcweb use cases and requirements.
Precedence: list

--------------090800020007060104070806
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

at moment the requirements/use case for Data are in the following draft
http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-00


/Salvatore


On 3/27/12 1:36 PM, Harald Alvestrand wrote:
> On 03/27/2012 09:51 AM, ajrmeyn@gmail.com wrote:
>> Hi,
>>   
>> This is with regards to the following document:
>> Web Real-Time Communication Use-cases and Requirements
>> draft-ietf-rtcweb-use-cases-and-requirements-06.txt
>> http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/?include_text=1
>> I have noticed that the use cases with regards to Data API of web 
>> real time communication, have not been addressed. For example: use 
>> cases that are related to file sharing between browsers.
>> is there any particular reason for the same?
> Requirement F23 is a data-passing requirement.
>
> 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.
>
> The WG is suggesting data API/protocol solutions that can be used for 
> other things than fulfiling the most narrow interpretation of the 
> requirement listed, but did not feel a need to add a requirement 
> covering those.
>
> 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.
>
> My interpretation....
>
>                       Harald
>
>
>
>
>> Regards,
>> Antony Meyn
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>


-- 
Salvatore Loreto, PhD
www.sloreto.com


--------------090800020007060104070806
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    at moment the requirements/use case for Data are in the following
    draft<br>
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-00">http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-00</a><br>
    <br>
    <br>
    /Salvatore<br>
    <br>
    <br>
    On 3/27/12 1:36 PM, Harald Alvestrand wrote:
    <blockquote cite="mid:4F71982B.4010208@alvestrand.no" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      On 03/27/2012 09:51 AM, <a moz-do-not-send="true"
        class="moz-txt-link-abbreviated" href="mailto:ajrmeyn@gmail.com">ajrmeyn@gmail.com</a>
      wrote:
      <blockquote cite="mid:FA86515700364A16B4EDF69E88E3FA1A@devbox"
        type="cite">
        <meta content="text/html; charset=ISO-8859-1"
          http-equiv="Content-Type">
        <div dir="ltr">
          <div style="font-family: 'Arial'; color: rgb(0, 0, 0);
            font-size: 10pt;">
            <div style="font-style: normal; display: inline;
              font-family: 'Calibri'; color: rgb(0, 0, 0); font-size:
              small; font-weight: normal; text-decoration: none;">
              <div dir="ltr">
                <div style="font-family: 'Arial'; color: rgb(0, 0, 0);
                  font-size: 10pt;">
                  <pre style="line-height: 12pt; background-color: rgb(255, 255, 255); margin-top: 0px; margin-bottom: 0px;">Hi,</pre>
                  <pre style="line-height: 12pt; background-color: rgb(255, 255, 255); margin-top: 0px; margin-bottom: 0px;">&nbsp;</pre>
                  <pre style="line-height: 12pt; background-color: rgb(255, 255, 255); margin-top: 0px; margin-bottom: 0px;">This is with regards to the following document:</pre>
                  <pre style="line-height: 12pt; background-color: rgb(255, 255, 255); margin-top: 0px; margin-bottom: 0px;">Web Real-Time Communication Use-cases and Requirements
draft-ietf-rtcweb-use-cases-and-requirements-06.txt
</pre>
                  <a moz-do-not-send="true"
href="http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/?include_text=1"
                    target="_blank"><font face="Tahoma">http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/?include_text=1</font></a><font
                    face="Tahoma"> </font>
                  <div><font face="Tahoma">I have noticed that the use
                      cases with regards to Data API of web real time
                      communication, have not been addressed. For
                      example: use cases that are related to file
                      sharing between browsers. </font></div>
                  <div>&nbsp;</div>
                  <div><font face="Tahoma">is there any particular
                      reason for the same?</font></div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      Requirement F23 is a data-passing requirement.<br>
      <br>
      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.<br>
      <br>
      The WG is suggesting data API/protocol solutions that can be used
      for other things than fulfiling the most narrow interpretation of
      the requirement listed, but did not feel a need to add a
      requirement covering those.<br>
      <br>
      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.<br>
      <br>
      My interpretation....<br>
      <br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Harald<br>
      <br>
      <br>
      <br>
      <br>
      <blockquote cite="mid:FA86515700364A16B4EDF69E88E3FA1A@devbox"
        type="cite">
        <div dir="ltr">
          <div style="font-family: 'Arial'; color: rgb(0, 0, 0);
            font-size: 10pt;">
            <div style="font-style: normal; display: inline;
              font-family: 'Calibri'; color: rgb(0, 0, 0); font-size:
              small; font-weight: normal; text-decoration: none;">
              <div dir="ltr">
                <div style="font-family: 'Arial'; color: rgb(0, 0, 0);
                  font-size: 10pt;">
                  <div>&nbsp;</div>
                  <div><font face="Tahoma">Regards,</font></div>
                  <div><font face="Tahoma">Antony Meyn</font></div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rtcweb mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rtcweb@ietf.org">rtcweb@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtcweb">https://www.ietf.org/mailman/listinfo/rtcweb</a>
</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Salvatore Loreto, PhD
<a class="moz-txt-link-abbreviated" href="http://www.sloreto.com">www.sloreto.com</a></pre>
  </body>
</html>

--------------090800020007060104070806--