IETF Logo Mail Archive

Re: draft-asveren-dispatch-http-overload

Martin Thomson <martin.thomson@gmail.com> Mon, 30 April 2018 06:11 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58F2712D879 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 29 Apr 2018 23:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.761
X-Spam-Level:
X-Spam-Status: No, score=-7.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Zb9THthn4fYj for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 29 Apr 2018 23:11:57 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (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 B0A541242F5 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 29 Apr 2018 23:11:57 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1fD1u6-00058E-UF for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Apr 2018 06:03:14 +0000
Resent-Date: Mon, 30 Apr 2018 06:03:14 +0000
Resent-Message-Id: <E1fD1u6-00058E-UF@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <martin.thomson@gmail.com>) id 1fD1tt-000575-8J for ietf-http-wg@listhub.w3.org; Mon, 30 Apr 2018 06:03:01 +0000
Received: from mail-ot0-f182.google.com ([74.125.82.182]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <martin.thomson@gmail.com>) id 1fD1to-000593-NG for ietf-http-wg@w3.org; Mon, 30 Apr 2018 06:03:00 +0000
Received: by mail-ot0-f182.google.com with SMTP id l13-v6so8312838otk.9 for <ietf-http-wg@w3.org>; Sun, 29 Apr 2018 23:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=999KFUdKSGsr1yDzLFiiEzThCRUgn9Q5pM4xALIePK8=; b=mUbjtfTKhgIbM+/wRenJqXdet/4joW+L8DWQe+2C01sUt+j6A40e0yri2svyotmB3y zKYCGD3JdSJtGrL7C1b9fKkaRFVkU7l1sFSpXC774DyRRqtVHJksKawpv5Rpn2rnvXu0 dJdBGXP8XKsOLv0CkhOceMrgNlSP5/c6qqWnqMu2Wyx59rgIPU3ri9O8vnDN1XKfthB/ rqNHipSSRADZz0ZZiEZAt4Qcx8lmFJjSl6rh8xyYrk33N0w6yNZD0pMUVUz5kjrkHtEN ltJ4SMTDyOQJs22JbTdToT0entU+5BdxmCOB1edo+/Rv0aotXIHxtf6TMyk1/osGjtJG 7gmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=999KFUdKSGsr1yDzLFiiEzThCRUgn9Q5pM4xALIePK8=; b=dvtdDqgdKR6QTaxgn4Ww68qv5XnrOjuKOyGIXXtOtD1KksnXBDiVqy0p3HM3Bnq/KA pw279H8F5tehYM3h9TymfIUD/UEqKJhRbjmnaz2PeK3dU7JyMYWYNCedOgMx4t8gRq+V MQWocy4TvJ3Id5EoE1r4cifmf2EkWhRdmLo/5SGrRXebNiL9RkFAm9AOYZWeEWOO/6w7 1BkBg7fESTXTFJoYpEBM8fNEP+bL718HZ3aMCd2gvpFp1nfMuflfTzkCRnaKB1ZhgZpE BEjOwIKT6xnLdR7aPh8X9lmmAhpBuHFXRnS77JTd8ZaxWRpe382sb2vCOgxuO3ZfewlR t4VA==
X-Gm-Message-State: ALQs6tBGWKIBMmzvYI2dRVjeoKKj9a/fJdPMfJwNkMsKZ6baENe6NYRB wEIRE8H3+yclrFTnNbXB3p/k8Id1+2snxtUzH9Q=
X-Google-Smtp-Source: AB8JxZpk8TnsJvrbYRiCLfQJZ/512HneZ7jHgBXzV16/8ZseJMvdMBrohayn61PANPEIVX/ANKgtfFknwgPV9Q+txRw=
X-Received: by 2002:a9d:3a65:: with SMTP id j92-v6mr8103106otc.352.1525067670891; Sun, 29 Apr 2018 22:54:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:29ce:0:0:0:0:0 with HTTP; Sun, 29 Apr 2018 22:54:30 -0700 (PDT)
In-Reply-To: <CY4PR03MB31607A155630036128CD091FA5830@CY4PR03MB3160.namprd03.prod.outlook.com>
References: <CY4PR03MB31607A155630036128CD091FA5830@CY4PR03MB3160.namprd03.prod.outlook.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 30 Apr 2018 15:54:30 +1000
Message-ID: <CABkgnnVZcfzpCOsCmpC8rYEugOz2TjxnerkQgZaKJ52nqT7bFA@mail.gmail.com>
To: "Asveren, Tolga" <tasveren@rbbn.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: AWL=-0.124, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1fD1to-000593-NG a842b9275aa6bd4ec02fc519bc75ed4d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: draft-asveren-dispatch-http-overload
Archived-At: <https://www.w3.org/mid/CABkgnnVZcfzpCOsCmpC8rYEugOz2TjxnerkQgZaKJ52nqT7bFA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/35318
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

This is the right working group, for sure.  However, I don't find the
introduction convincing.  Maybe I'm missing something.  How is
Retry-After inadequate?

As for the mechanism described, how does it not expose information
about the server configuration such that DOS could be more precisely
targetted?  What is the scope of the table?  What is the point of
multiple values?


On Mon, Apr 30, 2018 at 3:50 AM, Asveren, Tolga <tasveren@rbbn.com> wrote:
> I submitted draft-asveren-dispatch-http-overload-control to DISPATCH WG a
> while ago. It aims to specify a generic overload control mechanism for
> HTTP/HTTPS applications.
>
>
>
> https://www.ietf.org/id/draft-asveren-dispatch-http-overload-control-00.txt
>
>
>
>
>
> I thought it could be a good idea to herald it here as well as some folks
> may not be following DISPATCH WG.
>
>
>
> I would appreciate any feedback about overall idea/need/alternatives/in
> general.
>
>
>
> Thanks,
>
> Tolga
>
>

v2.23.0 | Report a Bug | By Email