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

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 02 February 2013 00:39 UTC

Return-Path: <bernard_aboba@hotmail.com>
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 279E01F0CFE for <rtcweb@ietfa.amsl.com>; Fri, 1 Feb 2013 16:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.421
X-Spam-Level:
X-Spam-Status: No, score=-102.421 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 EKJ6OZhyCSfT for <rtcweb@ietfa.amsl.com>; Fri, 1 Feb 2013 16:39:01 -0800 (PST)
Received: from blu0-omc3-s37.blu0.hotmail.com (blu0-omc3-s37.blu0.hotmail.com [65.55.116.112]) by ietfa.amsl.com (Postfix) with ESMTP id 833191F0CFB for <rtcweb@ietf.org>; Fri, 1 Feb 2013 16:39:01 -0800 (PST)
Received: from BLU002-W149 ([65.55.116.73]) by blu0-omc3-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Feb 2013 16:39:01 -0800
X-EIP: [3Kk4UlDqqDu8VSqPEjQHd9Y/sHjhldVp]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU002-W149D09F7296C2465CA4968093030@phx.gbl>
Content-Type: multipart/alternative; boundary="_88149b80-9ac7-4dd3-895c-e7458a7d3899_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "harald@alvestrand.no" <harald@alvestrand.no>
Date: Fri, 01 Feb 2013 16:39:00 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 02 Feb 2013 00:39:01.0178 (UTC) FILETIME=[B1D769A0:01CE00DD]
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: Sat, 02 Feb 2013 00:39:02 -0000

Harald said:
"I object to requiring interworking with emergency services."

[BA] The concrete question is "what would such a requirement consist of?" beyond the use cases 
and requirements that are already in the document. 

Martin and I examined how WebRTC stacks up against PhoneBCP in draft-aboba-rtcweb-ecrit, 
and the most obvious gap (location) appears to be more in the balliwick of IETF GEOPRIV/W3C 
location APIs than WebRTC. 

Lots of stuff that *might* be useful in emergency services (e.g. SIP or XMPP-based instant 
messaging,  XMPP or data-channel based realtime text, video, etc.) looks like it could be 
implemented in WebRTC without adding any more native functionality, use cases or requirements.  
Just because we don't have a use case or requirement, doesn't mean it can't be done.  For
example, there is no use case for "playing an imaginary xylophone with your fingers" or 
"projecting a stream on a spinning TV", but it seems to be possible.