Re: [quicwg/base-drafts] encoding of CONNECTION_CLOSE reason phrases (#1990)

janaiyengar <notifications@github.com> Thu, 15 November 2018 04:00 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 A08471277D2 for <quic-issues@ietfa.amsl.com>; Wed, 14 Nov 2018 20:00:57 -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 UrR9baZGx-pA for <quic-issues@ietfa.amsl.com>; Wed, 14 Nov 2018 20:00:55 -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 611B212426A for <quic-issues@ietf.org>; Wed, 14 Nov 2018 20:00:55 -0800 (PST)
Date: Wed, 14 Nov 2018 20:00:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542254454; bh=QTIx1r2gj71rV505aBemkJGmaRK7IB2XamWaXbIOlhI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lHZg9UN1+kY4u7L+HM0xUd16TB9eh325wfYF0Cabnk4ZAr2Ne5NP0mwumBtACMqxE JalvHXW32O9AIhr5bRddCY/KWgkts59xU7OyBMqiaOdC6IRxm89FLOdS/k/YSZLyrk Sw+HlyiBCD956JKzMuirJbnToUEqzsFQgbRy5uOU=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abefc26d5738f98051a343e46732ddd451a0d004fa92cf000000011804b17692a169ce169ea713@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/438909280@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_5becef76330af_4a643fbae30d45c017851b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/W8CFZrPc3WNP7F_3LOByhYjxZ7Q>
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: Thu, 15 Nov 2018 04:00:58 -0000

(I do think the protocol is in English and Binary. The protocol is not only
what's on the wire, it's also what to do with the bits, and that's the RFC.
I'll concede that there can be translations though.)

On Wed, Nov 14, 2018 at 1:40 AM Mike Bishop <notifications@github.com>
wrote:

> @janaiyengar <https://github.com/janaiyengar>, the protocol isn't in
> English, it's in binary. The RFC is in English, but that doesn't mean there
> won't be translations later. (E.g. RFC7540 in Chinese
> <https://github.com/abbshr/rfc7540-translation-zh_cn>)
>
> This is ultimately useful for the developer of the implementation emitting
> it, so they know what language to expect there. The key requirement for
> everyone else is something easy to log and relay back to that developer,
> and I think UTF-8 is our best option there. I'd support MUST UTF-8.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1990#issuecomment-438418928>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AKjg1KgJ8senerh3wILBYg-bsM2BMbBHks5uuycygaJpZM4YYWmQ>
> .
>


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