1 / 5

Data Only Emergency Alerts tools.ietf/html/draft-ietf-ecrit-data-only-ea-01

Data Only Emergency Alerts http://tools.ietf.org/html/draft-ietf-ecrit-data-only-ea-01. Document Authors: Brian Rosen, Henning Schulzrinne , Hannes Tschofenig. Status. At IETF#78 (Maastricht) Brian gave a presentation http://www.ietf.org/proceedings/78/slides/ecrit-9/ecrit-9.htm

jania
Download Presentation

Data Only Emergency Alerts tools.ietf/html/draft-ietf-ecrit-data-only-ea-01

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. Data Only Emergency Alertshttp://tools.ietf.org/html/draft-ietf-ecrit-data-only-ea-01 Document Authors: Brian Rosen, Henning Schulzrinne, HannesTschofenig

  2. Status • At IETF#78 (Maastricht) Brian gave a presentation http://www.ietf.org/proceedings/78/slides/ecrit-9/ecrit-9.htm • Including a problem statement • motivating the usage of SIP and CAP. • Diff: • http://tools.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-01.txt

  3. Two Communication Exchanges • I)Location-Based Emergency Alert Routing II) Targeted Emergency Alert Routing Sensor PSAP Sensor Aggregator

  4. CAP and PIDF-LO MESSAGE sip:aggregator@domain.com SIP/2.0 Via: SIP/2.0/TCP sensor1.domain.com;branch=z9hG4bK776sgdkse Max-Forwards: 70 From: sip:sensor1@domain.com;tag=49583 To: sip:aggregator@domain.com Call-ID: asd88asd77a@1.2.3.4 Geolocation: <cid:abcdef@domain.com> ;routing-allowed=yes Supported: geolocation Accept: application/pidf+xml, application/common-alerting-protocol+xml CSeq: 1 MESSAGE Content-Type: multipart/mixed; boundary=boundary1 Content-Length: ... --boundary1 CAP --boundary1 PIDF-LO • Location for routing is in the PIDF-LO. • If location is available in CAP then it is copied to PIDF-LO

  5. Next Steps? • Start Working Group Last Call to solicit comments.

More Related