[Dime] Mirja Kühlewind's No Objection on draft-ietf-dime-drmp-05: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Wed, 11 May 2016 17:34 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: dime@ietf.org
Delivered-To: dime@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 42BFD12D0F7; Wed, 11 May 2016 10:34:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160511173425.15223.72665.idtracker@ietfa.amsl.com>
Date: Wed, 11 May 2016 10:34:25 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/6XxW_0dC1YtzA7zrDuzF8SIEoYI>
Cc: draft-ietf-dime-drmp@ietf.org, dime-chairs@ietf.org, dime@ietf.org
Subject: [Dime] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-dime-drmp-05=3A_=28with_COMMENT=29?=
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
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 17:34:25 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-dime-drmp-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dime-drmp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I still think this part needs further clarification mostly regarding
applicability and maybe a warning as it could lead to starvation of
requests that do not define a priority, e.g. because there are not
supporting it (yet) while effectively having a higher priortiy than the
requests that they get starved by:
"When using DRMP priority information, Diameter nodes MUST use the
   default priority for transactions that do not have priority specified
   in a DRMP AVP."