[Sipping-tispan] AW: AOC requirements
"Schmidt, Christian" <christian-schmidt@siemens.com> Thu, 08 September 2005 07:48 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EDH9J-00037j-Bc; Thu, 08 Sep 2005 03:48:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EDH9H-00037e-JR
for sipping-tispan@megatron.ietf.org; Thu, 08 Sep 2005 03:48:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05542
for <sipping-tispan@ietf.org>; Thu, 8 Sep 2005 03:48:41 -0400 (EDT)
Received: from david.siemens.de ([192.35.17.14])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDHCb-0003Sf-BJ
for sipping-tispan@ietf.org; Thu, 08 Sep 2005 03:52:10 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
by david.siemens.de (8.12.6/8.12.6) with ESMTP id j887meY4009070;
Thu, 8 Sep 2005 09:48:40 +0200
Received: from mhpahx0c.ww002.siemens.net (mhpahx0c.ww020.siemens.net
[139.25.165.42] (may be forged))
by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j887mcQR002333;
Thu, 8 Sep 2005 09:48:38 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by
mhpahx0c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.211);
Thu, 8 Sep 2005 09:47:01 +0200
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Sep 2005 09:47:54 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E7700583F8@MCHP7R5A.ww002.siemens.net>
Thread-Topic: AOC requirements
Thread-Index: AcWzgeOypb52NlzYSNyLZd2Apr63BAAxVIyQ
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>
X-OriginalArrivalTime: 08 Sep 2005 07:47:01.0671 (UTC)
FILETIME=[7F9FAB70:01C5B449]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Subject: [Sipping-tispan] AW: AOC requirements
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN
<sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>,
<mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>,
<mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org
Hi Miguel,
some more comments / proposals inline.
Regards,
Christian
> - AOC-3: This section gives the impression, that the changing
> cumultative charging values are not reported to the user.
I see your point. What about if the first sentence if reworded to say:
The information supplied to the user is asynchronously generated,
updated and reported to the user when new charging information is
available.
Christian: That not really hits the point. What about an extension of
the
example?
For example, when the cumultative charging value changes more then a
certain predefined value; or, as time passes by, the charging
implications might change; or a re-INVITE can request new media
streams that will impact charging.
>
> Questions:
> - Do we need a requirement for limiting the rate for this
asynchronously
> charging messages?
I don't know, perhaps someone else can comment this one. In my opinion
it would a "nice-to-have" feature.
> - Do we need a requirement that the user can stop further
transmissions?
Another good point. I don't know, but I also think it would be nice to
have.
Christian: This could be described in Non-Requirements or perhaps as
possible extensions. What do you think about this?
A rate limitation for asynchronously charging messages is not
requested.
The possibililty for a user to stop further delivery asynchronously
charging messages
during a call is not requested.
_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan
- [Sipping-tispan] AW: AOC requirements Schmidt, Christian