Internet DRAFT - draft-haluska-dispatch-charge-number-needed
draft-haluska-dispatch-charge-number-needed
DISPATCH J. Haluska
Internet-Draft Telcordia
Intended status: Informational February 16, 2010
Expires: August 20, 2010
The Need to Convey Charge Number in SIP
draft-haluska-dispatch-charge-number-needed-00
Abstract
This draft documents a need for the ability to signal a Charge Number
using SIP, and identifies one deployed though not yet standard
mechanism which addresses this need.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
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 August 20, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Haluska Expires August 20, 2010 [Page 1]
Internet-Draft Charge Number Needed February 2010
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
3. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Haluska Expires August 20, 2010 [Page 2]
Internet-Draft Charge Number Needed February 2010
1. Introduction
This draft documents a need for the ability to signal a Charge Number
using SIP, and identifies one deployed though not yet standardized
mechanism which addresses this need.
Haluska Expires August 20, 2010 [Page 3]
Internet-Draft Charge Number Needed February 2010
2. Problem Statement
In the current PSTN in North America, a Charge Number is signaled
with call originations. The Charge Number identifies the customer or
account with which the caller is associated. In many cases it is the
same as the Calling Party Number, while in others it is different -
e.g. the main number for a business which has many individual calling
numbers. This might be needed for usage collection, but it also
could influence call processing, especially when a particular type of
service applies for any caller associated with a particular charge
number.
Services currently implemented in the PSTN including Operator
Services and Directory Assistance make use of Charge Number in
processing a call. Such services are migrating to SIP based
platforms, and the need to know the Charge Number still exists. For
example, branding may be based on the value of the Charge Number.
There is currently no IETF standardized mechanism to convey the
Charge Number in SIP.
Current SIP-ISUP interworking standards do not specify a SIP mapping
for the Charge Number parameter. Thus, when interworking from ISUP
to SIP, Charge Number is carried in an encapsulated ISUP message in a
MIME body. The P-Charge-Info header, if standardized, would be
useful in this role.
For SIP originated calls, there is no currently standardized way to
carry this information. The P-Charge-Info header, if standardized,
would be useful in this role.
[I-D.draft-york-sipping-p-charge-info-07] proposes a "P-Charge-Info"
SIP header for carrying charge information for a call. It is
intended to facilitate carrying information equivalent to Charge
Number for SIP originated calls. It is also intended to support PSTN
interworking by carrying the ISUP Charge Number value.
Haluska Expires August 20, 2010 [Page 4]
Internet-Draft Charge Number Needed February 2010
3. Conclusion
Operator Services and Directory Assistance, which are migrating to
SIP based platforms, have a continuing need to convey the Charge
Number associated with a caller. There is currently no standardized
mechanism defined for conveying this information in SIP; such a
mechanism is needed in order to provide these services. The
mechanism defined in [I-D.draft-york-sipping-p-charge-info-07] fills
this need.
Haluska Expires August 20, 2010 [Page 5]
Internet-Draft Charge Number Needed February 2010
4. IANA Considerations
This memo includes no request to IANA.
Haluska Expires August 20, 2010 [Page 6]
Internet-Draft Charge Number Needed February 2010
5. Security Considerations
Disclosure of Charge Number information to unauthorized parties could
reveal information about the caller's usage patterns. It could also
allow for the potential use of the Charge Number value by others
either to interfere with billing, or to access unauthorized services.
Thus, the Charge Number should not be disclosed to unauthorized
parties, should not be accepted from unauthorized parties, and should
not be modified by unauthorized parties.
Haluska Expires August 20, 2010 [Page 7]
Internet-Draft Charge Number Needed February 2010
6. References
6.1. Normative References
6.2. Informative References
[I-D.draft-york-sipping-p-charge-info-07]
York, D., "P-Charge-Info - A Private Header (P-Header)
Extension to the Session Initiation Protocol (SIP)".
Haluska Expires August 20, 2010 [Page 8]
Internet-Draft Charge Number Needed February 2010
Appendix A. Acknowledgements
The author would like to thank Dan York, Martin Dolly, Gary Munson,
and the members of the Operator Services Technical Forum.
Haluska Expires August 20, 2010 [Page 9]
Internet-Draft Charge Number Needed February 2010
Author's Address
John Haluska
Telcordia
331 Newman Springs Road
Red Bank, NJ 07701
USA
Phone:
Email: jhaluska@telcordia.com
Haluska Expires August 20, 2010 [Page 10]
