IETF Logo Mail Archive

Re: [quicwg/base-drafts] Core terminology in QPACK (#3520)

Martin Thomson <notifications@github.com> Mon, 20 April 2020 05:30 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 D7B563A101D for <quic-issues@ietfa.amsl.com>; Sun, 19 Apr 2020 22:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.152
X-Spam-Level:
X-Spam-Status: No, score=-0.152 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.048, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 ZN7nv7mvvvsW for <quic-issues@ietfa.amsl.com>; Sun, 19 Apr 2020 22:30:44 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93713A1024 for <quic-issues@ietf.org>; Sun, 19 Apr 2020 22:30:44 -0700 (PDT)
Received: from github-lowworker-56fcc46.va3-iad.github.net (github-lowworker-56fcc46.va3-iad.github.net [10.48.102.32]) by smtp.github.com (Postfix) with ESMTP id 07C3B5201F6 for <quic-issues@ietf.org>; Sun, 19 Apr 2020 22:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1587360644; bh=mwHumcKfkN0RP8ltqaUpkAVxFFe6t4JyFtpo630QkeE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jq4KzAgN9zU4jKmbxZa25/IFb6Im2jUw+4CFgaQ0FlchF0SmBTRkBlitrWotSVkwl ZUslrMNd73Xj3hfMd1cTT/VDNQducES5oBJohkPUGhv1rvrKg07Th8gQBglR0E+4u8 3U+dgD6+phygE1h1fBPbSyCV1a/LgcyCTrE5W9sk=
Date: Sun, 19 Apr 2020 22:30:43 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ2CSQ2SOTXUQMO52V4VEKIHEVBNHHCFHBAYE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3520/c616320081@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3520@github.com>
References: <quicwg/base-drafts/pull/3520@github.com>
Subject: Re: [quicwg/base-drafts] Core terminology in QPACK (#3520)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e9d3383ed4c6_6f913fec6c2cd95c10509e1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/k35KYmv9ttBfSV-iO9qeBxdvJsc>
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, 20 Apr 2020 05:30:46 -0000

@MikeBishop, are you going to take up the task of explaining how various colloquialisms map to the weird formal terms we end up using?

-- 
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/pull/3520#issuecomment-616320081

v2.29.0 | Report a Bug | By Email | System Status