1 / 10

Emergency Context Resolution with Internet Technologies (ecrit)

Emergency Context Resolution with Internet Technologies (ecrit) . Hannes Tschofenig, Marc Linsner IETF 65. Administrative Stuff. Blue Sheets! Minute Taker? Jabber Scribe?. Interim Meeting.

roman
Download Presentation

Emergency Context Resolution with Internet Technologies (ecrit)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Administrative Stuff • Blue Sheets! • Minute Taker? • Jabber Scribe?

  3. Interim Meeting • Meeting Minuteshttp://www.ietf-ecrit.org/Interim2006/MeetingMinutes.htmlhttp://www.ietf-ecrit.org/Interim2006/MeetingMinutes.txt • Slides can be found at: http://www.ietf-ecrit.org/Interim2006/ • Jabber Log Files/Original Version: http://www.xmpp.org/ietf-logs/ecrit@ietf.xmpp.org/2006-02-01.htmlhttp://www.xmpp.org/ietf-logs/ecrit@ietf.xmpp.org/2006-02-02.html • Jabber Log Files/Cached Version: http://www.ietf-ecrit.org/Interim2006/Jabber-Log_2006-02-01.htmlhttp://www.ietf-ecrit.org/Interim2006/Jabber-Log_2006-02-02.html

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

  5. 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.txt • draft-schulzrinne-sipping-service-01.txt • Work on draft-ietf-sipping-sos-02.txt stopped. • draft-schulzrinne-sipping-service-01.txt become ECRIT WG item: draft-ietf-ecrit-service-urn-01.txt

  6. 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.

  7. Interim Meeting SummaryBefore Re-Chartering • 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 milestone in the past

  8. Interim Meeting SummaryAfter Re-Chartering • 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-*) in time

  9. Agenda (1/2) o Agenda Bashing / Current Status (Chairs) o Open Issues in the Requirements Document (Roger Marshall) http://www.ietf.org/internet-drafts/draft-ietf-ecrit-requirements-06.txt o Open Issues in the Security Threats Document (Tom Taylor) http://www.ietf.org/internet-drafts/draft-taylor-ecrit-security-threats-03.txt o A Uniform Resource Name for Services(Henning Schulzrinne) http://www.ietf.org/internet-drafts/draft-ietf-ecrit-service-urn-01.txt Input to the service URN DDDS Application (Martin Thomson)

  10. Agenda (2/2) o LoST: A Location-to-Service Translation Protocol (T. Hardie/A. Newton/H. Schulzrinne) http://www.ietf-ecrit.org/cache/draft-hardie-ecrit-lost-00.txt oDiscussion about Future Work - Architecture - Phone BCP - Requirements for Emergency Authority to Citizen Notifications (Steve Norreys) o Agenda Bashing / Current Status (Chairs)

More Related