IETF Logo Mail Archive

Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10 - real-time text

Harald Alvestrand <harald@alvestrand.no> Thu, 31 January 2013 23:07 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4683D21F8888 for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 15:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.373
X-Spam-Level:
X-Spam-Status: No, score=-109.373 tagged_above=-999 required=5 tests=[AWL=-1.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_OFF=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgAYuL+LHUH9 for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 15:07:38 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 73B1D21F8887 for <rtcweb@ietf.org>; Thu, 31 Jan 2013 15:07:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3660239E1C4 for <rtcweb@ietf.org>; Fri, 1 Feb 2013 00:07:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLz4lqHWNIgs for <rtcweb@ietf.org>; Fri, 1 Feb 2013 00:07:33 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 6A8A939E1B7 for <rtcweb@ietf.org>; Fri, 1 Feb 2013 00:07:33 +0100 (CET)
Message-ID: <510AF934.2030800@alvestrand.no>
Date: Fri, 01 Feb 2013 00:07:32 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <50F97303.4070906@ericsson.com> <5102FE7E.5000109@omnitor.se> <51039976.1000600@alvestrand.no> <51098D5A.4040009@omnitor.se>
In-Reply-To: <51098D5A.4040009@omnitor.se>
Content-Type: multipart/alternative; boundary="------------080809080004090005050306"
Subject: Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10 - real-time text
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 23:07:39 -0000

FWIW, I strongly object to a couple of formalities here:

- I object to making normative reference to F.700 and F.703.
- I object to requiring interworking with emergency services.

If there's strong support in the WG for including the use case, I'm 
willing to go along with that.

(The reason for not wanting to normatively reference F.700 and F.703 is 
that they're very large balls of string, and I have no idea where the 
string may lead; for instance, the definition of "Total Conversation" in 
section A.3.2.3 of F.700 requires font support for all characters in 
ISO-10646-1; I doubt somewhat that the person who wrote that paragraph 
has studied the task of providing such font support - I found that 
particular linkage in a few minutes of scanning the docs.)

On 01/30/2013 10:15 PM, Gunnar Hellstrom wrote:
> 4.2.15.Simple Total Conversation service
>
> 4.2.15.1.Description
>   
>     This use-case has the audio and video communication of the Simple
>     Video Communication Service use-case (Section 4.2.1  <http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and-requirements-09#section-4.2.1>).
>   
>     In addition to this, the users can send and receive real-time text
>     in the same call.  While one user types in the real-time text area, it
>      is nearly immediately presented to the other user.
>
>     By providing these three media together, the Total Conversation
>     service is provided.
>
>     Interworking with SIP calls with the same media set, and with SIP
>     based emergency services is also in scope of this use case.
>   
> 4.2.15.2  <imap://hta@eikenes.alvestrand.no:143/fetch%3EUID%3E.INBOX.IETF.Areas.rai.rtcweb%3E5874#section-4.3.1.2>.   Derived Requirements
>   
>     F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F21,
>   
>     F39,F40, F41
>   
>     A1, A2, A3, A4, A7, A8, A9, A10, A11, A12, A27
>   
> ..............
>
>     F39              The browser MUST be able to handle text entry
>                     via applications to generate real-time
>                     text streams to be included in Total Conversation
>                     calls. Real-time text and Total Conversation
>                     Services are defined in ITU-T F.700 and F.703.
>     ----------------------------------------------------------------
>     F40               The browser MUST be able to send real-time text
>                     streams to a peer.
>   
>     ----------------------------------------------------------------
>     F41               The browser MUST be able to receive, process and
>                       convey real-time text streams from peers to
>                      applications.
>     ----------------------------------------------------------------
>     
>   
>
> .....
>
>     A27              The Web API MUST provide a mechanisms for  
>                     handling real-time text among the streams.  
>   ----------------------------------------------------------------

v2.23.0 | Report a Bug | By Email