IETF Logo Mail Archive

[Masque] TCP-CONNECT errors in H2 & H3 was Re: Call for MASQUE use cases

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 24 February 2020 18:12 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72FCB3A1070 for <masque@ietfa.amsl.com>; Mon, 24 Feb 2020 10:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NkR2-PXPwTbG for <masque@ietfa.amsl.com>; Mon, 24 Feb 2020 10:12:21 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 9AB323A1065 for <masque@ietf.org>; Mon, 24 Feb 2020 10:12:21 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id a5so290594wmb.0 for <masque@ietf.org>; Mon, 24 Feb 2020 10:12:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jhiYHNd2hYY53s9WD7G4VbvPnjAUx+KJPSANfcJ4NLY=; b=GLQJFPAVjuuQVb14qTYjilO3YEzv51QTWcnrm2N40ZIdtubo2B+/Ahay+khN7KOvup mqu8soHnWczKnmvss3cVY/zbR8KOg5DIaSn4+UVmHMtamH/28r5cIdYiuRGA7W1xerCr c+XDvq6TTo0az3mPesLvbhXo+921oFHMschJWtNfQuYKMnpYGGFWFckNkBM6I3jq6Ngf fOJs8P5HDY4mTPOt9iBVfszw7nH6AqyJfA7QYHzm/7gos6SPSyMk51iAKqySdxhnddEz +asMomZekGAOusFHLRBQnCyAUsiubBxZAZjK3U+TyqQZRUVvcDphk7PUHiyHewM+ej1t BKmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jhiYHNd2hYY53s9WD7G4VbvPnjAUx+KJPSANfcJ4NLY=; b=VWxtdTclnGV7WAtUH23o2vMulU2nwdAUGQ9wiljtt6r+ynRVLRETZfqwZpAyG6M0ZP SjVHgg7G80bsNwxbQdUhq54TLUoLaZkDUbNl10/6jqNQpLcqScDN46Kf+m6nHlSINddu HqnAwJ8LX0e/zAXcaUdAyOIiWJZlak4D7GTKbqVtS396Za4CS0p1+TKNlynXXgM2X3ul d0xL6Q8nCt3ynLeP2J17z+eOquRHOLonuoRDxSK01OzPLAkSG0PPLN1C6J4MOZwJeNZ0 Al0g0rxT4aUyweIySY9BT06ksqhIy2EHm3XsmRK/zYDvrglS3wiP837N0V2lWTYiOec2 suUg==
X-Gm-Message-State: APjAAAVRLekZ8oF6J8xIZCIG4nYDSawOP2Je2ia+dzWZRJmWb/aEYwzb kgQgvOG/qIz/5+/i8xO6zz55mKTHUfzzSGRf7BY=
X-Google-Smtp-Source: APXvYqyrSQ0ULy/yYilTxeikvH1xBEeTp35Ne7aD2LRb3qMToKqo3eGyHOkrN3N3oSYlHLhe4ZhAu8LRImQB0TKcsV0=
X-Received: by 2002:a1c:9c87:: with SMTP id f129mr330159wme.26.1582567940161; Mon, 24 Feb 2020 10:12:20 -0800 (PST)
MIME-Version: 1.0
References: <D46D764C-F682-472A-AFDA-32DDF5CA5F6B@heapingbits.net> <CABcZeBPMUNgOVWMS_sXPTsCU2R+EaK9JDuZsJQ5KSQROXE+4Sg@mail.gmail.com> <CAHbrMsAVXmyvqJKNzcmHOvM3NvPqhpfC9MuDEq9kNUBKe7=7=g@mail.gmail.com> <CAKKJt-etTk6CAqbL1MdSV6gdCgqC2Wz8cdUqbdzbM2h3LKAMhw@mail.gmail.com> <CAHbrMsDqgx7h+TRKLOgW+a3B3+TLWoRE9_DVBVhcKGRC3G=rog@mail.gmail.com>
In-Reply-To: <CAHbrMsDqgx7h+TRKLOgW+a3B3+TLWoRE9_DVBVhcKGRC3G=rog@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 24 Feb 2020 18:12:08 +0000
Message-ID: <CALGR9obK2qY2hsB9Benonkv_LFp+CD+9zTddWGPQro1VNdKcZA@mail.gmail.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, Christopher Wood <caw@heapingbits.net>, MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8068d059f564f62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/sdkP3a7R_8_soyjp_I4s50AtRGI>
Subject: [Masque] TCP-CONNECT errors in H2 & H3 was Re: Call for MASQUE use cases
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2020 18:12:24 -0000

On Mon, Feb 24, 2020 at 5:53 PM Ben Schwartz <bemasc=
40google.com@dmarc.ietf.org> wrote:

>
> I wasn't really thinking about QUIC; I was thinking primarily about TCP.
> If we're in the business of modernizing CONNECT, one thing that I would
> like would be an HTTP Trailer indicating _why_ the connection was closed,
> e.g. who closed it, FIN vs. RST vs. timeout.  Similarly, if CONNECT fails,
> it would be nice to have a header indicating why it failed, and perhaps
> some clarity about which status codes to use.  My main use case here is
> "showing users the right error message" when something goes wrong.
>

If we're talking only HTTP/2 and HTTP/3, I don't think trailers is the
right fit here but nor do I see that being a problem because the terminal
state of the TCP connection is reflected in the terminal state of the HTTP
stream. FIN -> END_STREAM, TCP error -> RST_STREAM with CONNECT_ERROR code.
Other failure conditions could be communicated by adding new error codes.

In failure case that occurs when CONNECT fails to even get off the ground,
a standard 4xx/5xx error seems apropriate and I'm reminded of
https://tools.ietf.org/html/rfc7807 which describes machine-readable
details for "problems".

v2.23.0 | Report a Bug | By Email