Re: [Ecrit] IETF#65 ECRIT Agenda

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Fri, 10 March 2006 16:11 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHkCl-0002jt-1D; Fri, 10 Mar 2006 11:11:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHkCi-0002ja-Mw for ecrit@ietf.org; Fri, 10 Mar 2006 11:11:01 -0500
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FHkCh-0003QC-8L for ecrit@ietf.org; Fri, 10 Mar 2006 11:11:00 -0500
Received: (qmail invoked by alias); 10 Mar 2006 16:10:58 -0000
Received: from socks2.netz.sbs.de (EHLO [192.35.17.25]) [192.35.17.25] by mail.gmx.net (mp022) with SMTP; 10 Mar 2006 17:10:58 +0100
X-Authenticated: #29516787
Message-ID: <4411A50A.8020400@gmx.net>
Date: Fri, 10 Mar 2006 17:10:50 +0100
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: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: [Ecrit] IETF#65 ECRIT Agenda
References: <441139A6.1020306@gmx.net>
In-Reply-To: <441139A6.1020306@gmx.net>
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: 37af5f8fbf6f013c5b771388e24b09e7
Cc: ecrit@ietf.org
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,

I forgot to Henning's draft about "Location-to-URL Mapping Architecture 
and Framework"
http://www.ietf.org/internet-drafts/draft-schulzrinne-ecrit-mapping-arch-00.txt

Sorry.

Ciao
Hannes

Hannes Tschofenig wrote:
> Hi all,
> 
> below you find a first proposal for the agenda.
> 
> A few notes:
> 
> - Our focus is on finishing ongoing work. We will discuss open issues 
> with the req. and service urn draft. Tom has rewritten the threats draft 
> as discussed during the interim meeting (see Tom's mail on this subject).
> 
> - Then, we are going to discuss future work. These presentations aim to 
> solicit feedback from the group whether a particular item should be 
> added to the charter. We have listed a few items but we maybe have 
> forgotten some others. Please let us know if you have more topics to 
> discuss.
> 
> Ciao
> Hannes
> 
> ************************************************************
> 
> Emergency Context Resolution with Internet Technologies WG
> 
> TUESDAY, March 21, 2006
> 
> 0900-1130 Morning Session I
> 
> =====================================================
> 
> CHAIRS:
> 
>    Hannes Tschofenig <Hannes.Tschofenig@siemens.com>
>    Marc Linsner <Marc.Linsner@cisco.com>
> 
> AGENDA
> 
> 
>  o Agenda Bashing / Current Status (Chairs, 15 min)
> 
> 
>  o Requirements (Roger Marshall, 15 min)
>    http://www.ietf.org/internet-drafts/draft-ietf-ecrit-requirements-06.txt
> 
>    Issues raised during WGLC
> 
> 
>  o Security Threats Document (Tom Taylor, 15 min)
> 
>    Discussion of open issues
> 
> 
>  o A Uniform Resource Name for Services (Henning Schulzrinne, 15 min)
>    http://www.ietf.org/internet-drafts/draft-ietf-ecrit-service-urn-01.txt
> 
>    Discussion of open issues
> 
> 
>  o LoST: A Location-to-Service Translation Protocol
>    (T. Hardie/A. Newton/H. Schulzrinne, 30 min)
>    http://www.ietf-ecrit.org/cache/draft-hardie-ecrit-lost-00.txt
> 
>    Current status, open issues and next steps
> 
> 
>  o Discussion about future work (All, 75 min)
> 
>    Emergency Context Routing of Internet Technologies
>    Architecture Considerations
> 
> http://www.ietf.org/internet-drafts/draft-polk-newton-ecrit-arch-considerations-02.txt 
> 
> 
>    Best Current Practice for Communications Services in support of
>    Emergency Calling
>    http://www.ietf.org/internet-drafts/draft-rosen-ecrit-phonebcp-00.txt
> 
>    Analyzing ECRIT Mapping of a Location to an
>    Emergency URI for Emergency Calling
> 
> http://www.ietf.org/internet-drafts/draft-polk-ecrit-mapping-events-00.txt
> 
>    ECRIT Mapping During Session Initiation Protocol Registration
> 
> http://www.ietf.org/internet-drafts/draft-polk-ecrit-mapping-during-registration-00.txt 
> 
> 
>    Using the Session Initiation Protocol REGISTER Method
>    To Obtain an Emergency Dialstring
> 
> http://www.ietf.org/internet-drafts/draft-polk-ecrit-emergency-dialstring-00.txt 
> 
> 
>    A Dynamic Host Configuration Protocol Option for
>    Requesting and Receiving Uniform Resource Identifiers
>    http://www.ietf.org/internet-drafts/draft-polk-dhc-uri-03.txt
> 
> 
> _______________________________________________
> 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