IETF Logo Mail Archive

Re: [quicwg/base-drafts] HTTP/3 Client handling of SERVER_BUSY error code needs to be specified (#2699)

Praveen Balasubramanian <notifications@github.com> Thu, 23 May 2019 16:27 UTC

Return-Path: <noreply@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 65A0D120113 for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 09:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.393
X-Spam-Level:
X-Spam-Status: No, score=-6.393 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 cvqhFi4E18ca for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 09:27:07 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD151120043 for <quic-issues@ietf.org>; Thu, 23 May 2019 09:27:06 -0700 (PDT)
Date: Thu, 23 May 2019 09:27:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558628825; bh=ZCKbJyu8Dfs7Rxfd5wmjpZhPuM0us4lSZHaAma+jiRQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xxJU86ezoez4zdbNQ+ss3qTMKwR+kVLPqFT1Cp0CzdZM4iPx8ynAqcm7ZYdcL+Q9z pNGmZdrI4sVh+JnswXqsBX3JvrUzm1gICHTTPQYiHNvCIzgCZuqPhkk5rhzYWoJ3cg T4J9M2fCh7MjV7AEIyWhJJVB5FmMzvQDnlKo/VHQ=
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5H6YDWQYBMAJBYRSN26P6FTEVBNHHBU6IQGY@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/495290018@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_5ce6c9d920a61_7f273fd9a00cd960114071a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/OQsHMh8MRVAkzQQt0IzzlfEzTOo>
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: Thu, 23 May 2019 16:27:09 -0000

"So any client with implementation of happyeyeball-like race mechanism between QUIC and TCP should fallback to TCP."
AFAICT this race mechanism isn't described anywhere in H3. Some implementations may choose to not always race and cache the server response per session and if H3 succeeds then continue doing just H3.  IMO therefore we need additional text suggesting that the client stop retrying QUIC for a period or use exponential backoff and fallback to H2 when it receives SERVER_BUSY. 

-- 
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-495290018

v2.23.0 | Report a Bug | By Email