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

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 11 May 2016 11:02 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6849512D66A for <dime@ietfa.amsl.com>; Wed, 11 May 2016 04:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=iGyuVGs/; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=SkcZGPi9
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ADdlYCM7vrHA for <dime@ietfa.amsl.com>; Wed, 11 May 2016 04:02:06 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B36C012D9A7 for <dime@ietf.org>; Wed, 11 May 2016 04:01:40 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A148B20BA5 for <dime@ietf.org>; Wed, 11 May 2016 06:54:18 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 11 May 2016 06:54:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=+ByskY2yFz3qGlNgJcyhdHd9FV0=; b=iGyuVG s/sQvRU31TfexWV/O2ynlvN58tDrr8wXpMcfRSiPGDroOJ6zzuudUDdemUvyybWS JGMiUPHkTchcJt7DzOFJRqO/Q0IDsRryYT0BmUMn8DYJS7lo3j8pqQQgk4GpJjNZ OhxbAlHpo46d4G5MSav23TMSsTU7uNAF1lyCc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=+ByskY2yFz3qGlN gJcyhdHd9FV0=; b=SkcZGPi9dwhhtKNpzZ9tf6uHV90FTlnTzUN9BkBJ9I62oQb F/Br+CHAUHAoB/azIZW7qqdr8AlSUwcedEA0qoa3ej5eFm6a/Gx31HQxAAAn3Riu UcpAmdgOge+GhUVzT2XDg0rF3ba4JdU+RCrgauYy9OsmptLqi24wcYTrU0gw=
X-Sasl-enc: H4umvkd/uPQtV4tk2q4PIOdzI2oMhTpZFnCdvxXO8XsG 1462964058
Received: from [10.0.0.58] (c-66-30-10-217.hsd1.ma.comcast.net [66.30.10.217]) by mail.messagingengine.com (Postfix) with ESMTPA id 4F81368021F; Wed, 11 May 2016 06:54:18 -0400 (EDT)
Content-Type: text/plain; charset=windows-1251
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <74E6ECC0-283D-4A14-AF19-66E76EBAA743@kuehlewind.net>
Date: Wed, 11 May 2016 06:59:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B348BA8A-5A92-4E44-8ECA-76E4F3E03426@fastmail.fm>
References: <20160504111323.8242.20592.idtracker@ietfa.amsl.com> <A8821F45-B9BA-4ACF-8EBF-01B64C100359@fastmail.fm> <B4F433FB-B2A2-4EDA-8ECF-5812BCB7517A@kuehlewind.net> <1462363396.2794286.597809745.0662E7A7@webmail.messagingengine.com> <033661D5-7963-4726-81C0-854E25C659D3@kuehlewind.net> <e6d1ab6472f14ec3b4b6b024563150ff@CSRRDU1EXM025.corp.csra.com> <F0C35A63-ADCA-4502-AC3B-C2DF5FA6EDFD@kuehlewind.net> <1462451530.3147432.598960497.7062C294@webmail.messagingengine.com> <4B86AEB1-415C-4AE3-82F7-368C38B19560@kuehlewind.net> <57324CE8.6040109@usdonovans.com> <74E6ECC0-283D-4A14-AF19-66E76EBAA743@kuehlewind.net>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/ML8pG5jiP3m8Vsx9HiP--y3RZ3M>
Cc: draft-ietf-dime-drmp@ietf.org, dime-chairs@ietf.org, dime@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [Dime] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-d?= =?utf-8?q?ime-drmp-05=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 11:02:07 -0000

Hi Mirja,

On 10 May 2016, at 17:59, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> 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.