[Dime] Proposed resolution to issue 75 (terminology)
Steve Donovan <srdonovan@usdonovans.com> Tue, 21 October 2014 09:35 UTC
Return-Path: <srdonovan@usdonovans.com>
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 045E41A19E3 for <dime@ietfa.amsl.com>; Tue, 21 Oct 2014 02:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.59
X-Spam-Level: *
X-Spam-Status: No, score=1.59 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779, T_HTML_ATTACH=0.01] autolearn=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 oOy0-j0SHHPB for <dime@ietfa.amsl.com>; Tue, 21 Oct 2014 02:35:51 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [74.124.197.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A63AE1A1A0A for <dime@ietf.org>; Tue, 21 Oct 2014 02:33:55 -0700 (PDT)
Received: from 187.31.0.109.rev.sfr.net ([109.0.31.187]:55296 helo=b8e856229362.netpoint.com) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1XgVpC-0002YQ-2S for dime@ietf.org; Tue, 21 Oct 2014 02:33:55 -0700
Message-ID: <54462880.8020009@usdonovans.com>
Date: Tue, 21 Oct 2014 11:33:52 +0200
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "dime@ietf.org" <dime@ietf.org>
Content-Type: multipart/mixed; boundary="------------070607050000000908020206"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srd+usdonovans.com/only user confirmed/virtual account not confirmed
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/D2ORrA3ulnP3dvLhLpI1cDARleY
X-Mailman-Approved-At: Tue, 21 Oct 2014 06:02:50 -0700
Subject: [Dime] Proposed resolution to issue 75 (terminology)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 09:35:55 -0000
I have updated the document with the proposals made in issue 75. I also added definitions for host-routed and realm-routed requests. The updated text is below. I will wait to close the issue until tomorrow to give time for comments. I have attached the diff file. Regards, Steve ---- Abatement Reaction to receipt of an overload report resulting in a reduction in traffic sent to the reporting node. Abatement actions include diversion and throttling. Abatement Algorithm An algorithm requested by reporting nodes and used by reacting nodes to reduce the amount of traffic sent during an occurrence of overload control. Diversion Abatement of traffic sent to a reporting node by a reacting node in response to receipt of an overload report. The abatement is achieved by diverting traffic from the reporting node to another Diameter node that is able to process the request. Host-Routed Request The set of requests that a reacting node knows will be served by a particular host, either due to the presence of a Destination-Host AVP, or by some other local knowledge on the part of the reacting node. Overload Control State (OCS) State describing an occurrence of overload control maintained by reporting and reacting nodes. Overload Report (OLR) A set of AVPs sent by a reporting node indicating the start or continuation of an occurrence of overload control. Reacting Node A Diameter node that consumes and acts upon a report. Realm-Routed Request The set of requests that a reacting node does not know the host that will service the request. Reporting Node A Diameter node that generates an overload report. (This may or may not be the overloaded node.) Throttling Throttling is the reduction of the number of requests sent to an entity. Throttling can include a client dropping requests, or an agent rejecting requests with appropriate error responses. In extreme cases servers can also throttle requests when requested reductions in traffic does not sufficiently address the overload scenario.
- [Dime] Proposed resolution to issue 75 (terminolo… Steve Donovan