< draft-rosen-ecrit-ecall-03.txt		draft-rosen-ecrit-ecall-04.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft NeuStar, Inc.		Internet-Draft NeuStar, Inc.
	Intended status: Informational H. Tschofenig		Intended status: Informational H. Tschofenig
	Expires: September 7, 2010 Nokia Siemens Networks		Expires: September 9, 2010 Nokia Siemens Networks
	U. Dietz		U. Dietz
	Vodafone		Vodafone
	March 6, 2010		March 8, 2010
	Best Current Practice for IP-based In-Vehicle Emergency Calls		Best Current Practice for IP-based In-Vehicle Emergency Calls
	draft-rosen-ecrit-ecall-03.txt		draft-rosen-ecrit-ecall-04.txt
	Abstract		Abstract
	This document describes how to use a subset of the IETF-based		This document describes how to use a subset of the IETF-based
	emergency call framework for accomplishing emergency calling support		emergency call framework for accomplishing emergency calling support
	in vehicles. Simplifications are possible due to the nature of the		in vehicles. Simplifications are possible due to the nature of the
	functionality that is going to be provided in vehicles with the usage		functionality that is going to be provided in vehicles with the usage
	of GPS. Additionally, further profiling needs to be done regarding		of GPS. Additionally, further profiling needs to be done regarding
	the encoding of location information.		the encoding of location information.
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 7, 2010.		This Internet-Draft will expire on September 9, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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 3, line 21 ¶		skipping to change at page 3, line 21 ¶
	victim(s) may not be able to call because they have been injured or		victim(s) may not be able to call because they have been injured or
	trapped.		trapped.
	In Europe the European Commission has launched the eCall initiative		In Europe the European Commission has launched the eCall initiative
	that may best be described as a user initiated or automatically		that may best be described as a user initiated or automatically
	triggered system to provide notifications to Public Safety Answering		triggered system to provide notifications to Public Safety Answering
	Point's (PSAP), by means of cellular communications, that a vehicle		Point's (PSAP), by means of cellular communications, that a vehicle
	has crashed, and to provide geodetic location information and where		has crashed, and to provide geodetic location information and where
	possible a voice channel to the PSAP. The current specifications		possible a voice channel to the PSAP. The current specifications
	being developed to offer the eCall solution are defined to work with		being developed to offer the eCall solution are defined to work with
	circuit switched telephony. This document details how the same		circuit switched telephony. This document details how similar or
	functionality can be accomplished using IP-based mechanisms. Since		more extended functionality can be accomplished using IP-based
	cellular systems are being enhanced with IP-based infrastructure this		mechanisms.
	document complements the ambiguous goal to provide widespread
	availability of in-vehicular emergency services solutions.
	This document is organized as follows: Section 2 defines the		This document is organized as follows: Section 2 defines the
	terminology, Section 3 illustrates the required protocol		terminology, Section 3 illustrates the required protocol
	functionality, Section 4 indicates the required data that has to be		functionality, Section 4 indicates the required data that has to be
	transmitted within a PIDF-LO and Section 5 shows an example message		transmitted within a PIDF-LO and Section 5 shows an example message
	exchange. This document concludes with the security considerations		exchange. This document concludes with the security considerations
	in Section 6 and IANA considerations in Section 7.		in Section 6 and IANA considerations in Section 7.
	2. Terminology		2. Terminology
	skipping to change at page 7, line 17 ¶		skipping to change at page 7, line 17 ¶
	Mid-call behavior: The description in Section 11 of [2] is fully		Mid-call behavior: The description in Section 11 of [2] is fully
	applicable to this document.		applicable to this document.
	Call termination: The description in Section 12 of [2] is fully		Call termination: The description in Section 12 of [2] is fully
	applicable to this document.		applicable to this document.
	Disabling of features: The description in Section 13 of [2] is fully		Disabling of features: The description in Section 13 of [2] is fully
	applicable to this document.		applicable to this document.
	Media: Real-time text and video may be supported in devices some		Media: If hardware and software for real-time text, voice, and video
	time in the future. If voice calls are supported then the		is available in the end device then the requirements regarding
	description in Section 14 is applicable to this document.		multi-media support described in [2] are applicable.
	Testing: The description in Section 15 of [2] is fully applicable to		Testing: The description in Section 15 of [2] is fully applicable to
	this document.		this document.
	4. Data Profile		4. Data Profile
	Due to the requirement for a built-in GPS receiver only geodetic		Due to the requirement for a built-in GPS receiver only geodetic
	location information will be sent within an emergency call.		location information will be sent within an emergency call.
	Furthermore, the number of location shapes is is restricted. Hence,		Furthermore, the number of location shapes is is restricted. Hence,
	the following location shapes of [6] MUST be implemented: 2d and 3d		the following location shapes of [6] MUST be implemented: 2d and 3d
	skipping to change at page 13, line 7 ¶		skipping to change at page 13, line 7 ¶
	IANA is requested to register the URN 'urn:service:ecall' under the		IANA is requested to register the URN 'urn:service:ecall' under the
	sub-services 'sos' registry defined in Section 4.2 of [8].		sub-services 'sos' registry defined in Section 4.2 of [8].
	urn:service:ecall This service identifier reaches a public safety		urn:service:ecall This service identifier reaches a public safety
	answering point (PSAP), which in turn dispatches aid appropriate		answering point (PSAP), which in turn dispatches aid appropriate
	to the emergency related to accidents of vehicles.		to the emergency related to accidents of vehicles.
	8. Acknowledgements		8. Acknowledgements
	We would like to thank Michael Montag for his feedback.		We would like to thank Michael Montag, Arnoud van Wijk, and Gunnar
			Hellstroem for their feedback.
	9. Open Issues		9. Open Issues
	While working on this document a few aspects where discovered that		While working on this document a few aspects where discovered that
	require further discussion:		require further discussion:
	o Today's work on the eCall system does not necessarily require a		o Today's work on the eCall system does not necessarily require a
	voice call to be established; a voice call may be established		voice call to be established; a voice call may be established
	whenever possible by the functionality offered by the device.		whenever possible by the functionality offered by the device.
	From a protocol mechanims, however, the design for establishing an		From a protocol mechanims, however, the design for establishing an
	skipping to change at page 15, line 35 ¶		skipping to change at page 15, line 35 ¶
	RFC 3841, August 2004.		RFC 3841, August 2004.
	[6] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV		[6] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
	Presence Information Data Format Location Object (PIDF-LO)		Presence Information Data Format Location Object (PIDF-LO)
	Usage Clarification, Considerations, and Recommendations",		Usage Clarification, Considerations, and Recommendations",
	RFC 5491, March 2009.		RFC 5491, March 2009.
	[7] Schulzrinne, H., Singh, V., Tschofenig, H., and M. Thomson,		[7] Schulzrinne, H., Singh, V., Tschofenig, H., and M. Thomson,
	"Dynamic Extensions to the Presence Information Data Format		"Dynamic Extensions to the Presence Information Data Format
	Location Object (PIDF-LO)",		Location Object (PIDF-LO)",
	draft-singh-geopriv-pidf-lo-dynamic-07 (work in progress),		draft-singh-geopriv-pidf-lo-dynamic-08 (work in progress),
	August 2009.		March 2010.
	[8] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency		[8] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency
	and Other Well-Known Services", RFC 5031, January 2008.		and Other Well-Known Services", RFC 5031, January 2008.
	10.2. Informative references		10.2. Informative references
	[9] Schulzrinne, H. and R. Marshall, "Requirements for Emergency		[9] Schulzrinne, H. and R. Marshall, "Requirements for Emergency
	Context Resolution with Internet Technologies", RFC 5012,		Context Resolution with Internet Technologies", RFC 5012,
	January 2008.		January 2008.
	[10] Taylor, T., Tschofenig, H., Schulzrinne, H., and M. Shanmugam,		[10] Taylor, T., Tschofenig, H., Schulzrinne, H., and M. Shanmugam,
	"Security Threats and Requirements for Emergency Call Marking		"Security Threats and Requirements for Emergency Call Marking
	and Mapping", RFC 5069, January 2008.		and Mapping", RFC 5069, January 2008.
	[11] Tschofenig, H., Schulzrinne, H., and B. Aboba, "Trustworthy		[11] Tschofenig, H., Schulzrinne, H., and B. Aboba, "Trustworthy
	Location Information",		Location Information",
	draft-tschofenig-ecrit-trustworthy-location-02 (work in		draft-tschofenig-ecrit-trustworthy-location-03 (work in
	progress), July 2009.		progress), March 2010.
	Authors' Addresses		Authors' Addresses
	Brian Rosen		Brian Rosen
	NeuStar, Inc.		NeuStar, Inc.
	470 Conrad Dr		470 Conrad Dr
	Mars, PA 16046		Mars, PA 16046
	US		US
	Phone:		Phone:
End of changes. 9 change blocks.
	17 lines changed or deleted		16 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/