Re: [quicwg/base-drafts] encoding of CONNECTION_CLOSE reason phrases (#1990)
Marten Seemann <notifications@github.com> Mon, 12 November 2018 06:48 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 7A818130DDB for <quic-issues@ietfa.amsl.com>; Sun, 11 Nov 2018 22:48:40 -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 S6wSh9qfljvW for <quic-issues@ietfa.amsl.com>; Sun, 11 Nov 2018 22:48:39 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B0E12D4EB for <quic-issues@ietf.org>; Sun, 11 Nov 2018 22:48:38 -0800 (PST)
Date: Sun, 11 Nov 2018 22:48:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542005318; bh=+2DHs6aXM2fGlFiAHBOaHMTI4D/6FtTOdMml4WUfdbA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OEW16fhheld1IzxbJT8ESc7X16PEWvPe0SjlllTNxRYxC2PFPfqibQW47RY8mJmVH g1+34eKfJDCRPslZJsjYS8wNFRxy65FSaxedBtq+klUJffAbsAJiuOh0RaVqaTKGsF QxpS11bUO78pm0dYB/A7jT47yltX1I8n/kWbLIzU=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6bd74ede09f854f48cff1cb3a51b9ef03f97940792cf000000011800e44692a169ce169ea713@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/437774510@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_5be92246379b_15f23fab0c2d45b4427736"; 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/V-KotoEPT_AlnQYEl-yKQdun02k>
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, 12 Nov 2018 06:48:41 -0000
I agree that this is purely for debugging, and should probably never be displayed to the user, so I18n shouldn't be an issue. Is there any reason not to require this to be UTF-8 though? I think it would help debugging interoperability testing (and error logging) if you can rely on the charset. -- 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-437774510
- [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