Re: [httpapi] client-specified timeout?

Sanjay Dalal <sanjay.dalal@cal.berkeley.edu> Fri, 05 February 2021 19:49 UTC

Return-Path: <sanjay.dalal@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA103A083E for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 11:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cal-berkeley-edu.20150623.gappssmtp.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 CharSIuhHHuM for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 11:49:21 -0800 (PST)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B88FB3A0839 for <httpapi@ietf.org>; Fri, 5 Feb 2021 11:49:21 -0800 (PST)
Received: by mail-oo1-xc2e.google.com with SMTP id u7so1930233ooq.0 for <httpapi@ietf.org>; Fri, 05 Feb 2021 11:49:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cal-berkeley-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uQLNgJEfPdFezvBj0643F5hdDNQ1B2dXEh5gKe2T3uA=; b=Bc9RvwJr+Hz6tc3n+xBok808zwfZDD7DStL74KTc4awKQUKKDiUVZU2368TR45dx8F 6+LqnAtmseiacVgQFZlL6qX1amUN3/u4+CMvk0jxLOgvcU0SZa5n9ABtLwqoki2/pVSs 0lH+LdA9s6NNxs3I0hDlhcyWNLrVkUbsjp9JdKcLRvvSZX7zDiKwmCe9WNETkadu7rc9 Kqh1XJMOc5dCIs4EnepS7lXQuq1owd0mtRcnKSBCQoXjyc+iDBdVOz+BF+GcGbTq8W+v pEDNaYBvRjeI+O0wvaoRGo/PXrNA9CmZY657fadvk0j34BVCdKdXo8sk3e7MQnI6+ChQ LVZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uQLNgJEfPdFezvBj0643F5hdDNQ1B2dXEh5gKe2T3uA=; b=VF807DsP4VCT+LLgRJQg4BxI7WHqXauvOuXkHTGw7H3KmiI/bOIPcroLKatb96YBKT WkiVzXaNaOswz4o51S5YyHETHfYmvrQN7DqlAMGhU11ptUIl87ilJoo1h/AUQEJxiv6J lTsSdeCp8clwvtuS8BV4sh9FpodtHOyXzIxOXuP2j5ln/rLWivZ12leKoGGwzc7w5wez ZqRFeC+YNNWBJs5SF+nZhVoLQ7Z/SWzyKK05t2fxurJh6STTL0Losvmj0WxB3vBQw45Z gLJZE0G82DgLZkddCN/ItigydBKN1+A/fq87YDmHaXQo+RfKV/i7SfsIrC6ISmwCR1Ls XIQw==
X-Gm-Message-State: AOAM532NxKS0by1gsmxC38cCx6csl7Fedr7oofDN4rLYLwCvoPZMuApm RvBPOaLYbTna25qCmCcR9cJB74fLm+MOXRgVdSE=
X-Google-Smtp-Source: ABdhPJygPd8IVl6OH8lphpr1jjFQGrELDCjSlI7kDUM33ja0rBvOlCXwDUmbMLw5QW4sMkrqgMfPOx/hoVFF7cNKAXU=
X-Received: by 2002:a4a:7616:: with SMTP id t22mr4703324ooc.65.1612554561055; Fri, 05 Feb 2021 11:49:21 -0800 (PST)
MIME-Version: 1.0
References: <7613F010-431C-47B3-802E-5258BAA5E156@akamai.com> <CAO+dDxmHSDX1=ouEqNJMX-=Z4ygWysEciWq=QygVm_kF_58OFQ@mail.gmail.com>
In-Reply-To: <CAO+dDxmHSDX1=ouEqNJMX-=Z4ygWysEciWq=QygVm_kF_58OFQ@mail.gmail.com>
From: Sanjay Dalal <sanjay.dalal@cal.berkeley.edu>
Date: Fri, 05 Feb 2021 11:49:09 -0800
Message-ID: <CAC5fHGOET_U_O6WY41NAo2rMPTyBzP51pXCDSQsoZh1=d69ZxQ@mail.gmail.com>
To: James <james.ietf@gmail.com>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000caf10105ba9c1d08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/a0vjbqa_akU9My542pkrqyem1D4>
Subject: Re: [httpapi] client-specified timeout?
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2021 19:49:23 -0000

Should there be a standard way for a client to ask for this using the
Prefer header https://tools.ietf.org/html/rfc7240?

sanjay

On Fri, Feb 5, 2021 at 11:04 AM James <james.ietf@gmail.com> wrote:

> If your ask is about standardisation of the request header and
> negotiation of it, yes I would be interested. But my biggest question
> is about how the server should respond - 504 assumes the server is a
> proxy, 408 is for unused connections, neither of these at initial
> glance appear to fit the use case.
>
> - J
>
> On Fri, 5 Feb 2021 at 19:54, Salz, Rich
> <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> >
> > Is it reasonable for a client to want the ability to say things like “if
> this takes more than 300ms send a failure status code back” ?
> >
> > Anyone in the WG interested in thinking/working on this?
> >
> >
> >
> > --
> > httpapi mailing list
> > httpapi@ietf.org
> > https://www.ietf.org/mailman/listinfo/httpapi
>
> --
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi
>