Presentation on theme: "ECRIT Virtual Interim Meeting 26th February, 2PM EST Marc Linsner Hannes Tschofenig."— Presentation transcript:
ECRIT Virtual Interim Meeting 26th February, 2PM EST Marc Linsner Hannes Tschofenig
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: -the IETF plenary session, -any IETF working group or portion thereof, -the IESG or any member thereof on behalf of the IESG, -the IAB or any member thereof on behalf of the IAB, -any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, -the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979(updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3978 (and RFC 4748) for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.
Logistics The ECRIT Wiki page contains all the necessary information: http://tools.ietf.org/wg/ecrit/trac/wiki
WG Status draft-patel-ecrit-sos-parameter will be AD sponsored (with Gonzalo being the expert reviewer) draft-patel-ecrit-sos-parameter Main WG documents got updated this year LoST Sync WGLC started and good reviews received. Roger is document shepherd. LoST Sync draft-ietf-ecrit-mapping-arch got stuck somewhere in the IESG. draft-ietf-ecrit-mapping-arch Lots of discussions around ECRIT RPH. Marc is document shepherd.ECRIT RPH Final WGLC for PhoneBCP/Framework started.PhoneBCPFramework Btw, feedback on how to work more efficiently in the group is appreciated.
Proposed Milestones Done Informational RFC containing terminology definitions and the requirements Done An Informational document describing the threats and security considerations Done A Standards Track RFC on "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services" Done A Standards Track RFC on "Discovering LoST Servers Using DHCP" Done A Standards Track RFC describing the Location-to-Service Translation (LoST) Protocol Done An Informational document describing the Mapping Protocol Architecture Done Submit 'Location Hiding: Problem Statement and Requirements' to the IESG for consideration as an Informational RFC Done Submit 'Specifying Holes in LoST Service Boundaries' to the IESG for consideration as an Informational RFC Mar 2009 Submit 'Best Current Practice for Communications Services in support of Emergency Calling' to the IESG for consideration as an BCP RFC Mar 2009 Submit 'Framework for Emergency Calling using Internet Multimedia' to the IESG for consideration as an Informational RFC Mar 2009 Submit 'Synchronizing Location-to-Service Translation (LoST) Servers' to the IESG for consideration as an Informational RFC
Planned Charter Update See initial proposal here: – http://www.ietf.org/mail-archive/web/ecrit/current/msg05793.html http://www.ietf.org/mail-archive/web/ecrit/current/msg05793.html In addition to the previously mentioned milestone update we would include the following milestones: – Mar 2009 Submit "IANA Registering a SIP RPH Namespace for Local Emergency Communications" to the IESG for consideration as a Standards Track RFC – Mar 2009 Submit "RFC 5031bis" to the IESG for consideration as a Standards Track RFC – Apr 2009 Submit "Using Imprecise Location for Emergency Context Resolution" to the IESG for consideration as an Informational RFC – May 2009 Submit "Location-to-Service Translation Protocol (LoST) Extensions" to the IESG for consideration as an Informational RFC Suggestion for these two items was to submit them to the RFC Editor directly with expert review from the ECRIT group: – "LoST Classification of Location-based Services" – "LoST Usage for discovering Shelter Services“ Will be sent to Jon at the same time as we get PhoneBCP/Framework sent to the IESG.