Re: [Sipping-emergency] New revision of proposed ECRIT charter
Tom Taylor <taylor@nortelnetworks.com> Wed, 13 October 2004 22:25 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20499 for <sipping-emergency-web-archive@ietf.org>; Wed, 13 Oct 2004 18:25:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHrjs-0001ui-7h for sipping-emergency-web-archive@ietf.org; Wed, 13 Oct 2004 18:36:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHrMU-0006HS-DR; Wed, 13 Oct 2004 18:12:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHr13-0001Dd-E5 for sipping-emergency@megatron.ietf.org; Wed, 13 Oct 2004 17:50:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14455 for <sipping-emergency@ietf.org>; Wed, 13 Oct 2004 17:50:36 -0400 (EDT)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHrC4-0000LT-F0 for sipping-emergency@ietf.org; Wed, 13 Oct 2004 18:02:00 -0400
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9DLo1H18921; Wed, 13 Oct 2004 17:50:02 -0400 (EDT)
Received: from [47.130.17.208] (acart551.ca.nortel.com [47.130.17.208]) by zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SPNPMB95; Wed, 13 Oct 2004 17:50:02 -0400
Message-ID: <416DA308.7060302@nortelnetworks.com>
Date: Wed, 13 Oct 2004 17:50:00 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>, sipping-emergency@ietf.org
Subject: Re: [Sipping-emergency] New revision of proposed ECRIT charter
References: <7927C67249E4AD43BC05B539AF0D129801AF423D@stntexch04.cis.neustar.com>
In-Reply-To: <7927C67249E4AD43BC05B539AF0D129801AF423D@stntexch04.cis.neustar.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: sipping-emergency.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Sender: sipping-emergency-bounces@ietf.org
Errors-To: sipping-emergency-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: 7bit
I forgot to say I'm happy with the charter as rewritten. I'll volunteer my services as chair or editor. Peterson, Jon wrote: > All, > > Here's a new version of the ECRIT charter for your consideration, that > attempts to incorporate the discussion over the past couple of weeks. > > Any further issues? > > Jon Peterson > NeuStar, Inc. > > --- > > Emergency Context Resolution with Internet Technologies (ECRIT) > > Transport Area Director(s): > Allison Mankin <mankin@psg.com> > Jon Peterson <jon.peterson@neustar.biz> > > Transport Area Advisor: TBD > > Working Group Chairs: TBD > > In a number of areas the public switched telephone network (PSTN) > has been configured to recognize an explicitly specified number (commonly > one that is short and easily memorized) as a call for emergency services. > These numbers (e.g. 911, 112) relate to an emergency service context and > depend > on a broad, regional configuration of service contact methods and a > geographically > constrained context of service delivery. These calls are intended to be > delivered to > special call centers equipped to manage emergency response. Successful > delivery > of an emergency service call within those systems requires both an > association of > the physical location of the originator with an appropriate emergency > service > center and call routing to deliver the call to the center. > > Calls placed using Internet technologies do not use the same systems to > achieve those goals, and the common use of overlay networks and tunnels > (either as VPNs or for mobility) makes meeting them more challenging. There > are, however, Internet technologies available to describe location and to > manage call routing. This working group will describe when these may be > appropriate > and how they may be used. Explicitly outside the scope of this group > is the question of pre-emption or prioritization of emergency services > traffic. This group is considering emergency services calls which might be > made by > any user of the PSTN or Internet, as opposed to government or military > services that may impose very different authentication and routing > requirements. > > The group will show how the availability of location data and call routing > information > at different steps in session setup would enable communication between a > user > and a relevant emergency response center. Though the term "call routing" is > used in this > document, it should be understood that some of the mechanisms which > will be described might be used to enable other types of media > streams. Video and text messaging, for example, might be used to request > emergency services. > > While this group anticipates a close working relationship with NENA, any > solution > presented must be useful regardless of jurisdiction, and it must be possible > to > use without a single, central authority. Further, it must be possible for > multiple > delegations within a jurisdiction to be handled independently, as call > routing > for specific emergency types may be indepdent. > > Deliverables: > > Informational RFC containing terminology definitions and the requirements. > > A BCP describing how to identify a session set-up request is to an emergency > response center. > > A BCP describing strategies for associating session originators with > physical locations. > > A BCP or Standards Track RFC describing how to route an emergency call > based on location information. Either within that document or as a separate > document, a description of how error conditions are returned to the session > originator and how to test for error conditions without activating an > emergency > response. Privacy concerns related to that testing must be addressed > in this document set. > > A BCP describing how to discover the media stream types an ERC supports. > > An Informational document describing the threats and security > considerations. > > > _______________________________________________ > Sipping-emergency mailing list > Sipping-emergency@ietf.org > https://www1.ietf.org/mailman/listinfo/sipping-emergency > > -- Tom Taylor Carrier VoIP Standards Development Nortel Networks Phone +1 613 763 1496 (ESN 393-1496) E-mail: taylor@nortelnetworks.com _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- [Sipping-emergency] New revision of proposed ECRI… Peterson, Jon
- RE: [Sipping-emergency] New revision of proposed … Brian Rosen
- RE: [Sipping-emergency] New revision of proposed … Marc Linsner
- Re: [Sipping-emergency] New revision of proposed … Henning Schulzrinne
- RE: [Sipping-emergency] New revision of proposed … wilcox
- Re: [Sipping-emergency] New revision of proposed … Jonathan Rosenberg
- Re: [Sipping-emergency] New revision of proposed … Tom Taylor
- RE: [Sipping-emergency] New revision of proposed … Roger Marshall
- RE: [Sipping-emergency] New revision of proposed … Peterson, Jon
- RE: [Sipping-emergency] New revision of proposed … Roger Marshall
- RE: [Sipping-emergency] New revision of proposed … Abbott, Nadine B.
- RE: [Sipping-emergency] New revision of proposed … James M. Polk
- RE: [Sipping-emergency] New revision of proposed … Tschofenig Hannes
- RE: [Sipping-emergency] New revision of proposed … James M. Polk
- Re: [Sipping-emergency] New revision of proposed … Henning Schulzrinne
- RE: [Sipping-emergency] New revision of proposed … Tschofenig Hannes
- Re: [Sipping-emergency] New revision of proposed … Henning Schulzrinne
- Re: [Sipping-emergency] New revision of proposed … James M. Polk
- Re: [Sipping-emergency] New revision of proposed … Henning Schulzrinne
- RE: [Sipping-emergency] New revision of proposed … Abbott, Nadine B.