Re: [rtcweb] Possible New Cases - Emergency Services Call & Text

Randell Jesup <randell-ietf@jesup.org> Sun, 31 July 2011 21:23 UTC

Return-Path: <randell-ietf@jesup.org>
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 0592F21F8862 for <rtcweb@ietfa.amsl.com>; Sun, 31 Jul 2011 14:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.375
X-Spam-Level:
X-Spam-Status: No, score=-2.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599]
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 voKbQQAXb-mZ for <rtcweb@ietfa.amsl.com>; Sun, 31 Jul 2011 14:23:43 -0700 (PDT)
Received: from arthur.webserversystems.com (arthur.webserversystems.com [174.132.191.98]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2F221F885C for <rtcweb@ietf.org>; Sun, 31 Jul 2011 14:23:43 -0700 (PDT)
Received: from pool-98-111-140-38.phlapa.fios.verizon.net ([98.111.140.38] helo=[192.168.1.12]) by arthur.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1QndUB-00011H-Dv for rtcweb@ietf.org; Sun, 31 Jul 2011 16:23:47 -0500
Message-ID: <4E35C78F.1070402@jesup.org>
Date: Sun, 31 Jul 2011 17:22:23 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <9EF49A9D-7F17-4E92-AECA-55BC7ABC7339@gmail.com> <4E354B2C.2040505@alvestrand.no>
In-Reply-To: <4E354B2C.2040505@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - arthur.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Possible New Cases - Emergency Services Call & 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: Sun, 31 Jul 2011 21:23:44 -0000

On 7/31/2011 8:31 AM, Harald Alvestrand wrote:
> On 07/30/11 07:03, Paul Beaumont wrote:
>> This was mentioned is the initial RTCWeb session at IETF 81 but just 
>> to make sure it has been captured and understood.
>>
>> (1) Please can a separate use case be added for an Emergency Services 
>> telephony call (eg 999 in UK, 112 in EU, 911 in NA, etc).
> I am skeptical to adding this use case. The most important issues and 
> complications that ES brings to the table are with call setup, which I 
> believe is outside of what RTCWEB should be focusing on. As long as 
> there is nothing special about the media plane issues here, I would 
> prefer not to take it on.

The main media-plane issues that we should focus on (as opposed to the 
services built with it)
are ones that involve making capabilities available to the application, 
such as the aforementioned
ability to turn off VAD or to force a change from a "voice" codec to a 
more "general" codec (and
maybe to allow in this case automatic activation of the camera, but 
that's slightly arguable AND
with the one exception of VRS-911 there's no current support for cameras 
in 911 centers.  Most
of the rest of the requirements fall on the application/service.

-- 
Randell Jesup
randell-ietf@jesup.org