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

Lucas Pardue <> Wed, 20 March 2019 22:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8EF241311C4 for <>; Wed, 20 Mar 2019 15:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cKUEk6pOQ36Q for <>; Wed, 20 Mar 2019 15:48:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C48DA131212 for <>; Wed, 20 Mar 2019 15:48:19 -0700 (PDT)
Date: Wed, 20 Mar 2019 15:48:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1553122098; bh=eqQB0BJtl6XERWkGxCJXXUI0hRg40xEZq4wteggIN9g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=X3Km4S+fyftPA2Xa0sjRZSdSxEmNnzccAFa0cFdR4OdtO7SitiMq9fkBZywQfEy7q ZO73v3JfSnKLvBqGkYwlI+7VlSMid+CNm59iEVh6+lVgV3RbIoNgFXPEmKywtK6je7 CVkma3POeiH7LNANnOYlAD7jasM+sZqfmTGlWvG8=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2533/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Handling of PRIORITY Frame Empty bits (#2533)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c92c3329dc0e_4f9f3fb4f66d45bc523123"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Mar 2019 22:48:21 -0000

Looking back to HTTP/2, it had this to say about in-frame PADDING in DATA frames.

> Padding octets that contain no application semantic value.
      Padding octets MUST be set to zero when sending.  A receiver is
      not obligated to verify padding but MAY treat non-zero padding as
      a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: