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

ianswett <notifications@github.com> Thu, 21 March 2019 02:03 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 05A6A129524 for <quic-issues@ietfa.amsl.com>; Wed, 20 Mar 2019 19:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 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_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: 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 Hyk17XlK02NN for <quic-issues@ietfa.amsl.com>; Wed, 20 Mar 2019 19:03:42 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C8F91277E7 for <quic-issues@ietf.org>; Wed, 20 Mar 2019 19:03:42 -0700 (PDT)
Date: Wed, 20 Mar 2019 19:03:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553133821; bh=Hr4brSSd0FfkLiM5ur6TDBRwKhEtkJ+PKpdY/tkqHPs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hFLfk4pqREmnkHPktHarV/wtKLkyWFDveYwNPKh5bIsjYrxfWWZXg/LIIKCx+1jnE cJPsz3bVW0iQMQ2G12reoWvDUItFVIdHtIEwqlAE4v3bEkkXkRX9fEh+Cnj53BJb6o azX2L0mBErPwoEXNbvRfQRbdlBz3DZ8BIzRZnr2Q=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abedeea1a829d078d8a71dd38178223b5c7179e30f92cf0000000118aab2fd92a169ce180fd1a3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2377/475091450@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2377@github.com>
References: <quicwg/base-drafts/issues/2377@github.com>
Subject: Re: [quicwg/base-drafts] Crypto Frames/Packets Aren't Blocked by CC (#2377)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c92f0fd855ed_60e93f995b4d45c0415258"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/UwUm1lrPZd4xL2QPvFq-PG6vGs8>
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: Thu, 21 Mar 2019 02:03:44 -0000

To clarify, there are no exceptions for TLS data in TCP, correct?  If so, I'd suggest we not make exceptions for CRYPTO frames in QUIC unless we have evidence this is an issue.

-- 
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/2377#issuecomment-475091450