[Dime] [dime] #91 (drmp): Handling of requests without Priority indication
"dime issue tracker" <trac+dime@trac.tools.ietf.org> Fri, 11 September 2015 15:41 UTC
Return-Path: <trac+dime@trac.tools.ietf.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 327C71B4666 for <dime@ietfa.amsl.com>; Fri, 11 Sep 2015 08:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 NYeynEH-ksnG for <dime@ietfa.amsl.com>; Fri, 11 Sep 2015 08:41:43 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83F431B47C8 for <dime@ietf.org>; Fri, 11 Sep 2015 08:41:43 -0700 (PDT)
Received: from localhost ([::1]:37939 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+dime@trac.tools.ietf.org>) id 1ZaQSM-0006B9-LY; Fri, 11 Sep 2015 08:41:42 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: dime issue tracker <trac+dime@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ietf-dime-drmp@tools.ietf.org, lionel.morand@orange.com
X-Trac-Project: dime
Date: Fri, 11 Sep 2015 15:41:42 -0000
X-URL: http://tools.ietf.org/wg/dime/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/91
Message-ID: <066.5cd36866b0450471e4d1318bdc01e524@trac.tools.ietf.org>
X-Trac-Ticket-ID: 91
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-dime-drmp@tools.ietf.org, lionel.morand@orange.com, dime@ietf.org
X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To:
Resent-Message-Id: <20150911154143.83F431B47C8@ietfa.amsl.com>
Resent-Date: Fri, 11 Sep 2015 08:41:43 -0700
Resent-From: trac+dime@trac.tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/rT7TifrwFD1TQ6xdgjHFuPH5sDU>
Cc: dime@ietf.org
Subject: [Dime] [dime] #91 (drmp): Handling of requests without Priority indication
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: dime@ietf.org
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: Fri, 11 Sep 2015 15:41:45 -0000
#91: Handling of requests without Priority indication In the current version, we have the following text: When there is a mix of transactions specifying priority in request messages and transactions that do not have the priority specified, transactions that do not have a specified priority SHOULD be treated as having the PRIORITY_0 priority. With PRIORITY_0 being the highest priority (PRIORITY_4 being the lowest priority). If I'm correct, this implies that request with no priority info at all would be handled with the highest priority. I think this is not correct. Current Diameter implementations make no use of priority info and using this mechanism should be a way to explicitly prioritize requests with priority indication compared to request without priority info. Otherwise, the priority indication would be only used to somehow enable the de-prioritization of some requests whereas all the other ones with no priority indication will have de facto the highest priority. This is more relevant from an agent point of view, in an early phase of deployment of this new priority mechanism, with few clients setting explicitly the priority in the requests and the rest of the clients not supporting the new feature and therefore no adding the priority info in the requests. Keeping the idea of 5-value priority indication, the value PRIORITY_0 should therefore be the lowest priority level or, if the current order is kept, request without priority indication should be handled as having PRIORITY_4. Another approach, which would enable explicit upgrade or downgrade of request priority handling, would be to define a range of e.g. 10 values for priority (e.g. 0 - 9) and to handle requests without priority indication as having the an intermediary value, e.g. value 4. It would mean that using the priority indication in the request, it will be possible to explicitly indicate if the current request should be handle with a higher or lower priority than existing requests without priority indication. It could be a way to indicate that a given request can be handled with a lower priority than all the other requests. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-dime- lionel.morand@orange.com | drmp@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: drmp | Version: Severity: Active WG Document | Keywords: -------------------------------------+------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/91> dime <http://tools.ietf.org/wg/dime/>
- [Dime] [dime] #91 (drmp): Handling of requests wi… dime issue tracker