Emergency Context Resolution with Internet Technologies (ecrit)
---------------------------------------------------------------

Charter
Last Modified: 2009-09-30

Current Status: Active Working Group

Chair(s):
    Hannes Tschofenig  <[email protected]>
    Marc Linsner  <[email protected]>

Real-time Applications and Infrastructure Area Director(s):
    Robert Sparks  <[email protected]>
    Cullen Jennings  <[email protected]>

Real-time Applications and Infrastructure Area Advisor:
    Cullen Jennings  <[email protected]>

Secretary(ies):
    Roger Marshall  <[email protected]>

Mailing Lists:
    General Discussion:[email protected]
    To Subscribe:      https://www.ietf.org/mailman//listinfo/ecrit
    Archive:           http://www.ietf.org/mail-archive/web/ecrit/current/maillist.html

Description of Working Group:

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 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 groups
such as NENA and ETSI EMTEL, 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 independent.

This working group cares about privacy and security concerns, and will
address them within its documents.

Goals and Milestones:

  Done         Informational RFC containing terminology definitions and the
               requirements

  Done         An Informational document describing the threats and security
               considerations

  Done         A Standards Track RFC describing how to identify a session
               set-up request is to an emergency response center

  Done         A Standards Track RFC describing how to route an emergency call
               based on location information

  Done         An Informational document describing the Mapping Protocol
               Architecture

  Done         Submit 'Location Hiding: Problem Statement and Requirements' to
               the IESG for consideration as an Informational RFC.

  Done         Submit 'Framework for Emergency Calling using Internet
               Multimedia' to the IESG for consideration as an Informational
               RFC.

  Done         Submit 'Best Current Practice for Communications Services in
               support of Emergency Calling' to the IESG for consideration as
               a BCP document

  Oct 2009       Submit 'Synchronizing Location-to-Service Translation (LoST)
               Protocol based Service Boundaries and Mapping Elements' to the
               IESG for consideration as an Experimental RFC

  Dec 2009       Submit "LoST Extension for returning Boundary Information for
               Services" to the IESG for consideration as an Experimental RFC

  Mar 2010       Submit "Using Imprecise Location for Emergency Call Routing" to
               the IESG for consideration as an Informational RFC


Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Oct 2006 Jan 2010   <draft-ietf-ecrit-phonebcp-14.txt>
               Best Current Practice for Communications Services in support of
               Emergency Calling

Oct 2006 Jul 2009   <draft-ietf-ecrit-framework-10.txt>
               Framework for Emergency Calling using Internet Multimedia

Jun 2008 Jul 2009   <draft-ietf-ecrit-location-hiding-req-02.txt>
               Location Hiding: Problem Statement and Requirements

Jun 2008 Oct 2008   <draft-ietf-ecrit-specifying-holes-01.txt>
               Specifying Holes in LoST Service Boundaries

Jul 2008 Oct 2009   <draft-ietf-ecrit-lost-sync-08.txt>
               Synchronizing Location-to-Service Translation (LoST) Protocol
               based Service Boundaries and Mapping Elements

Oct 2009 Feb 2010   <draft-ietf-ecrit-lost-servicelistboundary-02.txt>
               Location-to-Service Translation Protocol (LoST) Extension:
               <serviceListBoundary>

Oct 2009 Jan 2010   <draft-ietf-ecrit-rough-loc-01.txt>
               Using Imprecise Location for Emergency Context Resolution

Request For Comments:

 RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC5012 I    Jan 2008    Requirements for Emergency Context Resolution with
                      Internet Technologies

RFC5031 PS   Jan 2008    A Uniform Resource Name (URN) for Emergency and Other
                      Well-Known Services

RFC5069 I    Jan 2008    Security Threats and Requirements for Emergency Call
                      Marking and Mapping

RFC5222 PS   Aug 2008    LoST: A Location-to-Service Translation Protocol

RFC5223 PS   Aug 2008    Discovering Location-to-Service Translation (LoST)
                      Servers Using the Dynamic Host Configuration Protocol
                      (DHCP)

RFC5582 I    Sep 2009    Location-to-URL Mapping Architecture and Framework

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.