Re: [Dime] [dime] #52: Throttling not needed to be based on previous history
Ben Campbell <ben@nostrum.com> Fri, 14 February 2014 21:24 UTC
Return-Path: <ben@nostrum.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 204E71A0405 for <dime@ietfa.amsl.com>; Fri, 14 Feb 2014 13:24:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] 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 vGD_6KZYoju8 for <dime@ietfa.amsl.com>; Fri, 14 Feb 2014 13:24:15 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A84BF1A03EE for <dime@ietf.org>; Fri, 14 Feb 2014 13:24:13 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s1ELO7BC052013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Feb 2014 15:24:09 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <087A34937E64E74E848732CFF8354B92097745AF@ESESSMB101.ericsson.se>
Date: Fri, 14 Feb 2014 15:24:07 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F08E5F1-0FDA-44D6-B129-42D0A58F51C6@nostrum.com>
References: <075.fdee2d1220a4dd797b0b12767aebd1cf@trac.tools.ietf.org> <087A34937E64E74E848732CFF8354B92097740BB@ESESSMB101.ericsson.se> <D62D012E-2BDD-42A9-90A5-5E9461E7BF8B@gmail.com> <087A34937E64E74E848732CFF8354B92097745AF@ESESSMB101.ericsson.se>
To: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/_jbrzhBNneENPm3-ZF_hpoxj6vQ
Cc: "dime@ietf.org" <dime@ietf.org>
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: Fri, 14 Feb 2014 21:24:17 -0000
+1 On Feb 12, 2014, at 7:34 AM, Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> wrote: > Thanks Jouni, I didn't realize. > One more correction added > >> 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 instead of 100. 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. > > > -----Original Message----- > From: Jouni Korhonen [mailto:jouni.nospam@gmail.com] > Sent: miércoles, 12 de febrero de 2014 10:36 > To: Maria Cruz Bartolome > Cc: dime@ietf.org > Subject: Re: [Dime] [dime] #52: Throttling not needed to be based on previous history > > > Fine by me.. though you then need to apply the same change to the rest of this paragraph, not only the first one. > > Also, please update this additional concern into the issue tracker issue #52. > > - Jouni > > On Feb 12, 2014, at 10:56 AM, Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> wrote: > >> 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 mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/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