IETF Logo Mail Archive

Re: [Sipping] Next draft (-03) of P-Charge-Info now out

Sumit Garg <sgarg@cedarpointcom.com> Fri, 16 May 2008 14:51 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCFD03A6AF2; Fri, 16 May 2008 07:51:41 -0700 (PDT)
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 BE9893A67A1 for <sipping@core3.amsl.com>; Fri, 16 May 2008 07:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Du3ni5+8J-8h for <sipping@core3.amsl.com>; Fri, 16 May 2008 07:51:38 -0700 (PDT)
Received: from web65614.mail.ac4.yahoo.com (web65614.mail.ac4.yahoo.com [76.13.9.82]) by core3.amsl.com (Postfix) with SMTP id 2F6BE3A6A66 for <sipping@ietf.org>; Fri, 16 May 2008 07:51:38 -0700 (PDT)
Received: (qmail 86696 invoked by uid 60001); 16 May 2008 14:51:29 -0000
X-YMail-OSG: 6fvNbKYVM1mfz8mWl2w0ZfMgLAqgVpvLZhacjbofohNzYKBrw7Tbp9SvBIWICTItHi6qYceQe8cyJKR87dbw6YpgnLT4CwkUQhRv
Received: from [67.151.79.70] by web65614.mail.ac4.yahoo.com via HTTP; Fri, 16 May 2008 07:51:28 PDT
X-RocketYMMF: emailsumitgarg
Date: Fri, 16 May 2008 07:51:28 -0700
From: Sumit Garg <sgarg@cedarpointcom.com>
To: sipping@ietf.org
MIME-Version: 1.0
Message-ID: <63646.86271.qm@web65614.mail.ac4.yahoo.com>
Subject: Re: [Sipping] Next draft (-03) of P-Charge-Info now out
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: sgarg@cedarpointcom.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

How does this Header compare with P-DCS-Billing-Info
defined in RFC3603 and standard in PacketCable
Standards. The latest update to that RFC
draft-andreasen-sipping-rfc3603bis-05 also now support
specifying jip (Jurisdiction Info parameter) within
the same Header.

Without the support of JIP, P-Charge-Info would not
work properly for porting scenarios as the wrong
RateCenter would end-up getting used by a Billing
service for the examples mentioned in the draft.

I understand that that header also required a
unique-ID...but that should not be the reason to have
2 standards.

-Sumit



      
_______________________________________________
Sipping mailing list  https://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

v2.23.0 | Report a Bug | By Email