RFC 8496 on P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Wed, 31 October 2018 21:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43E8E130DF5 for <ietf-announce@ietfa.amsl.com>; Wed, 31 Oct 2018 14:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cnHtEKlT_AfR for <ietf-announce@ietfa.amsl.com>; Wed, 31 Oct 2018 14:14:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E78B130DFA for <ietf-announce@ietf.org>; Wed, 31 Oct 2018 14:14:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7C8AEB805B1; Wed, 31 Oct 2018 14:14:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8496 on P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181031211447.7C8AEB805B1@rfc-editor.org>
Date: Wed, 31 Oct 2018 14:14:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Wf3jT3n2Jnn26LMktdLdjGDdw-Y>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2018 21:15:02 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8496
Title: P-Charge-Info: A Private Header Field (P-Header)
Extension to the Session Initiation Protocol (SIP)
Author: D. York,
T. Asveren
Status: Informational
Stream: IETF
Date: October 2018
Mailbox: dyork@lodestar2.com,
tasveren@rbbn.com
Pages: 11
Characters: 24002
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-york-p-charge-info-08.txt
URL: https://www.rfc-editor.org/info/rfc8496
DOI: 10.17487/RFC8496
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC