IETF Logo Mail Archive

Re: [Dime] OVLI: comments to 4.2

Jouni Korhonen <jouni.nospam@gmail.com> Mon, 09 December 2013 12:17 UTC

Return-Path: <jouni.nospam@gmail.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 221401ADBD5 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 04:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 b6bhA22zcyk2 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 04:17:42 -0800 (PST)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2855C1AE253 for <dime@ietf.org>; Mon, 9 Dec 2013 04:17:41 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id el20so1508134lab.9 for <dime@ietf.org>; Mon, 09 Dec 2013 04:17:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=G1JQDgt8of8/ldUKguSJsd8Cdl7ul0MSlX7l7Ngqf0o=; b=cWWn/MRR5qMBaMtTKWlTNZa/UjwPJDnUYC01eAcgSxn/Zkzvug1mMKBBOryfYaK4p1 O/mniyRGkrfrnrxo+bnAUvAD01DzQIr5pgkcTzsSSJ21lV7Who6b00toUBAKLjeAdp/q irHgieWLtViEM8nUc7LCr859OyHABV0DYQKtNFfesK9OfyVVlcRwkST6wDaKZRLhkbAN JCeYfdsdw/WE1RTy9Yv45cgZ1miZQmMUYjIN2+n6DucfCRV5oKaT52g2xKH7jUPZ/Yba chXjp3uonQbh+Nxci8BdlBT881WVVamqsJVfgSyPUABzj3Q8SwyzqoiTbLUaUgDauSlO 5Atg==
X-Received: by 10.152.10.10 with SMTP id e10mr2177514lab.56.1386591456682; Mon, 09 Dec 2013 04:17:36 -0800 (PST)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id m5sm14134416laj.4.2013.12.09.04.17.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 04:17:35 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <F9C9771E-A858-43B3-A707-CDD4425ABA8C@nostrum.com>
Date: Mon, 09 Dec 2013 14:17:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B5ED268-1936-44DB-93AD-68341378DCF7@gmail.com>
References: <5BCBA1FC2B7F0B4C9D935572D90006681519DAA6@DEMUMBX014.nsn-intra.net> <01D3D8A5-2584-4D81-A010-982C8BF77614@gmail.com> <F9C9771E-A858-43B3-A707-CDD4425ABA8C@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] OVLI: comments to 4.2
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: Mon, 09 Dec 2013 12:17:44 -0000

On Dec 6, 2013, at 11:31 PM, Ben Campbell <ben@nostrum.com> wrote:

> 
> On Dec 6, 2013, at 4:19 AM, Jouni Korhonen <jouni.nospam@gmail.com> wrote:
> 
>>> 
>>> 2. Supporting OLR_DEFAULT_ALGO means different things depending on the endpoint’s role (reacting/reporting).
>>> Proposal is to expand the text to read:
>>> 
>>> 
>>>     When this flag is set by the overload control reacting endpoint it means
>>>     that the default traffic abatement (loss) algorithm is supported by the
>>>     reacting endpoint, i.e. the reacting endpont is able and willing to execute
>>>    the default traffic abatement algorithm if so requested by the reporting
>>>    endpoint.
>>>     When this flag is set by the overload control reporting endpoint it means
>>>    that the reporting endpoint when overloaded is able and willing to demand
>>>    executing the default traffic abatement algorithm from the reacting endpoint.
>> 
>> OK with me.
>> 
> 
> On reflection, if that's all it means why does the reporting node need to send it at all? It can just choose to send OLRs for the algorithm the reacting node has advertised. Or is the reporting node declaring that this is the algorithm it will use?

mmmmmyes.. 

- Jouni



> 
>> - Jouni
>

v2.23.0 | Report a Bug | By Email