IETF Logo Mail Archive

Re: [dispatch] draft-asveren-dispatch-http-overload-control

Cullen Jennings <fluffy@iii.ca> Sun, 15 April 2018 13:22 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B731200C5 for <dispatch@ietfa.amsl.com>; Sun, 15 Apr 2018 06:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 3b9Bwsg1BVhd for <dispatch@ietfa.amsl.com>; Sun, 15 Apr 2018 06:22:43 -0700 (PDT)
Received: from smtp112.iad3a.emailsrvr.com (smtp112.iad3a.emailsrvr.com [173.203.187.112]) (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 8FBE91200A0 for <dispatch@ietf.org>; Sun, 15 Apr 2018 06:22:43 -0700 (PDT)
Received: from smtp7.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp7.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 3079E4D2D; Sun, 15 Apr 2018 09:22:40 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp7.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C060F19B4; Sun, 15 Apr 2018 09:22:39 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (S0106004268479ae3.cg.shawcable.net [70.77.44.153]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Sun, 15 Apr 2018 09:22:40 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_B8177E06-AE0C-4C7B-9C0D-72CA97C061B5"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CY4PR03MB3160F7165D883F529D7DB499A5B20@CY4PR03MB3160.namprd03.prod.outlook.com>
Date: Sun, 15 Apr 2018 07:22:38 -0600
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Message-Id: <3E8C4615-78DE-4C45-95F2-D77856BDB7BC@iii.ca>
References: <CY4PR03MB3160F7165D883F529D7DB499A5B20@CY4PR03MB3160.namprd03.prod.outlook.com>
To: "Asveren, Tolga" <tasveren@rbbn.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/1A68hZtyPgHk2dL7DSvpVPA3LzQ>
Subject: Re: [dispatch] draft-asveren-dispatch-http-overload-control
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Apr 2018 13:22:45 -0000

If the client finds out it should use a 50% drop rate. How does that interact with retries and retransmissions on the client? I’m just looking for a bit more detail on what the client does once it knows a given set of requests should have a 50% drop rate. 


> On Apr 14, 2018, at 12:57 PM, Asveren, Tolga <tasveren@rbbn.com> wrote:
> 
> I just submitted draft-asveren-dispatch-http-overload-control, which specifies a generic overload control mechanism for HTTP/HTTPS applications.
>  
> https://www.ietf.org/id/draft-asveren-dispatch-http-overload-control-00.txt <https://www.ietf.org/id/draft-asveren-dispatch-http-overload-control-00.txt>
>  
>  
> I would appreciate any feedback (as a first step mainly about whether this is something people would be interested in).
>  
> Thanks,
> Tolga 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org <mailto:dispatch@ietf.org>
> https://www.ietf.org/mailman/listinfo/dispatch <https://www.ietf.org/mailman/listinfo/dispatch>

v2.23.0 | Report a Bug | By Email