Re: [quicwg/base-drafts] Consider a specific error when switching to an HTTP/3 connection that does not support an extension (#3833)
Lucas Pardue <notifications@github.com> Thu, 09 July 2020 20:19 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 24B193A07E5 for <quic-issues@ietfa.amsl.com>; Thu, 9 Jul 2020 13:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 9gU_irbhplxS for <quic-issues@ietfa.amsl.com>; Thu, 9 Jul 2020 13:19:36 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C1F3A07C2 for <quic-issues@ietf.org>; Thu, 9 Jul 2020 13:19:36 -0700 (PDT)
Received: from github-lowworker-ca235ff.ash1-iad.github.net (github-lowworker-ca235ff.ash1-iad.github.net [10.56.110.15]) by smtp.github.com (Postfix) with ESMTP id E171FE02BF for <quic-issues@ietf.org>; Thu, 9 Jul 2020 13:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594325975; bh=mrHYOfzD/qvrQnj3s5H4AwAOgfytcx6c/0uippZXLRU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uu/7p0+O9dJ4oEXIpTxYzLiCJQHbMDshbmSL0gDngrHsp9NuBkLfXA86U99AqT1oY PX3+/yJDlumpOAZG7Y6/7d6JeAqT+/C9PiDwxoIJgrhLz8+dG8Nbh3kAveap0h4p0J p6EQyJkkSC/AwL/ZMH6xhzYFukJb+PwZETMliAlI=
Date: Thu, 09 Jul 2020 13:19:35 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7DZYZYVLMGT2SN4YV5CNONPEVBNHHCNZ746I@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3833/656331410@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3833@github.com>
References: <quicwg/base-drafts/issues/3833@github.com>
Subject: Re: [quicwg/base-drafts] Consider a specific error when switching to an HTTP/3 connection that does not support an extension (#3833)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f077bd7d329f_24053fc8612cd96830844a"; 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/i5St-9mpMXKfuahMK2lWh9i_9PM>
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, 09 Jul 2020 20:19:38 -0000
Yeah, my first primary motivation was to catch misconfigurations or synchronisation issues across the same fleet (maybe even cross-CDN or cross-cloud). The h2->h3 path is only one manifestation. And as you rightly describe, this issue has a slew of broader considerations. For that reason, I think this needs to actually be its own draft which some other group of people can worry about. Furthermore, there is fundamentally nothing in the H3 protocol that makes the situation any worse than it than it already is. Let's just close this. -- 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/3833#issuecomment-656331410
- [quicwg/base-drafts] Consider a specific error wh… Lucas Pardue
- Re: [quicwg/base-drafts] Consider a specific erro… Kazuho Oku
- Re: [quicwg/base-drafts] Consider a specific erro… Lucas Pardue
- Re: [quicwg/base-drafts] Consider a specific erro… Lucas Pardue
- Re: [quicwg/base-drafts] Consider a specific erro… Mike Bishop
- Re: [quicwg/base-drafts] Consider a specific erro… Lucas Pardue
- Re: [quicwg/base-drafts] Consider a specific erro… Lucas Pardue
- Re: [quicwg/base-drafts] Consider a specific erro… Lucas Pardue