[Ecrit] Rechartering Discussion

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Tue, 18 April 2006 19:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVvtk-0000GS-KI; Tue, 18 Apr 2006 15:30:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVvtj-0000GM-Us for ecrit@ietf.org; Tue, 18 Apr 2006 15:30:03 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FVvti-00025e-Ir for ecrit@ietf.org; Tue, 18 Apr 2006 15:30:03 -0400
Received: (qmail invoked by alias); 18 Apr 2006 19:30:01 -0000
Received: from p549879CF.dip.t-dialin.net (EHLO [192.168.2.33]) [84.152.121.207] by mail.gmx.net (mp011) with SMTP; 18 Apr 2006 21:30:01 +0200
X-Authenticated: #29516787
Message-ID: <44453E33.7020700@gmx.net>
Date: Tue, 18 Apr 2006 21:29:55 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ecrit@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Subject: [Ecrit] Rechartering Discussion
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ecrit.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Errors-To: ecrit-bounces@ietf.org

Hi all,

at the last ECRIT WG meeting we had a discussion about rechartering. Jon 
  indicated that it might be a good time to start a discussion about the 
text. Here is a first attempt:

-------------

March 2006	  	Informational RFC containing terminology
definitions and the requirements

(Draft: "Requirements for Emergency Context Resolution with Internet 
Technologies"; draft-ietf-ecrit-requirements-*)

May 2006	  	An Informational document describing the threats
and security considerations

(Example document: "Security Threats and Requirements for Emergency Call 
Marking and Mapping"; draft-taylor-ecrit-security-threats-*)

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

(Draft: "A Uniform Resource Name (URN) for Services"; 
draft-ietf-ecrit-service-urn-*)

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

(Example document: "LoST: A Location-to-Service Translation Protocol"; 
draft-hardie-ecrit-lost-*)

TBD TBD           An Informational document describing the Mapping 
Protocol Architecture

(Example document: "Location-to-URL Mapping Architecture and Framework";
draft-schulzrinne-ecrit-mapping-arch-*)

TBD TBD           An Informational document describing the ECRIT 
Architecture

(Example documents are draft-schulzrinne-sipping-emergency-arch-02.txt 
and draft-polk-newton-ecrit-arch-considerations-02.txt)

TBD TBD           A BCP RFC describing the emergency call support for 
devices.

(Example document: "Best Current Practice for Communications Services in 
support of Emergency Calling"; draft-rosen-ecrit-phonebcp-*)

-------------

Please note that the milestone date is missing for the last 3 items. I 
would like to solicit input from the group: When can we finish these 
documents?

Ciao
Hannes

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit