IETF Logo Mail Archive

[quicwg/base-drafts] What if a client sends a NEW TOKEN frame? (#2382)

Christian Huitema <notifications@github.com> Tue, 29 January 2019 02: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 701D01277BB for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 18:00:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.007
X-Spam-Level:
X-Spam-Status: No, score=-11.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, 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 4U6XqwGajThK for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 18:00:05 -0800 (PST)
Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0413C129B88 for <quic-issues@ietf.org>; Mon, 28 Jan 2019 18:00:05 -0800 (PST)
Date: Mon, 28 Jan 2019 18:00:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548727204; bh=HMGnMbvuesYTpe0jx9a3+jfM3VuuhhC/sJHaQwfHdnI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=oOD02gmn/uwegDgcIFwKk3Yr3j0D8OrOHHyo+hsW5GCKbxIae6Pi99Ty3wvWwsF/p ggK5kZ0RGMiel/8//1JajwYvojmlw6eS8hofDMlMK/TzQEWvEikUzIcLqBk4EC8R9y pFnkRAx2RgRxonh6oskJWVir/HCiamw5ifpAK+nw=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab02f9e92610a35aa080bde7a4b6c7095c5aebf8c192cf00000001186775a492a169ce1815e5d1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2382@github.com>
Subject: [quicwg/base-drafts] What if a client sends a NEW TOKEN frame? (#2382)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4fb3a4212bc_5fa3f8fb46d45c41954ad"; 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/4eZbexjaDBxvsRTwcrJYTTIcx3M>
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: Tue, 29 Jan 2019 02:00:07 -0000

Should the server just ignore it, or is is a protocol violation?

-- 
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/2382

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