Re: [quicwg/base-drafts] allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame (#3186)

ianswett <> Tue, 05 November 2019 19:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F19B01209C0 for <>; Tue, 5 Nov 2019 11:02:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 0l-bxF_avn23 for <>; Tue, 5 Nov 2019 11:02:42 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 35E0C12088E for <>; Tue, 5 Nov 2019 11:02:13 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 58AFDC60507 for <>; Tue, 5 Nov 2019 11:02:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572980532; bh=et/++tLRAcH/4aaAbI+uGujuQnJMtBPqw3d2k6Ew90Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OWCQPs5CCfYcRSHUs4oLGwsNe8HJzd51/lUEhjPtZqSpEJGoBJOsTukEv7T5RgW3P DEk6uUNfodBaaKsnmsB9XGcrAEEKy4lZFGNMnvzUqHQBfQzEr5oYJs48x3YP7SptVJ 1rzpf1wJPsClkHRtbxi1qMlxsFjpEtk5YqSWqVCg=
Date: Tue, 05 Nov 2019 11:02:12 -0800
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3186/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame (#3186)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc1c73449bc3_22e3fcce4ccd9682471b4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Tue, 05 Nov 2019 19:02:44 -0000

I think we should either:
1) Espouse a new principle that fits the existing text and this PR and use that going forward 
2) Stick with the original principle and remove the OR FLOW_CONTROL_ERROR from the text.

If we don't have a principle that matches the text, we're prone to having this discussion a few more times.

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