< draft-rosen-ecrit-ecall-02.txt		draft-rosen-ecrit-ecall-03.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 8, 2009 Nokia Siemens Networks		Expires: September 7, 2010 Nokia Siemens Networks
	U. Dietz		U. Dietz
	Vodafone		Vodafone
	March 7, 2009		March 6, 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-02.txt		draft-rosen-ecrit-ecall-03.txt
			Abstract
			This document describes how to use a subset of the IETF-based
			emergency call framework for accomplishing emergency calling support
			in vehicles. Simplifications are possible due to the nature of the
			functionality that is going to be provided in vehicles with the usage
			of GPS. Additionally, further profiling needs to be done regarding
			the encoding of location information.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 35 ¶		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 8, 2009.		This Internet-Draft will expire on September 7, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 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 in effect on the date of		Provisions Relating to IETF Documents
	publication of this document (http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info) in effect on the date of
	Please review these documents carefully, as they describe your rights		publication of this document. Please review these documents
	and restrictions with respect to this document.		carefully, as they describe your rights and restrictions with respect
			to this document. Code Components extracted from this document must
	Abstract		include Simplified BSD License text as described in Section 4.e of
			the Trust Legal Provisions and are provided without warranty as
	This document describes how to use a subset of the IETF-based		described in the BSD License.
	emergency call framework for accomplishing emergency calling support
	in vehicles. Simplifications are possible due to the nature of the
	functionality that is going to be provided in vehicles with the usage
	of GPS. Additionally, further profiling needs to be done regarding
	the encoding of location information.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Protocol Profile . . . . . . . . . . . . . . . . . . . . . . . 5		3. Protocol Profile . . . . . . . . . . . . . . . . . . . . . . . 5
	4. Data Profile . . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Data Profile . . . . . . . . . . . . . . . . . . . . . . . . . 8
	5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 9		5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 11		6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	skipping to change at page 15, line 13 ¶		skipping to change at page 15, line 13 ¶
	provided to run LoST at the end host as well as on the VSP.		provided to run LoST at the end host as well as on the VSP.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[2] Rosen, B. and J. Polk, "Best Current Practice for		[2] Rosen, B. and J. Polk, "Best Current Practice for
	Communications Services in support of Emergency Calling",		Communications Services in support of Emergency Calling",
	draft-ietf-ecrit-phonebcp-08 (work in progress), February 2009.		draft-ietf-ecrit-phonebcp-14 (work in progress), January 2010.
	[3] Peterson, J., "A Presence-based GEOPRIV Location Object		[3] Peterson, J., "A Presence-based GEOPRIV Location Object
	Format", RFC 4119, December 2005.		Format", RFC 4119, December 2005.
	[4] Polk, J. and B. Rosen, "Location Conveyance for the Session		[4] Polk, J. and B. Rosen, "Location Conveyance for the Session
	Initiation Protocol", draft-ietf-sip-location-conveyance-12		Initiation Protocol", draft-ietf-sipcore-location-conveyance-02
	(work in progress), November 2008.		(work in progress), February 2010.
	[5] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller		[5] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller
	Preferences for the Session Initiation Protocol (SIP)",		Preferences for the Session Initiation Protocol (SIP)",
	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
	PIDF-LO Usage Clarification, Considerations and		Presence Information Data Format Location Object (PIDF-LO)
	Recommendations", draft-ietf-geopriv-pdif-lo-profile-14 (work		Usage Clarification, Considerations, and Recommendations",
	in progress), November 2008.		RFC 5491, March 2009.
	[7] Vishal, S., Schulzrinne, H., and H. Tschofenig, "Dynamic		[7] Schulzrinne, H., Singh, V., Tschofenig, H., and M. Thomson,
	Feature 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-04 (work in progress),		draft-singh-geopriv-pidf-lo-dynamic-07 (work in progress),
	October 2008.		August 2009.
	[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. and H. Schulzrinne, "Trustworthy Location		[11] Tschofenig, H., Schulzrinne, H., and B. Aboba, "Trustworthy
	Information", draft-tschofenig-ecrit-trustworthy-location-01		Location Information",
	(work in progress), March 2009.		draft-tschofenig-ecrit-trustworthy-location-02 (work in
			progress), July 2009.
	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. 11 change blocks.
	33 lines changed or deleted		38 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/