Re: [Dime] RFC 7944 on Diameter Routing Message Priority

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 05 August 2016 17:30 UTC

Return-Path: <jouni.nospam@gmail.com>
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 E436A12D16C for <dime@ietfa.amsl.com>; Fri, 5 Aug 2016 10:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zB81bGnwwvmi for <dime@ietfa.amsl.com>; Fri, 5 Aug 2016 10:30:57 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (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 41C6912D65F for <dime@ietf.org>; Fri, 5 Aug 2016 10:30:57 -0700 (PDT)
Received: by mail-pa0-x22e.google.com with SMTP id ti13so16331719pac.0 for <dime@ietf.org>; Fri, 05 Aug 2016 10:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:subject:references:to:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=PLxaxv7MQGTSjza9J7TRcBuhawQmBdIGnOMo7NV7H80=; b=bWa7XugyDHhLZu+FGaQWYH9ft8oo4Tj7ZSEjN0cEiCPWZ9fHOVBH7u4zGH1I8CRFAa 2b9NJfcZUNuffGDvbOjEFkPLYCYLCPujqWfmr6czryg9cHxYp82vttAlERtBdb0IrMBB O60cJ5o7ikCn8niaObiw8uKJxVFSFrfWql97kYa9jdQnOEHhgp6omk3gJC46IPFmEJhL g05nwvRVmCL7OIa965jc8r0lAy2i4PAjC10YznLk0d7gIh5F5Sp/LAV/iU82rfdywxdG 8Kp07Om9ilst+EO3V+ZtZ7wYp9wD+VTBpNPzOFpalTgh6dbtPkKZeeaZ2MeuHni+VG/j GoTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=PLxaxv7MQGTSjza9J7TRcBuhawQmBdIGnOMo7NV7H80=; b=hlIBrZE2/qF2WEzNURw0OwX+y4+7x64FhEBD6gyb58elUB2+LbfoJJME7xnGQ1KhnK iT1nwfMsP8vFu3rgEnVDeIb33YdEy3y9Cr3cm/f3mlKAh++rC4ByOgfBrW+DT/vcizBd tIW4OPQHC7E2eiuqXxnvsdDO+Mwc+rvjpIgEe428OMlVZjIxboJLi54lr6Wp7KR3Pi9R AQO6FF6IjEBt5F87jGb14C5fEA+G1X8DRXAKEEx6vGqyVS/Q3TtMgqBYICSrG3P1exSD 5xm0urj/Urn1mxutUHryl0EK4sNHr9MsSeR8KCX51N65BKld24zCuB8hHOxkh6hiinXe doyg==
X-Gm-Message-State: AEkoouv+517PjOMC1HjOlmYBEwc2SgKH6R16Oi5eBRFKOSJ8nlmrxn/1gk3SF4Q3GNpKaA==
X-Received: by 10.66.136.74 with SMTP id py10mr4783534pab.114.1470418256710; Fri, 05 Aug 2016 10:30:56 -0700 (PDT)
Received: from [10.16.65.74] ([216.31.219.19]) by smtp.googlemail.com with ESMTPSA id c66sm29459483pfd.24.2016.08.05.10.30.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Aug 2016 10:30:56 -0700 (PDT)
References: <20160805000344.7F343B810E9@rfc-editor.org>
To: dime@ietf.org, Steve Donovan <srdonovan@usdonovans.com>
From: Jouni Korhonen <jouni.nospam@gmail.com>
Message-ID: <cdaa51c6-0deb-7c2e-8de7-c71cf68c6d1f@gmail.com>
Date: Fri, 5 Aug 2016 10:30:51 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160805000344.7F343B810E9@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/TdJUbi3LTcxWUo7zb8gJ5pMIJDI>
Subject: Re: [Dime] RFC 7944 on Diameter Routing Message Priority
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jouni.nospam@gmail.com
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, 05 Aug 2016 17:31:00 -0000

Congrats! And big thanks to Steve driving this through to completion.

- Jouni & Lionel

8/4/2016, 5:03 PM, rfc-editor@rfc-editor.org kirjoitti:
> 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
>
>