IETF Logo Mail Archive

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

Paul Beaumont <paulbeaumont.ietf@gmail.com> Sat, 30 July 2011 11:03 UTC

Return-Path: <paulbeaumont.ietf@gmail.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 8381621F84DD for <rtcweb@ietfa.amsl.com>; Sat, 30 Jul 2011 04:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 I1-KghSdpw81 for <rtcweb@ietfa.amsl.com>; Sat, 30 Jul 2011 04:03:58 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4D82B21F861E for <rtcweb@ietf.org>; Sat, 30 Jul 2011 04:03:54 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3498498fxe.31 for <rtcweb@ietf.org>; Sat, 30 Jul 2011 04:03:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:content-type:x-mailer:message-id:date:to :content-transfer-encoding:mime-version; bh=1qTzyjHLxzx2UC2fxyS4W4KOs9+OEt6wa7cdXQtgi58=; b=IVuQtgsHUO2tSNA5SldBYyqjWOi9AzDHMB3u8xhKoeW7Pq89rEvhA/7RBE7T0uuE3x 25ZLOQF4vZmIp1MLp37nc+h6Q8RsaTamAfyelYu6bm8nHzi3oznXfnt5z5G3Dn+yL+kk ZYe9dUfITT8R/H2P8H2H+WgRilYDFAh3PyNfo=
Received: by 10.204.5.206 with SMTP id 14mr670727bkw.181.1312023834071; Sat, 30 Jul 2011 04:03:54 -0700 (PDT)
Received: from [10.101.1.222] (static-93.158.79.70.got.public.icomera.com [93.158.79.70]) by mx.google.com with ESMTPS id n11sm794616bkd.14.2011.07.30.04.03.52 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Jul 2011 04:03:53 -0700 (PDT)
From: Paul Beaumont <paulbeaumont.ietf@gmail.com>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: iPad Mail (8J2)
Message-Id: <9EF49A9D-7F17-4E92-AECA-55BC7ABC7339@gmail.com>
Date: Sat, 30 Jul 2011 12:03:09 +0100
To: IETF - RTCWeb <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 8J2)
Subject: [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: Sat, 30 Jul 2011 11:03:58 -0000

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). 

(2) Please can a further separate use case be added for an Emergency Services real time text (eg 18000 in UK, via TextDirect operator to ES operator for hearing impaired persons). FYI today this is a low speed in-band voice band data call on the text leg. Presumably the replacement would be some kind of Presence/Messaging replacement with assured delivery or similar.

Please note these are treated differently today in current networks and I would suggest we aim to preserve the capabilities - subject to discussion in the community, in the right WG - eg ECRIT. These are, using legacy terminology ...

A). Prioritisation in processing of Emergency Services calls above Ordinary Calls, particularly when server in overload.

B). Marking of Emergency Services calls to a specific A-/Calling Party Category to allow them to be identified downstream.

C). Release control modified to B-/Called Party Control with changed RTCWeb browser client behaviour along with indication as to "Off Hook" and "On Hook".

Paul

v2.23.0 | Report a Bug | By Email