Emergency Context Resolution with Internet Technologies (ecrit)

1
Emergency Context Resolution with Internet
Technologies (ecrit)

• Hannes Tschofenig, Marc Linsner
• IETF 66, Montreal, June 2006

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
  functionAll IETF Contributions are subject to
  the rules of RFC 3978 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 for details.

3
Administrative Stuff

• Blue Sheets!
• Minute Taker?
• Jabber Scribe?

4
WG Documents

• WGLC passed and document ready for
  IESGdraft-ietf-ecrit-requirements-10.txt
• WGLC passed and document ready for
  IESGdraft-ietf-ecrit-service-urn-03.txt
• WGLC passed, small update necessarydraft-ietf-ec
  rit-security-threats-02.txt
• LoST A Location-to-Service Translation Protocol
• draft-ietf-ecrit-lost-00.txt
• First WG version of the merged mapping
  protocol draft. Issue Tracker at
  http//www.tschofenig.com8080/lost/

5
Non-WG Items

• Framework for Emergency Calling in Internet
  Multimedia
• draft-rosen-ecrit-framework-00.txt
• Work done in a design team lead by Brian Rosen
  James Polk
• Location-to-URL Mapping Architecture and
  Framework
• draft-schulzrinne-ecrit-mapping-arch-00.txt
• Best Current Practice for Communications Services
  in support of Emergency Calling
• draft-rosen-sos-phonebcp-01.txt

6
Rechartering

• July 2006 Informational RFC containing
  terminology definitions and the requirements
• (Draft "Requirements for Emergency Context
  Resolution with Internet Technologies"
  draft-ietf-ecrit-requirements-)
• July 2006 An Informational document describing
  the threats and security considerations
• (Draft "Security Threats and Requirements for
  Emergency Call Marking and Mapping"
  draft-ietf-ecrit-security-threats-)
• July 2006 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 2006 A Standards Track RFC describing how
  to route an emergency call based on location
  information
