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

 Charter
 Last Modified: 2009-09-30

 Current Status: Active Working Group

 Chair(s):
     Hannes Tschofenig  <Hannes.Tschofenig@gmx.net>
     Marc Linsner  <marc.linsner@cisco.com>

 Real-time Applications and Infrastructure Area Director(s):
     Robert Sparks  <rjsparks@nostrum.com>
     Cullen Jennings  <fluffy@cisco.com>

 Real-time Applications and Infrastructure Area Advisor:
     Cullen Jennings  <fluffy@cisco.com>

 Secretary(ies):
     Roger Marshall  <rmarshall@telecomsys.com>

 Mailing Lists: 
     General Discussion:ecrit@ietf.org
     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:

No description available


 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 Jul 2009   <draft-ietf-ecrit-phonebcp-13.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 Aug 2009   <draft-ietf-ecrit-lost-sync-07.txt>
                Synchronizing Location-to-Service Translation (LoST) Protocol 
                based Service Boundaries and Mapping Elements 

 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