< draft-ietf-ecrit-ecall-08.txt   draft-ietf-ecrit-ecall-09.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Consultant Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: January 2, 2017 Individual Expires: January 22, 2017 Individual
July 1, 2016 July 21, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-08.txt draft-ietf-ecrit-ecall-09.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of the Pan European in- mechanisms to support the next generation of the Pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 January 2, 2017. This Internet-Draft will expire on January 22, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 8 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 9
8. eCall-Specific Control/Metadata . . . . . . . . . . . . . . . 9 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. The eCall Control Block . . . . . . . . . . . . . . . . . 10 9. eCall-Specific Control/Metadata . . . . . . . . . . . . . . . 10
8.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 11 9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 11
8.1.1.1. Attributes of the <ack> element . . . . . . . . . 11 9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 12
8.1.1.2. Child Elements of the <ack> element . . . . . . . 12 9.1.1.1. Attributes of the <ack> element . . . . . . . . . 12
8.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 12 9.1.1.2. Child Elements of the <ack> element . . . . . . . 13
8.1.2. The <request> element . . . . . . . . . . . . . . . . 12 9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 13
8.1.2.1. Attributes of the <request> element . . . . . . . 12 9.1.2. The <request> element . . . . . . . . . . . . . . . . 13
8.1.2.2. Request Example . . . . . . . . . . . . . . . . . 13 9.1.2.1. Attributes of the <request> element . . . . . . . 13
9. The emergencyCallData.eCall INFO package . . . . . . . . . . 13 9.1.2.2. Request Example . . . . . . . . . . . . . . . . . 14
9.1. INFO Package Requirements . . . . . . . . . . . . . . . . 13 10. The emergencyCallData.eCall INFO package . . . . . . . . . . 14
9.1.1. Overall Description . . . . . . . . . . . . . . . . . 14 10.1. INFO Package Requirements . . . . . . . . . . . . . . . 14
9.1.2. Applicability . . . . . . . . . . . . . . . . . . . . 14 10.1.1. Overall Description . . . . . . . . . . . . . . . . 14
9.1.3. Info Package Name . . . . . . . . . . . . . . . . . . 15 10.1.2. Applicability . . . . . . . . . . . . . . . . . . . 15
9.1.4. Info Package Parameters . . . . . . . . . . . . . . . 15 10.1.3. Info Package Name . . . . . . . . . . . . . . . . . 15
9.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . 15 10.1.4. Info Package Parameters . . . . . . . . . . . . . . 15
9.1.6. INFO Message Body Parts . . . . . . . . . . . . . . . 15 10.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 16
9.1.7. Info Package Usage Restrictions . . . . . . . . . . . 15 10.1.6. INFO Message Body Parts . . . . . . . . . . . . . . 16
9.1.8. Rate of INFO Requests . . . . . . . . . . . . . . . . 15 10.1.7. Info Package Usage Restrictions . . . . . . . . . . 16
9.1.9. Info Package Security Considerations . . . . . . . . 15 10.1.8. Rate of INFO Requests . . . . . . . . . . . . . . . 16
9.1.10. Implementation Details . . . . . . . . . . . . . . . 16 10.1.9. Info Package Security Considerations . . . . . . . . 16
9.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 16 10.1.10. Implementation Details . . . . . . . . . . . . . . . 16
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 16
11. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 20 12. Security Considerations . . . . . . . . . . . . . . . . . . . 22
13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 20 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 23
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Service URN Registrations . . . . . . . . . . . . . . . 22 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
14.2. MIME Content-type Registration for 15.1. Service URN Registrations . . . . . . . . . . . . . . . 25
'application/emergencyCallData.eCall.MSD+per' . . . . . 23 15.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 26
14.3. MIME Content-type Registration for 15.3. MIME Content-type Registration for
'application/emergencyCallData.eCall.control+xml' . . . 24 'application/emergencyCallData.eCall.control+xml' . . . 27
14.4. Registration of the 'eCall.MSD' entry in the Emergency 15.4. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 26 Call Additional Data Blocks registry . . . . . . . . . . 29
14.5. Registration of the 'eCall.control' entry in the 15.5. Registration of the 'eCall.control' entry in the
Emergency Call Additional Data Blocks registry . . . . . 26 Emergency Call Additional Data Blocks registry . . . . . 29
14.6. Registration of the emergencyCallData.eCall Info Package 26 15.6. Registration of the emergencyCallData.eCall Info Package 29
14.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 26 15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 29
14.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 26 15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 29
14.7.2. Registration for 15.7.2. Registration for
urn:ietf:params:xml:ns:eCall:control . . . . . . . . 27 urn:ietf:params:xml:ns:eCall:control . . . . . . . . 30
14.8. Registry creation . . . . . . . . . . . . . . . . . . . 28 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 31
14.8.1. eCall Control Action Registry . . . . . . . . . . . 28 15.8.1. eCall Control Action Registry . . . . . . . . . . . 31
14.8.2. eCall Control Extension Registry . . . . . . . . . . 29 15.8.2. eCall Control Extension Registry . . . . . . . . . . 32
15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 29 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 32
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
17. Changes from Previous Versions . . . . . . . . . . . . . . . 30 18. Changes from Previous Versions . . . . . . . . . . . . . . . 33
17.1. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 30 18.1. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 33
17.2. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 30 18.2. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 33
17.3. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 30 18.3. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 34
17.4. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 31 18.4. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 34
17.5. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 31 18.5. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 34
17.6. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 31 18.6. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 34
17.7. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 31 18.7. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 34
17.8. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 31 18.8. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 34
17.9. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 32 18.9. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 35
17.10. Changes from draft-gellens-02 to -03 . . . . . . . . . . 32 18.10. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 35
17.11. Changes from draft-gellens-01 to -02 . . . . . . . . . . 32 18.11. Changes from draft-gellens-02 to -03 . . . . . . . . . . 35
17.12. Changes from draft-gellens-00 to -01 . . . . . . . . . . 32 18.12. Changes from draft-gellens-01 to -02 . . . . . . . . . . 35
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 18.13. Changes from draft-gellens-00 to -01 . . . . . . . . . . 35
18.1. Normative References . . . . . . . . . . . . . . . . . . 32 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
18.2. Informative references . . . . . . . . . . . . . . . . . 34 19.1. Normative References . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 19.2. Informative references . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
1. Terminology 1. 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 [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
skipping to change at page 4, line 31 skipping to change at page 4, line 31
| | | | | |
| MSD | Minimum Set of Data | | MSD | Minimum Set of Data |
| | | | | |
| PSAP | Public Safety Answering Point | | PSAP | Public Safety Answering Point |
+--------+----------------------------------------+ +--------+----------------------------------------+
2. Document Scope 2. Document Scope
This document is limited to the signaling, data exchange, and This document is limited to the signaling, data exchange, and
protocol needs of next-generation eCall (NG-eCall, also referred to protocol needs of next-generation eCall (NG-eCall, also referred to
as packet-switched eCall (PS-eCall) and all-IP eCall) within the SIP as packet-switched eCall or all-IP eCall) within the SIP framework
framework for emergency calls, as described in [RFC6443] and for emergency calls, as described in [RFC6443] and [RFC6881]. eCall
[RFC6881]. eCall itself is specified by 3GPP and CEN and these itself is specified by 3GPP and CEN and these specifications include
specifications include far greater scope than is covered here. far greater scope than is covered here.
The eCall service operates over cellular wireless communication, but The eCall service operates over cellular wireless communication, but
this document does not address cellular-specific details, nor client this document does not address cellular-specific details, nor client
domain selection (e.g., circuit-switched versus packet-switched). domain selection (e.g., circuit-switched versus packet-switched).
All such aspects are the purview of their respective standards All such aspects are the purview of their respective standards
bodies. The scope of this document is limited to eCall operating bodies. The scope of this document is limited to eCall operating
within a SIP-based environment (e.g., 3GPP IMS Emergency Calling). within a SIP-based environment (e.g., 3GPP IMS Emergency Calling).
The technical contents of this document can be suitable for use in The technical contents of this document can be suitable for use in
other vehicle-initiated emergency call systems, but this is out of other vehicle-initiated emergency call systems, but this is out of
scope for this document. scope for this document.
Vehicles designed for multiple regions might need to support eCall Vehicles designed for multiple regions might need to support eCall
and other Advanced Automatic Crash Notification (AACN) systems, such and other Advanced Automatic Crash Notification (AACN) systems, such
as described in [I-D.ietf-ecrit-car-crash]. That system is as described in [I-D.ietf-ecrit-car-crash].
compatible with eCall, differing primarily in the specific data set
that is sent.
3. Introduction 3. Introduction
Emergency calls made from vehicles (e.g., in the event of a crash) Emergency calls made from vehicles (e.g., in the event of a crash)
assist in significantly reducing road deaths and injuries by allowing assist in significantly reducing road deaths and injuries by allowing
emergency services to be aware of the incident, the state of the emergency services to be aware of the incident, the state of the
vehicle, the location of the vehicle, and to have a voice channel vehicle, the location of the vehicle, and to have a voice channel
with the vehicle occupants. This enables a quick and appropriate with the vehicle occupants. This enables a quick and appropriate
response. response.
skipping to change at page 6, line 34 skipping to change at page 6, line 34
eCall requirements are specified by CEN in [EN_16072] and by 3GPP in eCall requirements are specified by CEN in [EN_16072] and by 3GPP in
[TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle [TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle
data are contained in EN 15722 [msd]. data are contained in EN 15722 [msd].
5. Vehicle Data 5. Vehicle Data
Pan-European eCall provides a standardized and mandated set of Pan-European eCall provides a standardized and mandated set of
vehicle related data, known as the Minimum Set of Data (MSD). The vehicle related data, known as the Minimum Set of Data (MSD). The
European Committee for Standardization (CEN) has specified this data European Committee for Standardization (CEN) has specified this data
in EN 15722 [msd], along with both ASN.1 and XML encodings for the in EN 15722 [msd], along with both ASN.1 and XML encodings. Both
MSD [msd]. Both circuit-switched eCall and this document use the circuit-switched eCall and this document use the ASN.1 PER encoding,
ASN.1 PER encoding, which is specified in Annex A of EN 15722 [msd] which is specified in Annex A of EN 15722 [msd] (the XML encoding
(the XML encoding specified in Annex C is not used in this document). specified in Annex C is not used in this document).
The "Additional Data related to an Emergency Call" document
[I-D.ietf-ecrit-additional-data] establishes a general mechanism for
attaching blocks of data to a SIP emergency call. This document
makes use of that mechanism to carry the eCall MSD in a SIP emergency
call.
This document registers the 'application/ This document registers the 'application/
emergencyCallData.eCall.MSD+per' MIME Content-Type to enable the MSD emergencyCallData.eCall.MSD+per' MIME Content-Type to enable the MSD
to be carried in SIP. As an ASN.1 PER encoded object, the data is to be carried in SIP. As an ASN.1 PER encoded object, the data is
binary and transported using binary content transfer encoding within binary and transported using binary content transfer encoding within
SIP messages. This document also adds the 'eCall.MSD' entry to the SIP messages. This document also adds the 'eCall.MSD' entry to the
Emergency Call Additional Data Blocks registry (established by Emergency Call Additional Data Blocks registry to enable the MSD to
[I-D.ietf-ecrit-additional-data]) to enable the MSD to be recognized be recognized as such in a SIP-based eCall emergency call. (See
as such in a SIP-based eCall emergency call. [I-D.ietf-ecrit-additional-data] for more information about the
registry and how it is used.)
See Section 6 for a discussion of how the MSD vehicle data is
conveyed in an NG-eCall.
6. Data Transport
The "Additional Data related to an Emergency Call" document
[I-D.ietf-ecrit-additional-data] establishes a general mechanism for
attaching blocks of data to a SIP emergency call. This mechanism
permits certain MIME types to be attached to SIP messages. This
document makes use of that mechanism.
Note that if additional data sets are defined and registered (e.g., Note that if additional data sets are defined and registered (e.g.,
in the future or in other regions) and transmitted using the same in the future or in other regions) and transmitted using the same
mechanisms, the size and frequency of transmission during a dialog mechanisms, the size and frequency of transmission during a dialog
need to be evaluated to be sure it is appropriate to use the need to be evaluated to be sure it is appropriate to use the
signaling channel. signaling channel.
6. Call Setup An In-Vehicle System (IVS) transmits the MSD (see Section 5) by
encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP
message as a MIME body part per [I-D.ietf-ecrit-additional-data].
The body part is identified by its MIME content-type ('application/
emergencyCallData.eCall.MSD+per') in the Content-Type header field of
the body part. The body part is assigned a unique identifier which
is listed in a Content-ID header field in the body part. The SIP
message is marked as containing the MSD by adding (or appending to) a
Call-Info header field at the top level of the SIP message. This
Call-Info header field contains a CID URL referencing the body part's
unique identifier, and a 'purpose' parameter identifying the data as
the eCall MSD per the Emergency Call Additional Data Blocks registry
entry; the 'purpose' parameter's value is
'emergencyCallData.eCall.MSD'.
A PSAP transmits a metadata/control object (see Section 9) by
encoding it per the description in this document and attaching it to
a SIP message as a MIME body part per
[I-D.ietf-ecrit-additional-data]. The body part is identified by its
MIME content-type ('application/emergencyCallData.eCall.control+xml')
in the Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header
field in the body part. The SIP message is marked as containing the
MSD by adding (or appending to) a Call-Info header field at the top
level of the SIP message. This Call-Info header field contains a CID
URL referencing the body part's unique identifier, and a 'purpose'
parameter identifying the data as an eCall metadata/control block per
the Emergency Call Additional Data Blocks registry entry; the
'purpose' parameter's value is 'emergencyCallData.eCall.control'.
An In-Vehicle System (IVS) initiating an NG-eCall attaches the MSD to
the initial INVITE. The PSAP creates a metadata/control object
acknowledging receipt of the MSD and attaches it to the SIP response
to the INVITE.
A PSAP can request the vehicle to send an updated MSD during a call.
The PSAP creates a metadata/control object requesting the MSD and
attaches it to a SIP INFO message which it sends within the dialog.
The IVS then attaches an updated MSD to a SIP INFO message and sends
it within the dialog. The metadata/control object and the MSD are
attached to an INFO message in the same way they are attached to
other messages (such as the INVITE and the reply to the INVITE as
discussed above). See Section 10 for information about the use of
INFO messages to carry data within an eCall.
When data is being carried in an INFO request message, the body part
also carries a Content-Disposition header field set to "Info-
Package".
Support for the data blocks defined in
[I-D.ietf-ecrit-additional-data] is NOT REQUIRED for conformance with
this document .
7. Call Setup
In circuit-switched eCall, the IVS places a special form of a 112 In circuit-switched eCall, the IVS places a special form of a 112
emergency call which carries an eCall flag (indicating that the call emergency call which carries an eCall flag (indicating that the call
is an eCall and also if the call was manually or automatically is an eCall and also if the call was manually or automatically
triggered); the mobile network operator (MNO) recognizes the eCall triggered); the mobile network operator (MNO) recognizes the eCall
flag and routes the call to an eCall-capable PSAP; vehicle data is flag and routes the call to an eCall-capable PSAP; vehicle data is
transmitted to the PSAP via the eCall in-band modem (in the voice transmitted to the PSAP via the eCall in-band modem (in the voice
channel). channel).
///----\\\ 112 voice call with eCall flag +------+ ///----\\\ 112 voice call with eCall flag +------+
||| IVS |||---------------------------------------->+ PSAP | ||| IVS |||---------------------------------------->+ PSAP |
\\\----/// vehicle data via eCall in-band modem +------+ \\\----/// vehicle data via eCall in-band modem +------+
Figure 1: circuit-switched eCall Figure 1: circuit-switched eCall
An In-Vehicle System (IVS) initiating an NG-eCall transmits the MSD
in accordance with [I-D.ietf-ecrit-additional-data] by encoding it as
specified (per Annex A of EN 15722 [msd]) and attaching it to an
INVITE as a MIME body part. The body part is identified by its MIME
content-type ('application/emergencyCallData.eCall.MSD+per') in the
Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header
field in the body part. The INVITE is marked as containing the MSD
by adding (or appending to) a Call-Info header field at the top level
of the INVITE. This Call-Info header field contains a CID URL
referencing the body part's unique identifier, and a 'purpose'
parameter identifying the data as the eCall MSD per the registry
entry; the 'purpose' parameter's value is 'emergencyCallData.' plus
the root of the MIME type (not including the 'emergencyCallData.'
prefix and any suffix such as '+per', so in this case,
'purpose=emergencyCallData.eCall.MSD'.
For NG-eCall, the IVS establishes an emergency call using a Request- For NG-eCall, the IVS establishes an emergency call using a Request-
URI indicating a manual or automatic eCall; the MNO (or ESInet) URI indicating a manual or automatic eCall; the MNO (or ESInet)
recognizes the eCall URN and routes the call to an NG-eCall capable recognizes the eCall URN and routes the call to an NG-eCall capable
PSAP; the PSAP interpets the vehicle data sent with the call and PSAP; the PSAP interpets the vehicle data sent with the call and
makes it available to the call taker. makes it available to the call taker.
///----\\\ IMS emergency call with eCall URN +------+ ///----\\\ IMS emergency call with eCall URN +------+
IVS ----------------------------------------->+ PSAP | IVS ----------------------------------------->+ PSAP |
\\\----/// vehicle data included in call setup +------+ \\\----/// vehicle data included in call setup +------+
Figure 2: NG-eCall Figure 2: NG-eCall
See Section 6 for information on how the MSD is transported within an
NG-eCall.
This document registers new service URN children within the "sos" This document registers new service URN children within the "sos"
subservice. These URNs provide the mechanism by which an eCall is subservice. These URNs provide the mechanism by which an eCall is
identified, and differentiate between manually and automatically identified, and differentiate between manually and automatically
triggered eCalls (which might be subject to different treatment, triggered eCalls (which might be subject to different treatment,
depending on policy). The two service URNs are: depending on policy). The two service URNs are:
urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual,
which requests resources associated with an emergency call placed by
an in-vehicle system, carrying a standardized set of data related to
the vehicle and incident.
6.1. Call Routing 7.1. Call Routing
The routing applied to eCalls might differ from those of other The routing applied to eCalls might differ from those of other
emergency calls, as eCalls are intended to be handled by PSAPs that emergency calls, as eCalls are intended to be handled by PSAPs that
support eCall. In regions without ESInets, typically the emergency support eCall. In regions without ESInets, typically the emergency
services authorities and the originating network determine how such services authorities and the originating network determine how such
calls are routed. In a region that uses ESInets, the originating calls are routed. In a region that uses ESInets, the originating
network passes all types of emergency calls to an ESInet (calls which network passes all types of emergency calls to an ESInet (calls which
have a request URI containing the "SOS" service URN). The ESInet is have a request URI containing the "SOS" service URN). The ESInet is
then responsible for routing such calls to the appropriate PSAP. then responsible for routing such calls to the appropriate PSAP.
7. Test Calls 8. Test Calls
eCall requires the ability to place test calls. These are calls that eCall requires the ability to place test calls (see [TS22.101] clause
are recognized and treated to some extent as eCalls but are not given 10.7 and [EN_16062] clause 7.2.2). These are calls that are
recognized and treated to some extent as eCalls but are not given
emergency call treatment and are not handled by call takers. The emergency call treatment and are not handled by call takers. The
specific handling of test eCalls is not itself standardized; specific handling of test eCalls is not itself standardized;
typically, the test call facility allows the IVS or user to verify typically, the test call facility allows the IVS or user to verify
that an eCall can be successfully established with voice that an eCall can be successfully established with voice
communication. The IVS might also be able to verify that the MSD was communication. The IVS might also be able to verify that the MSD was
successfully received. successfully received.
A service URN starting with "test." indicates a test call. For A service URN starting with "test." indicates a test call. For
eCall, "urn:service:test.sos.ecall" indicates such a test feature. eCall, "urn:service:test.sos.ecall" indicates such a test feature.
This functionality is defined in [RFC6881]. This functionality is defined in [RFC6881].
This document registers "urn:service:test.sos.ecall" for eCall test This document registers "urn:service:test.sos.ecall" for eCall test
calls. calls.
The CS-eCall test call facility is a non-emergency number so does not The CS-eCall test call facility is a non-emergency number so does not
get treated as an emergency call. For NG-eCall, MNOs, emergency get treated as an emergency call. For NG-eCall, MNOs, emergency
authorities, and PSAPs can determine how to treat a vehicle call authorities, and PSAPs can determine how to treat a vehicle call
requesting the "test" service URN so that the desired functionality requesting the "test" service URN so that the desired functionality
is tested, but this is outside the scope of this document. (One is tested, but this is outside the scope of this document.
possibility is that MNOs route such calls as non-emergency calls to a
PSAP that supports NG-eCall; the PSAP accepts test calls, sends an
MSD acknowledgment, and plays an audio clip (for example, saying that
the call reached an eCall PSAP) in addition to supporting media
loopback per [RFC6881]).
8. eCall-Specific Control/Metadata 9. eCall-Specific Control/Metadata
eCall requires the ability for the PSAP to acknowledge successful eCall requires the ability for the PSAP to acknowledge successful
receipt of an MSD sent by the IVS, and for the PSAP to request that receipt of an MSD sent by the IVS, and for the PSAP to request that
the IVS send an MSD (e.g., the call taker can initiate a request for the IVS send an MSD (e.g., the call taker can initiate a request for
a new MSD to see if there have been changes in the vehicle's state, a new MSD to see if there have been changes in the vehicle's state,
e.g., location, direction, number of fastened seatbelts). e.g., location, direction, number of fastened seatbelts).
The mechanism established in [I-D.ietf-ecrit-additional-data], used This document defines a block of metadata/control data as an XML
in Section 5 of this document to carry the MSD from the IVS to the structure containing eCall-specific elements. When the PSAP needs to
PSAP, is also used to carry a block of metadata/control data from the send an eCall control block that is in response to data sent by the
PSAP to the IVS. This eCall control block (sometimes referred to as IVS in a SIP request (e.g., the MSD in the initial INVITE), the
eCall metadata) is an XML structure containing eCall-specific control block can be sent in the SIP response to that request (e.g.,
elements. When the PSAP needs to send an eCall control block that is the response to the INVITE request). When the PSAP needs to send an
in response to data sent by the IVS in a SIP request (e.g., the MSD eCall control block in other circumstances (e.g., mid-call), the
in the initial INVITE), the control block can be sent in the SIP control block can be transmitted from the PSAP to the IVS in a SIP
response to that request (e.g., the response to the INVITE request). INFO request within the established dialog. The IVS sends the
When the PSAP needs to send an eCall control block in other requested data (the MSD) in a new INFO request. This mechanism
circumstances (e.g., mid-call), the control block can be transmitted flexibly allows the PSAP to send eCall-specific data to the IVS and
from the PSAP to the IVS in a SIP INFO request within the established the IVS to respond. See Section 6 for more information on attaching
dialog. The IVS sends the requested data (the MSD) in a new INFO a metadata/control block to a SIP message.
request. This mechanism flexibly allows the PSAP to send eCall-
specific data to the IVS and the IVS to respond.
This mechanism requires This mechanism requires
o An XML definition of the eCall control object o An XML definition of the eCall control object
o An extension mechanism by which new elements, attributes, and o An extension mechanism by which new elements, attributes, and
values can be added to the control object definition values can be added to the control object definition
o A MIME type registration for the control object (so it can be o A MIME type registration for the control object (so it can be
carried in SIP messages and responses) carried in SIP messages and responses)
o An entry in the Emergency Call Additional Data Blocks sub-registry o An entry in the Emergency Call Additional Data Blocks sub-registry
(established by [I-D.ietf-ecrit-additional-data]) so that the (established by [I-D.ietf-ecrit-additional-data]) so that the
skipping to change at page 10, line 6 skipping to change at page 10, line 48
o An Info-Package registration per [RFC6086] permitting data blocks o An Info-Package registration per [RFC6086] permitting data blocks
registered in the Emergency Call Additional Data Blocks sub- registered in the Emergency Call Additional Data Blocks sub-
registry (established by [I-D.ietf-ecrit-additional-data]) within registry (established by [I-D.ietf-ecrit-additional-data]) within
Info messages Info messages
When the IVS includes an unsolicited MSD in a SIP request (e.g., the When the IVS includes an unsolicited MSD in a SIP request (e.g., the
initial INVITE), the PSAP sends a metadata/control block indicating initial INVITE), the PSAP sends a metadata/control block indicating
successful/unsuccessful receipt of the MSD in the SIP response to the successful/unsuccessful receipt of the MSD in the SIP response to the
request. This also informs the IVS that an NG-eCall is in operation. request. This also informs the IVS that an NG-eCall is in operation.
If the IVS receives a SIP response without the metadata/control If the IVS receives a SIP response without the metadata/control
block, it indicates that the SIP dialog is not an NG-eCall. When the block, it indicates that the SIP dialog is not an NG-eCall (e.g.,
some part of the call is being handled as a legacy call). When the
IVS sends a solicited MSD (e.g., in a SIP INFO request sent following IVS sends a solicited MSD (e.g., in a SIP INFO request sent following
receipt of a SIP INFO request containing a metadata/control block receipt of a SIP INFO request containing a metadata/control block
requesting an MSD), the PSAP does not send a metadata/control block requesting an MSD), the PSAP does not send a metadata/control block
indicating successful or unsuccessful receipt of the MSD. (Normal indicating successful or unsuccessful receipt of the MSD. (Normal
SIP retransmission handles non-receipt of requested data; if the IVS SIP retransmission handles non-receipt of requested data; if the IVS
sends a requested MSD in an INFO request and does not receive a SIP sends a requested MSD in an INFO request and does not receive a SIP
status message for the INFO request, it resends it; if the PSAP status message for the INFO request, it resends it; if the PSAP
requests an MSD and does not receive a SIP status message for the requests an MSD and does not receive a SIP status message for the
INFO request, it resends it.) INFO request, it resends it.)
This provides flexibility to handle various circumstances. For This provides flexibility to handle various circumstances. For
example, if a PSAP is unable to accept an eCall (e.g., due to example, if a PSAP is unable to accept an eCall (e.g., due to
overload or too many calls from the same location), it can reject the overload or too many calls from the same location), it can reject the
INVITE. Since a metadata/control object is also included in the SIP INVITE. Since a metadata/control object is also included in the SIP
response that rejects the call, the IVS knows if the PSAP received response that rejects the call, the IVS knows if the PSAP received
the MSD, and can inform the occupants that the PSAP successfully the MSD, and can inform the vehicle occupants that the PSAP
received the vehicle location and information but can't talk to the successfully received the vehicle location and information but can't
occupants at that time. Especially for SIP response codes that talk to the occupants at that time. Especially for SIP response
indicate an inability to conduct a call (as opposed to a technical codes that indicate an inability to conduct a call (as opposed to a
inability to process the request), the IVS can also determine that technical inability to process the request), the IVS can also
the call was successful on a technical level (e.g., not necessary to determine that the call was successful on a technical level (e.g.,
retry as a CS-eCall). The SIP response code 600 (Busy Everywhere) not helpful to retry as a CS-eCall). The SIP response codes 600
can be used to indicate this. Other SIP response codes that can be (Busy Everywhere), 486 (Busy Here), and 603 (Decline) are used when
interpreted in this way include 480 (Temporarily Unavailable), 486 the PSAP wants to reject a call but inform the vehicle occupants that
(Busy Here), and 603 (Decline). it is aware of the situation. (Note that there could be edge cases
where the PSAP response is not received by the IVS, e.g., if an
intermediary sends a CANCEL, and an error response is forwarded
towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.)
8.1. The eCall Control Block 9.1. The eCall Control Block
The eCall control block is an XML data structure allowing for The eCall control block is an XML data structure allowing for
acknowledgments and requests. It is carried in a SIP body part with acknowledgments and requests. It is carried in a SIP body part with
a specific MIME content type. It can be extended via an IANA a specific MIME content type. It can be extended via an IANA
registry to add additional elements, attributes, and values. Two registry to add additional elements, attributes, and values. Two
top-level elements are defined for use within an eCall control block: top-level elements are defined for use within an eCall control block:
ack Used in a control block sent by the PSAP to acknowledge ack Used in a control block sent by the PSAP to acknowledge
receipt of a data set sent by the IVS. receipt of a data set sent by the IVS.
skipping to change at page 11, line 4 skipping to change at page 11, line 50
receipt of a data set sent by the IVS. receipt of a data set sent by the IVS.
request Used in a control block sent by the PSAP to request the request Used in a control block sent by the PSAP to request the
vehicle to perform an action. The only action defined vehicle to perform an action. The only action defined
in this document is a request for the IVS to send an in this document is a request for the IVS to send an
MSD. MSD.
Mandatory Actions (the IVS and the PSAP MUST support): Mandatory Actions (the IVS and the PSAP MUST support):
o Transmit data object o Transmit data object
Optional Actions (the IVS and the PSAP MAY support): Optional Actions (the IVS and the PSAP MAY support):
o None o None
The <ack> element indicates the object being acknowledged (e.g., the The <ack> element indicates the object being acknowledged (e.g., the
MSD), and reports success or failure. MSD), and reports success or failure.
The <request> element contains attributes to indicate the request and The <request> element contains attributes to indicate the request and
to supply related information. The 'action' attribute is mandatory to supply related information. The 'action' attribute is mandatory
and indicates the specific action. An IANA registry is created in and indicates the specific action. An IANA registry is created in
Section 14.8.1 to contain the allowed values. Section 15.8.1 to contain the allowed values.
Extensibility: New elements, child elements, attributes of new and Extensibility: New elements, child elements, attributes of new and
existing elements, and values for new and existing attributes can be existing elements, and values for new and existing attributes can be
added in the IANA registry created in Section 14.8.2. The registry added in the IANA registry created in Section 15.8.2. The registry
permits implementors to see what has been added, with a reference to permits implementors to see what has been added, with a reference to
the defining document. (Implementations are not expected to the defining document. (Implementations are not expected to
dynamically check the registry.) Implementations MUST ignore dynamically check the registry.) Implementations MUST ignore
unsupported elements, attributes, and values. unrecognized elements, attributes, and values (this allows new items
to be added without breaking older implementations).
8.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element is transmitted by the PSAP to acknowledge receipt The <ack> element is transmitted by the PSAP to acknowledge receipt
of an eCall data object. An <ack> element sent by a PSAP references of an eCall data object. An <ack> element sent by a PSAP references
the unique ID of the data object that was sent by the IVS, and the unique ID of the data object that was sent by the IVS, and
further indicates if the PSAP considers the receipt successful or further indicates if the PSAP considers the receipt successful or
not. not.
The <ack> element has the following attributes: The <ack> element has the following attributes:
8.1.1.1. Attributes of the <ack> element 9.1.1.1. Attributes of the <ack> element
The <ack> element has the following attributes: The <ack> element has the following attributes:
Name: ref Name: ref
Usage: Mandatory Usage: Mandatory
Type: anyURI Type: anyURI
Description: References the Content-ID of the body part that Description: References the Content-ID of the body part that
contained the data object being acknowledged. contained the data object being acknowledged.
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/> Example: <ack received="yes" ref="1234567890@atlanta.example.com"/>
Name: received Name: received
Usage: Conditional: mandatory in an >ack< element sent by a PSAP Usage: Conditional: mandatory in an >ack< element sent by a PSAP
Type: Boolean Type: Boolean
Description: Indicates if the referenced object was successfully Description: Indicates if the referenced object was successfully
received or not received or not
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/> Example: <ack received="yes" ref="1234567890@atlanta.example.com"/>
8.1.1.2. Child Elements of the <ack> element 9.1.1.2. Child Elements of the <ack> element
The <ack> element has no child elements The <ack> element has no child elements
8.1.1.3. Ack Examples 9.1.1.3. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<ack received="true" ref="1234567890@atlanta.example.com"/> <ack received="true" ref="1234567890@atlanta.example.com"/>
</EmergencyCallData.eCall.Control> </EmergencyCallData.eCall.Control>
Figure 3: Ack Example from PSAP to IVS Figure 3: Ack Example from PSAP to IVS
8.1.2. The <request> element 9.1.2. The <request> element
A <request> element allows the PSAP to request that the IVS send an A <request> element allows the PSAP to request that the IVS send an
MSD. The following attributes are defined: MSD. The following attributes are defined:
8.1.2.1. Attributes of the <request> element 9.1.2.1. Attributes of the <request> element
The <request> element has the following attributes: The <request> element has the following attributes:
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Description: Identifies the action that the vehicle is requested to Description: Identifies the action that the vehicle is requested to
perform. An IANA registry is established in Section 14.8.1 to perform. An IANA registry is established in Section 15.8.1 to
contain the allowed values. contain the allowed values.
Example: action="send-data" Example: action="send-data"
Name: datatype Name: datatype
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Mandatory with a "send-data" action. Specifies the Description: Mandatory with a "send-data" action. Specifies the
data block that the IVS is requested to transmit, using the same data block that the IVS is requested to transmit, using the same
identifier as in the 'purpose' attribute set in a Call-Info header identifier as in the 'purpose' attribute set in a Call-Info header
field to point to the data block. Permitted values are contained field to point to the data block. Permitted values are contained
in the 'Emergency Call Data Types' IANA registry established in in the 'Emergency Call Data Types' IANA registry established in
[I-D.ietf-ecrit-additional-data]. [I-D.ietf-ecrit-additional-data]. Only the "eCall.MSD" value is
mandatory to support.
Example: datatype="eCall.MSD" Example: datatype="eCall.MSD"
8.1.2.2. Request Example 9.1.2.2. Request Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<request action="send-data" datatype="eCall.MSD"/> <request action="send-data" datatype="eCall.MSD"/>
</EmergencyCallData.eCall.Control> </EmergencyCallData.eCall.Control>
Figure 4: Request Example Figure 4: Request Example
9. The emergencyCallData.eCall INFO package 10. The emergencyCallData.eCall INFO package
This document registers the 'emergencyCallData.eCall' INFO package. This document registers the 'emergencyCallData.eCall' INFO package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall' in a Recv-Info header field per [RFC6086] 'emergencyCallData.eCall' in a Recv-Info header field per [RFC6086]
to indicate ability to receive INFO messages carrying data as to indicate ability to receive INFO messages carrying data as
described here. described here.
Support for the 'emergencyCallData.eCall' INFO package indicates the Support for the 'emergencyCallData.eCall' INFO package indicates the
ability to receive body parts registered in the 'Emergency Call Data ability to receive body parts registered in the 'Emergency Call Data
Types' IANA registry established in [I-D.ietf-ecrit-additional-data]. Types' IANA registry.
An INFO request message carrying data related to an emergency call An INFO request message carrying data related to an emergency call
has an Info-Package header field set to 'emergencyCallData.eCall' per has an Info-Package header field set to 'emergencyCallData.eCall' per
[RFC6086]. Per [I-D.ietf-ecrit-additional-data], the INFO request [RFC6086]. See Section 6 for details on how to attach eCall data to
message contains one or more Call-Info header fields containing a CID an INFO message.
URL referencing the unique identifier of a body part, and a 'purpose'
parameter identifying the data. Because the data is being carried in
an INFO request message, the body part also carries a Content-
Disposition header field set to "Info-Package".
9.1. INFO Package Requirements 10.1. INFO Package Requirements
The requirements of Section 10 of [RFC6086] are addressed in the The requirements of Section 10 of [RFC6086] are addressed in the
following sections. following sections.
9.1.1. Overall Description 10.1.1. Overall Description
This section describes "what type of information is carried in INFO This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package." applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall INFO INFO requests associated with the emergencyCallData.eCall INFO
package carry data associated with emergency calls as registered in package carry data associated with emergency calls as registered in
the 'Emergency Call Data Types' IANA registry established in the 'Emergency Call Data Types' IANA registry. The application is
[I-D.ietf-ecrit-additional-data]. The application is emergency calls emergency calls established using SIP. The functionality is to carry
established using SIP. The functionality is to carry data, metadata, data, metadata, and control information (requests) between vehicles
and control information (requests) between vehicles and PSAPs. Refer and PSAPs. Refer to [TBD: THIS DOCUMENT] for more information.
to [TBD: THIS DOCUMENT] for more information.
9.1.2. Applicability 10.1.2. Applicability
This section describes "why the Info Package mechanism, rather than This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...." some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, emergency call data blocks occurs within a SIP emergency dialog, per
using the mechanism established in [I-D.ietf-ecrit-additional-data], Section 6, and is normally carried in the initial INVITE and its
and is normally carried in the initial INVITE and its response; the response; the use of INFO only occurs when emergency-call-related
use of INFO only occurs when emergency-call-related data needs to be data needs to be sent mid-call. While MESSAGE could be used, it is
sent mid-call. While MESSAGE could be used, it is not tied to a SIP not tied to a SIP dialog as is INFO and thus might not be associated
dialog as is INFO and thus might not be associated with the dialog. with the dialog. SIP OPTIONS or re-INVITE could also be used, but is
SIP OPTIONS or re-INVITE could also be used, but is seen as less seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into
clean than INFO. SUBSCRIBE/NOTIFY could be coerced into service, but service, but the semantics are not a good fit, e.g., the subscribe/
the semantics are not a good fit, e.g., the subscribe/notify notify mechanism provides one-way communication consisting of (often
mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog. is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport) overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large, and further, a high-level would be disproportionately large.
application protocol identifying the specific data block being sent
within the media plane (as provided by the Call-Info header field
parameters and MIME body part content type within INFO) would need to
be defined.
Based on the the analyses, the SIP INFO method was chosen to provide Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport. for mid-call data transport.
9.1.3. Info Package Name 10.1.3. Info Package Name
The info package name is emergencyCallData.eCall. The info package name is emergencyCallData.eCall.
9.1.4. Info Package Parameters 10.1.4. Info Package Parameters
None. None.
9.1.5. SIP Option-Tags 10.1.5. SIP Option-Tags
None. None.
9.1.6. INFO Message Body Parts 10.1.6. INFO Message Body Parts
Only those body parts registered in the 'Emergency Call Data Types' Only those body parts registered in the 'Emergency Call Data Types'
IANA registry established in [I-D.ietf-ecrit-additional-data] are IANA registry are associated with this INFO package.
associated with this INFO package.
When more than one body part is included, they are enclosed in a When more than one body part is included, they are enclosed in a
multipart body part (e.g., multipart/mixed). When a body part is multipart body part (e.g., multipart/mixed). When a body part is
digitally signed or encrypted, it is enclosed in an appropriate body digitally signed or encrypted, it is enclosed in an appropriate body
part (e.g., multipart/signed or multipart/encrypted). part (e.g., multipart/signed or multipart/encrypted).
The Content-Disposition value of a message body part associated with The Content-Disposition value of a message body part associated with
the emergencyCallData.eCall info package is "info-package". the emergencyCallData.eCall info package is "info-package".
9.1.7. Info Package Usage Restrictions 10.1.7. Info Package Usage Restrictions
None. None.
9.1.8. Rate of INFO Requests 10.1.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The rate of SIP INFO requests associated with the
emergencyCallData.eCall info package is expected to be quite low emergencyCallData.eCall info package is expected to be quite low
(most dialogs are likely to contain zero INFO requests, while others (most dialogs are likely to contain zero INFO requests, while others
can be expected to carry occasional requests). can be expected to carry occasional requests).
9.1.9. Info Package Security Considerations 10.1.9. Info Package Security Considerations
The MIME content type registation for each data block registered in The MIME content type registation for each data block listed in the
the 'Emergency Call Data Types' IANA registry established in 'Emergency Call Data Types' IANA registry contains a discussion of
[I-D.ietf-ecrit-additional-data] contains a discussion of the the security and/or privacy considerations specific to that data
security and/or privacy considerations specific to that data block. block. The "Security Considerations" and "Privacy Considerations"
The "Security Considerations" and "Privacy Considerations" sections sections of [TBD: THIS DOCUMENT] discuss security and privacy
of [TBD: THIS DOCUMENT] discuss security and privacy considerations considerations of the data carried in eCealls.
of the data carried in eCealls.
9.1.10. Implementation Details 10.1.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
9.1.11. Examples 10.1.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See [TBD: THIS DOCUMENT] for protocol examples.
10. Examples 11. Examples
Figure 5 illustrates an eCall. The call uses the request URI Figure 5 illustrates an eCall. The call uses the request URI
'urn:service:sos.ecall.automatic' service URN and is recognized as an 'urn:service:sos.ecall.automatic' service URN and is recognized as an
eCall, and further as one that was invoked automatically by the IVS eCall, and further as one that was invoked automatically by the IVS
due to a crash or other serious incident. In this example, the due to a crash or other serious incident. In this example, the
originating network routes the call to an ESInet which routes the originating network routes the call to an ESInet which routes the
call to the appropriate NG-eCall capable PSAP. The emergency call is call to the appropriate NG-eCall capable PSAP. The emergency call is
received by the ESInet's Emergency Services Routing Proxy (ESRP), as received by the ESInet's Emergency Services Routing Proxy (ESRP), as
the entry point into the ESInet. The ESRP routes the call to a PSAP, the entry point into the ESInet. The ESRP routes the call to a PSAP,
where it is received by a call taker. In deployments where there is where it is received by a call taker. In deployments where there is
skipping to change at page 16, line 46 skipping to change at page 17, line 38
| | | | | | | |
| | | +-------+ | | | | +-------+ |
| | | | PSAP3 | | | | | | PSAP3 | |
| Originating| | +-------+ | | Originating| | +-------+ |
| Mobile | | | | Mobile | | |
| Network | | ESInet | | Network | | ESInet |
+------------+ +---------------------------------------+ +------------+ +---------------------------------------+
Figure 5: Example of NG-eCall Message Flow Figure 5: Example of NG-eCall Message Flow
The example, shown in Figure 6, illustrates a SIP eCall INVITE that Figure 6 illustrates an eCall call flow with a mid-call PSAP request
for an updated MSD. The call flow shows the IVS initiating an
emergency call, including the MSD in the INVITE. The PSAP includes
in the 200 OK response a metadata/control object acknowledging
receipt of the MSD. During the call, the PSAP sends a request for an
MSD in an INFO message. The IVS sends the requested MSD in a new
INFO message.
IVS PSAP
|(1) INVITE (eCall MSD) |
|------------------------------------------->|
| |
|(2) 200 OK (eCall metadata [ack MSD]) |
|<-------------------------------------------|
| |
|(3) start media stream(s) |
|............................................|
| |
|(4) INFO (eCall metadata [request MSD]) |
|<-------------------------------------------|
| |
|(5) 200 OK |
|------------------------------------------->|
| |
|(6) INFO (eCall MSD) |
|------------------------------------------->|
| |
|(7) 200 OK |
|<-------------------------------------------|
| |
|(8) BYE |
|<-------------------------------------------|
| |
|(9) end media streams |
|............................................|
| |
|(10) 200 OK |
|------------------------------------------->|
Figure 6: NG-eCall Call Flow Illustration
The example, shown in Figure 7, illustrates a SIP eCall INVITE that
contains an MSD. For simplicity, the example does not show all SIP contains an MSD. For simplicity, the example does not show all SIP
headers, nor the SDP contents, nor does it show any additional data headers, nor the SDP contents, nor does it show any additional data
blocks added by the IVS or the originating mobile network. Because blocks added by the IVS or the originating mobile network. Because
the MSD is encoded in ASN.1 PER, which is a binary encoding, its the MSD is encoded in ASN.1 PER, which is a binary encoding, its
contents cannot be included in a text document. contents cannot be included in a text document.
INVITE urn:service:sos.ecall.automatic SIP/2.0 INVITE urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Geolocation: <cid:target123@example.com> Geolocation: <cid:target123@example.com>
Geolocation-Routing: no Geolocation-Routing: no
Call-Info: cid:1234567890@atlanta.example.com; Call-Info: cid:1234567890@atlanta.example.com;
purpose=emergencyCallData.eCall.MSD; purpose=emergencyCallData.eCall.MSD;
cid:2345678901@atlanta.example.com;
purpose=emergencyCallData.eCall.control;
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml application/emergencyCallData.eCall.control+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall Recv-Info: emergencyCallData.eCall
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
skipping to change at page 17, line 39 skipping to change at page 19, line 37
--boundary1 --boundary1
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: 1234567890@atlanta.example.com Content-ID: 1234567890@atlanta.example.com
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
Content-Transfer-Encoding: binary Content-Transfer-Encoding: binary
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundary1-- --boundary1--
Figure 6: SIP NG-eCall INVITE Figure 7: SIP NG-eCall INVITE
Continuing the example, Figure 7 illustrates a SIP 200 OK response to Continuing the example, Figure 8 illustrates a SIP 200 OK response to
the INVITE of Figure 6, containing an eCall control block the INVITE of Figure 7, containing an eCall control block
acknowledging successful receipt of the eCall MSD. (For simplicity, acknowledging successful receipt of the eCall MSD. (For simplicity,
the example does not show all SIP headers.) the example does not show all SIP headers.)
SIP/2.0 200 OK SIP/2.0 200 OK
To: <sip:+13145551111@example.com>;tag=9fxced76sl To: <sip:+13145551111@example.com>;tag=9fxced76sl
From: Exemplar PSAP <urn:service:sos.ecall.automatic> From: Exemplar PSAP <urn:service:sos.ecall.automatic>
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:2345678901@atlanta.example.com; Call-Info: cid:2345678901@atlanta.example.com;
purpose=emergencyCallData.eCall.control; purpose=emergencyCallData.eCall.control;
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml, application/emergencyCallData.eCall.control+xml,
skipping to change at page 18, line 43 skipping to change at page 20, line 43
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<ack received="true" ref="1234567890@atlanta.example.com"/> <ack received="true" ref="1234567890@atlanta.example.com"/>
</EmergencyCallData.eCall.Control> </EmergencyCallData.eCall.Control>
--boundaryX-- --boundaryX--
Figure 7: 200 OK response to INVITE Figure 8: 200 OK response to INVITE
11. Security Considerations Figure 9 illustrates an INFO message containing an eCall metadata/
control block requesting an eCall MSD. (For simplicity, the example
does not show all SIP headers.)
INFO sip:+13145551111@example.com SIP/2.0
To: <sip:+13145551111@example.com>;tag=9fxced76sl
From: Exemplar PSAP <urn:service:sos.ecall.automatic>
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:3456789012@atlanta.example.com;
purpose=emergencyCallData.eCall.control;
Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml,
application/emergencyCallData.eCall.MSD+per
CSeq: 41862 INFO
Recv-Info: emergencyCallData.eCall
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE
Content-Type: application/EmergencyCallData.eCall.control+xml
Content-ID: 3456789012@atlanta.example.com
Content-Disposition: info-package
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<request action="send-data" datatype="eCall.MSD"/>
</EmergencyCallData.eCall.Control>
Figure 9: INFO requesting MSD
Figure 10 illustrates a SIP eCall INFO that contains an MSD. For
simplicity, the example does not show all SIP headers. Because the
MSD is encoded in ASN.1 PER, which is a binary encoding, its contents
cannot be included in a text document.
INFO urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:4567890123@atlanta.example.com;
purpose=emergencyCallData.eCall.MSD;
Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml
CSeq: 51862 INFO
Recv-Info: emergencyCallData.eCall
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE
Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: 4567890123@atlanta.example.com
Content-Disposition: info-package
Content-Transfer-Encoding: binary
...MSD in ASN.1 PER encoding goes here...
Figure 10: INFO containing MSD
12. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] apply here.
In addition to any network-provided location (which might be In addition to any network-provided location (which might be
determined solely by the network, or in cooperation with or possibly determined solely by the network, or in cooperation with or possibly
entirely by the originating device), an eCall carries an IVS-supplied entirely by the originating device), an eCall carries an IVS-supplied
location within the MSD. This is likely to be useful to the PSAP, location within the MSD. This is likely to be useful to the PSAP,
especially when no network-provided location is included, or when the especially when no network-provided location is included, or when the
two locations are independently determined. Even in situations where two locations are independently determined. Even in situations where
the network-supplied location is limited to the cell site, this can the network-supplied location is limited to the cell site, this can
be useful as a sanity check on the device-supplied location contained be useful as a sanity check on the device-supplied location contained
in the MSD. in the MSD.
The document [RFC7378] discusses trust issues regarding location The document [RFC7378] discusses trust issues regarding location
provided by or determined in cooperation with end devices. provided by or determined in cooperation with end devices.
Security considerations specific to the mechanism by which the PSAP Security considerations specific to the mechanism by which the PSAP
sends acknowledgments and requests to the vehicle are discussed in sends acknowledgments and requests to the vehicle are discussed in
the "Security Considerations" block of Section 14.3. the "Security Considerations" block of Section 15.3.
Data received from external sources inherently carries implementation Data received from external sources inherently carries implementation
risks. For example, depending on the platform, buffer overflows can risks. For example, depending on the platform, buffer overflows can
introduce remote code execution vulnerabilities, null characters can introduce remote code execution vulnerabilities, null characters can
corrupt strings, numeric values used for internal calculations can corrupt strings, numeric values used for internal calculations can
result in underflow/overflow errors, malformed XML objects can expose result in underflow/overflow errors, malformed XML objects can expose
parsing bugs, etc. Implementations need to be cognizant of the parsing bugs, etc. Implementations need to be cognizant of the
potential risks, observe best practices (which might include potential risks, observe best practices (which might include
sufficiently capable static code analysis, fuzz testing, component sufficiently capable static code analysis, fuzz testing, component
isolation, avoiding use of unsafe coding techniques, third-party isolation, avoiding use of unsafe coding techniques, third-party
attack tests, signed software, over-the-air updates, etc.), and have attack tests, signed software, over-the-air updates, etc.), and have
multiple levels of protection. Implementors need to be aware that, multiple levels of protection. Implementors need to be aware that,
potentially, the data objects described here and elsewhere might be potentially, the data objects described here and elsewhere might be
malformed, might contain unexpected characters, excessively long malformed, might contain unexpected characters, excessively long
attribute values, elements, etc. attribute values, elements, etc.
Since this document depends on [I-D.ietf-ecrit-additional-data], the The security considerations discussed in
security considerations discussed there apply here (see especially [I-D.ietf-ecrit-additional-data] apply here (see especially the
the discussion of TLS, TLS versions, cypher suites, and PKI). discussion of TLS, TLS versions, cypher suites, and PKI).
When vehicle data or control/metadata is contained in a signed or When vehicle data or control/metadata is contained in a signed or
encrypted body part, the enclosing multipart (e.g., multipart/signed encrypted body part, the enclosing multipart (e.g., multipart/signed
or multipart/encrypted) has the same Content-ID as the enclosed data or multipart/encrypted) has the same Content-ID as the enclosed data
part. This allows an entity to identify and access the data blocks part. This allows an entity to identify and access the data blocks
it is interested in without having to dive deeply into the message it is interested in without having to dive deeply into the message
structure or decrypt parts it is not interested in. (The 'purpose' structure or decrypt parts it is not interested in. (The 'purpose'
parameter in a Call-Info header field identifies the data and parameter in a Call-Info header field identifies the data and
contains a CID URL pointing to the data block in the body, which has contains a CID URL pointing to the data block in the body, which has
a matching Content-ID body part header field). a matching Content-ID body part header field).
12. Privacy Considerations 13. Privacy Considerations
Since this document builds on [I-D.ietf-ecrit-additional-data], the The privacy considerations discussed in
data structures specified there, and the corresponding privacy [I-D.ietf-ecrit-additional-data] apply here. The MSD carries some
considerations discussed there, apply here as well. The MSD carries identifying and personal information (mostly about the vehicle and
some additional identifying and personal information (mostly about less about the owner), as well as location information, and so needs
the vehicle and less about the owner), as well as location to be protected against unauthorized disclosure. Local regulations
information, and so needs to be protected against unauthorized may impose additional privacy protection requirements.
disclosure. Local regulations may impose additional privacy
protection requirements.
Privacy considerations specific to the data structure containing Privacy considerations specific to the data structure containing
vehicle information are discussed in the "Security Considerations" vehicle information are discussed in the "Security Considerations"
block of Section 14.2. block of Section 15.2.
Privacy considerations specific to the mechanism by which the PSAP Privacy considerations specific to the mechanism by which the PSAP
sends acknowledgments and requests to the vehicle are discussed in sends acknowledgments and requests to the vehicle are discussed in
the "Security Considerations" block of Section 14.3. the "Security Considerations" block of Section 15.3.
13. XML Schema 14. XML Schema
This section defines an XML schema for the eCall control block. The This section defines an XML schema for the eCall control block. The
text description of the eCall control block in Section 8.1 is text description of the eCall control block in Section 9.1 is
normative and supersedes any conflicting aspect of this schema. normative and supersedes any conflicting aspect of this schema.
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" elementFormDefault="qualified"
skipping to change at page 22, line 19 skipping to change at page 25, line 41
<xs:attribute type="cx:iana-token" minOccurs="0" <xs:attribute type="cx:iana-token" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:anyAttribute/> <xs:anyAttribute/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 8: eCall Control Block Schema Figure 11: eCall Control Block Schema
14. IANA Considerations 15. IANA Considerations
14.1. Service URN Registrations 15.1. Service URN Registrations
IANA is requested to register the URN 'urn:service:sos.ecall' under IANA is requested to register the URN 'urn:service:sos.ecall' under
the sub-services 'sos' registry defined in Section 4.2 of [RFC5031]. the sub-services 'sos' registry defined in Section 4.2 of [RFC5031].
This service requests resources associated with an emergency call This service requests resources associated with an emergency call
placed by an in-vehicle system, carrying a standardized set of data placed by an in-vehicle system, carrying a standardized set of data
related to the vehicle and incident. Two sub-services are registered related to the vehicle and incident. Two sub-services are registered
as well: as well:
urn:service:sos.ecall.manual urn:service:sos.ecall.manual
skipping to change at page 23, line 5 skipping to change at page 26, line 24
urn:service:sos.ecall.automatic urn:service:sos.ecall.automatic
Used with an eCall invoked automatically, for example, due to a Used with an eCall invoked automatically, for example, due to a
crash or other serious incident. crash or other serious incident.
IANA is also requested to register the URN IANA is also requested to register the URN
'urn:service:test.sos.ecall' under the sub-service 'test' registry 'urn:service:test.sos.ecall' under the sub-service 'test' registry
defined in Setcion 17.2 of [RFC6881]. defined in Setcion 17.2 of [RFC6881].
14.2. MIME Content-type Registration for 'application/ 15.2. MIME Content-type Registration for 'application/
emergencyCallData.eCall.MSD+per' emergencyCallData.eCall.MSD+per'
IANA is requested to add application/emergencyCallData.eCall.MSD+per IANA is requested to add application/emergencyCallData.eCall.MSD+per
as a MIME content type, with a reference to this document, in as a MIME content type, with a reference to this document, in
accordance to the procedures of RFC 6838 [RFC6838] and guidelines in accordance to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.MSD+per MIME subtype name: emergencyCallData.eCall.MSD+per
skipping to change at page 24, line 4 skipping to change at page 27, line 23
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: None File Extension: None
Macintosh file type code: 'BINA' Macintosh file type code: 'BINA'
Person and email address for further information: Randall Gellens, Person and email address for further information: Randall Gellens,
rg+ietf@randy.pensive.org rg+ietf@randy.pensive.org
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: The MSD specification was produced by the European Author: The MSD specification was produced by the European
Committee For Standardization (CEN). For contact information, Committee For Standardization (CEN). For contact information,
please see <http://www.cen.eu/cen/Pages/contactus.aspx>. please see <http://www.cen.eu/cen/Pages/contactus.aspx>.
Change controller: The European Committee For Standardization Change controller: The European Committee For Standardization
(CEN) (CEN)
14.3. MIME Content-type Registration for 'application/ 15.3. MIME Content-type Registration for 'application/
emergencyCallData.eCall.control+xml' emergencyCallData.eCall.control+xml'
IANA is requested to add application/ IANA is requested to add application/
emergencyCallData.eCall.control+xml as a MIME content type, with a emergencyCallData.eCall.control+xml as a MIME content type, with a
reference to this document, in accordance to the procedures of RFC reference to this document, in accordance to the procedures of RFC
6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.control+xml MIME subtype name: emergencyCallData.eCall.control+xml
skipping to change at page 24, line 31 skipping to change at page 28, line 4
reference to this document, in accordance to the procedures of RFC reference to this document, in accordance to the procedures of RFC
6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.control+xml MIME subtype name: emergencyCallData.eCall.control+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of the XML content. Indicates the character encoding of the XML content.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 7303 [RFC7303]. Section 3.2 of RFC 7303 [RFC7303].
Security considerations: Security considerations:
This content type carries metadata and control information and This content type carries metadata and control information and
requests, such as from a Public Safety Answering Point (PSAP) requests, such as from a Public Safety Answering Point (PSAP)
to an In-Vehicle System (IVS) during an emergency call. to an In-Vehicle System (IVS) during an emergency call.
Metadata (such as an acknowledgment that data sent by the IVS Metadata (such as an acknowledgment that data sent by the IVS
to the PSAP was successfully received) has limited privacy and to the PSAP was successfully received) has limited privacy and
security implications. Control information (such as requests security implications. Control information (such as requests
from the PSAP that the vehicle perform an action) has some from the PSAP that the vehicle perform an action) has some
privacy and security implications. The privacy concern arises privacy and security implications. The privacy concern arises
from the ability to request the vehicle to transmit a data set, from the ability to request the vehicle to transmit a data set,
which as described in Section 14.2, can contain personal which as described in Section 15.2, can contain personal
information. The security concern is the ability to request information. The security concern is the ability to request
the vehicle to perform an action. Control information needs to the vehicle to perform an action. Control information needs to
originate only from a PSAP or other emergency services originate only from a PSAP or other emergency services
provider, and not be modified en-route. The level of integrity provider, and not be modified en-route. The level of integrity
of the cellular network over which the emergency call is placed of the cellular network over which the emergency call is placed
is a consideration: when the IVS initiates an eCall over a is a consideration: when the IVS initiates an eCall over a
cellular network, in most cases it relies on the MNO to route cellular network, in most cases it relies on the MNO to route
the call to a PSAP. (Calls placed using other means, such as the call to a PSAP. (Calls placed using other means, such as
Wi-Fi or over-the-top services, generally incur somewhat higher Wi-Fi or over-the-top services, generally incur somewhat higher
levels of risk than calls placed "natively" using cellular levels of risk than calls placed "natively" using cellular
networks.) A call-back from a PSAP merits additional networks.) A call-back from a PSAP merits additional
consideration, since current mechanisms are not ideal for consideration, since current mechanisms are not ideal for
verifying that such a call is indeed a call-back from a PSAP in verifying that such a call is indeed a call-back from a PSAP in
response to an emergency call placed by the IVS. See the response to an emergency call placed by the IVS. See the
discussion in Section 11 and the PSAP Callback document discussion in Section 12 and the PSAP Callback document
[RFC7090]. One potential safeguard, applicable regardless of [RFC7090].
which end initiated the call and the means of the call, is for
the PSAP or emergency service provider to sign the body part
using a certificate issued by a known emergency services
certificate authority and for which the IVS can verify the root
certificate; however, this depends on deployed key
infrastructure including a recognized certificate authority,
certificate revocation mechanisms, etc.
Sections 7 and Section 8 of [I-D.ietf-ecrit-additional-data] Sections 7 and Section 8 of [I-D.ietf-ecrit-additional-data]
contain more discussion. contain more discussion.
Interoperability considerations: None Interoperability considerations: None
Published specification: This document Published specification: This document
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
skipping to change at page 25, line 38 skipping to change at page 29, line 4
contain more discussion. contain more discussion.
Interoperability considerations: None Interoperability considerations: None
Published specification: This document Published specification: This document
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Randall Gellens, Person and email address for further information: Randall Gellens,
rg+ietf@randy.pensive.org rg+ietf@randy.pensive.org
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: The IETF ECRIT WG. Author: The IETF ECRIT WG.
Change controller: The IETF ECRIT WG. Change controller: The IETF ECRIT WG.
14.4. Registration of the 'eCall.MSD' entry in the Emergency Call 15.4. Registration of the 'eCall.MSD' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.MSD' entry to the This specification requests IANA to add the 'eCall.MSD' entry to the
Emergency Call Additional Data Blocks registry (established by Emergency Call Additional Data Blocks registry, with a reference to
[I-D.ietf-ecrit-additional-data]), with a reference to this document. this document.
14.5. Registration of the 'eCall.control' entry in the Emergency Call 15.5. Registration of the 'eCall.control' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.control' entry to This specification requests IANA to add the 'eCall.control' entry to
the Emergency Call Additional Data Blocks registry (established by the Emergency Call Additional Data Blocks registry, with a reference
[I-D.ietf-ecrit-additional-data]), with a reference to this document. to this document.
14.6. Registration of the emergencyCallData.eCall Info Package 15.6. Registration of the emergencyCallData.eCall Info Package
IANA is requested to add emergencyCallData.eCall to the Info Packages IANA is requested to add emergencyCallData.eCall to the Info Packages
Registry under "Session Initiation Protocol (SIP) Parameters", with a Registry under "Session Initiation Protocol (SIP) Parameters", with a
reference to this document. reference to this document.
14.7. URN Sub-Namespace Registration 15.7. URN Sub-Namespace Registration
14.7.1. Registration for urn:ietf:params:xml:ns:eCall 15.7.1. Registration for urn:ietf:params:xml:ns:eCall
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall URI: urn:ietf:params:xml:ns:eCall
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 27, line 22 skipping to change at page 30, line 22
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for eCall Data</title> <title>Namespace for eCall Data</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.7.2. Registration for urn:ietf:params:xml:ns:eCall:control 15.7.2. Registration for urn:ietf:params:xml:ns:eCall:control
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall:control URI: urn:ietf:params:xml:ns:eCall:control
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 28, line 24 skipping to change at page 31, line 24
Control Block</title> Control Block</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<h2>Control Block</h2> <h2>Control Block</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.8. Registry creation 15.8. Registry creation
This document creates a new registry called 'eCall Control Data'. This document creates a new registry called 'eCall Control Data'.
The following sub-registries are created for this registry. The following sub-registries are created for this registry.
14.8.1. eCall Control Action Registry 15.8.1. eCall Control Action Registry
This document creates a new sub-registry called "eCall Control Action This document creates a new sub-registry called "eCall Control Action
Registry". As defined in [RFC5226], this registry operates under Registry". As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the proposed "Expert Review" rules. The expert should determine that the proposed
action is within the purview of a vehicle, is sufficiently action is within the purview of a vehicle, is sufficiently
distinguishable from other actions, and the action is clearly and distinguishable from other actions, and the action is clearly and
fully described. In most cases, a published and stable document is fully described. In most cases, a published and stable document is
referenced for the description of the action. referenced for the description of the action.
The content of this registry includes: The content of this registry includes:
skipping to change at page 29, line 5 skipping to change at page 32, line 5
eCall control <request> element. eCall control <request> element.
Description: A description of the action. In most cases this will Description: A description of the action. In most cases this will
be a reference to a published and stable document. The be a reference to a published and stable document. The
description MUST specify if any attributes or child elements are description MUST specify if any attributes or child elements are
optional or mandatory, and describe the action to be taken by the optional or mandatory, and describe the action to be taken by the
vehicle. vehicle.
The initial set of values is listed in Table 2. The initial set of values is listed in Table 2.
+-----------+------------------------------------------+ +-----------+--------------------------------------+
| Name | Description | | Name | Description |
+-----------+------------------------------------------+ +-----------+--------------------------------------+
| send-data | Section Section 8.1.2.1 of this document | | send-data | See Section 9.1.2.1 of this document |
+-----------+------------------------------------------+ +-----------+--------------------------------------+
Table 2: eCall Control Action Registry Initial Values Table 2: eCall Control Action Registry Initial Values
14.8.2. eCall Control Extension Registry 15.8.2. eCall Control Extension Registry
This document creates a new sub-registry called "eCall Control This document creates a new sub-registry called "eCall Control
Extension Registry". This registry contains elements, attributes, Extension Registry". This registry contains elements, attributes,
and values for the eCall metadata/control object. As defined in and values for the eCall metadata/control object. As defined in
[RFC5226], this registry operates under "Expert Review" rules. The [RFC5226], this registry operates under "Expert Review" rules. The
expert should determine that the proposed elements, attributes, and/ expert should determine that the proposed elements, attributes, and/
or values are within the purview of a vehicle, are sufficiently or values are within the purview of a vehicle, are sufficiently
distinguishable, and clearly and fully described. In most cases, a distinguishable, and clearly and fully described. In most cases, a
published and stable document is referenced for the description of published and stable document is referenced for the description of
each element, attribute, or value. New values MUST indicate for each element, attribute, or value. New values MUST indicate for
skipping to change at page 29, line 46 skipping to change at page 32, line 46
Type: 'Element', 'Attribute', or 'Value'. Type: 'Element', 'Attribute', or 'Value'.
Name: The name of the new element or attribute. Not used for new Name: The name of the new element or attribute. Not used for new
values. values.
Description: A description of the element, attribute, or value. In Description: A description of the element, attribute, or value. In
most cases this will be a reference to a published and stable most cases this will be a reference to a published and stable
document. document.
15. Contributors 16. Contributors
Brian Rosen was a co-author of the original document upon which this Brian Rosen was a co-author of the original document upon which this
document is based. document is based.
16. Acknowledgements 17. Acknowledgements
We would like to thank Bob Williams and Ban Al-Bakri for their We would like to thank Bob Williams and Ban Al-Bakri for their
feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith
Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and
James Winterbottom for their review and comments; Robert Sparks and James Winterbottom for their review and comments; Robert Sparks and
Paul Kyzivat for their help with the SIP mechanisms. We would like Paul Kyzivat for their help with the SIP mechanisms. We would like
to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and
Ulrich Dietz for their help with the original document upon which Ulrich Dietz for their help with the original document upon which
this document is based. this document is based.
17. Changes from Previous Versions 18. Changes from Previous Versions
17.1. Changes from draft-ietf-07 to draft-ietf-08 18.1. Changes from draft-ietf-08 to draft-ietf-09
o Created a new "Data Transport" section that describes how the MSD
and metadata/control blocks are attached, and then referred to
that section rather than repeat the information about the CID and
Call-Info and so forth, which means most references to the
additional-data draft have now been deleted
o Mentioned edge cases where a PSAP response to INVITE isn't
received by the IVS
o Reworded description of which status codes are used when a PSAP
wishes to reject a call but inform the vehicle occupants that it
is aware of the situation to be more definite
o Added examples showing INFO
o Added references for eCall test call requirement
o Described meaning of eCall URNs in Section 8 as well as in IANA
registration
18.2. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, call-backs, and control usage, such as use in rejected calls, and solicited MSDs
solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section Section 6.1 to be a subsection of Section 6 o Moved new Section Section 7.1 to be a subsection of Section 7
o Moved new Section Section 9 to be a main section instead of a o Moved new Section Section 10 to be a main section instead of a
subsection of Section 8 subsection of Section 9
o Revised SIP INFO usage and package registration per advice from o Revised SIP INFO usage and package registration per advice from
Robert Sparks and Paul Kyzivat Robert Sparks and Paul Kyzivat
17.2. Changes from draft-ietf-06 to draft-ietf-07 18.3. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
17.3. Changes from draft-ietf-05 to draft-ietf-06 18.4. Changes from draft-ietf-05 to draft-ietf-06
o Added additional security and privacy clarifications regarding o Added additional security and privacy clarifications regarding
signed and encrypted data signed and encrypted data
o Additional security and privacy text o Additional security and privacy text
o Deleted informative section on ESINets as unnecessary. o Deleted informative section on ESINets as unnecessary.
17.4. Changes from draft-ietf-04 to draft-ietf-05 18.5. Changes from draft-ietf-04 to draft-ietf-05
o Reworked the security and privacy considerations material in the o Reworked the security and privacy considerations material in the
document as a whole and in the MIME registation sections of the document as a whole and in the MIME registation sections of the
MSD and control objects MSD and control objects
o Clarified that the <actionResult> element can appear multiple o Clarified that the <actionResult> element can appear multiple
times within an <ack> element times within an <ack> element
o Fixed IMS definition o Fixed IMS definition
o Added clarifying text for the 'msgid' attribute o Added clarifying text for the 'msgid' attribute
17.5. Changes from draft-ietf-03 to draft-ietf-04 18.6. Changes from draft-ietf-03 to draft-ietf-04
o Added Privacy Considerations section o Added Privacy Considerations section
o Reworded most uses of non-normative "may", "should", "must", and o Reworded most uses of non-normative "may", "should", "must", and
"recommended." "recommended."
o Fixed nits in examples o Fixed nits in examples
17.6. Changes from draft-ietf-02 to draft-ietf-03 18.7. Changes from draft-ietf-02 to draft-ietf-03
o Added request to enable cameras o Added request to enable cameras
o Improved examples and XML schema o Improved examples and XML schema
o Clarifications and wording improvements o Clarifications and wording improvements
17.7. Changes from draft-ietf-01 to draft-ietf-02 18.8. Changes from draft-ietf-01 to draft-ietf-02
o Added clarifying text reinforcing that the data exchange is for o Added clarifying text reinforcing that the data exchange is for
small blocks of data infrequently transmitted small blocks of data infrequently transmitted
o Clarified that dynamic media is conveyed using SIP re-INVITE to o Clarified that dynamic media is conveyed using SIP re-INVITE to
establish a one-way media stream establish a one-way media stream
o Clarified that the scope is the needs of eCall within the SIP o Clarified that the scope is the needs of eCall within the SIP
emergency call environment emergency call environment
o Added informative statement that the document may be suitable for o Added informative statement that the document may be suitable for
reuse by other ACN systems reuse by other ACN systems
o Clarified that normative language for the control block applies to o Clarified that normative language for the control block applies to
both IVS and PSAP both IVS and PSAP
o Removed 'ref', 'supported-mime', and <media> elements o Removed 'ref', 'supported-mime', and <media> elements
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
17.8. Changes from draft-ietf-00 to draft-ietf-01 18.9. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the eCall o Added IANA registration for the MIME content type for the eCall
control object control object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
eCall control object eCall control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
17.9. Changes from draft-gellens-03 to draft-ietf-00 18.10. Changes from draft-gellens-03 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf-. o Renamed from draft-gellens- to draft-ietf-.
o Added mention of and reference to ETSI TR "Mobile Standards Group o Added mention of and reference to ETSI TR "Mobile Standards Group
(MSG); eCall for VoIP" (MSG); eCall for VoIP"
o Added text to Introduction regarding migration/co-existence being o Added text to Introduction regarding migration/co-existence being
out of scope out of scope
o Added mention in Security Considerations that even if the network- o Added mention in Security Considerations that even if the network-
supplied location is just the cell site, this can be useful as a supplied location is just the cell site, this can be useful as a
sanity check on the IVS-supplied location sanity check on the IVS-supplied location
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
17.10. Changes from draft-gellens-02 to -03 18.11. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
17.11. Changes from draft-gellens-01 to -02 18.12. Changes from draft-gellens-01 to -02
o Minor wording improvements o Minor wording improvements
o Removed ".automatic" and ".manual" from o Removed ".automatic" and ".manual" from
"urn:service:test.sos.ecall" registration and discussion text. "urn:service:test.sos.ecall" registration and discussion text.
17.12. Changes from draft-gellens-00 to -01 18.13. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to MIME subtypes, in accordance with changes to
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
18. References 19. References
18.1. Normative References 19.1. Normative References
[EN_16062]
CEN, , "Intelligent transport systems - eSafety - eCall
High Level Application Requirements (HLAP) Using GSM/UMTS
Circuit Switched Networks, EN 16062", April 2015.
[EN_16072] [EN_16072]
CEN, , "Intelligent transport systems - eSafety - Pan- CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April European eCall operating requirements, EN 16072", April
2015. 2015.
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", draft-ietf-ecrit-additional-data-38 (work in Call", draft-ietf-ecrit-additional-data-38 (work in
skipping to change at page 34, line 5 skipping to change at page 37, line 24
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
DOI 10.17487/RFC7303, July 2014, DOI 10.17487/RFC7303, July 2014,
<http://www.rfc-editor.org/info/rfc7303>. <http://www.rfc-editor.org/info/rfc7303>.
[TS22.101] [TS22.101]
3GPP, , "3GPP TS 22.101: Technical Specification Group 3GPP, , "3GPP TS 22.101: Technical Specification Group
Services and System Aspects; Service aspects; Service Services and System Aspects; Service aspects; Service
principles". principles".
18.2. Informative references 19.2. Informative references
[CEN] "European Committee for Standardization", [CEN] "European Committee for Standardization",
<http://www.cen.eu>. <http://www.cen.eu>.
[I-D.ietf-ecrit-car-crash] [I-D.ietf-ecrit-car-crash]
Gellens, R., Rosen, B., and H. Tschofenig, "Next- Gellens, R., Rosen, B., and H. Tschofenig, "Next-
Generation Vehicle-Initiated Emergency Calls", draft-ietf- Generation Vehicle-Initiated Emergency Calls", draft-ietf-
ecrit-car-crash-07 (work in progress), February 2016. ecrit-car-crash-08 (work in progress), July 2016.
[MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for [MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for
VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04), VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04),
April 2014. April 2014.
[RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, DOI 10.17487/RFC5012, January 2008, RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>. <http://www.rfc-editor.org/info/rfc5012>.
skipping to change at page 35, line 8 skipping to change at page 38, line 25
"3d Generation Partnership Project", "3d Generation Partnership Project",
<http://www.3gpp.org/>. <http://www.3gpp.org/>.
[SDO-ETSI] [SDO-ETSI]
"European Telecommunications Standards Institute (ETSI)", "European Telecommunications Standards Institute (ETSI)",
<http://www.etsi.org>. <http://www.etsi.org>.
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Consultant Core Technology Consulting
6755 Mira Mesa Blvd 123-151
San Diego 92121
US
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Hannes Tschofenig Hannes Tschofenig
Individual Individual
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
 End of changes. 117 change blocks. 
301 lines changed or deleted 444 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/