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

Data Only Emergency Alertshttp://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 – Including a problem statement– motivating the usage of SIP and CAP.

• Diff:– http://tools.ietf.org/rfcdiff?url2=draft-ietf-ecrit-dat

a-only-ea-01.txt

Two Communication Exchanges

Sensor Aggregator

II) Targeted Emergency Alert Routing

Sensor PSAP

I) Location-Based Emergency Alert Routing

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

Next Steps?

• Start Working Group Last Call to solicit comments.