Re: [quicwg/base-drafts] Crypto Frames/Packets Aren't Blocked by CC (#2377)

Subodh Iyengar <> Wed, 30 January 2019 01:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 644311310BC for <>; Tue, 29 Jan 2019 17:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Status: No, score=-10.935 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_24=1.618, 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 Oal02FrW97Sw for <>; Tue, 29 Jan 2019 17:28:43 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E3C801310B3 for <>; Tue, 29 Jan 2019 17:28:42 -0800 (PST)
Date: Tue, 29 Jan 2019 17:28:41 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548811721; bh=T16w3ArqrCRim2iq3Ts3JY5TO9y78jeMZPAmIfLY9/8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UFABi1vrBxA6snXWeZSOaRhX6sOcrNGjuw7cDcML/UJhL1V6H66rx0RzKLgmVh8sx SohVjFx7zd8bcw2cDxWhx3PRbzucxq8yveV7aRdrVNBIsMZqgPRtUOVsJxWVUMSooL 3TNpaaPTWXxPYK0k5KmTe4IVeEzYtGGe8l5OyNyA=
From: Subodh Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2377/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Crypto Frames/Packets Aren't Blocked by CC (#2377)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c50fdc9c1d31_4d13ff0ae8d45bc1052d1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
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, 30 Jan 2019 01:28:45 -0000

I think it just makes it easier to make crypto subject to the same cc algorithm vs making a special case for it in this way. Why would it matter if crypto is limited by CC?

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