IETF Logo Mail Archive

[Sipping] Comment on draft-narayanan-sipping-aaa-diameter-00.txt

"Cullen Jennings" <fluffy@cisco.com> Sun, 15 September 2002 21:15 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11219 for <sipping-archive@odin.ietf.org>; Sun, 15 Sep 2002 17:15:33 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8FLGpg14002 for sipping-archive@odin.ietf.org; Sun, 15 Sep 2002 17:16:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8FLGpv13999 for <sipping-web-archive@optimus.ietf.org>; Sun, 15 Sep 2002 17:16:51 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11211 for <sipping-web-archive@ietf.org>; Sun, 15 Sep 2002 17:15:03 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8FLFmv13978; Sun, 15 Sep 2002 17:15:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8FL2Bv13229 for <sipping@optimus.ietf.org>; Sun, 15 Sep 2002 17:02:11 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11059 for <sipping@ietf.org>; Sun, 15 Sep 2002 17:00:20 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8FL0jKB013597; Sun, 15 Sep 2002 14:00:45 -0700 (PDT)
Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-9.cisco.com (Mirapoint) with SMTP id AEA22762; Sun, 15 Sep 2002 14:00:47 -0700 (PDT)
From: Cullen Jennings <fluffy@cisco.com>
To: abk2001@cs.columbia.edu, schulzrinne@cs.columbia.edu, sankaran@windows.microsoft.com, sipping@ietf.org
Date: Sun, 15 Sep 2002 14:01:15 -0700
Message-ID: <MFEJKLHKCMNFOPKPHMBPCEBDCDAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Comment on draft-narayanan-sipping-aaa-diameter-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I am very happy to see some work in this area - thanks.

Given a call-id does not specify a dialog, I don't think it is a good map to
a diameter session-id. It should at least include the to and from tags.

I think a better solution would involve a network generated billing id. (ala
DCS)

Accounting-Input/Output-Octets/Packets serves no purpose I can imagine.

I think it would be good to look at the things people are currently
collecting from SIP and H.323 calls in billing system. Figure out what they
want to accomplish with this information then figure out a good way to do
that.

If you are defining some AVP, you might want to make the media ones specific
to RTP instead of SIP so they can be used by H.323/MGCP/H.248.

I'd give some thought to what you would need to bill for a call that got
transferred and what is needed for a conference call.

Hope that helps,

Cullen

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