1 / 10

NENA-IETF I3 Proposal

NENA-IETF I3 Proposal. No carrier presumed Fixed, nomadic and true mobile clients supported Multiple media types supported (voice, text, video, etc) International operation supported not a NENA requirement, but is an IETF requirement No assumption of e.164 telephone number addressing

belita
Download Presentation

NENA-IETF I3 Proposal

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. NENA-IETF I3 Proposal • No carrier presumed • Fixed, nomadic and true mobile clients supported • Multiple media types supported (voice, text, video, etc) • International operation supported • not a NENA requirement, but is an IETF requirement • No assumption of e.164 telephone number addressing • Big “I” Internet is part of the call path; • PSAP(s) may be on a private IP net • PSAP(s) may have specialized VSP for Emergency Services • Both have a firewall, etc... between PSAP and the Internet.

  2. NENA-IETF I3 Proposal • SIP-only signaling • protocol interwork at source/VSP for non-SIP systems • sos@<anydomain> as universal address for assistance, allowing use of international emergency access codes • IETF PIDF-LO (location object), geo and/or civil • contained in the initial SIP INVITE message • Call answers as (native) SIP inside the PSAP • Callback address in Contact field of SIP message • Skills based routing, based on source-based indicators

  3. Not Yet Resolved • Retain needed E9-1-1 features/capabilities Much requirements review to be done • Maintain/improve security, be highly non-disruptable Not yet fully defined • Have plug-and-play integration capability Assumes future devices will be IP capable

  4. Not Yet Resolved • Identify relationship of general Internet and trusted host intranets as applied to future E9-1-1 and transition a major current issue

  5. Three Structures for I3 ILECs Current E9-1-1 System CLECs CAD MSCs PSAP IP Net Mapping Enterprise VoIP General Internet Radio VoI (some in place)

  6. Some Would Say: ILECs Current E9-1-1 System CLECs CAD MSCs PSAP IP Net Mapping General Internet Enterprise VoIP Radio VoI (some in place)

  7. Or: ILECs Current E9-1-1 System CLECs CAD MSCs PSAP IP Net Mapping General Internet Enterprise VoIP Radio VoI (some in place)

  8. Or Should We: ILECs Current E9-1-1 System CLECs CAD MSCs E9-1-1 IP Net Mapping Enterprise VoIP General Internet Radio VoI

  9. NENA Future Path Plan: Many Other Emergency Services Providers ILECs CLECs CAD MSCs E9-1-1 IP Net Mapping Enterprise VoIP General Internet Radio VoI

  10. NENA Future Path Plan: Many Other Emergency Services Providers ILECs CLECs CAD MSCs E9-1-1 IP Net Mapping Enterprise VoIP General Internet Radio VoI Really Secure Firewall !

More Related