Re: [Dime] Ben's comments on 4.3, third paragraph from end

Steve Donovan <srdonovan@usdonovans.com> Tue, 20 January 2015 18:27 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 1EA091B2AFD for <dime@ietfa.amsl.com>; Tue, 20 Jan 2015 10:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.579
X-Spam-Level: *
X-Spam-Status: No, score=1.579 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_NEUTRAL=0.779] 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 dwCYoS5yEyik for <dime@ietfa.amsl.com>; Tue, 20 Jan 2015 10:27:26 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.250]) (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 B19421ACDA2 for <dime@ietf.org>; Tue, 20 Jan 2015 10:27:26 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:51392 helo=Steves-MacBook-Air-2.local) by biz131.inmotionhosting.com with esmtpsa (UNKNOWN:RC4-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1YDdWM-0002GA-Ki; Tue, 20 Jan 2015 10:27:25 -0800
Message-ID: <54BE9E0A.7040307@usdonovans.com>
Date: Tue, 20 Jan 2015 12:27:22 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>, ext Ben Campbell <ben@nostrum.com>
References: <5BCBA1FC2B7F0B4C9D935572D90006681523F07F@DEMUMBX014.nsn-intra.net> <54B7BD25.4040103@usdonovans.com> <5BC32AB7-6DA7-4B27-90E6-40203B3C35D2@nostrum.com> <5BCBA1FC2B7F0B4C9D935572D90006681523F249@DEMUMBX014.nsn-intra.net>
In-Reply-To: <5BCBA1FC2B7F0B4C9D935572D90006681523F249@DEMUMBX014.nsn-intra.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OutGoing-Spam-Status: No, score=-1.0
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/EpsznzcObJmVLepVD16hoMXtNVE>
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] Ben's comments on 4.3, third paragraph from end
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, 20 Jan 2015 18:27:28 -0000

  I have removed the last sentence in the paragraph in question.  The 
before and after for the paragraph is as follows:

Before:

    Reporting nodes can change the overload abatement algorithm indicated
    in the OC-Feature-Vector AVP if the reporting node is not currently
    in an overload condition and sending overload reports.  The reporting
    node is not allowed to change the overload abatement algorithm while
    the reporting node is in an overload condition.

After:

    Reporting nodes can change the overload abatement algorithm indicated
    in the OC-Feature-Vector AVP if the reporting node is not currently
    in an overload condition and sending overload reports.

Ulrich,

I'm not sure I understand your point about the assignment of commonly 
supported algorithms.  Are you ok with this change?

Regards,

Steve
On 1/16/15 4:30 AM, Wiehe, Ulrich (NSN - DE/Munich) wrote:
> Ben
>
> The Note at the beginning of 5.1 is about change of announced capabilities in reacting nodes, while the text in 4.2 (and 5.2.1.4) is about change of selected algorithm by reporting nodes.
> I don't think the text in 4.2 (and 5.2.1.4) is totally wrong. Of course, if the reacting node changes the set of announced capabilities, the reporting node may change (or even need to  change) the selected algorithm. What is not allowed to be changed by the reporting node during an overload condition is the deterministic function that assignes to every set of commonly supported algorithms a distinct selected algorithm.
>
>
> Ulrich
>
>
> -----Original Message-----
> From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Ben Campbell
> Sent: Thursday, January 15, 2015 4:19 PM
> To: Steve Donovan
> Cc: dime@ietf.org
> Subject: Re: [Dime] Ben's comments on 4.3, third paragraph from end
>
> Sorry, that was 4.2.
>
>> On Jan 15, 2015, at 7:14 AM, Steve Donovan <srdonovan@usdonovans.com> wrote:
>>
>> I agree with Ulrich, I don't see the issue.
>>
>>
>> On 1/15/15 3:58 AM, Wiehe, Ulrich (NSN - DE/Munich) wrote:
>>> Ben wrote:
>>> -- 4.3, third paragraph from end:
>>>   
>>> This still assumes that reporting nodes cannot change algorithms during overload. I thought we agreed to remove that. (The normative text is also still there--see later comment.)
>>>   
>>> <Ulrich> I don't understand. In my copy of -06 the third paragraph from end in 4.3 reads:
>>>     Two types of overload abatement treatment are defined, diversion and
>>>     throttling.  Reacting nodes are responsible for determining which
>>>     treatment is appropriate for individual requests.
>>> How does this text assume that reporting nodes cannot change algorithms during overload?
>>>   
>>>   
>>>
>>>
>>> _______________________________________________
>>> 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 mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>