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> Wed, 08 July 2020 01:20 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 C1D933A0CE6 for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 18:20:13 -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 WAGDVxC3r-HD for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 18:20:12 -0700 (PDT)
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 897B93A0CE4 for <quic-issues@ietf.org>; Tue, 7 Jul 2020 18:20:12 -0700 (PDT)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net [10.48.17.39]) by smtp.github.com (Postfix) with ESMTP id 623D366098E for <quic-issues@ietf.org>; Tue, 7 Jul 2020 18:20:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594171211; bh=R2Sv7AWYdVznDek331UInXWpuWi137sNefsBhqPQKgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UwBgAvgaG2kFJg1Bh0gYS251szmnNfoQWTBsVz0Sxl2J+9d4bnRCx7gtyKsp4A+cD fXSjCQyJO5qSCr39Y9FHgRKH9GdO71opo0DwvyvyXixZY6tqQiGdwH2qV/g7KYOOLe xRYiG0xUNSqjZ7mpWvmebSyPk+MvVUVhaLoNTTZo=
Date: Tue, 07 Jul 2020 18:20:11 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5X4TVJ66EX376GSIV5CEAEXEVBNHHCNZ746I@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/655223549@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_5f051f4b53126_1c353f86eb8cd960243033"; 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/mQQVfHD7gvTRaVMGpmf-30L5O-4>
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, 08 Jul 2020 01:20:14 -0000

I'm not sure I follow, sorry.

In my contrived example, the extension is negotiated via a SETTINGS parameter but it requires the client to burn an HTTP/3 handshake to learn that the HTTP/3 version of the same server instance does not implement the extension. At that stage there are a few options, one would be to send CONNECTION_CLOSE with error code H3_DESIRED_EXTENSION_UNSUPPORTED, one would be to migrate the vanilla HTTP requests to the H3 connection and maintain H2 only for the websocket. I think leaving most of that up to the implementation is fine, but having an error code could allow a server to discriminate this type of client problem from others.

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