RFC 7944 on Diameter Routing Message Priority
rfc-editor@rfc-editor.org Fri, 05 August 2016 00:03 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A316612D7DC; Thu, 4 Aug 2016 17:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 8SMpEI0PAcoS; Thu, 4 Aug 2016 17:03:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDDD12D729; Thu, 4 Aug 2016 17:03:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F343B810E9; Thu, 4 Aug 2016 17:03:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7944 on Diameter Routing Message Priority
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160805000344.7F343B810E9@rfc-editor.org>
Date: Thu, 04 Aug 2016 17:03:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vyEbEL7qwWgO9_6Lrm-0c_a9Q9o>
Cc: drafts-update-ref@iana.org, dime@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 00:03:49 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7944
Title: Diameter Routing Message Priority
Author: S. Donovan
Status: Standards Track
Stream: IETF
Date: August 2016
Mailbox: srdonovan@usdonovans.com
Pages: 18
Characters: 41028
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dime-drmp-07.txt
URL: https://www.rfc-editor.org/info/rfc7944
DOI: http://dx.doi.org/10.17487/RFC7944
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.
This document is a product of the Diameter Maintenance and Extensions Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC