Re: [Ecrit] Rechartering Discussion

"James M. Polk" <jmpolk@cisco.com> Wed, 19 April 2006 03:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FW3hH-0002AU-VD; Tue, 18 Apr 2006 23:49:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FW3hG-00027X-Hg for ecrit@ietf.org; Tue, 18 Apr 2006 23:49:42 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW3hG-0001XD-6y for ecrit@ietf.org; Tue, 18 Apr 2006 23:49:42 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 18 Apr 2006 20:49:42 -0700
X-IronPort-AV: i="4.04,132,1144047600"; d="scan'208"; a="269567814:sNHT30842670"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k3J3nfRT006715; Tue, 18 Apr 2006 20:49:41 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Apr 2006 20:49:41 -0700
Received: from jmpolk-wxp.cisco.com ([10.89.20.22]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Apr 2006 20:49:40 -0700
Message-Id: <4.3.2.7.2.20060418224723.02988ec8@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 18 Apr 2006 22:49:39 -0500
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, ecrit@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ecrit] Rechartering Discussion
In-Reply-To: <44453E33.7020700@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 19 Apr 2006 03:49:41.0065 (UTC) FILETIME=[49ADE390:01C66364]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc:
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

Hannes

Brian and I are working on the last item listed, so we know we can finish 
that one.

I know the design team will churn out an Arch ID, so that one can be finished.

I have no input, other than review and comments, into Hennings LUMP Arch ID.


At 09:29 PM 4/18/2006 +0200, Hannes Tschofenig wrote:
>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

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