< draft-ietf-ecrit-ecall-09.txt		draft-ietf-ecrit-ecall-10.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: January 22, 2017 Individual		Expires: January 22, 2017 Individual
	July 21, 2016		July 21, 2016
	Next-Generation Pan-European eCall		Next-Generation Pan-European eCall
	draft-ietf-ecrit-ecall-09.txt		draft-ietf-ecrit-ecall-10.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 2, line 34 ¶		skipping to change at page 2, line 34 ¶
	9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 11		9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 11
	9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 12		9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 12
	9.1.1.1. Attributes of the <ack> element . . . . . . . . . 12		9.1.1.1. Attributes of the <ack> element . . . . . . . . . 12
	9.1.1.2. Child Elements of the <ack> element . . . . . . . 13		9.1.1.2. Child Elements of the <ack> element . . . . . . . 13
	9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 13		9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 13
	9.1.2. The <request> element . . . . . . . . . . . . . . . . 13		9.1.2. The <request> element . . . . . . . . . . . . . . . . 13
	9.1.2.1. Attributes of the <request> element . . . . . . . 13		9.1.2.1. Attributes of the <request> element . . . . . . . 13
	9.1.2.2. Request Example . . . . . . . . . . . . . . . . . 14		9.1.2.2. Request Example . . . . . . . . . . . . . . . . . 14
	10. The emergencyCallData.eCall INFO package . . . . . . . . . . 14		10. The emergencyCallData.eCall INFO package . . . . . . . . . . 14
	10.1. INFO Package Requirements . . . . . . . . . . . . . . . 14		10.1. INFO Package Requirements . . . . . . . . . . . . . . . 14
	10.1.1. Overall Description . . . . . . . . . . . . . . . . 14		10.1.1. Overall Description . . . . . . . . . . . . . . . . 15
	10.1.2. Applicability . . . . . . . . . . . . . . . . . . . 15		10.1.2. Applicability . . . . . . . . . . . . . . . . . . . 15
	10.1.3. Info Package Name . . . . . . . . . . . . . . . . . 15		10.1.3. Info Package Name . . . . . . . . . . . . . . . . . 15
	10.1.4. Info Package Parameters . . . . . . . . . . . . . . 15		10.1.4. Info Package Parameters . . . . . . . . . . . . . . 16
	10.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 16		10.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 16
	10.1.6. INFO Message Body Parts . . . . . . . . . . . . . . 16		10.1.6. INFO Message Body Parts . . . . . . . . . . . . . . 16
	10.1.7. Info Package Usage Restrictions . . . . . . . . . . 16		10.1.7. Info Package Usage Restrictions . . . . . . . . . . 16
	10.1.8. Rate of INFO Requests . . . . . . . . . . . . . . . 16		10.1.8. Rate of INFO Requests . . . . . . . . . . . . . . . 16
	10.1.9. Info Package Security Considerations . . . . . . . . 16		10.1.9. Info Package Security Considerations . . . . . . . . 16
	10.1.10. Implementation Details . . . . . . . . . . . . . . . 16		10.1.10. Implementation Details . . . . . . . . . . . . . . . 16
	10.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 16		10.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 17
	11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17		11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	12. Security Considerations . . . . . . . . . . . . . . . . . . . 22		12. Security Considerations . . . . . . . . . . . . . . . . . . . 22
	13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 23		13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 23
	14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 23		14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 23
	15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25		15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
	15.1. Service URN Registrations . . . . . . . . . . . . . . . 25		15.1. Service URN Registrations . . . . . . . . . . . . . . . 25
	15.2. MIME Content-type Registration for		15.2. MIME Content-type Registration for
	'application/emergencyCallData.eCall.MSD+per' . . . . . 26		'application/emergencyCallData.eCall.MSD+per' . . . . . 26
	15.3. MIME Content-type Registration for		15.3. MIME Content-type Registration for
	'application/emergencyCallData.eCall.control+xml' . . . 27		'application/emergencyCallData.eCall.control+xml' . . . 27
	skipping to change at page 4, line 29 ¶		skipping to change at page 4, line 29 ¶
	| | |		| | |
	| MNO | Mobile Network Operator |		| MNO | Mobile Network Operator |
	| | |		| | |
	| 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 focused on 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 or all-IP eCall) within the SIP framework		as packet-switched eCall or all-IP eCall) within the SIP framework
	for emergency calls, as described in [RFC6443] and [RFC6881]. eCall		for emergency calls, as described in [RFC6443] and [RFC6881]. eCall
	itself is specified by 3GPP and CEN and these specifications include		itself is specified by 3GPP and CEN and these 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 also provide a basis for
	other vehicle-initiated emergency call systems, but this is out of		reuse and extension for other vehicle-initiated emergency call
	scope for this document.		systems.
	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].		as described in [I-D.ietf-ecrit-car-crash].
	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
	skipping to change at page 8, line 21 ¶		skipping to change at page 8, line 21 ¶
	other messages (such as the INVITE and the reply to the INVITE as		other messages (such as the INVITE and the reply to the INVITE as
	discussed above). See Section 10 for information about the use of		discussed above). See Section 10 for information about the use of
	INFO messages to carry data within an eCall.		INFO messages to carry data within an eCall.
	When data is being carried in an INFO request message, the body part		When data is being carried in an INFO request message, the body part
	also carries a Content-Disposition header field set to "Info-		also carries a Content-Disposition header field set to "Info-
	Package".		Package".
	Support for the data blocks defined in		Support for the data blocks defined in
	[I-D.ietf-ecrit-additional-data] is NOT REQUIRED for conformance with		[I-D.ietf-ecrit-additional-data] is NOT REQUIRED for conformance with
	this document .		this document.
	7. Call Setup		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).
	skipping to change at page 14, line 33 ¶		skipping to change at page 14, line 33 ¶
	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.		Types' IANA registry. Because new body parts can be added to the
			registry, implementations MUST ignore any unsupported or unrecognized
			body parts. Only the 'application/emergencyCallData.eCall.MSD+per'
			and 'application/emergencyCallData.eCall.control+xml' body parts are
			REQUIRED to be supported for conformance with this document.
	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]. See Section 6 for details on how to attach eCall data to		[RFC6086]. See Section 6 for details on how to attach eCall data to
	an INFO message.		an INFO message.
	10.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.
End of changes. 8 change blocks.
	10 lines changed or deleted		14 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/