1 / 6

Emergency Context Resolution with Internet Technologies (ecrit)

Explore the latest advancements in using Internet technologies for handling emergency situations, including SIP-based calls and requirements for IP telephony services. This session covers essential aspects and future steps in emergency service development.

jeannineh
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. Hannes Tschofenig, Marc Linser Chairs Emergency Context Resolution with Internet Technologies (ecrit)

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

  3. 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 3667 and RFC 3668.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 3667 for details.

  4. Agenda (1/2) Agenda (Chairs, 5 min) Requirements for Session Initiation Protocol (SIP)-based Emergency Calls / Emergency Services for Internet Telephony based on the Session Initiation Protocol (SIP) (H. Schulzrinne, 15 min) http://www.ietf.org/internet-drafts/draft-schulzrinne-sipping-emergency-req-01.txt http://www.ietf-ecrit.org/cache/draft-schulzrinne-sipping-sos-04.txt Emergency Call Requirements for IP Telephony Services In Japan (M. Kawanishi, 10 min) http://www.ietf.org/internet-drafts/draft-arai-ecrit-japan-req-00.txt

  5. Agenda (2/2) NENA Requirements for Emergency Call processing (B. Rosen, 10 min) http://www.ietf.org/internet-drafts/draft-rosen-nena-ecrit-requirements-00.txt The basic requirements for emergency services via the Internet (R. Stastny, 10 min) http://www.ietf.org/internet-drafts/draft-stastny-ecrit-requirements-00.txt ECRIT Location Scope Requirements (J. Winterbottom, 10 min) http://www.ietf.org/internet-drafts/draft-winterbottom-ecrit-location-scope-req-00.txt Next Steps and AOB (Chairs, 5 min)

  6. Next Steps Charter Milestone: • Apr 05:  Informational RFC containing terminology definitions and the requirements • Please read the available documents and provide comments on the requirements. • We need a requirements WG document

More Related