Re: [Sipping] [Fwd: I-D Action:draft-york-sipping-p-charge-info-00.txt]
Dan York <dyork@voxeo.com> Tue, 19 February 2008 15:01 UTC
Return-Path: <sipping-bounces@ietf.org>
X-Original-To: ietfarch-sipping-archive@core3.amsl.com
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CADC528C5F4; Tue, 19 Feb 2008 07:01:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.091
X-Spam-Level:
X-Spam-Status: No, score=0.091 tagged_above=-999 required=5 tests=[AWL=-0.372, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulgu4FWvPbKb; Tue, 19 Feb 2008 07:01:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F71A28C4EA; Tue, 19 Feb 2008 07:01:03 -0800 (PST)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E39328C44F for <sipping@core3.amsl.com>; Tue, 19 Feb 2008 07:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wswcHdWCASnO for <sipping@core3.amsl.com>; Tue, 19 Feb 2008 07:01:01 -0800 (PST)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with ESMTP id 6DDFF28C4EA for <sipping@ietf.org>; Tue, 19 Feb 2008 07:01:00 -0800 (PST)
Received: from [75.68.245.43] (account dyork HELO [172.20.12.144]) by voxeo.com (CommuniGate Pro SMTP 5.1.14) with ESMTPSA id 28061406; Tue, 19 Feb 2008 15:00:55 +0000
In-Reply-To: <47BACC50.5010608@nsn.com>
References: <47BA8443.30309@gmx.net> <47BACC50.5010608@nsn.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <87442CDA-5006-48EA-A27E-FB2ADCFC195A@voxeo.com>
From: Dan York <dyork@voxeo.com>
Date: Tue, 19 Feb 2008 10:00:52 -0500
To: Miguel Garcia <Miguel.Garcia@nsn.com>
X-Mailer: Apple Mail (2.753)
Cc: SIPPING LIST <sipping@ietf.org>
Subject: Re: [Sipping] [Fwd: I-D Action:draft-york-sipping-p-charge-info-00.txt]
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1945252653=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
Miguel, Yes, as soon as I saw that we were considering using P-Charge-Info I went looking around to see if it had been registered with IANA (it wasn't) and looking at what *was* registered with IANA. I did see RFC 3455 (and indeed reference it in my draft) and looked at P- Charging-Vector. However, P-Charging-Vector is more complicated than we need. Undoubtedly P-Charging-Vector works well within the larger context of 3GPP, but all we want to do is provide a single billing identifier to the upstream proxies. What I am really aiming to do with this draft is register an already existing practice of using the P-Charge-Info P-Header with IANA, as is required under RFC 3427 (section 4.1). Sonus Networks is using this in their switches and has mentioned it to carriers using their gear. One of those carriers, who we work with, suggested it as a way to solve our billing issues. We're now using it and it's working fine. There are now other carriers with whom we are seeking to solve the same issue and we will probably wind up using the same solution. We can obviously just continue to do this in the private SIP communication between ourselves and the carriers without pursuing IANA registration, but, being a "standards guy" I would like to "do the right thing" per RFC 3427 and document/register current usage. I would also, frankly, like a document out there to which we can point when we talk to yet another carrier saying "here's one way of dealing with billing issues, is that applicable to your network?" Hannes, thanks for the links. Again, though, all we are doing is passing along a simple billing identifier. The -01 draft that I'll get in for Monday will include that information. (And someone from Sonus Networks has also agreed to co- author.) Regards, Dan On Feb 19, 2008, at 7:32 AM, Miguel Garcia wrote: > We also did some work in RFC 3455 in the format of the P-Charging- > Vector header field. > > /Miguel > > Hannes Tschofenig wrote: >> Hi Dan, >> are you aware of the work done on advice of charge by TISPAN/3GPP? >> http://www.3gpp.org/ftp/Specs/html-info/24447.htm >> Have you looked at the work some of us did with >> http://merlot.tools.ietf.org/html/draft-jennings-sipping-pay-06 >> It also includes an charge info XML schema. >> Ciao >> Hannes >> -------- Original Message -------- >> Subject: I-D Action:draft-york-sipping-p-charge-info-00.txt >> Date: Mon, 18 Feb 2008 14:00:02 -0800 (PST) >> From: Internet-Drafts@ietf.org >> Reply-To: internet-drafts@ietf.org >> To: i-d-announce@ietf.org >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> Title : P-Charge-Info - A Private Header (P-Header) >> Extension to the Session Initiation Protocol (SIP) >> Author(s) : D. York >> Filename : draft-york-sipping-p-charge-info-00.txt >> Pages : 6 >> Date : 2008-02-18 >> This document describes 'P-Charge-Info', a private Session Initiation >> Protocol (SIP) header (P-header) used by a number of equipment >> vendors and carriers to convey simple billing information. >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-york-sipping-p-charge- >> info-00.txt >> To remove yourself from the I-D Announcement list, send a message to >> i-d-announce-request@ietf.org with the word unsubscribe in the >> body of the message. >> You can also visit https://www1.ietf.org/mailman/listinfo/I-D- >> announce >> to change your subscription settings. >> Internet-Drafts are also available by anonymous FTP. Login with >> the username "anonymous" and a password of your e-mail address. >> After logging in, type "cd internet-drafts" and then >> "get draft-york-sipping-p-charge-info-00.txt". >> A list of Internet-Drafts directories can be found in >> http://www.ietf.org/shadow.html >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> Internet-Drafts can also be obtained by e-mail. >> Send a message to: >> mailserv@ietf.org. >> In the body type: >> "FILE /internet-drafts/draft-york-sipping-p-charge-info-00.txt". >> NOTE: The mail server at ietf.org can return the document in >> MIME-encoded form by using the "mpack" utility. To use this >> feature, insert the command "ENCODING mime" before the "FILE" >> command. To decode the response(s), you will need "munpack" or >> a MIME-compliant mail reader. Different MIME-compliant mail readers >> exhibit different behavior, especially when dealing with >> "multipart" MIME messages (i.e. documents which have been split >> up into multiple messages), so check your local documentation on >> how to manipulate these messages. >> Below is the data which will enable a MIME compliant mail reader >> implementation to automatically retrieve the ASCII version of the >> Internet-Draft. >> _______________________________________________ >> Sipping mailing list http://www.ietf.org/mailman/listinfo/sipping >> This list is for NEW development of the application of SIP >> Use sip-implementors@cs.columbia.edu for questions on current sip >> Use sip@ietf.org for new developments of core SIP > > -- > Miguel A. Garcia tel:+358-50-4804586 > Nokia Siemens Networks Espoo, Finland > -- Dan York, CISSP, Director of Emerging Communication Technology Office of the CTO Voxeo Corporation dyork@voxeo.com Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com Bring your web applications to the phone. Find out how at http://evolution.voxeo.com
_______________________________________________ Sipping mailing list http://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] [Fwd: I-D Action:draft-york-sipping-p-c… Hannes Tschofenig
- Re: [Sipping] [Fwd: I-D Action:draft-york-sipping… Miguel Garcia
- Re: [Sipping] [Fwd: I-D Action:draft-york-sipping… Dan York
- Re: [Sipping] [Fwd: I-D Action:draft-york-sipping… Miguel Garcia
- Re: [Sipping] [Fwd: I-D Action:draft-york-sipping… Dan York
- [Sipping] Draft -01 now posted - Re: [Fwd: I-D Ac… Dan York
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Christer Holmberg
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Dan York
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Christer Holmberg
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Miguel Garcia
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Dan York
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Dan York
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Christer Holmberg
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Miguel Garcia
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Miguel Garcia
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Paul Kyzivat
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Paul Kyzivat
- Re: [Sipping] Draft -01 now posted - Re: [Fwd:I-D… hannes.tschofenig
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… DRAGE, Keith (Keith)
- Re: [Sipping] Draft -01 now posted - Re: [Fwd:I-D… DRAGE, Keith (Keith)
- Re: [Sipping] Draft -01 now posted - Re: [Fwd:I-D… Asveren, Tolga
- Re: [Sipping] Draft -01 now posted - Re: [Fwd: I-… Dan York
- [Sipping] Draft -02 now posted - [Fwd: I-DAction:… Dan York