draft-rosen-ecrit-emergency-framework-00

1
draft-rosen-ecrit-emergency-framework-00

• Brian Rosen
• NeuStar

2
Purpose

• Big Picture overview of how emergency calling
  on the Internet works
• Pointers to relevant documents
• Listing of specific options/combinations of
  existing specs that need to be used
• Should not be duplicative of other specs, but be
  readable stand alone
• Currently has overlap with phonebcp
• Intention to make framework informative,
  -phonebcp normative

3
Location Issues

• Has a lot of informative why this is done this
  way text, which if duplicated in other specs
  probably should be here
• I will delete/move some similar text now in
  phonebcp

4
Call-Back Other Information

• Must include Contact (for immediate call to same
  device)
• Must include AoR (for later additional
  information)
• Can include URI for additional info on caller
• opaque URI
• opt-in
• could be carrier independent)
• Can include URI for additional info on call
• Includes carrier ID and contact info
• Class of service
• Reference info carrier needs to assist PSAP

5
Testing

• Provide full test of signaling and media path for
  emergency call without PSAP human intervention
• Signaled by test URN parameter
• Routes just like emergency call
• Includes media offer/answer
• Auto-answer at PSAP
• Media loopback
• Will be limited use, and may not be
  available/enabled at every PSAP

6
Things to do

• Call Flows
• Alternatives Considered
• Suggestions welcomed
• Alignment of informative text with other
  documents
• Should this be adopted as a WG item now, or let
  design team keep working 1 more rev first?