Re: [quicwg/base-drafts] encoding of CONNECTION_CLOSE reason phrases (#1990)
Christian Huitema <notifications@github.com> Mon, 17 December 2018 04:13 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 6D8921286E7 for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 20:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 ZOQngX5cuCmY for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 20:13:45 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDCCC1200D7 for <quic-issues@ietf.org>; Sun, 16 Dec 2018 20:13:44 -0800 (PST)
Date: Sun, 16 Dec 2018 20:13:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545020023; bh=zHEvjXzKAR5f+/hP1RYNEAgFJWVzEp0frexxC0Nh8IU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TSTIt5VFZ03P/vxndzmOtnGDMuYJ1iipUl1V6Zfct3bqOczcdzhGb8gJzRoTcpIJo Qu1DYfn3j4qL68yPh8UMfameScglh7+cjkQ+yHyDqlpnKYJCJIid/t/v6b0IYnF3Xc HXN8RQ8QHfA5Vq5SualF06IgE+C7/IsSk1li95aQ=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf71cd646fee73dc38e39b83abaa6b8f629f7cee592cf00000001182ee47792a169ce169ea713@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1990/447717598@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1990@github.com>
References: <quicwg/base-drafts/issues/1990@github.com>
Subject: Re: [quicwg/base-drafts] encoding of CONNECTION_CLOSE reason phrases (#1990)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c17227797aec_702d3fe0616d45bc1743b3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/2M4fcjFnLNAv33f1o7EYENTGxcE>
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: Mon, 17 Dec 2018 04:13:46 -0000
I could see that some kind of text could be useful in debug more. But when running in production mode, I would just use the error code number, no text at all. If the error code is not precise enough, then we should create new error codes. The classic counter argument is that creating too many error codes provides information about the state of the stack that can be used by attackers. But then, adding explicit messages provides just as much information to attackers, so cannot possibly be better than adding more error codes... -- 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/1990#issuecomment-447717598
- [quicwg/base-drafts] encoding of CONNECTION_CLOSE… Marten Seemann
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… MikkelFJ
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Martin Thomson
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Kazuho Oku
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Marten Seemann
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Kazuho Oku
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… MikkelFJ
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Martin Thomson
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… MikkelFJ
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… janaiyengar
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Kazuho Oku
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Kazuho Oku
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… MikkelFJ
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Lars Eggert
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Lars Eggert
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… MikkelFJ
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Dmitri Tikhonov
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… ianswett
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… martinduke
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Mike Bishop
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… janaiyengar
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Christian Huitema
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Martin Thomson
- Re: [quicwg/base-drafts] encoding of CONNECTION_C… Martin Thomson