P-Charge-Info - A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)
draft-york-p-charge-info-08

Document Type Active Internet-Draft (individual in art area)
Last updated 2018-09-18 (latest revision 2018-06-30)
Replaces draft-york-dispatch-p-charge-info
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Jean Mahoney
Shepherd write-up Show (last changed 2018-04-23)
IESG IESG state RFC Ed Queue
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
RFC Editor RFC Editor state EDIT
Internet Engineering Task Force                                  D. York
Internet-Draft                                                Individual
Intended status: Informational                                T. Asveren
Expires: January 1, 2019                           Ribbon Communications
                                                           June 30, 2018

   P-Charge-Info - A Private Header Field (P-Header) Extension to the
                   Session Initiation Protocol (SIP)
                      draft-york-p-charge-info-08

Abstract

   This text documents the current usage of P-Charge-Info, an existing
   private Session Initiation Protocol (SIP) 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 usage since at least 2007.  This
   document is submitted to request the registration of this header
   field with the Internet Assigned Numbers Authority (IANA).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on January 1, 2019.

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
   (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

York & Asveren           Expires January 1, 2019                [Page 1]
Internet-Draft  P-Charge-Info, a SIP Private Header Field      June 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Purpose of this Document  . . . . . . . . . . . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  The P-Charge-Info Header  . . . . . . . . . . . . . . . . . .   4
     5.1.  Applicability Statement for the P-Charge-Info header
           field . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Usage of the P-Charge-Info header field . . . . . . . . .   4
       5.2.1.  Procedures at the UA  . . . . . . . . . . . . . . . .   5
       5.2.2.  Procedures at the Proxy . . . . . . . . . . . . . . .   5
     5.3.  Example of Usage  . . . . . . . . . . . . . . . . . . . .   6
   6.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Header Field  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     8.1.  Trust Relationship  . . . . . . . . . . . . . . . . . . .   7
     8.2.  Untrusted Peers . . . . . . . . . . . . . . . . . . . . .   7
       8.2.1.  Ingress from        Untrusted Peers . . . . . . . . .   7
       8.2.2.  Egress to        Untrusted Peers  . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  Alternatives . . . . . . . . . . . . . . . . . . . .   9
     A.1.  P-Charging-Vector . . . . . . . . . . . . . . . . . . . .   9
     A.2.  P-DCS-Billing-Info  . . . . . . . . . . . . . . . . . . .  10
     A.3.  P-Asserted-Identity . . . . . . . . . . . . . . . . . . .  10
   Appendix B.  Changes  . . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

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-
Show full document text