RE: [AAA-WG]: DCCA Draft 05: Tariff-Time-Change

[<[e-mail]>]

Hi,
 
I think the Peter answer indicated that this is not a problem.
 
Indeed, who decide the billing model is the server in the home network and not the client in the
visited network, this was already discussed in the mailing list a while ago.
If the server sent a tariff-time-change in the answer is because it requires this model, perhaps 
it has also contractual implications with the user if the model is broken, and therefore it is correct for 
the client to reject the answer if it doesn't support the tariff-time-change mechanism.
 
It is up to the server to eventually track that the origin-host X rejected an answer with Tariff-Time-Change AVP
and at the next attempt change the billing model if possible. However, typically an agreement between
DCC-Client and server exist and the server can control whether to send the tariff-time-change or not.
 
Marco
 

-----Original Message-----
From: ext Ahmad Muhanna [mailto:[e-mail]]
Sent: 08 June, 2004 15:51
To: 'Peter Zackrisson (KA/EAB)'; [e-mail]
Cc: '[e-mail]'; '[e-mail]'; Koskinen Juha-Pekka (Nokia-NET/Tampere); Stura Marco (Nokia-NET/Helsinki); Loughney John (Nokia-NRC/Helsinki); Ahmad Muhanna
Subject: RE: [AAA-WG]: DCCA Draft 05: Tariff-Time-Change


So far the only comment received is from Peter. 
Does this mean that every one agrees that this is a problem that needs to be fixed.
If so, what do you think the solution should be?

Regards, 
Ahmad 

-----Original Message-----
From: Muhanna, Ahmad [RICH2:2Q30:EXCH] 
Sent: Friday, June 04, 2004 8:59 AM
To: 'Peter Zackrisson (KA/EAB)'; [e-mail]
Subject: RE: [AAA-WG]: DCCA Draft 05: Tariff-Time-Change


Thanks Peter,
 
Is it fair to say that your argument is based on the assumption that all DCC Servers are always aware of all DCC clients capabilities with respect to Tariff-Time-Change mechanism support.
 
Thanks again.

Regards, 
Ahmad 

-----Original Message-----
From: Peter Zackrisson (KA/EAB) [mailto:[e-mail]] 
Sent: Friday, June 04, 2004 8:48 AM
To: Muhanna, Ahmad [RICH2:2Q30:EXCH]; [e-mail]
Subject: RE: [AAA-WG]: DCCA Draft 05: Tariff-Time-Change


I think the DCC specification is correct regarding the tariff change mechanism.
 
If a DCC client does not support the tariff change mechanism the DCC server must use a charging model towards that client that is not based on time,
which means that Tariff-Time-Change is not to be sent.
This means that it is up to the DCC server to be able to control if Tariff-Time-Change should be sent or not.
If you have a charging model saying that the price for e.g. volume will be different between 8 and 18 o'clock the clients will have to support
tariff change mechanism.
It is a very bad idea if some clients are allowed to break the charging model (instead the charging model should be changed).
 
/ Peter

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]On Behalf Of Ahmad Muhanna
Sent: den 4 juni 2004 15:15
To: [e-mail]
Cc: Harri Hakala (JO/LMF); Leena Mattila (TU/LMF); '[e-mail]'; '[e-mail]'; '[e-mail]'
Subject: [AAA-WG]: DCCA Draft 05: Tariff-Time-Change



Hi all, 

According to the DCC draft under section 5.1, support of Tariff-Time-Change is optional by the DCC client and Server. 

" 
   The Diameter credit-control server and client MAY optionally support 
   a tariff change mechanism. The Diameter credit-control server may 
   include a Tariff-Time-Change AVP in the answer message. 
" 

On the other hand and under the same section, it mandates the DCC client which does not support this functionality to terminate the DCC session if it receives a CCA with Tariff-Time-Change AVP included.

Under section 5.1, it reads: 
" 
   If a client does not support the tariff change mechanism, and it 
   receives a CCA message carrying the Tariff-Time-Change AVP, it MUST 
   terminate the credit control session, giving a reason of 
   DIAMETER_BAD_ANSWER in the Termination-Cause AVP. 
" 

The problem I see is the following: 
There is a very good possibility that a DCC server supports Tariff-Time-Change and DCC Client does not. 
This may cause a denial of service for an end-user which home Diameter CC server supports Tariff-Time-Change mechanism while it is at an access where DCC client does not.

Am I making sense here? 
Your thoughts please. 


Thanks, 
Ahmad