P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)
RFC 8496
| Document | Type |
RFC - Informational
(October 2018; No errata)
Was draft-york-p-charge-info (individual in art area)
|
|
|---|---|---|---|
| Last updated | 2018-10-31 | ||
| Replaces | draft-york-dispatch-p-charge-info | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Jean Mahoney | ||
| Shepherd write-up | Show (last changed 2018-04-23) | ||
| IESG | IESG state | RFC 8496 (Informational) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) D. York
Request for Comments: 8496 Individual
Category: Informational T. Asveren
ISSN: 2070-1721 Ribbon Communications
October 2018
P-Charge-Info: A Private Header Field (P-Header) Extension to the
Session Initiation Protocol (SIP)
Abstract
This text documents the current usage of P-Charge-Info, an existing
Session Initiation Protocol (SIP) private header field (P-Header)
used to convey billing information about the party to be charged.
This P-Header is currently used in production by several equipment
vendors and carriers and has been in use since at least 2007. This
document details the registration of this header field with IANA.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8496.
York & Asveren Informational [Page 1]
RFC 8496 P-Charge-Info October 2018
Copyright Notice
Copyright (c) 2018 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
(https://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
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 Simplified BSD License.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Purpose of This Document . . . . . . . . . . . . . . . . . . 4
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. The P-Charge-Info Header . . . . . . . . . . . . . . . . . . 5
5.1. Applicability Statement for the P-Charge-Info Header
Field . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Usage of the P-Charge-Info Header Field . . . . . . . . . 5
5.2.1. Procedures at the UA . . . . . . . . . . . . . . . . 5
5.2.2. Procedures at the Proxy . . . . . . . . . . . . . . . 6
5.3. Use-Case Example . . . . . . . . . . . . . . . . . . . . 6
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. Header Field . . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8.1. Trust Relationship . . . . . . . . . . . . . . . . . . . 7
8.2. Untrusted Peers . . . . . . . . . . . . . . . . . . . . . 8
8.2.1. Ingress from Untrusted Peers . . . . . . . . . . . . 8
8.2.2. Egress to Untrusted Peers . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Alternatives . . . . . . . . . . . . . . . . . . . . 10
A.1. P-Charging-Vector . . . . . . . . . . . . . . . . . . . . 10
A.2. P-DCS-Billing-Info . . . . . . . . . . . . . . . . . . . 10
A.3. P-Asserted-Identity . . . . . . . . . . . . . . . . . . . 11
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
York & Asveren Informational [Page 2]
RFC 8496 P-Charge-Info October 2018
1. Overview
In certain network configurations, several network entities have
found it useful to decouple the identity of the caller (what is
normally thought of as "Caller ID") from the identity/number used for
billing purposes. This document records the current usage of
P-Charge-Info, a private SIP header field, to provide simple billing
Show full document text