IETF Logo Mail Archive

[quicwg/base-drafts] Handling of PRIORITY Frame Empty bits (#2533)

martinduke <notifications@github.com> Wed, 20 March 2019 20:15 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 E54071310C1 for <quic-issues@ietfa.amsl.com>; Wed, 20 Mar 2019 13:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 O2dm1NxCRQjd for <quic-issues@ietfa.amsl.com>; Wed, 20 Mar 2019 13:15:48 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38C3B1310AB for <quic-issues@ietf.org>; Wed, 20 Mar 2019 13:15:48 -0700 (PDT)
Date: Wed, 20 Mar 2019 13:15:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553112947; bh=sWTekR6ckB4Io5yDFpo2J6wAFIF+q3W7rwQcb5fLmXE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Zd+fduYXUJEo/UVER574uW6jDaqyfEc15FK+zq9mkVRljZ7SxUc2p+Q+VLvOHTJBd J02ieQeQ6ykT0kqAQ7gRGomd24OiolWNy8dKNk3sSDkB+1WDl7tSQExQLhzJp2KNOd jX23UX55YpBhh95EXdwZdyOhHQNgXxswB9vt6AII=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba2c4ee809ff5d2c8645473e7aa18e1d07add03f292cf0000000118aa617392a169ce193d5dd3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2533@github.com>
Subject: [quicwg/base-drafts] Handling of PRIORITY Frame Empty bits (#2533)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c929f732b941_48b83fa7c82d45c41160e0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/Cl9qG5bSXTVzmZT7-XZr2J4Ws0g>
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: Wed, 20 Mar 2019 20:15:50 -0000

PR #2501 kicked up a bit more controversy than expected, so I'm opening an issue. Currently he Empty bits it the PRIORITY frame MUST be zero and MUST be ignored by the receiver.

In most other areas, we're killing connections for this kind of violation. Then again, HTTP/3 is a different protocol from QUIC.

What do people think?

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

v2.23.0 | Report a Bug | By Email