< draft-ietf-ecrit-ecall-25.txt   draft-ietf-ecrit-ecall-26.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: August 10, 2017 Individual Expires: August 14, 2017 Individual
February 6, 2017 February 10, 2017
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-25.txt draft-ietf-ecrit-ecall-26.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 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 10, 2017. This Internet-Draft will expire on August 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 49 skipping to change at page 2, line 49
9.1.3. The <request> element . . . . . . . . . . . . . . . . 16 9.1.3. The <request> element . . . . . . . . . . . . . . . . 16
9.1.3.1. Attributes of the <request> element . . . . . . . 17 9.1.3.1. Attributes of the <request> element . . . . . . . 17
9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 24 11. Security Considerations . . . . . . . . . . . . . . . . . . . 24
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 25 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 25
13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26 13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 28 14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 28
14.2. Service URN Registrations . . . . . . . . . . . . . . . 29 14.2. Service URN Registrations . . . . . . . . . . . . . . . 29
14.3. MIME Structured Syntax Suffix Registration for +PER . . 29 14.3. MIME Media Type Registration for
'application/emergencyCallData.eCall.MSD' . . . . . . . 29
14.4. MIME Media Type Registration for 14.4. MIME Media Type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 'application/emergencyCallData.control+xml' . . . . . . 31
14.5. MIME Media Type Registration for
'application/emergencyCallData.control+xml' . . . . . . 32 14.5. Registration of the 'eCall.MSD' entry in the Emergency
14.6. Registration of the 'eCall.MSD' entry in the Emergency Call Additional Data Types registry . . . . . . . . . . 32
Call Additional Data Types registry . . . . . . . . . . 33 14.6. Registration of the 'control' entry in the Emergency
14.7. Registration of the 'control' entry in the Emergency Call Additional Data Types registry . . . . . . . . . . 32
Call Additional Data Types registry . . . . . . . . . . 34 14.7. Registration for
14.8. URN Sub-Namespace Registration . . . . . . . . . . . . . 34 urn:ietf:params:xml:ns:EmergencyCallData:control . . . . 33
14.8.1. Registration for 14.8. Registry Creation . . . . . . . . . . . . . . . . . . . 33
urn:ietf:params:xml:ns:EmergencyCallData:control . . 34 14.8.1. Emergency Call Action Registry . . . . . . . . . . . 33
14.9. Registry Creation . . . . . . . . . . . . . . . . . . . 34 14.8.2. Emergency Call Action Failure Reason Registry . . . 34
14.9.1. Emergency Call Action Registry . . . . . . . . . . . 35 14.9. The emergencyCallData.eCall.MSD INFO package . . . . . . 35
14.9.2. Emergency Call Action Failure Reason Registry . . . 35 14.9.1. Overall Description . . . . . . . . . . . . . . . . 35
14.10. The emergencyCallData.eCall.MSD INFO package . . . . . . 36 14.9.2. Applicability . . . . . . . . . . . . . . . . . . . 36
14.10.1. Overall Description . . . . . . . . . . . . . . . . 37 14.9.3. Info Package Name . . . . . . . . . . . . . . . . . 36
14.10.2. Applicability . . . . . . . . . . . . . . . . . . . 37 14.9.4. Info Package Parameters . . . . . . . . . . . . . . 36
14.10.3. Info Package Name . . . . . . . . . . . . . . . . . 38 14.9.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 37
14.10.4. Info Package Parameters . . . . . . . . . . . . . . 38 14.9.6. INFO Request Body Parts . . . . . . . . . . . . . . 37
14.10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 38 14.9.7. Info Package Usage Restrictions . . . . . . . . . . 37
14.10.6. INFO Request Body Parts . . . . . . . . . . . . . . 38 14.9.8. Rate of INFO Requests . . . . . . . . . . . . . . . 37
14.10.7. Info Package Usage Restrictions . . . . . . . . . . 38 14.9.9. Info Package Security Considerations . . . . . . . . 38
14.10.8. Rate of INFO Requests . . . . . . . . . . . . . . . 38 14.9.10. Implementation Details . . . . . . . . . . . . . . . 38
14.10.9. Info Package Security Considerations . . . . . . . 39 14.9.11. Examples . . . . . . . . . . . . . . . . . . . . . . 38
14.10.10. Implementation Details . . . . . . . . . . . . . . 39 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38
14.10.11. Examples . . . . . . . . . . . . . . . . . . . . . 39 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38
15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39 17. Changes from Previous Versions . . . . . . . . . . . . . . . 38
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 17.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 38
17. Changes from Previous Versions . . . . . . . . . . . . . . . 39 17.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 39
17.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 40 17.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 39
17.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 40 17.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 39
17.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 40 17.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 39
17.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 40 17.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 39
17.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 40 17.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 39
17.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 40 17.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 39
17.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 40 17.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 40
17.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 40 17.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 40
17.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 41 17.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 40
17.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 41 17.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 40
17.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 41 17.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 41
17.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41 17.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 41
17.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42 17.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 41
17.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42 17.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 41
17.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42 17.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41
17.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42 17.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42
17.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 43 17.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42
17.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 43 17.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 42
17.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 43 17.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42
17.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 43 17.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43
17.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 44 17.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 43
17.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 44 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
17.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 44 18.1. Normative References . . . . . . . . . . . . . . . . . . 43
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 18.2. Informative references . . . . . . . . . . . . . . . . . 44
18.1. Normative References . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
18.2. Informative references . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47
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 7, line 6 skipping to change at page 6, line 50
This document indicates how to use IP-based emergency services This document indicates how to use IP-based emergency services
mechanisms to support next-generation eCall. mechanisms to support next-generation eCall.
This document also registers MIME media types and an Emergency Call This document also registers MIME media types and an Emergency Call
Additional Data Block for the eCall vehicle data (MSD) and metadata/ Additional Data Block for the eCall vehicle data (MSD) and metadata/
control data, and an INFO package to enable carrying this data in SIP control data, and an INFO package to enable carrying this data in SIP
INFO requests. INFO requests.
The MSD is carried in the MIME type 'application/ The MSD is carried in the MIME type 'application/
emergencyCallData.eCall.MSD+per' and the metadata/control block is emergencyCallData.eCall.MSD' and the metadata/control block is
carried in the MIME type 'application/emergencyCallData.control+xml' carried in the MIME type 'application/emergencyCallData.control+xml'
(both of which are registered in Section 14). An INFO package is (both of which are registered in Section 14). An INFO package is
defined (in Section 14.10) to enable these MIME types to be carried defined (in Section 14.9) to enable these MIME types to be carried in
in SIP INFO requests, per [RFC6086]. SIP INFO requests, per [RFC6086].
4. eCall Requirements 4. eCall Requirements
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 and [TS24.229] section 4.7.6. [TS22.101] clauses 10.7 and A.27 and [TS24.229] section 4.7.6.
Requirements specific to vehicle data are contained in EN 15722 Requirements specific to vehicle data are contained in EN 15722
[msd]. [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 (including VIN, vehicle type, propulsion type, vehicle related data (including VIN, vehicle type, propulsion type,
current and optionally previous location coordinates, and number of current and optionally previous location coordinates, and number of
occupants), known as the Minimum Set of Data (MSD). The European occupants), known as the Minimum Set of Data (MSD). The European
Committee for Standardization (CEN) has specified this data in EN Committee for Standardization (CEN) has specified this data in EN
15722 [msd], along with both ASN.1 and XML encodings. Both circuit- 15722 [msd], along with both ASN.1 and XML encodings. Both circuit-
switched eCall and this document use the ASN.1 PER encoding, which is switched eCall and this document use the ASN.1 PER encoding, which is
specified in Annex A of EN 15722 [msd] (the XML encoding specified in specified in Annex A of EN 15722 [msd] (the XML encoding specified in
Annex C is not used in this document, per 3GPP [SDO-3GPP]). Annex C is not used in this document, per 3GPP [SDO-3GPP]).
This document registers the 'application/ This document registers the 'application/emergencyCallData.eCall.MSD'
emergencyCallData.eCall.MSD+per' MIME media type to enable the MSD to MIME media type to enable the MSD to be carried in SIP. As an ASN.1
be carried in SIP. As an ASN.1 PER encoded object, the data is PER encoded object, the data is binary and transported using binary
binary and transported using binary content transfer encoding within content transfer encoding within SIP messages. This document also
SIP messages. This document also adds the 'eCall.MSD' entry to the adds the 'eCall.MSD' entry to the Emergency Call Additional Data
Emergency Call Additional Data Types registry to enable the MSD to be Types registry to enable the MSD to be recognized as such in a SIP-
recognized as such in a SIP-based eCall emergency call. (See based eCall emergency call. (See [RFC7852] for more information
[RFC7852] for more information about the registry and how it is about the registry and how it is used.)
used.)
See Section 6 for a discussion of how the MSD vehicle data is See Section 6 for a discussion of how the MSD vehicle data is
conveyed in an NG-eCall. conveyed in an NG-eCall.
6. Data Transport 6. Data Transport
[RFC7852] establishes a general mechanism for conveying blocks of [RFC7852] establishes a general mechanism for conveying blocks of
data within a SIP emergency call. This document makes use of that data within a SIP emergency call. This document makes use of that
mechanism to include vehicle data (the MSD, see Section 5) and/or mechanism to include vehicle data (the MSD, see Section 5) and/or
metadata/control information (see Section 9) within SIP messages. metadata/control information (see Section 9) within SIP messages.
This document also registers an INFO package (in Section 14.10) to This document also registers an INFO package (in Section 14.9) to
enable eCall related data blocks to be carried in SIP INFO requests enable eCall related data blocks to be carried in SIP INFO requests
(per [RFC6086], new INFO usages require the definition of an INFO (per [RFC6086], new INFO usages require the definition of an INFO
package). package).
Note that if other data sets need to be transmitted in the future, Note that if other data sets need to be transmitted in the future,
the appropriate signalling mechanism for such data needs to be the appropriate signalling mechanism for such data needs to be
evaluated, including factors such as the size and frequency of such evaluated, including factors such as the size and frequency of such
data. data.
An In-Vehicle System (IVS) transmits an MSD (see Section 5) by An In-Vehicle System (IVS) transmits an MSD (see Section 5) by
encoding it per Annex A of EN 15722 [msd], and including it as a MIME encoding it per Annex A of EN 15722 [msd], and including it as a MIME
body part within a SIP message per [RFC7852]. The body part is body part within a SIP message per [RFC7852]. The body part is
identified by its MIME media type ('application/ identified by its MIME media type ('application/
emergencyCallData.eCall.MSD+per') in the Content-Type header field of emergencyCallData.eCall.MSD') in the Content-Type header field of the
the body part. The body part is assigned a unique identifier which body part. The body part is assigned a unique identifier which is
is listed in a Content-ID header field in the body part. The SIP 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 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 at the top level of the SIP message. This
Call-Info header field contains a CID URL referencing the body part's Call-Info header field contains a CID URL referencing the body part's
unique identifier, and a 'purpose' parameter identifying the data as unique identifier, and a 'purpose' parameter identifying the data as
the eCall MSD per the Emergency Call Additional Data Types registry the eCall MSD per the Emergency Call Additional Data Types registry
entry; the 'purpose' parameter's value is entry; the 'purpose' parameter's value is
'emergencyCallData.eCall.MSD'. Per [RFC6086], an MSD is carried in a 'emergencyCallData.eCall.MSD'. Per [RFC6086], an MSD is carried in a
SIP INFO request by using the INFO package defined in Section 14.10. SIP INFO request by using the INFO package defined in Section 14.9.
A PSAP or IVS transmits a metadata/control object (see Section 9) by A PSAP or IVS transmits a metadata/control object (see Section 9) by
encoding it per the description in this document, and including it encoding it per the description in this document, and including it
within a SIP message as a MIME body part per [RFC7852]. The body within a SIP message as a MIME body part per [RFC7852]. The body
part is identified by its MIME media type ('application/ part is identified by its MIME media type ('application/
emergencyCallData.control+xml') in the Content-Type header field of emergencyCallData.control+xml') in the Content-Type header field of
the body part. The body part is assigned a unique identifier which 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 is listed in a Content-ID header field in the body part. The SIP
message is marked as containing the metadata/control object by adding message is marked as containing the metadata/control object by adding
(or appending to) a Call-Info header field at the top level of the (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 SIP message. This Call-Info header field contains a CID URL
referencing the body part's unique identifier, and a 'purpose' referencing the body part's unique identifier, and a 'purpose'
parameter identifying the data as an eCall metadata/control block per parameter identifying the data as an eCall metadata/control block per
the Emergency Call Additional Data Types registry entry; the the Emergency Call Additional Data Types registry entry; the
'purpose' parameter's value is 'emergencyCallData.control'. Per 'purpose' parameter's value is 'emergencyCallData.control'. Per
[RFC6086], a metadata/control object is carried in a SIP INFO request [RFC6086], a metadata/control object is carried in a SIP INFO request
by using the INFO package defined in Section 14.10. by using the INFO package defined in Section 14.9.
An MSD or a metadata/control block is always enclosed in a multipart An MSD or a metadata/control block is always enclosed in a multipart
(normally multipart/mixed) body part (even if it would otherwise be (normally multipart/mixed) body part (even if it would otherwise be
the only body part in the SIP message), since as of the date of this the only body part in the SIP message), since as of the date of this
document, the use of Content-ID as a SIP header field is not defined document, the use of Content-ID as a SIP header field is not defined
(while it is defined for use as a MIME header field). (while it is defined for use as a MIME header field).
A body part containing an MSD or metadata/control object has a A body part containing an MSD or metadata/control object has a
Content-Disposition header field value containing "By-Reference". Content-Disposition header field value containing "By-Reference".
skipping to change at page 9, line 47 skipping to change at page 9, line 40
(e.g., upon manual request of the PSAP call taker who suspects (e.g., upon manual request of the PSAP call taker who suspects
vehicle state may have changed.) To do so, the PSAP creates a vehicle state may have changed.) To do so, the PSAP creates a
metadata/control object requesting an MSD and includes it within a metadata/control object requesting an MSD and includes it within a
SIP INFO request sent within the dialog. The IVS then includes an SIP INFO request sent within the dialog. The IVS then includes an
updated MSD within a SIP INFO request and sends it within the dialog. updated MSD within a SIP INFO request and sends it within the dialog.
If the IVS is unable to send an MSD, it instead sends a metadata/ If the IVS is unable to send an MSD, it instead sends a metadata/
control object acknowledging the request with the 'success' parameter control object acknowledging the request with the 'success' parameter
set to 'false' and a 'reason' parameter (and optionally a 'details' set to 'false' and a 'reason' parameter (and optionally a 'details'
parameter) indicating why the request could not be accomplished. Per parameter) indicating why the request could not be accomplished. Per
[RFC6086], metadata/control objects and MSDs are sent using the INFO [RFC6086], metadata/control objects and MSDs are sent using the INFO
package defined in Section 14.10. In addition, to align with how an package defined in Section 14.9. In addition, to align with how an
MSD or metadata/control block is transmitted in a SIP message other MSD or metadata/control block is transmitted in a SIP message other
than an INFO request, a Call-Info header field is included in the SIP than an INFO request, a Call-Info header field is included in the SIP
INFO request to reference the MSD or metadata/control block per INFO request to reference the MSD or metadata/control block per
[RFC7852]. See Section 14.10 for information about the use of SIP [RFC7852]. See Section 14.9 for information about the use of SIP
INFO requests to carry data within an eCall. INFO requests to carry data within an eCall.
The IVS is not expected to send an unsolicited MSD after the initial The IVS is not expected to send an unsolicited MSD after the initial
INVITE. INVITE.
This document does not mandate support for the data blocks defined in This document does not mandate support for the data blocks defined in
[RFC7852]. [RFC7852].
7. Call Setup 7. Call Setup
skipping to change at page 12, line 4 skipping to change at page 11, line 51
emergency call systems and extension points. (This metadata/control emergency call systems and extension points. (This metadata/control
block is in effect a high-level protocol between the PSAP and IVS.) block is in effect a high-level protocol between the PSAP and IVS.)
When the PSAP sends a metadata/control block in response to data sent When the PSAP sends a metadata/control block in response to data sent
by the IVS in a SIP request other than INFO (e.g., the MSD in the by the IVS in a SIP request other than INFO (e.g., the MSD in the
initial INVITE), the metadata/control block is sent in the SIP initial INVITE), the metadata/control block is sent in the SIP
response to that request (e.g., the response to the INVITE request). response to that request (e.g., the response to the INVITE request).
When the PSAP sends a control block in other circumstances (e.g., When the PSAP sends a control block in other circumstances (e.g.,
mid-call), the control block is transmitted from the PSAP to the IVS mid-call), the control block is transmitted from the PSAP to the IVS
in a SIP INFO request within the established dialog. The IVS sends in a SIP INFO request within the established dialog. The IVS sends
the requested data (the MSD) in a new SIP INFO request (per the requested data (the MSD) in a new SIP INFO request (per
[RFC6086]). This mechanism flexibly allows the PSAP to send eCall- [RFC6086]). This mechanism flexibly allows the PSAP to send eCall-
specific data to the IVS and the IVS to respond. SIP INFO requests specific data to the IVS and the IVS to respond. SIP INFO requests
are sent using an appropriate SIP INFO Package. See Section 6 for are sent using an appropriate SIP INFO Package. See Section 6 for
more information on sending a metadata/control block within a SIP more information on sending a metadata/control block within a SIP
message. See Section 14.10 for information about the use of SIP INFO message. See Section 14.9 for information about the use of SIP INFO
requests to carry data within an eCall. requests to carry data within an eCall.
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 final response without the metadata/control If the IVS receives a SIP final response without the metadata/control
block, it indicates that the SIP dialog is not an NG-eCall (e.g., 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 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
skipping to change at page 13, line 38 skipping to change at page 13, line 34
request Used in a control block sent by the PSAP to the IVS, to request Used in a control block sent by the PSAP to the IVS, to
request the vehicle to perform an action. request the vehicle to perform an action.
The <ack> element indicates the object being acknowledged and reports The <ack> element indicates the object being acknowledged and reports
success or failure. 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.9.1 to contain the allowed values. Section 14.8.1 to contain the allowed values.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element acknowledges receipt of an eCall data object or The <ack> element acknowledges receipt of an eCall data object or
request. An <ack> element references the Content-ID of the object request. An <ack> element references the Content-ID of the object
being acknowledged. The PSAP MUST send an <ack> element being acknowledged. The PSAP MUST send an <ack> element
acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in
skipping to change at page 15, line 10 skipping to change at page 15, line 8
Usage: Mandatory Usage: Mandatory
Type: Boolean Type: Boolean
Description: Indicates if the action was successfully Description: Indicates if the action was successfully
accomplished accomplished
Name: reason Name: reason
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used when 'success' is "false", this attribute Description: Used when 'success' is "false", this attribute
contains a reason code for a failure. A registry for reason contains a reason code for a failure. A registry for reason
codes is defined in Section 14.9.2. The initial values are: codes is defined in Section 14.8.2. The initial values are:
damaged (required components are damaged), data-unsupported damaged (required components are damaged), data-unsupported
(the data item referenced in a 'send-data' request is not (the data item referenced in a 'send-data' request is not
supported), security-failure (the authenticity of the request supported), security-failure (the authenticity of the request
or the authority of the requestor could not be verified), or the authority of the requestor could not be verified),
unable (a generic error for use when no other code is unable (a generic error for use when no other code is
appropriate), and unsupported (the 'action' value is not appropriate), and unsupported (the 'action' value is not
supported). supported).
Name: details Name: details
Usage: optional Usage: optional
skipping to change at page 17, line 16 skipping to change at page 17, line 16
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
Direction: Sent in either direction Direction: Sent in either direction
Description: Identifies the action that the vehicle is requested to Description: Identifies the action that the vehicle is requested to
perform (in a <request> element within a <capabilities> element, perform (in a <request> element within a <capabilities> element,
indicates an action that the vehicle is capable of performing). indicates an action that the vehicle is capable of performing).
An IANA registry is established in Section 14.9.1 to contain the An IANA registry is established in Section 14.8.1 to contain the
allowed values. allowed values.
Example: action="send-data" Example: action="send-data"
Name: int-id Name: int-id
Usage: Conditional Usage: Conditional
Type: int Type: int
Direction: Sent in either direction Direction: Sent in either direction
Description: Defined for extensibility. Documents that make use of Description: Defined for extensibility. Documents that make use of
it are expected to explain when it is required and how it is used. it are expected to explain when it is required and how it is used.
Example: int-id="3" Example: int-id="3"
skipping to change at page 21, line 35 skipping to change at page 21, line 35
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundary1 --boundary1
Content-Type: application/pidf+xml Content-Type: application/pidf+xml
Content-ID: <target123@example.com> Content-ID: <target123@example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
...PIDF-LO goes in here ...PIDF-LO goes in here
--boundary1 --boundary1
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundary1-- --boundary1--
Figure 8: SIP NG-eCall INVITE Figure 8: SIP NG-eCall INVITE
Continuing the example, Figure 9 illustrates a SIP 200 OK response to Continuing the example, Figure 9 illustrates a SIP 200 OK response to
skipping to change at page 22, line 12 skipping to change at page 22, line 12
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: urn:service:sos.ecall.automatic;tag=8gydfe65t0 To: urn:service:sos.ecall.automatic;tag=8gydfe65t0
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
Call-Info: <cid:2345678901@atlanta.example.com>; Call-Info: <cid:2345678901@atlanta.example.com>;
purpose=emergencyCallData.control purpose=emergencyCallData.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml, application/emergencyCallData.control+xml,
application/emergencyCallData.eCall.MSD+per application/emergencyCallData.eCall.MSD
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall.MSD Recv-Info: emergencyCallData.eCall.MSD
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=boundaryX Content-Type: multipart/mixed; boundary=boundaryX
Content-Length: ... Content-Length: ...
--boundaryX --boundaryX
Content-Type: application/sdp Content-Type: application/sdp
skipping to change at page 24, line 20 skipping to change at page 24, line 20
purpose=emergencyCallData.eCall.MSD purpose=emergencyCallData.eCall.MSD
CSeq: 51862 INFO CSeq: 51862 INFO
Info-Package: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
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=boundaryLine Content-Type: multipart/mixed; boundary=boundaryLine
Content-Disposition: Info-Package Content-Disposition: Info-Package
Content-Length: ... Content-Length: ...
--boundaryLine --boundaryLine
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD
Content-ID: <4567890123@atlanta.example.com> Content-ID: <4567890123@atlanta.example.com>
Content-Disposition: by-reference Content-Disposition: by-reference
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundaryLine-- --boundaryLine--
Figure 11: INFO containing MSD Figure 11: INFO containing MSD
11. Security Considerations 11. Security Considerations
skipping to change at page 24, line 50 skipping to change at page 24, line 50
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.5. Note that an the "Security Considerations" block of Section 14.4. Note that an
attacker that has access to and is capable of generating a response attacker that has access to and is capable of generating a response
to the initial INVITE request could generate a 600 (Busy Everywhere), to the initial INVITE request could generate a 600 (Busy Everywhere),
486 (Busy Here), or 603 (Decline) response that includes a metadata/ 486 (Busy Here), or 603 (Decline) response that includes a metadata/
control object containing a reference to the MSD in the initial control object containing a reference to the MSD in the initial
INVITE and a "received=true" field, which could result in the IVS INVITE and a "received=true" field, which could result in the IVS
perceiving the PSAP to be overloaded and hence not attempting to perceiving the PSAP to be overloaded and hence not attempting to
reinitiate the call. The risk can be mitigated as discussed in the reinitiate the call. The risk can be mitigated as discussed in the
"Security Considerations" block of Section 14.5. "Security Considerations" block of Section 14.4.
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
skipping to change at page 26, line 7 skipping to change at page 26, line 7
The privacy considerations discussed in [RFC7852] apply here. The The privacy considerations discussed in [RFC7852] apply here. The
MSD carries some identifying and personal information (mostly about MSD carries some identifying and personal information (mostly about
the vehicle and less about the owner), as well as location the vehicle and less about the owner), as well as location
information, and so needs to be protected against unauthorized information, and so needs to be protected against unauthorized
disclosure. Local regulations may impose additional privacy disclosure. Local regulations may impose additional privacy
protection requirements. 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.4. block of Section 14.3.
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.5. the "Security Considerations" block of Section 14.4.
13. XML Schema 13. XML Schema
This section defines an XML schema for the control block. The text This section defines an XML schema for the control block. The text
description of the control block in Section 9.1 is normative and description of the control block in Section 9.1 is normative and
supersedes any conflicting aspect of this schema. supersedes any conflicting aspect of this schema.
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control"
skipping to change at page 29, line 14 skipping to change at page 29, line 14
the rules specified in Section 3.1 of [RFC6838], with the additional the rules specified in Section 3.1 of [RFC6838], with the additional
restriction that the standards-related organization MUST be restriction that the standards-related organization MUST be
responsible for some aspect of emergency communications. responsible for some aspect of emergency communications.
This subtree initially contains the following subtypes (defined here This subtree initially contains the following subtypes (defined here
or in [RFC7852]): or in [RFC7852]):
emergencyCallData.control+xml emergencyCallData.control+xml
EmergencyCallData.Comment+xml EmergencyCallData.Comment+xml
EmergencyCallData.DeviceInfo+xml EmergencyCallData.DeviceInfo+xml
EmergencyCallData.MSD+per EmergencyCallData.MSD
EmergencyCallData.ProviderInfo+xml EmergencyCallData.ProviderInfo+xml
EmergencyCallData.ServiceInfo+xml EmergencyCallData.ServiceInfo+xml
EmergencyCallData.SubscriberInfo+xml EmergencyCallData.SubscriberInfo+xml
14.2. Service URN Registrations 14.2. 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
skipping to change at page 29, line 46 skipping to change at page 29, line 46
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]. This service requests defined in Setcion 17.2 of [RFC6881]. This service requests
resources associated with a test (non-emergency) call placed by an resources associated with a test (non-emergency) call placed by an
in-vehicle system. See Section 8 for more information on the test in-vehicle system. See Section 8 for more information on the test
eCall request URN. eCall request URN.
14.3. MIME Structured Syntax Suffix Registration for +PER 14.3. MIME Media Type Registration for 'application/
emergencyCallData.eCall.MSD'
IANA is requested to add "+PER" to the as a media type structured
syntax suffix in the Structured Syntax Suffix registry. The ITU
defined the Packed Encoding Rules (PER) transfer syntax in
[ITU.X691]. The suffix "+per" MAY be used with any media type whose
representation follows the PER transfer syntax. The media type
structured syntax suffix registration form for +per follows:
Name: Packed Encoding Rules (PER) transfer syntax
+suffix: +per
References: [ITU.X691]
Encoding considerations: PER is a binary encoding
Interoperability considerations: none identified
Fragment identifier considerations:
At publication of this document, there is no fragment
identification syntax defined for +per.
The syntax and semantics for fragment identifiers for a
specific "xxx/yyy+per" SHOULD be processed as follows:
For cases defined in +per, where the fragment identifier
resolves per the +per rules, then process as specified in +per.
For cases defined in +per, where the fragment identifier does
not resolve per the +per rules, then process as specified in
"xxx/yyy+per".
For cases not defined in +per, then process as specified in
"xxx/yyy+per".
Security considerations:
Because of the binary and structured nature of PER, it is not
difficult to construct malicious content that could cause
buffer overruns, stack overflows, and other attack vectors.
Implementors should be aware of these issues and take
appropriate measures to guard against buffer overruns, stack
overflows, and related attack vectors.
Contact: Apps Area Working Group (art@ietf.org)
Author/Change controller:
The Apps Area Working Group. IESG has change control over this
registration.
14.4. MIME Media Type Registration for 'application/
emergencyCallData.eCall.MSD+per'
IANA is requested to add application/emergencyCallData.eCall.MSD+per IANA is requested to add application/emergencyCallData.eCall.MSD as a
as a MIME media type, with a reference to this document, in MIME media type, with a reference to this document, in accordance to
accordance to the procedures of RFC 6838 [RFC6838] and guidelines in the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303
RFC 7303 [RFC7303]. [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.MSD+per MIME subtype name: emergencyCallData.eCall.MSD
Mandatory parameters: none Mandatory parameters: none
Optional parameters: none Optional parameters: none
Encoding scheme: binary Encoding scheme: binary
Encoding considerations: Uses ASN.1 PER, which is a binary Encoding considerations: Uses ASN.1 PER, which is a binary
encoding; when transported in SIP, binary content transfer encoding; when transported in SIP, binary content transfer
encoding is used. encoding is used.
skipping to change at page 32, line 4 skipping to change at page 30, line 46
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.5. MIME Media Type Registration for 'application/ 14.4. MIME Media Type Registration for 'application/
emergencyCallData.control+xml' emergencyCallData.control+xml'
IANA is requested to add application/emergencyCallData.control+xml as IANA is requested to add application/emergencyCallData.control+xml as
a MIME media type, with a reference to this document, in accordance a MIME media type, with a reference to this document, in accordance
to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303
[RFC7303]. [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.control+xml MIME subtype name: emergencyCallData.control+xml
skipping to change at page 32, line 47 skipping to change at page 31, line 42
This media type carries metadata and control information and This media 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.4, can contain personal which as described in Section 14.3, 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
skipping to change at page 33, line 43 skipping to change at page 32, line 37
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.6. Registration of the 'eCall.MSD' entry in the Emergency Call 14.5. Registration of the 'eCall.MSD' entry in the Emergency Call
Additional Data Types registry Additional Data Types 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 Types registry, with a reference to Emergency Call Additional Data Types registry, with a reference to
this document; the 'Data About' value is 'The Call'. this document; the 'Data About' value is 'The Call'.
14.7. Registration of the 'control' entry in the Emergency Call 14.6. Registration of the 'control' entry in the Emergency Call
Additional Data Types registry Additional Data Types registry
This specification requests IANA to add the 'control' entry to the This specification requests IANA to add the 'control' entry to the
Emergency Call Additional Data Types registry, with a reference to Emergency Call Additional Data Types registry, with a reference to
this document; the 'Data About' value is 'The Call'. this document; the 'Data About' value is 'The Call'.
14.8. URN Sub-Namespace Registration 14.7. Registration for urn:ietf:params:xml:ns:EmergencyCallData:control
14.8.1. Registration for
urn:ietf:params:xml:ns:EmergencyCallData: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:EmergencyCallData:control URI: urn:ietf:params:xml:ns:EmergencyCallData: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 34, line 44 skipping to change at page 33, line 34
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Emergency Call Data Control Block</title> <title>Namespace for Emergency Call Data Control Block</title>
</head> </head>
<body> <body>
<h1>Namespace for Emergency Call Data Control Block</h1> <h1>Namespace for Emergency Call Data Control Block</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.9. Registry Creation 14.8. Registry Creation
This document creates a new registry called "Emergency Call Metadata/ This document creates a new registry called "Emergency Call Metadata/
Control Data". The following sub-registries are created for this Control Data". The following sub-registries are created for this
registry. registry.
14.9.1. Emergency Call Action Registry 14.8.1. Emergency Call Action Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Action". As defined in [RFC5226], this registry operates under Action". 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 35, line 36 skipping to change at page 34, line 24
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 | See Section 9.1.3.1 of this document | | send-data | See Section 9.1.3.1 of this document |
+-----------+--------------------------------------+ +-----------+--------------------------------------+
Table 2: Emergency Call Action Registry Initial Values Table 2: Emergency Call Action Registry Initial Values
14.9.2. Emergency Call Action Failure Reason Registry 14.8.2. Emergency Call Action Failure Reason Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Action Failure Reason" which contains values for the 'reason' Action Failure Reason" which contains values for the 'reason'
attribute of the <actionResult> element. As defined in [RFC5226], attribute of the <actionResult> element. As defined in [RFC5226],
this registry operates under "Expert Review" rules. The expert this registry operates under "Expert Review" rules. The expert
should determine that the proposed reason is sufficiently should determine that the proposed reason is sufficiently
distinguishable from other reasons and that the proposed description distinguishable from other reasons and that the proposed description
is understandable and correctly worded. is understandable and correctly worded.
The content of this registry includes: The content of this registry includes:
skipping to change at page 36, line 28 skipping to change at page 35, line 26
| | | | | |
| unable | The action could not be accomplished (a | | unable | The action could not be accomplished (a |
| | generic error for use when no other code is | | | generic error for use when no other code is |
| | appropriate). | | | appropriate). |
| | | | | |
| unsupported | The 'action' value is not supported. | | unsupported | The 'action' value is not supported. |
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
Table 3: Emergency Call Action Failure Reason Registry Initial Values Table 3: Emergency Call Action Failure Reason Registry Initial Values
14.10. The emergencyCallData.eCall.MSD INFO package 14.9. The emergencyCallData.eCall.MSD INFO package
This document registers the 'emergencyCallData.eCall.MSD' INFO This document registers the 'emergencyCallData.eCall.MSD' INFO
package. package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per 'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO requests carrying data [RFC6086] to indicate ability to receive INFO requests carrying data
as described here. as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive eCall related body parts as specified in [TBD: the ability to receive eCall related body parts as specified in [TBD:
THIS DOCUMENT]. THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086]. field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
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.
14.10.1. Overall Description 14.9.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.MSD INFO INFO requests associated with the emergencyCallData.eCall.MSD INFO
package carry data associated with emergency calls as defined in package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs. data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information. Refer to [TBD: THIS DOCUMENT] for more information.
14.10.2. Applicability 14.9.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 the SIP INFO method is based on an analysis of the The use of the SIP INFO method is based on an analysis of the
requirements against the intent and effects of the INFO method versus requirements against the intent and effects of the INFO method versus
other approaches (which included the SIP MESSAGE method, the SIP other approaches (which included the SIP MESSAGE method, the SIP
OPTIONS method, the SIP re-INVITE method, media plane transport, and OPTIONS method, the SIP re-INVITE method, media plane transport, and
non-SIP protocols). In particular, the transport of emergency call non-SIP protocols). In particular, the transport of emergency call
data blocks occurs within a SIP emergency dialog, per Section 6, and data blocks occurs within a SIP emergency dialog, per Section 6, and
skipping to change at page 38, line 5 skipping to change at page 36, line 43
what's needed here is two-way communication of data related to the what's needed here is two-way communication of data related to the
emergency dialog. Use of the media plane mechanisms was discounted emergency dialog. Use of the media plane mechanisms was discounted
because the number of messages needing to be exchanged in a dialog is because the number of messages needing to be exchanged in a dialog is
normally zero or very few, and the size of the data is likewise very normally zero or 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 small. The overhead caused by user plane setup (e.g., to use MSRP as
transport) would be disproportionately large. transport) would be disproportionately large.
Based on the analyses, the SIP INFO method was chosen to provide for Based on the analyses, the SIP INFO method was chosen to provide for
mid-call data transport. mid-call data transport.
14.10.3. Info Package Name 14.9.3. Info Package Name
The info package name is emergencyCallData.eCall.MSD The info package name is emergencyCallData.eCall.MSD
14.10.4. Info Package Parameters 14.9.4. Info Package Parameters
None None
14.10.5. SIP Option-Tags 14.9.5. SIP Option-Tags
None None
14.10.6. INFO Request Body Parts 14.9.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a The body for an emergencyCallData.eCall.MSD info package is a
multipart (normally multipart/mixed) body containing zero or one multipart (normally multipart/mixed) body containing zero or one
application/emergencyCallData.eCall.MSD+per part (containing an MSD) application/emergencyCallData.eCall.MSD part (containing an MSD) and
and zero or more application/emergencyCallData.control+xml zero or more application/emergencyCallData.control+xml (containing a
(containing a metadata/control object) parts. At least one MSD or metadata/control object) parts. At least one MSD or metadata/control
metadata/control body part is expected; the behavior upon receiving body part is expected; the behavior upon receiving an INFO request
an INFO request with neither is undefined. with neither is undefined.
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in SIP messages other than INFO with how these body parts are sent in SIP messages other than INFO
requests, each associated body part is referenced by a Call-Info requests, each associated body part is referenced by a Call-Info
header field at the top level of the SIP message. The body part has header field at the top level of the SIP message. The body part has
a Content-Disposition header field set to "By-Reference". a Content-Disposition header field set to "By-Reference".
An MSD or metadata/control block is always enclosed in a multipart An MSD or metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the body part (even if it would otherwise be the only body part in the
SIP message), since as of the date of this document, the use of SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field). The innermost multipart that for use as a MIME header field). The innermost multipart that
contains only body parts associated with the INFO package has a contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package. Content-Disposition value of Info-Package.
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
14.10.7. Info Package Usage Restrictions 14.9.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
14.10.8. Rate of INFO Requests 14.9.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated MSD, and dialog for the PSAP to request the IVS to send an updated MSD, and
for the IVS to send a requested MSD. Because this is normally done for the IVS to send a requested MSD. Because this is normally done
only on manual request of the PSAP call taker (who suspects some only on manual request of the PSAP call taker (who suspects some
aspect of the vehicle state has changed), the rate of SIP INFO aspect of the vehicle state has changed), the rate of SIP INFO
requests associated with the emergencyCallData.eCall.MSD info package requests associated with the emergencyCallData.eCall.MSD info package
is normally quite low (most dialogs are likely to contain zero INFO is normally quite low (most dialogs are likely to contain zero INFO
requests, while others might carry an occasional request). requests, while others might carry an occasional request).
14.10.9. Info Package Security Considerations 14.9.9. Info Package Security Considerations
The MIME media type registrations specified for use with this INFO The MIME media type registrations specified for use with this INFO
package (Section 14.4 and Section 14.5) contain a discussion of the package (Section 14.3 and Section 14.4) contain a discussion of the
security and/or privacy considerations specific to that data block. security and/or privacy considerations specific to that data block.
The "Security Considerations" and "Privacy Considerations" sections The "Security Considerations" and "Privacy Considerations" sections
of [TBD: THIS DOCUMENT] discuss security and privacy considerations of [TBD: THIS DOCUMENT] discuss security and privacy considerations
of the data carried in eCalls. of the data carried in eCalls.
14.10.10. Implementation Details 14.9.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
14.10.11. Examples 14.9.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See [TBD: THIS DOCUMENT] for protocol examples.
15. Contributors 15. 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 16. Acknowledgements
skipping to change at page 42, line 4 skipping to change at page 40, line 50
o Added references for eCall test call requirement o Added references for eCall test call requirement
o Described meaning of eCall URNs in Section 8 as well as in IANA o Described meaning of eCall URNs in Section 8 as well as in IANA
registration registration
17.12. Changes from draft-ietf-07 to draft-ietf-08 17.12. 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, and solicited MSDs control usage, such as use in rejected calls, and 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 7.1 to be a subsection of 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 14.10 to be a main section instead of a o Moved new Section Section 14.9 to be a main section instead of a
subsection of Section 9 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.13. Changes from draft-ietf-06 to draft-ietf-07 17.13. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
17.14. Changes from draft-ietf-05 to draft-ietf-06 17.14. Changes from draft-ietf-05 to draft-ietf-06
 End of changes. 57 change blocks. 
186 lines changed or deleted 126 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/