Re: [Dime] Issue#31 status

Ben Campbell <ben@nostrum.com> Thu, 20 February 2014 22:33 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 42C2E1A032E for <dime@ietfa.amsl.com>; Thu, 20 Feb 2014 14:33:18 -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 NEoXJ6siSbnZ for <dime@ietfa.amsl.com>; Thu, 20 Feb 2014 14:33:17 -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 1321B1A0328 for <dime@ietf.org>; Thu, 20 Feb 2014 14:33:17 -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 s1KMXBQs008074 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 16:33:13 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <53051027.1050608@usdonovans.com>
Date: Thu, 20 Feb 2014 16:33:12 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6914448-9ED4-43ED-BBE9-192B437BB6F2@nostrum.com>
References: <5BCBA1FC2B7F0B4C9D935572D9000668151B3CF7@DEMUMBX014.nsn-intra.net> <53051027.1050608@usdonovans.com>
To: Steve Donovan <srdonovan@usdonovans.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/IUzvr3kWu_B0P1AVb-3DEPB_nlg
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] Issue#31 status
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: Thu, 20 Feb 2014 22:33:18 -0000

+1

On Feb 19, 2014, at 2:12 PM, Steve Donovan <srdonovan@usdonovans.com> wrote:

> Agreed
> 
> On 2/19/14 8:17 AM, Wiehe, Ulrich (NSN - DE/Munich) wrote:
>> #31: Sending OC-Ongoing-Throttling-Info AVP in request messages that survived a throttling
>>  
>> Dear all,
>>  
>> I did not receive much support for the proposal to define an OC-Ongoing-Throttling-Info AVP in request messages that survived a throttlting.
>>  
>> However, we seem to agree on some principles:
>>  
>> Missing OLR in answer means “no change”; it does not mean “no overload/no throttling requested”
>>  
>> Reporting nodes SHOULD include OLR in every answer that it sends in response to a request message which indicatedOLR_DEFAULT_ALGO support unless the reporting node has very good reasons not to do so. Exact wording is not yet agreed.
>>  
>> Ulrich
>>  
>>  
>>  
>> 
>> 
>> _______________________________________________
>> 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