Re: [quicwg/base-drafts] Think carefully before blowing up (#3344)

Lucas Pardue <notifications@github.com> Wed, 15 January 2020 00:14 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 4E61A1201E5 for <quic-issues@ietfa.amsl.com>; Tue, 14 Jan 2020 16:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 axP0BG5cLmqU for <quic-issues@ietfa.amsl.com>; Tue, 14 Jan 2020 16:14:29 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B49F9120058 for <quic-issues@ietf.org>; Tue, 14 Jan 2020 16:14:29 -0800 (PST)
Received: from github-lowworker-5fb2734.va3-iad.github.net (github-lowworker-5fb2734.va3-iad.github.net [10.48.19.27]) by smtp.github.com (Postfix) with ESMTP id 0D5616608B2 for <quic-issues@ietf.org>; Tue, 14 Jan 2020 16:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579047269; bh=6Eu89bijot+/aC1ff+eDP0RmJwMofO2vLFMdiqXEUzM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fLUdsRzir/Kjm1YWBKLMtk5izhtEx1LZYT/8pvtTt+YyeSOd4VqBXV2L/SOh3ocJo BRgrfdd27gQ3q9oubuIJPd9wX4c32lVX9hWffJlq1BIrTmQDM3v68KxInXiPULNlO1 G+TkKtn7YwA40Nd8a40yRBQaCQVHUmSXKwrkhEww=
Date: Tue, 14 Jan 2020 16:14:28 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7GPGLLAMW4PQIEML54FOF6JEVBNHHCBRUN3U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3344/review/342921580@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3344@github.com>
References: <quicwg/base-drafts/pull/3344@github.com>
Subject: Re: [quicwg/base-drafts] Think carefully before blowing up (#3344)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1e5964f1579_5b153fdd66ecd96041038"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/PgwcRqh2xvY3cRVBHxkHQGdo1Wo>
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 Jan 2020 00:14:31 -0000

LPardue commented on this pull request.



> +An endpoint MAY choose to treat a stream error as a connection error under
+certain circumstances.  Implementations need to consider the impact on
+outstanding requests before making this choice.

LG. 

The other impact of closing conenction with an error relates to Alt-Svc. A client maintaining an Alt-Svc cache may interpret a connetion error as a broken service, which could cause a fallback (e.g. to HTTP/2) and a failure to switch to the alternative until the black mark expires. 

We saw _something_ like this between Chrome and Cloudflare, where one of us was mistakenly detecting something as an error. @RyanAtGoogle might recall.

-- 
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/pull/3344#pullrequestreview-342921580