< draft-patel-dispatch-cpc-oli-parameter-02.txt		draft-patel-dispatch-cpc-oli-parameter-03.txt >
	DISPATCH Working Group M. Patel		DISPATCH Working Group M. Patel
	Internet-Draft Nortel		Internet-Draft InterDigital Communications, LLC
	Intended status: Standards Track R. Jesske		Intended status: Standards Track R. Jesske
	Expires: June 3, 2010 Deutsche Telekom		Expires: December 10, 2010 Deutsche Telekom
	M. Dolly		M. Dolly
	AT&T		AT&T
	November 30, 2009		June 8, 2010
	Uniform Resource Identifier (URI) Parameters for indicating the Calling		Uniform Resource Identifier (URI) Parameters for indicating the Calling
	Party's Category and Originating Line Information		Party's Category and Originating Line Information
	draft-patel-dispatch-cpc-oli-parameter-02.txt		draft-patel-dispatch-cpc-oli-parameter-03.txt
	Abstract		Abstract
	This document defines two new URI parameters to describe the calling		This document defines two new URI parameters to describe the calling
	party's category and toll class of service originating line		party's category and toll class of service originating line
	information which are parameters also used in SS7 ISUP and other		information which are parameters also used in SS7 ISUP and other
	telephony signalling protocols. The intended use of these URI		telephony signalling protocols. The intended use of these URI
	parameters is for the tel URI address scheme.		parameters is for the tel URI address scheme.
	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). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		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."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on December 10, 2010.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on June 3, 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		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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Parameter Definitions . . . . . . . . . . . . . . . . . . . . . 3		3. Parameter Definitions . . . . . . . . . . . . . . . . . . . . . 3
	4. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5		4. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 5, line 5 ¶		skipping to change at page 5, line 5 ¶
	Alternatively, the tel URI may be included in the P-Asserted-Identity		Alternatively, the tel URI may be included in the P-Asserted-Identity
	header field [RFC3325]:		header field [RFC3325]:
	P-Asserted-Identity: <tel: +17005554141;cpc=payphone>		P-Asserted-Identity: <tel: +17005554141;cpc=payphone>
	The "oli" URI parameter usage is given in the following example,		The "oli" URI parameter usage is given in the following example,
	which uses the SIP URI representation of telephone numbers:		which uses the SIP URI representation of telephone numbers:
	From: <sip: +1700554141;oli=29@example.com>;tag=1928301774		From: <sip: +1700554141;oli=29@example.com>;tag=1928301774
	The "oli" parameter with value 29 indicates that the device that the		The "oli" parameter with value 29 indicates that the device that the
	call is initiated from is located within a prison. An "oli" with		call is initiated from is located within a prison.
	value "prison" is equally valid.
	4. Usage		4. Usage
	The CPC and OLI are generally useful only when describing the		The CPC and OLI are generally useful only when describing the
	originator of a telephone call or the station from where a telephone		originator of a telephone call or the station from where a telephone
	call is originated. Therefore, when this parameter is used in an		call is originated. Therefore, when this parameter is used in an
	application such as SIP, it is recommended that the parameter be		application such as SIP, it is recommended that the parameter be
	applied to URIs that characterize the originator of a call (such as a		applied to URIs that characterize the originator of a call (such as a
	tel URI or SIP URI in the P-Asserted-Identity header field or the		tel URI or SIP URI in the P-Asserted-Identity header field or the
	From header field of a SIP message). Note that many Calling Party's		From header field of a SIP message). Note that many Calling Party's
	skipping to change at page 9, line 23 ¶		skipping to change at page 9, line 23 ¶
	[RFC3323] Peterson, J., "A Privacy Mechanism for the Session		[RFC3323] Peterson, J., "A Privacy Mechanism for the Session
	Initiation Protocol (SIP)", RFC 3323, November 2002.		Initiation Protocol (SIP)", RFC 3323, November 2002.
	[RFC3324] Watson, M., "Short Term Requirements for Network Asserted		[RFC3324] Watson, M., "Short Term Requirements for Network Asserted
	Identity", RFC 3324, November 2002.		Identity", RFC 3324, November 2002.
	Authors' Addresses		Authors' Addresses
	Milan Patel		Milan Patel
	Nortel		InterDigital Communications, LLC
	Maidenhead Office Park, Westacott Way
	Maidenhead, Berkshire, UK
	Email: milanpa@nortel.com		Email: Milan.Patel@interdigital.com
	Roland Jesske		Roland Jesske
	Deutsche Telekom		Deutsche Telekom
	Heinrich-Hertz-Strasse 3-7		Heinrich-Hertz-Strasse 3-7
	Darmstadt, 64307, Germany		Darmstadt, 64307, Germany
	Email: r.jesske@telekom.de		Email: r.jesske@telekom.de
	Martin Dolly		Martin Dolly
	AT&T		AT&T
End of changes. 11 change blocks.
	22 lines changed or deleted		13 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/