Emergency Context Resolution with Internet Technologies (ecrit) Hannes Tschofenig, Marc Linsner IETF 65

Administrative Stuff Blue Sheets! Minute Taker? Jabber Scribe?

Interim Meeting Meeting Minutes ecrit.org/Interim2006/MeetingMinutes.txt ecrit.org/Interim2006/MeetingMinutes.txt Slides can be found at: Jabber Log Files/Original Version: Jabber Log Files/Cached Version:

Interim Meeting Summary Requirements WG got the impression that the document was ready for WGLC. Started at 28 th February Ended 14 th March A number of WGLC comments received. A first update was submitted (see draft-ietf-ecrit-requirements-06.txt) but more modifications are needed.draft-ietf-ecrit-requirements-06.txt Issues will be added to the issue tracker:

Interim Meeting Summary Emergency Identifier Charter item for identifying a session set-up request to an emergency response center. Two proposals: –draft-ietf-sipping-sos-02.txtdraft-ietf-sipping-sos-02.txt –draft-schulzrinne-sipping-service-01.txtdraft-schulzrinne-sipping-service-01.txt Work on draft-ietf-sipping-sos-02.txt stopped.draft-ietf-sipping-sos-02.txt draft-schulzrinne-sipping-service-01.txt become ECRIT WG item: draft-ietf-ecrit-service-urn- 01.txtdraft-schulzrinne-sipping-service-01.txtdraft-ietf-ecrit-service-urn- 01.txt

Interim Meeting Summary Mapping Protocols Mapping Protocol Proposals: –LUMP: draft-schulzrinne-ecrit-lump-01.txt –DNS-SOS: draft-rosen-dns-sos-03.txt –ECON-IRIS: draft-hardie-ecrit-iris-03.txt Proposal: –Merge LUMP & ECON-IRIS (=> LoST) – Work on DNS-SOS was stopped.

Interim Meeting Summary Before Re-Chartering milestone in the past Apr 05 Informational RFC containing terminology definitions and the requirements May 05 An Informational document describing the threats and security considerations Aug 05 A BCP describing how to identify a session set- up request is to an emergency response center Aug 05 A BCP describing strategies for associating session originators with physical locations Aug 05 A BCP or Standards Track RFC describing how to route an emergency call based on location information Nov 05 A BCP describing how to discover the media stream types an ERC supports

Interim Meeting Summary After Re-Chartering in time Mar 06 Informational RFC containing terminology definitions and the requirements (Draft: "Requirements for Emergency Context Resolution with Internet Technologies"; draft-ietf-ecrit-requirements-*) May 06 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-*) Mar 06 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 06 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-*)

Agenda (1/2) o Agenda Bashing / Current Status (Chairs) o Open Issues in the Requirements Document (Roger Marshall) o Open Issues in the Security Threats Document (Tom Taylor) o A Uniform Resource Name for Services (Henning Schulzrinne) Input to the service URN DDDS Application (Martin Thomson)

Agenda (2/2) o LoST: A Location-to-Service Translation Protocol (T. Hardie/A. Newton/H. Schulzrinne) o Discussion about Future Work - Architecture - Phone BCP - Requirements for Emergency Authority to Citizen Notifications (Steve Norreys) o Agenda Bashing / Current Status (Chairs)