< draft-ietf-ecrit-data-only-ea-05.txt   draft-ietf-ecrit-data-only-ea-06.txt >
ECRIT B. Rosen ECRIT B. Rosen
Internet-Draft NeuStar, Inc. Internet-Draft NeuStar, Inc.
Intended status: Standards Track H. Schulzrinne Intended status: Standards Track H. Schulzrinne
Expires: August 29, 2013 Columbia U. Expires: January 16, 2014 Columbia U.
H. Tschofenig H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
February 25, 2013 July 15, 2013
Data-Only Emergency Calls Data-Only Emergency Calls
draft-ietf-ecrit-data-only-ea-05.txt draft-ietf-ecrit-data-only-ea-06.txt
Abstract Abstract
RFC 6443 'Framework for Emergency Calling Using Internet Multimedia' RFC 6443 'Framework for Emergency Calling Using Internet Multimedia'
describes how devices use the Internet to place emergency calls and describes how devices use the Internet to place emergency calls and
how Public Safety Answering Points (PSAPs) can handle Internet how Public Safety Answering Points (PSAPs) can handle Internet
multimedia emergency calls natively. The exchange of multimedia multimedia emergency calls natively. The exchange of multimedia
traffic typically involves a SIP session establishment starting with traffic typically involves a SIP session establishment starting with
a SIP INVITE that negotiates various parameters for that session. a SIP INVITE that negotiates various parameters for that session.
In some cases, however, the transmission of application data is In some cases, however, the transmission of application data is
everything that is needed. Examples of such environments include a everything that is needed. Examples of such environments include a
temperature sensors issuing alerts, or vehicles sending crash data. temperature sensors issuing alerts, or vehicles sending crash data.
Often these alerts are conveyed as one-shot data transmissions. Often these alerts are conveyed as one-shot data transmissions.
These type of interactions are called 'data-only emergency calls'. These type of interactions are called 'data-only emergency calls'.
This document describes a container for the data based on the Common This document describes a container for the data based on the Common
Alerting Protocol (CAP) and its transmission using the SIP MESSAGE Alerting Protocol (CAP) and its transmission using the SIP MESSAGE
transaction. transaction.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 29, 2013. This Internet-Draft will expire on January 16, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Architectural Overview . . . . . . . . . . . . . . . . . . . . 5 3. Architectural Overview . . . . . . . . . . . . . . . . . . . 4
4. Protocol Specification . . . . . . . . . . . . . . . . . . . . 8 4. Protocol Specification . . . . . . . . . . . . . . . . . . . 6
4.1. CAP Transport . . . . . . . . . . . . . . . . . . . . . . 8 4.1. CAP Transport . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Profiling of the CAP Document Content . . . . . . . . . . 8 4.2. Profiling of the CAP Document Content . . . . . . . . . . 6
4.3. Sending a Data-Only Emergency Call . . . . . . . . . . . . 9 4.3. Sending a Data-Only Emergency Call . . . . . . . . . . . 7
5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. 425 (Bad Alert Message) Response Code . . . . . . . . . . 10 5.1. 425 (Bad Alert Message) Response Code . . . . . . . . . . 8
5.2. The AlertMsg-Error Header Field . . . . . . . . . . . . . 10 5.2. The AlertMsg-Error Header Field . . . . . . . . . . . . . 8
6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. Updates to the CAP Message . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8.1. Registration of the 'application/cap+xml' MIME type . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8.2. IANA Registration for 425 Response Code . . . . . . . . . 20 9.1. Registration of the 'application/emergencyCall.cap+xml'
8.3. IANA Registration of New AlertMsg-Error Header Field . . . 20 MIME type . . . . . . . . . . . . . . . . . . . . . . . . 16
8.4. IANA Registration for the SIP AlertMsg-Error Codes . . . . 21 9.2. IANA Registration of Additional Data Block . . . . . . . 17
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 9.3. IANA Registration for 425 Response Code . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.4. IANA Registration of New AlertMsg-Error Header Field . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . . 23 9.5. IANA Registration for the SIP AlertMsg-Error Codes . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . . 23 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1. Normative References . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
RFC 6443 [RFC6443] describes how devices use the Internet to place RFC 6443 [RFC6443] describes how devices use the Internet to place
emergency calls and how Public Safety Answering Points (PSAPs) can emergency calls and how Public Safety Answering Points (PSAPs) can
handle Internet multimedia emergency calls natively. The exchange of handle Internet multimedia emergency calls natively. The exchange of
multimedia traffic typically involves a SIP session establishment multimedia traffic typically involves a SIP session establishment
starting with a SIP INVITE that negotiates various parameters for starting with a SIP INVITE that negotiates various parameters for
that session. that session.
skipping to change at page 3, line 30 skipping to change at page 3, line 30
In this document, we use the term "call" so that similarities between In this document, we use the term "call" so that similarities between
full sessions with interactive media can be exploited. full sessions with interactive media can be exploited.
Data-only emergency calls are similar to regular emergency calls in Data-only emergency calls are similar to regular emergency calls in
the sense that they require the emergency indications, emergency call the sense that they require the emergency indications, emergency call
routing functionality and may even have the same location routing functionality and may even have the same location
requirements. However, the communication interaction will not lead requirements. However, the communication interaction will not lead
to the exchange of interactive media, that is, Real-Time Protocol to the exchange of interactive media, that is, Real-Time Protocol
packets, such as voice, video data or real-time text. packets, such as voice, video data or real-time text.
This document does not define a mechanism for updates to the data
contained in data-only emergency calls.
The Common Alerting Protocol (CAP) [cap] is a document format for The Common Alerting Protocol (CAP) [cap] is a document format for
exchanging emergency alerts and public warnings. CAP is mainly used exchanging emergency alerts and public warnings. CAP is mainly used
for conveying alerts and warnings between authorities and from for conveying alerts and warnings between authorities and from
authorities to citizen/individuals. This document is concerned with authorities to citizen/individuals. This document is concerned with
citizen to authority "alerts", where the alert is sent without any citizen to authority "alerts", where the alert is sent without any
interactive media. interactive media.
CAP payload is used to convey the alert data which is contained in This document describes a method of including a CAP message in a SIP
the body of a SIP MESSAGE. Note that further data may be added using transaction, either by value (CAP message is in the body of the
the already available 'additional data' structure message, using a CID) or by reference (A URI is included in the
[I-D.ietf-ecrit-additional-data]. Whenever data can be encoded in message, which when dereferenced returns the CAP message) by defining
the additional data structure it shall be used. it as a block of "additional data" as definded in
[I-D.ietf-ecrit-additional-data]. The additional data mechanism is
also used to send alert specific data beyond that available in the
CAP message.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Architectural Overview 3. Architectural Overview
This section illustrates two envisioned usage modes; targeted and This section illustrates two envisioned usage modes; targeted and
skipping to change at page 6, line 34 skipping to change at page 5, line 14
| | | |
Figure 1: Targeted Emergency Alert Routing Figure 1: Targeted Emergency Alert Routing
In Figure 2 a scenario is shown whereby the alert is routed using In Figure 2 a scenario is shown whereby the alert is routed using
location information and the Service URN. An emergency services location information and the Service URN. An emergency services
routing proxy (ESRP) may use LoST to determine the next hop proxy to routing proxy (ESRP) may use LoST to determine the next hop proxy to
route the alert message to. A possible receiver is a PSAP and the route the alert message to. A possible receiver is a PSAP and the
recipient of the alert may be call taker. In the generic case, there recipient of the alert may be call taker. In the generic case, there
is very likely no prior relationship between the originator and the is very likely no prior relationship between the originator and the
receiver, e.g. PSAP. A PSAP, for example, is likely to receive and receiver, e.g. PSAP. A PSAP, for example, is likely to receive and
accept alerts from entities it cannot authorize. This scenario accept alerts from entities it cannot authorize. This scenario
corresponds more to the classical emergency services use case and the corresponds more to the classical emergency services use case and the
description in [I-D.ietf-ecrit-phonebcp] is applicable. description in [RFC6881] is applicable.
+-----------+ +----------+ +-----------+ +----------+
+--------+ | ESRP | | PSAP | +--------+ | ESRP | | PSAP |
| Sensor | | | | | | Sensor | | | | |
+---+----+ +---+-------+ +---+------+ +---+----+ +---+-------+ +---+------+
| | | | | |
Sensors | | Sensors | |
trigger | | trigger | |
emergency | | emergency | |
alert | | alert | |
skipping to change at page 8, line 13 skipping to change at page 6, line 17
Figure 2: Location-Based Emergency Alert Routing Figure 2: Location-Based Emergency Alert Routing
4. Protocol Specification 4. Protocol Specification
4.1. CAP Transport 4.1. CAP Transport
A CAP message may be sent on the initial message of any SIP A CAP message may be sent on the initial message of any SIP
transaction. However, this document only describes specific behavior transaction. However, this document only describes specific behavior
when used with a SIP MESSAGE transaction for a one-shot, data-only when used with a SIP MESSAGE transaction for a one-shot, data-only
emergency call. Behavior with other transactions is not defined. emergency call. Behavior with other transactions is not defined.
The CAP message is sent in the body of the message. The MIME type is
set to 'application/cap+xml'. The CAP message included in a SIP message as an additional-data block
[I-D.ietf-ecrit-additional-data]. Accordingly, it is introduced to
the SIP message with a Call-Info header with a purpose of
"emergencyCall.cap". The header may contain a URI that is used by
the recipient (or in some cases, an intermediary) to obtain the CAP
message. Alternative, the Call-Info header may contain a Content
Indirect url [RFC2392] and the CAP message included in the body of
the message. In either case, the CAP message is located in a MIME
block. The MIME type is set to 'application/emergencyCall.cap+xml'.
If the server does not support the functionality required to fulfill If the server does not support the functionality required to fulfill
the request then a 501 Not Implemented MUST be returned as specified the request then a 501 Not Implemented MUST be returned as specified
in RFC 3261 [RFC3261]. This is the appropriate response when a UAS in RFC 3261 [RFC3261]. This is the appropriate response when a UAS
does not recognize the request method and is not capable of does not recognize the request method and is not capable of
supporting it for any user. supporting it for any user.
The 415 Unsupported Media Type error MUST be returned as specified in The 415 Unsupported Media Type error MUST be returned as specified in
RFC 3261 [RFC3261] if the server is refusing to service the request RFC 3261 [RFC3261] if the server is refusing to service the request
because the message body of the request is in a format not supported because the message body of the request is in a format not supported
skipping to change at page 8, line 40 skipping to change at page 7, line 6
4.2. Profiling of the CAP Document Content 4.2. Profiling of the CAP Document Content
The usage of CAP MUST conform to the specification provided with The usage of CAP MUST conform to the specification provided with
[cap]. For the usage with SIP the following additional requirements [cap]. For the usage with SIP the following additional requirements
are imposed: are imposed:
sender: A few sub-categories for putting a value in the <sender> sender: A few sub-categories for putting a value in the <sender>
element have to be considered: element have to be considered:
Originator is a SIP entity, Author indication irrelevant: When Originator is a SIP entity, Author indication irrelevant: When
the alert was created by a SIP-based originator and it is not the alert was created by a SIP-based originator and it is
useful to be explicit about the author of the alert then the not useful to be explicit about the author of the alert then
<sender> element MUST be populated with the SIP URI of the user the <sender> element MUST be populated with the SIP URI of
agent. the user agent.
Originator is a non-SIP entity, Author indication irrelevant: In Originator is a non-SIP entity, Author indication irrelevant: In
case that the alert was created by a non-SIP based entity and case that the alert was created by a non-SIP based entity
the identity of this original sender wants to be preserved then and the identity of this original sender wants to be
this identity MUST be placed into the <sender> element. In preserved then this identity MUST be placed into the
this category the it is not useful to be explicit about the <sender> element. In this category the it is not useful to
author of the alert. The specific type of identity being used be explicit about the author of the alert. The specific
will depends on the technology being used by the original type of identity being used will depends on the technology
originator. being used by the original originator.
Author indication relevant: In case the author is different from Author indication relevant: In case the author is different from
the actual originator of the message and this distinction the actual originator of the message and this distinction
should be preserved then the <sender> element MUST NOT contain should be preserved then the <sender> element MUST NOT
the SIP URI of the user agent. contain the SIP URI of the user agent.
incidents: The <incidents> element MUST be present. This incident incidents: The <incidents> element MUST be present. This incident
identifier MUST be chosen in such a way that it is unique for a identifier MUST be chosen in such a way that it is unique for a
given <sender, expires, incidents> combination. Note that the given <sender, expires, incidents> combination. Note that the
<expires> element is optional and may not be present. <expires> element is optional and may not be present.
scope: The value of the <scope> element MAY be set to "Private" if scope: The value of the <scope> element MAY be set to "Private" if
the alert is not meant for public consumption. The <addresses> the alert is not meant for public consumption. The <addresses>
element is, however, not used by this specification since the element is, however, not used by this specification since the
message routing is performed by SIP and the respective address message routing is performed by SIP and the respective address
skipping to change at page 9, line 32 skipping to change at page 8, line 4
parameter: The <parameter> element MAY contain additional parameter: The <parameter> element MAY contain additional
information specific to the sendor. information specific to the sendor.
area: It is RECOMMENDED to omit this element when constructing a area: It is RECOMMENDED to omit this element when constructing a
message. In case that the CAP message already contained an <area> message. In case that the CAP message already contained an <area>
element then the specified location information SHOULD be copied element then the specified location information SHOULD be copied
into the PIDF-LO structure of the 'geolocation' header. into the PIDF-LO structure of the 'geolocation' header.
4.3. Sending a Data-Only Emergency Call 4.3. Sending a Data-Only Emergency Call
A data-only emergency call is sent using a SIP MESSAGE transaction A data-only emergency call is sent using a SIP MESSAGE transaction
with a CAP body as described above in a manner similar to how an with a CAP URI or body as described above in a manner similar to how
emergency call with interactive media is sent, as described in an emergency call with interactive media is sent, as described in
[I-D.ietf-ecrit-phonebcp]. The MESSAGE transaction does not create a [RFC6881]. The MESSAGE transaction does not create a session or send
session or send media, but otherwise, the header content of the media, but otherwise, the header content of the transaction, routing,
transaction, routing, and processing of data-only calls are the same and processing of data-only calls are the same as those of other
as those of other emergency calls. emergency calls.
5. Error Handling 5. Error Handling
This section defines a new error response code and a header field for This section defines a new error response code and a header field for
additional information. additional information.
5.1. 425 (Bad Alert Message) Response Code 5.1. 425 (Bad Alert Message) Response Code
This SIP extension creates a new location-specific response code, This SIP extension creates a new location-specific response code,
defined as follows, defined as follows,
skipping to change at page 13, line 5 skipping to change at page 10, line 28
AlertMsg-Error: 102 ; code="Not enough information to determine the AlertMsg-Error: 102 ; code="Not enough information to determine the
purpose of the alert" purpose of the alert"
AlertMsg-Error: 103 ; code="Alert Payload was corrupted" AlertMsg-Error: 103 ; code="Alert Payload was corrupted"
Additionally, if an entity cannot or chooses not to process the alert Additionally, if an entity cannot or chooses not to process the alert
message from a SIP request, a 500 (Server Internal Error) SHOULD be message from a SIP request, a 500 (Server Internal Error) SHOULD be
used with or without a configurable Retry-After header field. used with or without a configurable Retry-After header field.
6. Example 6. Updates to the CAP Message
If the sender anticipates that the content of the CAP message may
need to be updated during the lifecycle of the event referred to in
the message, it may include an update block as defined in
[I-D.rosen-ecrit-addldata-subnot].
7. Example
Figure 3 shows a CAP document indicating a BURGLARY alert issued by a Figure 3 shows a CAP document indicating a BURGLARY alert issued by a
sensor called 'sensor1@domain.com'. The location of the sensor can sensor called 'sensor1@domain.com'. The location of the sensor can
be obtained from the attached location information provided via the be obtained from the attached location information provided via the
'geolocation' header contained in the SIP MESSAGE structure. 'geolocation' header contained in the SIP MESSAGE structure.
Additionally, the sensor provided some data long with the alert Additionally, the sensor provided some data long with the alert
message using proprietary information elements only to be processed message using proprietary information elements only to be processed
by the receiver, a SIP entity acting as an aggregator. This example by the receiver, a SIP entity acting as an aggregator. This example
reflects the description in Figure 1. reflects the description in Figure 1.
MESSAGE sip:aggregator@domain.com SIP/2.0 MESSAGE sip:aggregator@domain.com SIP/2.0
Via: SIP/2.0/TCP sensor1.domain.com;branch=z9hG4bK776sgdkse Via: SIP/2.0/TCP sensor1.domain.com;branch=z9hG4bK776sgdkse
Max-Forwards: 70 Max-Forwards: 70
From: sip:sensor1@domain.com;tag=49583 From: sip:sensor1@domain.com;tag=49583
To: sip:aggregator@domain.com To: sip:aggregator@domain.com
Call-ID: asd88asd77a@1.2.3.4 Call-ID: asd88asd77a@1.2.3.4
Geolocation: <cid:abcdef@domain.com> Geolocation: <cid:abcdef@domain.com>
;routing-allowed=yes ;routing-allowed=yes
Supported: geolocation Supported: geolocation
Accept: application/pidf+xml, application/cap+xml Accept: application/pidf+xml, application/emergencyCall.cap+xml
CSeq: 1 MESSAGE CSeq: 1 MESSAGE
Content-Type: multipart/mixed; boundary=boundary1 Call-Info: cid:abcdef2@domain.com;purpose=emergencyCall.cap
Content-Length: ... Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ...
--boundary1 --boundary1
Content-Type: cap+xml Content-Type: application/emergencyCall.cap
Content-ID: <abcdef2@domain.com> Content-ID: <abcdef2@domain.com>
<?xml version="1.0" encoding="UTF-8"?> Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?>
<alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1">
<identifier>S-1</identifier> <identifier>S-1</identifier>
<sender>sip:sensor1@domain.com</sender> <sender>sip:sensor1@domain.com</sender>
<sent>2008-11-19T14:57:00-07:00</sent> <sent>2008-11-19T14:57:00-07:00</sent>
<status>Actual</status> <status>Actual</status>
<msgType>Alert</msgType> <msgType>Alert</msgType>
<scope>Private</scope> <scope>Private</scope>
<incidents>abc1234</incidents> <incidents>abc1234</incidents>
<info> <info>
<category>Security</category> <category>Security</category>
<event>BURGLARY</event> <event>BURGLARY</event>
<urgency>Expected</urgency> <urgency>Expected</urgency>
<certainty>Likely</certainty> <certainty>Likely</certainty>
<severity>Moderate</severity> <severity>Moderate</severity>
<senderName>SENSOR 1</senderName> <senderName>SENSOR 1</senderName>
<parameter> <parameter>
<valueName>SENSOR-DATA-NAMESPACE1</valueName> <valueName>SENSOR-DATA-NAMESPACE1</valueName>
<value>123</value> <value>123</value>
</parameter> </parameter>
<parameter> <parameter>
<valueName>SENSOR-DATA-NAMESPACE2</valueName> <valueName>SENSOR-DATA-NAMESPACE2</valueName>
<value>TRUE</value> <value>TRUE</value>
</parameter> </parameter>
</info> </info>
</alert> </alert>
--boundary1 --boundary1
Content-Type: application/pidf+xml Content-Type: application/pidf+xml
Content-ID: <abcdef2@domain.com> Content-ID: <abcdef2@domain.com>
<?xml version="1.0" encoding="UTF-8"?> Content-Disposition: by-reference;handling=optional
<presence <?xml version="1.0" encoding="UTF-8"?>
xmlns="urn:ietf:params:xml:ns:pidf" <presence
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:gbp=
xmlns:gml="http://www.opengis.net/gml" "urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
entity="pres:alice@atlanta.example.com"> xmlns:gml="http://www.opengis.net/gml"
<dm:device id="sensor"> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
<gp:geopriv> entity="pres:alice@atlanta.example.com">
<gp:location-info> <dm:device id="sensor">
<gml:location> <gp:geopriv>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <gp:location-info>
<gml:pos>32.86726 -97.16054</gml:pos> <gml:location>
</gml:Point> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
</gml:location> <gml:pos>32.86726 -97.16054</gml:pos>
</gp:location-info> </gml:Point>
<gp:usage-rules> </gml:location>
<gbp:retransmission-allowed>false </gp:location-info>
</gbp:retransmission-allowed> <gp:usage-rules>
<gbp:retention-expiry>2010-11-14T20:00:00Z <gbp:retransmission-allowed>false
</gbp:retention-expiry> </gbp:retransmission-allowed>
</gp:usage-rules> <gbp:retention-expiry>2010-11-14T20:00:00Z
<gp:method>802.11</gp:method> </gbp:retention-expiry>
</gp:geopriv> </gp:usage-rules>
<dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp> <gp:method>802.11</gp:method>
</dm:device> </gp:geopriv>
</presence> <dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp>
--boundary1-- </dm:device>
</presence>
--boundary1--
Figure 3: Example Message conveying an Alert to an Aggregator Figure 3: Example Message conveying an Alert to an Aggregator
Figure 4 shows the same CAP document sent as a data-only emergency Figure 4 shows the same CAP document sent as a data-only emergency
call towards a PSAP. call towards a PSAP.
MESSAGE urn:service:sos SIP/2.0 MESSAGE urn:service:sos SIP/2.0
Via: SIP/2.0/TCP sip:aggregator.1.example.com;branch=z9hG4bK776abssa Via: SIP/2.0/TCP sip:aggreg.1.example.com;branch=z9hG4bK776abssa
Max-Forwards: 70 Max-Forwards: 70
From: sip:aggregator@example.com;tag=32336 From: sip:aggregator@example.com;tag=32336
To: 112 To: 112
Call-ID: asdf33443a@example.com Call-ID: asdf33443a@example.com
Route: sip:psap1.example.gov Route: sip:psap1.example.gov
Geolocation: <cid:abcdef@example.com> Geolocation: <cid:abcdef@example.com>
;routing-allowed=yes ;routing-allowed=yes
Supported: geolocation Supported: geolocation
Accept: application/pidf+xml, application/cap+xml Accept: application/pidf+xml, application/emergencyCall.cap+xml
CSeq: 1 MESSAGE Call-info: cid:abcdef2@domain.com;purpose=emergencyCall.cap
Content-Type: multipart/mixed; boundary=boundary1 CSeq: 1 MESSAGE
Content-Length: ... Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ...
--boundary1
Content-Type: cap+xml --boundary1
Content-ID: <abcdef2@example.com>
<?xml version="1.0" encoding="UTF-8"?>
<alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> Content-Type: application/emergencyCall.cap+xml
<identifier>S-1</identifier> Content-ID: <abcdef2@example.com>
<sender>sip:sensor1@domain.com</sender> <?xml version="1.0" encoding="UTF-8"?>
<sent>2008-11-19T14:57:00-07:00</sent>
<status>Actual</status>
<msgType>Alert</msgType>
<scope>Private</scope>
<incidents>abc1234</incidents>
<info>
<category>Security</category>
<event>BURGLARY</event>
<urgency>Expected</urgency>
<certainty>Likely</certainty>
<severity>Moderate</severity>
<senderName>SENSOR 1</senderName>
<parameter>
<valueName>SENSOR-DATA-NAMESPACE1</valueName>
<value>123</value>
</parameter>
<parameter>
<valueName>SENSOR-DATA-NAMESPACE2</valueName>
<value>TRUE</value>
</parameter> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1">
</info> <identifier>S-1</identifier>
</alert> <sender>sip:sensor1@domain.com</sender>
<sent>2008-11-19T14:57:00-07:00</sent>
<status>Actual</status>
<msgType>Alert</msgType>
<scope>Private</scope>
<incidents>abc1234</incidents>
<info>
<category>Security</category>
<event>BURGLARY</event>
<urgency>Expected</urgency>
<certainty>Likely</certainty>
<severity>Moderate</severity>
<senderName>SENSOR 1</senderName>
<parameter>
<valueName>SENSOR-DATA-NAMESPACE1</valueName>
<value>123</value>
</parameter>
<parameter>
<valueName>SENSOR-DATA-NAMESPACE2</valueName>
<value>TRUE</value>
</parameter>
</info>
</alert>
--boundary1 --boundary1
Content-Type: application/pidf+xml Content-Type: application/pidf+xml
Content-ID: <abcdef2@domain.com> Content-ID: <abcdef2@domain.com>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence <presence
xmlns="urn:ietf:params:xml:ns:pidf" xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:gbp=
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" "urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
xmlns:gml="http://www.opengis.net/gml" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:gml="http://www.opengis.net/gml"
entity="pres:alice@atlanta.example.com"> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
<dm:device id="sensor"> entity="pres:alice@atlanta.example.com">
<gp:geopriv> <dm:device id="sensor">
<gp:location-info> <gp:geopriv>
<gml:location> <gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <gml:location>
<gml:pos>32.86726 -97.16054</gml:pos> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
</gml:Point> <gml:pos>32.86726 -97.16054</gml:pos>
</gml:location> </gml:Point>
</gp:location-info> </gml:location>
<gp:usage-rules> </gp:location-info>
<gbp:retransmission-allowed>false <gp:usage-rules>
</gbp:retransmission-allowed> <gbp:retransmission-allowed>false
<gbp:retention-expiry>2010-11-14T20:00:00Z </gbp:retransmission-allowed>
</gbp:retention-expiry> <gbp:retention-expiry>2010-11-14T20:00:00Z
</gp:usage-rules> </gbp:retention-expiry>
<gp:method>802.11</gp:method> </gp:usage-rules>
</gp:geopriv> <gp:method>802.11</gp:method>
<dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp> </gp:geopriv>
</dm:device> <dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp>
</presence> </dm:device>
--boundary1-- </presence>
--boundary1--
Figure 4: Example Message conveying an Alert to a PSAP Figure 4: Example Message conveying an Alert to a PSAP
7. Security Considerations 8. Security Considerations
This section discusses security considerations when SIP user agents This section discusses security considerations when SIP user agents
issue emergency alerts utilizing MESSAGE and CAP. Location specific issue emergency alerts utilizing MESSAGE and CAP. Location specific
threats are not unique to this document and are discussed in threats are not unique to this document and are discussed in
[I-D.ietf-ecrit-trustworthy-location] and [RFC6442]. [I-D.ietf-ecrit-trustworthy-location] and [RFC6442].
The ECRIT emergency services architecture [RFC6443] considers The ECRIT emergency services architecture [RFC6443] considers
classical individual-to-authority emergency calling and the identity classical individual-to-authority emergency calling and the identity
of the emergency caller does not play a role at the time of the call of the emergency caller does not play a role at the time of the call
establishment itself, i.e., a response to the emergency call will not establishment itself, i.e., a response to the emergency call will not
skipping to change at page 19, line 5 skipping to change at page 16, line 10
that message is unchanged, then no additional security vulnerability that message is unchanged, then no additional security vulnerability
is created. Additionally, it is RECOMMENDED to make use of SIP is created. Additionally, it is RECOMMENDED to make use of SIP
security mechanisms, such as SIP Identity [RFC4474], to tie the CAP security mechanisms, such as SIP Identity [RFC4474], to tie the CAP
message to the SIP message. To provide protection of the entire SIP message to the SIP message. To provide protection of the entire SIP
message exchange between neighboring SIP entities the usage of TLS is message exchange between neighboring SIP entities the usage of TLS is
mandatory. mandatory.
Note that none of the security mechanism in this document protect Note that none of the security mechanism in this document protect
against a compromised sensor sending crafted alerts. against a compromised sensor sending crafted alerts.
8. IANA Considerations 9. IANA Considerations
8.1. Registration of the 'application/cap+xml' MIME type 9.1. Registration of the 'application/emergencyCall.cap+xml' MIME type
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of MIME media type application/ cap+xml Subject: Registration of MIME media type application/
emergencyCall.cap+xml
MIME media type name: application MIME media type name: application
MIME subtype name: cap+xml MIME subtype name: cap+xml
Required parameters: (none) Required parameters: (none)
Optional parameters: charset; Indicates the character encoding of Optional parameters: charset; Indicates the character encoding of
enclosed XML. Default is UTF-8 [RFC3629]. enclosed XML. Default is UTF-8 [RFC3629].
skipping to change at page 20, line 16 skipping to change at page 17, line 23
Tschofenig, Hannes.Tschofenig@nsn.com Tschofenig, Hannes.Tschofenig@nsn.com
Intended usage: Limited use Intended usage: Limited use
Author/Change controller: IETF ECRIT working group Author/Change controller: IETF ECRIT working group
Other information: This media type is a specialization of Other information: This media type is a specialization of
application/xml RFC 3023 [RFC3023], and many of the considerations application/xml RFC 3023 [RFC3023], and many of the considerations
described there also apply to application/cap+xml. described there also apply to application/cap+xml.
8.2. IANA Registration for 425 Response Code 9.2. IANA Registration of Additional Data Block
This document registers a new block type in the sub-registry called
'Additional Data Blocks' defined in [I-D.ietf-ecrit-additional-data].
The token is "cap" and the reference is this document.
9.3. IANA Registration for 425 Response Code
In the SIP Response Codes registry, the following is added In the SIP Response Codes registry, the following is added
Reference: RFC-XXXX (i.e., this document) Reference: RFC-XXXX (i.e., this document)
Response code: 425 (recommended number to assign) Response code: 425 (recommended number to assign)
Default reason phrase: Bad Alert Message Default reason phrase: Bad Alert Message
Registry: Registry:
Response Code Reference Response Code Reference
------------------------------------------ --------- ------------------------------------------ ---------
Request Failure 4xx Request Failure 4xx
425 Bad Alert Message [this doc] 425 Bad Alert Message [this doc]
This SIP Response code is defined in Section 5. This SIP Response code is defined in Section 5.
8.3. IANA Registration of New AlertMsg-Error Header Field 9.4. IANA Registration of New AlertMsg-Error Header Field
The SIP AlertMsg-error header field is created by this document, with The SIP AlertMsg-error header field is created by this document, with
its definition and rules in Section 5, to be added to the IANA sip- its definition and rules in Section 5, to be added to the IANA sip-
parameters registry with two actions: parameters registry with two actions:
1. Update the Header Fields registry with 1. Update the Header Fields registry with
Registry: Registry:
Header Name compact Reference Header Name compact Reference
----------------- ------- --------- ----------------- ------- ---------
AlertMsg-Error [this doc] AlertMsg-Error [this doc]
2. In the portion titled "Header Field Parameters and Parameter 2. In the portion titled "Header Field Parameters and Parameter
Values", add Values", add
Predefined Predefined
Header Field Parameter Name Values Reference Header Field Parameter Name Values Reference
----------------- ------------------- ---------- --------- ----------------- ------------------- ---------- ---------
AlertMsg-Error code yes [this doc] AlertMsg-Error code yes [this doc]
8.4. IANA Registration for the SIP AlertMsg-Error Codes 9.5. IANA Registration for the SIP AlertMsg-Error Codes
This document creates a new registry for SIP, called "AlertMsg-Error This document creates a new registry for SIP, called "AlertMsg-Error
Codes". AlertMsg-Error codes provide reason for the error discovered Codes". AlertMsg-Error codes provide reason for the error discovered
by recipients, categorized by action to be taken by error recipient. by recipients, categorized by action to be taken by error recipient.
The initial values for this registry are shown below. The initial values for this registry are shown below.
Registry Name: AlertMsg-Error Codes Registry Name: AlertMsg-Error Codes
Reference: [this doc] Reference: [this doc]
skipping to change at page 21, line 32 skipping to change at page 19, line 4
Reference: [this doc] Reference: [this doc]
Registration Procedures: Specification Required Registration Procedures: Specification Required
Code Default Reason Phrase Reference Code Default Reason Phrase Reference
---- --------------------------------------------------- --------- ---- --------------------------------------------------- ---------
100 "Cannot Process the Alert Payload" [this doc] 100 "Cannot Process the Alert Payload" [this doc]
101 "Alert Payload was not present or could not be found" [this doc] 101 "Alert Payload was not present or could not be found" [this doc]
102 "Not enough information to determine 102 "Not enough information to determine
the purpose of the alert" [this doc] the purpose of the alert" [this doc]
103 "Alert Payload was corrupted" [this doc] 103 "Alert Payload was corrupted" [this doc]
Details of these error codes are in Section 5. Details of these error codes are in Section 5.
9. Acknowledgments 10. Acknowledgments
The authors would like to thank the participants of the Early Warning The authors would like to thank the participants of the Early Warning
adhoc meeting at IETF#69 for their feedback. Additionally, we would adhoc meeting at IETF#69 for their feedback. Additionally, we would
like to thank the members of the NENA Long Term Direction Working like to thank the members of the NENA Long Term Direction Working
Group for their feedback. Group for their feedback.
Additionally, we would like to thank Martin Thomson, James Additionally, we would like to thank Martin Thomson, James
Winterbottom, Shida Schubert, Bernard Aboba, and Marc Linsner for Winterbottom, Shida Schubert, Bernard Aboba, and Marc Linsner for
their review comments. their review comments.
10. References 11. References
10.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[cap] Jones, E. and A. Botterell, "Common Alerting Protocol v. [cap] Jones, E. and A. Botterell, "Common Alerting Protocol v.
1.1", October 2005. 1.1 ", October 2005.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[I-D.ietf-ecrit-phonebcp]
Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in support of Emergency Calling",
draft-ietf-ecrit-phonebcp-20 (work in progress),
September 2011.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
for the Session Initiation Protocol", RFC 6442, Locators", RFC 2392, August 1998.
December 2011.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., [RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,
and D. Gurle, "Session Initiation Protocol (SIP) Extension and D. Gurle, "Session Initiation Protocol (SIP) Extension
for Instant Messaging", RFC 3428, December 2002. for Instant Messaging", RFC 3428, December 2002.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC3903] Niemi, A., "Session Initiation Protocol (SIP) Extension
for Event State Publication", RFC 3903, October 2004.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442, December
2011.
[RFC6665] Roach, A., "SIP-Specific Event Notification", RFC 6665,
July 2012.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013.
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Rosen, B., Tschofenig, H., Marshall, R., and R. Randy, Rosen, B., Tschofenig, H., Marshall, R., Randy, R., and J.
"Additional Data related to an Emergency Call", Winterbottom, "Additional Data related to an Emergency
draft-ietf-ecrit-additional-data-06 (work in progress), Call", draft-ietf-ecrit-additional-data-10 (work in
February 2013. progress), July 2013.
10.2. Informative References [I-D.rosen-ecrit-addldata-subnot]
Rosen, B., "Updating Additional Data related to an
Emergency Call using Subscribe/ Notify", draft-rosen-
ecrit-addldata-subnot-00 (work in progress), July 2013.
11.2. Informative References
[I-D.ietf-ecrit-trustworthy-location] [I-D.ietf-ecrit-trustworthy-location]
Tschofenig, H., Schulzrinne, H., and B. Aboba, Tschofenig, H., Schulzrinne, H., and B. Aboba,
"Trustworthy Location", "Trustworthy Location", draft-ietf-ecrit-trustworthy-
draft-ietf-ecrit-trustworthy-location-04 (work in location-06 (work in progress), July 2013.
progress), October 2012.
[RFC4474] Peterson, J. and C. Jennings, "Enhancements for [RFC4474] Peterson, J. and C. Jennings, "Enhancements for
Authenticated Identity Management in the Session Authenticated Identity Management in the Session
Initiation Protocol (SIP)", RFC 4474, August 2006. Initiation Protocol (SIP)", RFC 4474, August 2006.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325, Asserted Identity within Trusted Networks", RFC 3325,
November 2002. November 2002.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 2011. Multimedia", RFC 6443, December 2011.
Authors' Addresses Authors' Addresses
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US US
Phone:
Email: br@brianrosen.net Email: br@brianrosen.net
Henning Schulzrinne Henning Schulzrinne
Columbia University Columbia University
Department of Computer Science Department of Computer Science
450 Computer Science Building 450 Computer Science Building
New York, NY 10027 New York, NY 10027
US US
Phone: +1 212 939 7004 Phone: +1 212 939 7004
 End of changes. 49 change blocks. 
250 lines changed or deleted 289 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/