[Ecrit] draft-ietf-ecrit-phonebcp-05.txt: Which devices and services should support emergency calls
"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Tue, 14 October 2008 12:31 UTC
Return-Path: <ecrit-bounces@ietf.org>
X-Original-To: ecrit-archive@megatron.ietf.org
Delivered-To: ietfarch-ecrit-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F80E3A6826; Tue, 14 Oct 2008 05:31:07 -0700 (PDT)
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A70FC3A6826 for <ecrit@core3.amsl.com>; Tue, 14 Oct 2008 05:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.286
X-Spam-Level:
X-Spam-Status: No, score=-5.286 tagged_above=-999 required=5 tests=[AWL=1.313, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvzDQfBbzUWT for <ecrit@core3.amsl.com>; Tue, 14 Oct 2008 05:31:04 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 78FB23A67EA for <ecrit@ietf.org>; Tue, 14 Oct 2008 05:31:04 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id m9EBnWiL003997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ecrit@ietf.org>; Tue, 14 Oct 2008 13:49:32 +0200
Received: from demuexc023.nsn-intra.net (webmail.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id m9EBnVMT003464 for <ecrit@ietf.org>; Tue, 14 Oct 2008 13:49:32 +0200
Received: from demuexc024.nsn-intra.net ([10.159.32.11]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Oct 2008 13:49:31 +0200
Received: from FIESEXC007.nsn-intra.net ([10.159.0.15]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Oct 2008 13:49:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 14:49:17 +0300
Message-ID: <C41BFCED3C088E40A8510B57B165C162943ACC@FIESEXC007.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-ecrit-phonebcp-05.txt: Which devices and services should support emergency calls
Thread-Index: Ackt8uNyGncjF1p3QL6MPh/0uW5Drg==
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: ECRIT <ecrit@ietf.org>
X-OriginalArrivalTime: 14 Oct 2008 11:49:27.0517 (UTC) FILETIME=[E93CA0D0:01C92DF2]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 151667::081014134932-40300BB0-ACD21AD9/0-0/0-15
X-purgate-size: 3380/0
Subject: [Ecrit] draft-ietf-ecrit-phonebcp-05.txt: Which devices and services should support emergency calls
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ecrit-bounces@ietf.org
Errors-To: ecrit-bounces@ietf.org
ED-1 A device or application SHOULD support emergency calling if a user could reasonably expect to be able to place a call for help with the device. SP-1 If a device or application expects to be able to place a call for help, the service provider that supports it MUST facilitate emergency calling. ED-2 Devices that create media sessions and exchange audio, video and/or text, and have the capability to establish sessions to a wide variety of addresses, and communicate over private IP networks or the Internet, SHOULD support emergency calls. This is nice text and nice requirements. Still, I believe it would improve the credibility of the document if we acknowledge the fact that we aren't regulating the deployment. Maybe we can soften these requirements a bit and write something like. " As end users are typically not aware of the details of the technology they are using we below list the following high-level goals for the implementation and deployment of emergency services functionality: ED-1 / SP-1 It is RECOMMENDED that a device or application supports emergency calling if a user could reasonably expect to be able to place a call for help with the device. It is therefore RECOMMENDED that devices that create media sessions and exchange audio, video and/or text, and have the capability to establish sessions to a wide variety of communication end points, and deliver data over private IP networks or the Internet ,to support emergency calls. " The same is true for requirements listed below. In the past I suggested to soften them a bit and to add references about current regulation. One, however, has to acknowledge that these numbers are not applicable to all juristictions. 6.2.2. Access network "wire database" location information It is RECOMMENDED that interior location be provided when spaces exceed approximately 650 square meters. 6.2.3. End-system measured location information ED-16/INT-7 Devices MAY support end-system measured location. Uncertainty of less than 100 m with 95% confidence SHOULD be available for dispatch. ED-17/INT-8/AN-8 Devices that support endpoint measuring of location MUST have at least a coarse location capability (typically <1km accuracy when not location hiding) for routing of calls. The location mechanism MAY be a service provided by the access network. 6.2.4. Network-measured location information AN-9 Access networks MAY provide network-measured location determination. Wireless access network which do not support network measured location MUST require that all devices connected to the network have end-system measured location. Uncertainty of less than 100 m with 95% confidence SHOULD be available for dispatch. AN-10 Access networks that provide network measured location MUST have at least a coarse location (typically <1km when not location hiding) capability at all times for routing of calls. AN-11 Access networks with range of <10 meters (e.g. personnal area networks such as Bluetooth MUST provide a location to mobile devices connected to them. The location provided SHOULD be that of the access point location unless a more accurate mechanism is provided. _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit
- [Ecrit] draft-ietf-ecrit-phonebcp-05.txt: Which d… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] draft-ietf-ecrit-phonebcp-05.txt: Whi… Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-phonebcp-05.txt: Whi… Tschofenig, Hannes (NSN - FI/Espoo)