IETF Logo Mail Archive

[quicwg/base-drafts] frame type field of CONNECTION_CLOSE provides little value (#1989)

Marten Seemann <notifications@github.com> Sun, 11 November 2018 06:49 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 789F612D4E8 for <quic-issues@ietfa.amsl.com>; Sat, 10 Nov 2018 22:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 QmRNZznKt3M9 for <quic-issues@ietfa.amsl.com>; Sat, 10 Nov 2018 22:49:52 -0800 (PST)
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 B02771292F1 for <quic-issues@ietf.org>; Sat, 10 Nov 2018 22:49:52 -0800 (PST)
Date: Sat, 10 Nov 2018 22:49:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541918991; bh=+S1IAej2n0yKIku+HMu3QgkfB6q+zUMBwutr3GsyZ10=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bafSF/6I544SMEA5RjjcgvbMclxPZBEIB9fvhLCE0t5eH3OXGcqavnfilp+bopKdG qPoUXKAfWu34m0x/3il3apu78eqy8ZBbi1/uBXI2/MPhTe+JpstdodTjntCFYosR7V fQb2/n8QdsczkQk1unTpSjG07LF/W8NXTsv7tFEo=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab18d4a468eaf9ac6f5e0c2054c8a2d533498cd5b592cf0000000117ff930f92a169ce169ea5c2@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1989@github.com>
Subject: [quicwg/base-drafts] frame type field of CONNECTION_CLOSE provides little value (#1989)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be7d10fb9c84_5c853fa531ad45c48346d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/jnInLdyZ_QgH-QYGTdxjzD307Ow>
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: Sun, 11 Nov 2018 06:49:55 -0000

The frame type field of the CONNECTION_CLOSE frame seems to provide little value, except for the FRAME_ENCODING_ERROR error code.

For example, consider the FLOW_CONTROL_ERROR. The only two values that would make sense in that field is the type of a STREAM frame or a RST_STREAM frame (no guidance is provided regarding that in the draft, as far as I can see). Debugging such an error based on the frame type alone will be hardly possible, you'll need a clear reason string for that.

For other error codes, things look even worse. What is the appropriate frame type for a TRANSPORT_PARAMETER_ERROR? Probably the type of a CRYPTO frame, since transport parameters are carried in TLS messages that are carried in CRYPTO frames. But setting this value provides no additional information to the peer. And what about VERSION_NEGOTIATION_ERROR or 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/1989

v2.23.0 | Report a Bug | By Email