Re: [quicwg/base-drafts] HTTP/3 Client handling of SERVER_BUSY error code needs to be specified (#2699)
Lucas Pardue <notifications@github.com> Wed, 15 May 2019 18:55 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E090D120770 for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 11:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level:
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 MjwwkTOZGWpM for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 11:55:21 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 0112A120778 for <quic-issues@ietf.org>; Wed, 15 May 2019 11:55:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=MRyhKCo6Imy8VDrAx7YWuyjJvb4=; b=LPiDgcnyK1EvU0ja qM9QcHMfaINITj4KAm2HD8HwkbHRG+jbebQAqpGsnS5MOSAN5G/5YqN6YWCeG1qs CK+LX000mWRZvXYe8F0zgukHq39HTwpTNn0q7o82Pnx0TlzqUFmgMG49sNc7J+4v ddVrbcDXmZ9NFUK0xGPB8c6lSL8=
Received: by filter1769p1mdw1.sendgrid.net with SMTP id filter1769p1mdw1-26315-5CDC6097-21 2019-05-15 18:55:19.911902035 +0000 UTC m=+131742.243482340
Received: from github-lowworker-61c4d48.cp1-iad.github.net (unknown [140.82.115.69]) by ismtpd0061p1mdw1.sendgrid.net (SG) with ESMTP id RP2VAdgjTSaCX0YeH2l-0w for <quic-issues@ietf.org>; Wed, 15 May 2019 18:55:19.794 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-61c4d48.cp1-iad.github.net (Postfix) with ESMTP id 9C0131A006A for <quic-issues@ietf.org>; Wed, 15 May 2019 11:55:19 -0700 (PDT)
Date: Wed, 15 May 2019 18:55:20 +0000
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3DH5GS523KUZKM5XF25GJRPEVBNHHBU6IQGY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2699/492780278@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2699@github.com>
References: <quicwg/base-drafts/issues/2699@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3 Client handling of SERVER_BUSY error code needs to be specified (#2699)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdc60979a4cf_51af3faa7e4cd96c2038a9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2dyPSfBMFC3jQWmQES4AJvVp63G3O8BHN4q2 amN6r1NK44U9p3tANQ/+hVmHaJzpjiexpYJx0xMIcFiJELTFauZ/qca0CIjLrLQsiYv8gGAbekAlzO Zo8WkOdhV7koeQymlb5SxKcUVDbgcxaWsSPjdyBEy1NfK41AVSBidgXFjnrYWd5MV2aUYCXP+VoRrV o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VCdaKiCm7dRNv-eOcJM63QAWzEI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 18:55:23 -0000
Well GOAWAY is fairly broke in HTTP/2 right now anyway 😃 I think guidance is useful, I'm not convinced the HTTP/3 document is the correct place to capture that. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/2699#issuecomment-492780278
- [quicwg/base-drafts] HTTP/3 Client handling of SE… Praveen Balasubramanian
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Praveen Balasubramanian
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Nick Banks
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Praveen Balasubramanian
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Praveen Balasubramanian
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… ianswett
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… ianswett
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Udip Pant
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Praveen Balasubramanian
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Mike Bishop
- Re: [quicwg/base-drafts] HTTP/3 Client handling o… Mike Bishop