Re: [Dime] [dime] #52: Throttling not needed to be based on previous history
Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> Wed, 12 February 2014 08:56 UTC
Return-Path: <maria.cruz.bartolome@ericsson.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 3DC3B1A08C1 for <dime@ietfa.amsl.com>; Wed, 12 Feb 2014 00:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 o-kl613x4PJE for <dime@ietfa.amsl.com>; Wed, 12 Feb 2014 00:56:25 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB3E1A08C0 for <dime@ietf.org>; Wed, 12 Feb 2014 00:56:24 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-6f-52fb3736986d
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id BA.3E.23809.6373BF25; Wed, 12 Feb 2014 09:56:23 +0100 (CET)
Received: from ESESSMB101.ericsson.se ([169.254.1.172]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0387.000; Wed, 12 Feb 2014 09:56:22 +0100
From: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [dime] #52: Throttling not needed to be based on previous history
Thread-Index: AQHPJ8pHWh6U3x1NsUGCEW0ghWu/OpqxT/wg
Date: Wed, 12 Feb 2014 08:56:22 +0000
Message-ID: <087A34937E64E74E848732CFF8354B92097740BB@ESESSMB101.ericsson.se>
References: <075.fdee2d1220a4dd797b0b12767aebd1cf@trac.tools.ietf.org>
In-Reply-To: <075.fdee2d1220a4dd797b0b12767aebd1cf@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUyM+Jvja65+e8gg31PmC3m9q5gc2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtXpJ9gLzilVtDZMZmlgvKPYxcjBISFgIjHjlUwXIyeQKSZx 4d56ti5GLg4hgUOMEt9m7WKFcJYwSvzdMo0VpIpNwE7i0ukXTCDNIgLKEqd/OYCEhQUCJO60 bmQHsUUEAiUWnzvIDGEbSUx6OoMVpJxFQFXi9pECkDCvgK/EyhuLmUBsIQE3iVuLtrCB2JwC 7hKnps5nAbEZge75fmoNWA2zgLjErSfzmSDuFJBYsuc8M4QtKvHy8T9WCFtRYufZdmaQVcwC mhLrd+lDtCpKTOl+yA6xVlDi5MwnLBMYRWchmToLoWMWko5ZSDoWMLKsYmTPTczMSS832sQI DPeDW36r7mC8c07kEKM0B4uSOO+Ht85BQgLpiSWp2ampBalF8UWlOanFhxiZODilGhgX/Nrx XaThzI91mh/vvTxqHKjerJ/V56g3vyO07fDnXn/W4znVIrlS1WYnGPVDZh8PzyqzLvFYPotV LEHnRk7/u9KV7N6HO+dflFFPs1FQzZW93XIv6M+FA33eMko39z+IEg3a8Mtn/hnOaYal0nXX WFkNNYRLd0yc1X4gZflLhx/Tbxo0syuxFGckGmoxFxUnAgDLPqONRQIAAA==
Subject: Re: [Dime] [dime] #52: Throttling not needed to be based on previous history
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: Wed, 12 Feb 2014 08:56:27 -0000
Same comment also applies to following paragraph in 5.5.2 Now: 0 < value < 100 Indicates that the reporting node urges the reacting node to reduce its traffic by a given percentage. For example if the reacting node has been sending 100 packets per second to the reporting node, then a reception of OC-Reduction-Percentage value of 10 would mean that from now on the reacting node MUST only send 90 packets per second. How the reacting node achieves the "true reduction" transactions leading to the sent request messages is up to the implementation. The reacting node MAY simply drop every 10th packet from its output queue and let the generic application logic try to recover from it.0 < value < 100 Proposal: Indicates that the reporting node urges the reacting node to reduce its traffic by a given percentage. For example if the reacting node would send 100 packets to the <--- reporting node, then a reception of OC-Reduction-Percentage value of 10 would mean that from now on the reacting node MUST only send 90 packets per second. How the reacting node achieves the "true reduction" transactions leading to the sent request messages is up to the implementation. The reacting node MAY simply drop every 10th packet from its output queue and let the generic application logic try to recover from it. We should not specify a rates for the simple loss algorithm. It’s up to the implementation how to reduce, but no time unit has to be specified. -----Original Message----- From: dime issue tracker [mailto:trac+dime@trac.tools.ietf.org] Sent: miércoles, 12 de febrero de 2014 9:13 To: Maria Cruz Bartolome Cc: dime@ietf.org Subject: [dime] #52: Throttling not needed to be based on previous history #52: Throttling not needed to be based on previous history Now (chapter 4.7): The OC-Reduction-Percentage AVP (AVP code TBD8) is type of Unsigned32 and describes the percentage of the traffic that the sender is requested to reduce, compared to what it otherwise would have sent. Proposal: The OC-Reduction-Percentage AVP (AVP code TBD8) is type of Unsigned32 and describes the percentage of the traffic that the sender is requested to reduce, compared to what it otherwise would send. The intention is to avoid that anyone may interpret reacting node is required to consider history of sent information when throttling. -- -----------------------------------------------+------------------------ -----------------------------------------------+--- Reporter: maria.cruz.bartolome@ericsson.com | Owner: MCruz Type: defect | Bartolomé Priority: major | Status: new Component: draft-docdt-dime-ovli | Milestone: Severity: Active WG Document | Version: 1.0 | Keywords: -----------------------------------------------+------------------------ -----------------------------------------------+--- Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/52> dime <http://tools.ietf.org/wg/dime/>
- [Dime] [dime] #52: Throttling not needed to be ba… dime issue tracker
- Re: [Dime] [dime] #52: Throttling not needed to b… Maria Cruz Bartolome
- Re: [Dime] [dime] #52: Throttling not needed to b… Jouni Korhonen
- Re: [Dime] [dime] #52: Throttling not needed to b… Jouni Korhonen
- Re: [Dime] [dime] #52: Throttling not needed to b… Maria Cruz Bartolome
- Re: [Dime] [dime] #52: Throttling not needed to b… Steve Donovan
- Re: [Dime] [dime] #52: Throttling not needed to b… lionel.morand
- Re: [Dime] [dime] #52: Throttling not needed to b… Ben Campbell
- Re: [Dime] [dime] #52: Throttling not needed to b… Jouni Korhonen
- Re: [Dime] [dime] #52 (draft-docdt-dime-ovli): Th… dime issue tracker
- Re: [Dime] [dime] #52 (draft-docdt-dime-ovli): Th… dime issue tracker
- Re: [Dime] [dime] #52 (draft-ietf-dime-ovli): Thr… dime issue tracker