Re: [Dime] Mirja Kühlewind's Discuss on draft-ietf-dime-drmp-05: (with DISCUSS and COMMENT)

["Mirja Kuehlewind (IETF)" <[e-mail]>]

Okay let me go for an example here and see if that can be a use case that we are talking about.

You have a system where some clients run a communication service for emergency doctors as well as for firefighters and then there are also ‚normal‘ users that run some kind of communication service.

Now you actually have an emergency: some part of the system is down and the number of request is high such that the system is overloaded.

Both the emergency doctors have would have two different priority classes, one for important message about instruction (what and where people should do something) and one for communication between the doctors/firefighters which has still higher priority than any other communication of the other people (as you assume doctors and firefighters are more responsible to not misuse this communication channel).

Now only the emergency doctors communication service was upgraded to use this extension, but the firefighter’s administrations is just too slow or they currently have not enough money because they have specialized expensive hardware and software that is not easy to change.

Is it okay in this situation that the private chat of two doctors about their last ski-holidays starves requests to access the network to send instructor message to the firefighters?

(And how do i make sure that that all other other requests actually select a lower priority than 10…? But that’s a different question…)

Mirja


> Am 11.05.2016 um 06:59 schrieb Alexey Melnikov <[e-mail]>:
> 
> Hi Mirja,
> 
> On 10 May 2016, at 17:59, Mirja Kuehlewind (IETF) <[e-mail]> wrote:
> 
>>>> I don’t think it is a good idea to assign a default priority to non-priority-defined requests at all. If you have high priority traffic that does not support this extension (yet) this traffic could be starved by lower priority traffic when assigning a middle range priority. I don’t think that is what you want to achieve.
>>> SRD> Actually, this is what we want to achieve.  It is an requirement that messages explicitly marked as high priority get treated even if it results in starving lower priority messages.  The starving of lower priority messages is not an problem, it is a requirement.
>> 
>> I think we are still talking past each other.
> 
> Most definitely :-).
> 
>> If you explicitly assign a priority, starvation might be okay. However, if you don’t have a priority explicitly signaled, the transaction might have a very high priority
> 
> So some agent in the system needs to decide that a transaction is important.
>> but you just don’t know and by assigning a random mid-range priority this important request could get starved.
> 
> Here I disagree with you, because the way to know that a transaction is important is to upgrade client to explicitly assign high priority to it. So default priority is a backward compatibility mechanism, that would work for most common cases. You seem to be suggesting that when this extension is deployed all clients need to be updated at the same time. This is not realistic.
> 
>