1 / 11

Emergency Context Resolution with Internet Technologies (ecrit)

Emergency Context Resolution with Internet Technologies (ecrit). IETF 68, March 2007, Prague Hannes Tschofenig, Marc Linsner. Note Well.

frances-bowers
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) IETF 68, March 2007, Prague Hannes Tschofenig, Marc Linsner

  2. 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 4878) and RFC 3979. 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 (updated by RFC 4878) for details.

  3. Agenda 1. Agenda Bashing, Document Status and Milestones Chairs (10 minutes) 2. WG Future – Chairs (5 min.) 3. Related Emergency Service Activities – Chairs (5 min.) 4. draft-ietf-ecrit-phonebcp-01.txt – Brian Rosen (10 min.) 5. draft-ietf-ecrit-framework-01.txt – Brian Rosen (10 min.) 6. draft-ietf-ecrit-lost-05.txt – Henning Schulzrinne (10 min.) 7. draft-ietf-ecrit-mapping-arch-01.txt – Henning Schulzrinne (10 min.)

  4. Document Status • draft-ietf-ecrit-requirements-13.txt - IESG review AD followup • draft-ietf-ecrit-service-urn-06.txt - IESG review AD followup • draft-ietf-ecrit-security-threats-03.txt - IESG review AD eval • draft-ietf-ecrit-lost-05.txt - finished wglc March 2 – author team working suggested changes • draft-ietf-ecrit-dhc-lost-discovery-00.txt - finished wglc March 2 – draft update submitted • draft-ietf-ecrit-mapping-arch-01.txt - finished wglc March 16; more review necessary • draft-ietf-ecrit-phonebcp-01.txt – more work needed • draft-ietf-ecrit-framework-01.txt – more work needed

  5. Milestones Update Proposal(based on Jan 07 proposal) DONE - Informational RFC containing terminology definitions and the requirements DONE - An Informational document describing the threats and security considerations DONE - A Standards Track RFC describing how to identify a session set-up request is to an emergency response center March 2007 - A Standards Track RFC describing how to route an emergency call based on location information March 2007 - An Informational document describing the Mapping Protocol Architecture March 2007 - An Informational document describing the ECRIT Framework April 2007 - A BCP document describing the emergency call support for devices

  6. ECRIT WG Future • Milestones are well on their way to completion • Nothing new has been proposed that has WG support for new charter items • There may well be other work needed in support of emergency services • New work *may* be outside the current ECRIT charter. Could be done in a newly chartered group • ECRIT shutdown soon?

  7. Joint 3GPP/TISPAN/ECRIT Conf Call • Date: Nov. 15, 2006 • Information available at: • http://www.tschofenig.com/twiki/bin/view/EmergencyServices/EmergencyTopics • Follow-up discussions could be useful

  8. IAB Tech Chat • Slides available at: • http://www.tschofenig.com/twiki/pub/EmergencyServices/IetfEcritRoadMap/Emergency-Services.ppt • Follow-up actions require further discussions

  9. IETF ECRIT/IEEE Meeting • Slides • http://www.tschofenig.com/twiki/pub/EmergencyServices/IetfEcritRoadMap/11-07-0505-01-0000-emergency-services-shortened-tutorial.ppt • http://www.tschofenig.com/twiki/pub/EmergencyServices/IetfEcritRoadMap/LLDP__LLDP-MED_update_for_ECRIT-IEEE,_IETF-68.ppt • Meeting minutes will be distributed this week. • Follow-up actions needed • Review of the ECRIT framework document by the IEEE received this week • ECRIT should review IEEE documents as well • Internal interactions within the IEEE needed

  10. 2nd SDO Emergency Service Coordination Workshop • Host: U.S. Department of Transportation (DOT) • The workshop will be held April 10, 11 & 12, 2007, from 8:30 am – 6:00 pm., in the Jefferson Building of the Library of Congress, located at 101 Independence Avenue SE in Washington, D.C. • http://www.emergency-services-coordination.info/2007/

  11. ATIS Liaison • Slides • http://www.tschofenig.com/twiki/bin/view/EmergencyServices/IetfEcritRoadMap • Scroll down the page and look for ATIS • Reviewers needed • Should be coordinated with GEOPRIV

More Related