[Dime] Protocol Action: 'Diameter Routing Message Priority' to Proposed Standard (draft-ietf-dime-drmp-07.txt)
The IESG <firstname.lastname@example.org> Tue, 05 July 2016 19:20 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CC212D532; Tue, 5 Jul 2016 12:20:28 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
From: The IESG <email@example.com>
To: IETF-Announce <firstname.lastname@example.org>
Date: Tue, 05 Jul 2016 12:20:28 -0700
Cc: email@example.com, firstname.lastname@example.org, email@example.com, The IESG <firstname.lastname@example.org>, email@example.com
Subject: [Dime] Protocol Action: 'Diameter Routing Message Priority' to Proposed Standard (draft-ietf-dime-drmp-07.txt)
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 19:20:28 -0000
The IESG has approved the following document: - 'Diameter Routing Message Priority' (draft-ietf-dime-drmp-07.txt) as Proposed Standard This document is the product of the Diameter Maintenance and Extensions Working Group. The IESG contact persons are Stephen Farrell, Benoit Claise and Joel Jaeggli. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-drmp/ Technical Summary When making routing and resource allocation decisions, Diameter nodes currently have no generic mechanism to determine the relative priority of Diameter messages. This document addresses this by defining a mechanism to allow Diameter endpoints to indicate the relative priority of Diameter transactions. With this information Diameter nodes can factor that priority into routing, resource allocation and overload abatement decisions. Working Group Summary The document received a large support for adoption when initiated and it has been reviewed multiple times, with detailed comments and corrections. The version -03 addresses the last comments received after the WGLC process. There is a strong WG consensus on the content of this document, with a broad range of people, including key experts. Document Quality The proposed solution has not been implemented yet, as vendors are waiting for IANA AVP code value assignment before implementing. However, no issues are expected with implementation. Moreover, the solution defined in this document have been already introduced in standard specifications defined by 3GPP. It is therefore understood that the vendors implementing 3GPP specifications will implement this mechanism. Personnel The document shepherd is Lionel Morand. Stephen Farrell is being AD-like for this.