• (Draft "LoST A Location-to-Service Translation
  Protocol" draft-ietf-ecrit-lost-)
• Nov 2006 An Informational document
  describing the Mapping Protocol Architecture
  (Example document "Location-to-URL Mapping
  Architecture and Framework" draft-schulzrinne-ec
  rit-mapping-arch-)
• December 2006 An Informational document
  describing the ECRIT Framework (Example document
  "Framework for Emergency Calling in Internet
  Multimedia" draft-rosen-ecrit-framework-00.txt)
• February 2007 A BCP document describing
  the emergency call support for devices.
• (Example document "Best Current Practice for
  Communications Services in support of Emergency
  Calling" draft-rosen-ecrit-phonebcp-)

7
3GPP CT1 - IETF ECRIT Joint Session on Emergency
Calls

• Meeting on Sunday, 9th July
• Organized by Hannu Hietalahti (3GPP TSG CT
  chairman), Marc Linsner (IETF ECRIT) and Hannes
  Tschofenig (IETF ECRIT)
• Agenda http//www.ietf-ecrit.org/3GPP-IETF-2006/A
  genda.pdf
• Opening of the meeting (1300)
• Co chairs Hannu Hietalahti (CT) and Hannes
  Tschofenig (ECRIT) and Marc Linsner (ECRIT)
• Approval of the agenda (1310)
• Call for documents
• 3GPP requirements on emergency call (1315)
• Presentation of service requirements for
  emergency call (based on 3GPP TS 22.101)
• Presentation of emergency call architecture
  (based on 3GPP TS 23.167)
• CT1 open items list
• IETF protocols and architecture for emergency
  call (1400)
• Presentation of the currently ongoing ECRIT work
• Technical problems in need of solution (1430
  1700)
• Detection of emergency call in the terminal and
  in the network
• Priorisation and pre-emption
• Location of emergency calls
• Other technical topics

8
3GPP CT1 - IETF ECRIT Joint Session on Emergency
Calls

• Slides and meeting minutes will be available
  here
• http//www.ietf-ecrit.org/3GPP-IETF-2006/

9
SDO Coordination Meeting for Emergency Services
(1/2)

• Host Henning Schulzrinne/Columbia University
• Date September/October 2006
• Invitations will be sent to the following
  organizations

Organization
Organization

• IETF/IAB
• DSL Forum
• IEEE
• NENA
• EMTEL
• 3GPP
• 3GPP2
• TISPAN

• PacketCable
• ITU-T SG13
• GSC
• FCC
• Bundesnetzagentur
• ATIS-ESIF
• EU Commission
• Wimax?
• OMA?

10
SDO Coordination Meeting for Emergency Services
(2/2)

• Why do we schedule such a meeting?
• Getting informed about the ongoing emergency
  related work
• Synchronizing the work to produce a workable
  solution
• Receive feedback about our work and return
  feedback
• Work closer together with other organizations and
  groups
• Organizations
• Meeting per invitation only (?)
• Drop us a mail if you would be interested to
  attend the meeting.

11
Implementation Activities

• A number of implementation activities are
  currently ongoing (including Open Source
  activities)
• The chairs are going to setup a webpage.
• Goal
• Sharing implementation experience
• Potential interop later this year
• Please let us know if you are working on
  implementations.

12
Agenda (1/2)

• Status Update (10 min)
• Presented by Chairs
• LoST A Location-to-Service Translation
  Protocol (30 min)
• Presented by Ted/Andy/Henning
• http//www.ietf.org/internet-drafts/draft-ietf-ecr
  it-lost-00.txt
• Framework for Emergency Calling in Internet
  Multimedia (20 min)
• Presented by Brian Rosen
• http//www.ietf.org/internet-drafts/draft-rosen-ec
  rit-framework-00.txt
• Best Current Practice for Communications
  Services in support of
• Emergency Calling (10 min)
• Presented by Brian Rosen
• http//www.ietf.org/internet-drafts/draft-rosen-so
  s-phonebcp-01.txt

13
Agenda (2/2)

• A Dynamic Host Configuration Protocol Option
  for Requesting and
• Receiving a Uniform Resource Identifier for a
• Location-to-Service Translation (LoST) Server
  (10 min)
• Presented by James Polk
• http//www.ietf.org/internet-drafts/draft-polk-dhc
  -ecrit-lost-server-uri-00.txt
• Learning the Initial Location-to-Service
  Translation (LoST)
• Uniform Resource Identifier (URI) During
  Session Initiation
• Protocol (SIP) Registration (10 min)
• Presented by James Polk
• http//www.ietf.org/internet-drafts/draft-polk-ecr
  it-lost-server-uri-00.txt
• A Dynamic Host Configuration Protocol Option
  for the
• Locally Significant Emergency Calling
  Dialstring (10 min)
• Presented by James Polk
• http//www.ietf.org/internet-drafts/draft-polk-ecr
  it-dhc-emergency-dialstring-option-00.txt
• Using the Session Initiation Protocol REGISTER
  Method
• To Obtain an Emergency Dialstring (10 min)

14
"From a societal perspective, ECRIT is one of the
most important problems that the IETF is
undertaking right now," says Henning Schulzrinne
in http//www.networkworld.com/news/2006/031306spe
cialfocus-911-voip.html
15
Backup
16
Recently Submitted Documents

• draft-polk-ecrit-lost-server-uri-00.txt
• SIP header returned in a SIP Registration
  transaction indicating to a SIP user agent the
  appropriate LoST Server's URI to send this query
  to.
• draft-polk-dhc-ecrit-uri-psap-esrp-00.txt
• DHC Option for client requesting and/or
  receiving a Public Safety Answering Point (PSAP)
  or Emergency Services Routing Proxy (ESRP)
• draft-polk-dhc-ecrit-uri-lost-00.txt
• DHC Option to deliver a Location-to-Service
  Translation (LoST) Protocol URI to a client.
• draft-polk-ecrit-dhc-emergency-dialstring-option-0
  0.txt
• SIP REGISTER Request message is used to inform a
  user of which emergency dial string to use.
• draft-polk-ecrit-mapping-during-registration-00.tx
  t
• Document discusses four different Layer-7 options
  to solve the problem of getting the PSAP URI to
  the end host.

17
Related Work in the IETF

• SIP Location Conveyance
• draft-ietf-sip-location-conveyance-03.txt
• GEOPRIV Layer 7 Location Configuration Protocol
  Problem Statement and Requirements
• draft-tschofenig-geopriv-l7-lcp-ps-00.txt
• Work done in design team.
• Geopriv Work Items
• Dynamic Host Configuration Protocol (DHCPv4 and
  DHCPv6) Option for Civic Addresses Configuration
  Information
• GEOPRIV PIDF-LO Usage Clarification,
  Considerations and Recommendations
• Revised Civic Location Format for PIDF-LO
• A Document Format for Filtering and Reporting
  Location Notications in the Presence Information
  Document Format Location Object (PIDF-LO)