[Ecrit] Rechartering (Update)
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Tue, 02 May 2006 08:22 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Faq9H-0006Nq-Ij; Tue, 02 May 2006 04:22:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Faq9F-0006Lc-Ip for ecrit@ietf.org; Tue, 02 May 2006 04:22:21 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Faq9E-0006DT-59 for ecrit@ietf.org; Tue, 02 May 2006 04:22:21 -0400
Received: (qmail invoked by alias); 02 May 2006 08:22:18 -0000
Received: from socks2.netz.sbs.de (EHLO [192.35.17.25]) [192.35.17.25] by mail.gmx.net (mp043) with SMTP; 02 May 2006 10:22:18 +0200
X-Authenticated: #29516787
Message-ID: <445716BA.7090601@gmx.net>
Date: Tue, 02 May 2006 04:22:18 -0400
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: 82c9bddb247d9ba4471160a9a865a5f3
Subject: [Ecrit] Rechartering (Update)
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, here is the latest list of milesontes: ----------- 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-ietf-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-ietf-ecrit-lost-*) August 2006 An Informational document describing the Mapping Protocol Architecture (Example document: "Location-to-URL Mapping Architecture and Framework"; draft-schulzrinne-ecrit-mapping-arch-*) December 2006 An Informational document describing the ECRIT Framework (Example documents are draft-schulzrinne-sipping-emergency-arch-02.txt and draft-polk-newton-ecrit-arch-considerations-02.txt) February 2006 A BCP document describing the emergency call support for devices. (Example document: "Best Current Practice for Communications Services in support of Emergency Calling"; draft-rosen-ecrit-phonebcp-*) --------- Comments? Ciao Hannes _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www1.ietf.org/mailman/listinfo/ecrit
- [Ecrit] Rechartering (Update) Hannes Tschofenig
- Re: [Ecrit] Rechartering (Update) James M. Polk
- Re: [Ecrit] Rechartering (Update) Hannes Tschofenig
- Re: [Ecrit] Rechartering (Update) James M. Polk