Re: [Ecrit] ECRIT Agenda Version 3

[Cullen Jennings <[e-mail]>]

Thanks for doing this - seems good to me and I agree with Martin and Brian on I don't see any issues with framework, phonebcp, or draft-ietf-ecrit-specifying-holes that need agenda time.

On Mar 16, 2010, at 10:39 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:

> This mail was just in response to Cullen's note about the existing work items. So, I went through the list to explain that they are doing  fine.
>  
> The previous agenda has not changed and Marc & Richard need to figure out how to arrange the time.
>  
> Ciao
> Hannes
> 
> From: ext Winterbottom, James [mailto:[e-mail]] 
> Sent: 16 March, 2010 12:38
> To: Tschofenig, Hannes (NSN - FI/Espoo); [e-mail]; [e-mail]
> Cc: [e-mail]
> Subject: RE: Re: [Ecrit] ECRIT Agenda Version 3
> 
> Does this mean that none of the “intention” documents listed in the previous agendas have made the cut?
>  
> Cheers
> James
>  
>  
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Tschofenig, Hannes (NSN - FI/Espoo)
> Sent: Wednesday, 17 March 2010 3:29 AM
> To: [e-mail]; [e-mail]
> Cc: [e-mail]
> Subject: Re: [Ecrit] ECRIT Agenda Version 3
>  
> --- I let the new chairs figure out how to arrange the items properly but since I had written the mail already find my response below.
> 
> Let us take a look at the list of WG items we have:
> 
> Best Current Practice for Communications Services in support of Emergency Calling (107967 bytes)
> Framework for Emergency Calling using Internet Multimedia (96432 bytes)
> 
>  --> Brian says he does not need time for the two items above.
> 
> Location Hiding: Problem Statement and Requirements (20127 bytes)
> 
>  --> This document does not seem to require time. At least from the IESG review feedback I have not seen anything dramatic.
> 
> Specifying Holes in LoST Service Boundaries (22007 bytes)
> 
> There were a punch of review comments but Martin did not send us a request for a presentation. I assume that he feels comfortable addressing the comments. Is this correct, Martin?
> 
> Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements (50425 bytes)
> 
> The comments on the list by Alex got addressed and I shipped a new version. I don't believe it would make sense to discuss the comment again.
> 
> IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications (19327 bytes)
> 
> Marc is responsible for this work and I have not received a request for a presentation slot.
> 
> LoST Service List Boundary Extension (26226 bytes)
> Using Imprecise Location for Emergency Context Resolution (39455 bytes)
> 
> My understanding of the two documents from above is that they are essentially done; we are only waiting for the feedback from the APPS directorate on the Relax NG schema.
> 
> Ciao
> Hannes
> 
> Brian Rosen wrote:
> 
> I don't see any issues with -phonebcp and -framework that would need meeting
> time.
> 
> Brian
> 
> 
> On 3/12/10 6:09 PM, "Cullen Jennings" <[e-mail]> wrote:
> 
> This is a lot of things to fit in 2.5 hours. It's possible that if I saw how
> much time each had it would all look find but I'm very worried about just
> starting new work and not finishing things. I want to be sure there is no time
> required for any of the current WG items.
> 
> Cullen
> 
> 
> On Mar 5, 2010, at 2:32 AM, Hannes Tschofenig wrote:
> 
> ECRIT Meeting Agenda (Version 3)
> ================================
> 
> MONDAY, March 22, 2010
> 0900-1130 Morning Session I
> Room: Palos Verdes
> 
> * Agenda Bashing and Status Update (Marc, Hannes, Roger)
> 
> * PSAP Callback (TBD)
> http://trac.tools.ietf.org/wg/ecrit/trac/wiki
> http://tools.ietf.org/id/draft-schulzrinne-ecrit-psap-callback
> 
> Intention: Discuss potential feedback from emergency services groups on
> the requirements for this work.
> 
> * Unauthenticated emergency services (Dirk)
> http://tools.ietf.org/id/draft-schulzrinne-ecrit-unauthenticated-access
> 
> Intention: Determine next steps. The group wants to work on it but there
> are still lots of open issues and re-chartering is required to add it to
> the milestone list.
> * Transformations ID (James P.)
> http://tools.ietf.org/id/draft-polk-ecrit-lost-transformations-urn
> 
> Intention: TBD.
> 
> * ECRIT Direct (James W.)
> http://tools.ietf.org/id/draft-winterbottom-ecrit-direct
> 
> Intention: TBD.
> * Additional Data (Brian)
> http://tools.ietf.org/id/draft-rosen-ecrit-additional-data
> 
> Intention: Initial document version. Presentation of the history and the
> origin of the work. Determine interest.
> 
> * Data Only Emergency Calls (Brian)
> http://tools.ietf.org/id/draft-rosen-ecrit-data-only-ea
> 
> Intention: TBD.
> 
> * Completing the Request Location (Brian)
> http://tools.ietf.org/id/draft-rosen-ecrit-completed-location-00.txt
> 
> Intention: Discussion whether the group should work on this document. The
> document is making a normative change to RFC 5222.
> 
> * Service URN Update and Service Classification (Henning)
> http://tools.ietf.org/id/draft-forte-ecrit-service-classification
> http://tools.ietf.org/html/draft-forte-ecrit-service-urn-policy
> Intention: Documents are a bit stuck although group agreed to work on
> it. Henning will present a way forward.
> * Emergency Text Messaging using SIP MESSAGE (Henning)
> http://tools.ietf.org/id/draft-kim-ecrit-text-00.txt
> 
> Intention: Discussion about what the group should do in this area.
> 
> * Describing Boundaries for Civic Addresse
> http://tools.ietf.org/id/draft-thomson-ecrit-civic-boundary-00.txt
> 
> Intention: Discussion whether the group should work on this doc.
> _______________________________________________
> Ecrit mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ecrit
> 
>  
> Cullen Jennings
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> 
> 
> 
> _______________________________________________
> Ecrit mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ecrit
> 
> 
> 
> 
> 


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html