Re: [Dime] issue #56 proposed conclusion

Ulrich,

Please see inline.

Steve

>          Reporting nodes create an OCS identified by OCS-Id = (app-id,Alg) when receiving a
>
>          request of application app-id containing an OC-Supported-Features AVP
>
>          indicating support of the Abatement Algorithm Alg (which the reporting
>
>          node selects) while being overloaded, unless such OCS already exists.
>
> SRD> I would think the reporting node would create the OCS when it 
> determines it needs a reduction, independent when it receives requests 
> from various reacting nodes.
> <Ulrich> when not receiving requests, there is no need for reduction; 
> the need of reduction is determined when a request is received.
>
> Furthermore: If the reporting node determines that it needs a 
> reduction independently from a received request, which Algorithm would 
> it select? </Ulrich>
>
SRD2> You are correct that the algorithm can't be selected until the 
request arrives.  My point was that there would be state indicating the 
reporting node is overloaded already in place.
>
>   
>   
>      Reporting nodes delete an OCS when it expires.
>
> SRD> Or when it explicitly sends an OLR with validity duration of zero.
>
> <Ulrich> no. Let me give an example:
>
> Server S has an OCS identified by the pair (Application x, Loss) with 
> the content: Sequence number =5, duration= 30 sec/expiry time= 
> 9:45:59, percentage =10%.
>
> At 9:45:30 Client C1 sends an application x request to S and gets back 
> an OLR indicating 10% for 30 sec.
>
> At 9.45:57 Client C2 send an application x request to S and gets back 
> an OLR indicating 10% for 30sec.
>
> At 9:45:58 S decides that it is no longer overloaded. It therefore 
> updates the OCS to contain: sequence number=6, duration = 0sec/expiry 
> time= 9:46:30, percentage =0%.
>
> At 9:45:59 C1 sends an application x request to S and gets back the 
> explicit OLR with validity duration of zero. S must not delet the OCS 
> at this time.
>
> At 9:46:01 C2 sends an application x request to S and (because the OCS 
> was not deleted in the previous step) gets back the explicit OLR with 
> validity duration of zero. If the OCS was deleted in the previous step 
> C2 would continue throttling until 9:46:27.</Ulrich>
>
SRD> This is a good description of the need to keep the state in the 
server until it times out.  Thanks.
>
>
>
>   
>   
>      Reporting nodes update the OCS identified by OCS-Id = (app-id,Alg) when they detect the
>      need to modify the requested amount of application app-id traffic reduction.
>   
> Ulrich
>   
>   
> _______________________________________________
> DiME mailing list
> DiME@ietf.org  <mailto:DiME@ietf.org>
> https://www.ietf.org/mailman/listinfo/dime
>   
>