[Dime] Fwd: Re: Ongoing Throttling Information in request messages

Steve Donovan <srdonovan@usdonovans.com> Wed, 06 November 2013 17:01 UTC

Return-Path: <srdonovan@usdonovans.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBD411E8231 for <dime@ietfa.amsl.com>; Wed, 6 Nov 2013 09:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level:
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id csRuh5GH3hAu for <dime@ietfa.amsl.com>; Wed, 6 Nov 2013 09:01:07 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [192.249.113.76]) by ietfa.amsl.com (Postfix) with ESMTP id AAEEA11E8210 for <dime@ietf.org>; Wed, 6 Nov 2013 09:01:00 -0800 (PST)
Received: from dhcp-a236.meeting.ietf.org ([31.133.162.54]:55632) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <srdonovan@usdonovans.com>) id 1Ve6TS-0002dV-9q for dime@ietf.org; Wed, 06 Nov 2013 09:00:59 -0800
Message-ID: <527A75C9.3050103@usdonovans.com>
Date: Wed, 06 Nov 2013 09:00:57 -0800
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: dime@ietf.org
References: <527A6C8B.4080407@usdonovans.com>
In-Reply-To: <527A6C8B.4080407@usdonovans.com>
X-Forwarded-Message-Id: <527A6C8B.4080407@usdonovans.com>
Content-Type: multipart/alternative; boundary="------------040003070405050702050502"
X-OutGoing-Spam-Status: No, score=-2.9
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
Subject: [Dime] Fwd: Re: Ongoing Throttling Information in request messages
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
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, 06 Nov 2013 17:01:19 -0000

Resending with most of the message trimmed.  My first attempt to send 
this got a response that the message is awaiting moderator approval 
because it was bigger than 50k bytes.

Steve

-------- Original Message --------
Subject: 	Re: [Dime] Ongoing Throttling Information in request messages
Date: 	Wed, 06 Nov 2013 08:21:31 -0800
From: 	Steve Donovan <srdonovan@usdonovans.com>
To: 	dime@ietf.org



Nirav,

One qualification of your point below -- The server would only receive 
requests that survived throttling from clients that support DOIC.  The 
server will also receive requests from clients that do not support 
DOIC.  One of the benefits of Ulrich's proposal is that it tells the 
server when a request has not gone through throttling.  The server can 
then choose to do something different with that set of requests.

As to the question of which is more work for the server, which is the 
important question, that isn't yet clear to me.

Steve

On 11/6/13, 7:02 AM, Nirav Salot (nsalot) wrote:
>
> Ulrich,
>
> I might be missing something here so please bear with me.
>
> Number of answer messages sent by server = number of request messages 
> received by the server.
>
> During the overload, the server would receive only those requests 
> which survived throttling.
>
> And then the server would send answer messages to only those request 
> messages.
>
> So "every" and "some" are actually equal in the below equation. No?
>
> Regards,
>
> Nirav.
>
>