IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify Actions on nonzero Reserved Bits (#2280)

martinduke <notifications@github.com> Thu, 10 January 2019 16:11 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 BDC1E130DE7 for <quic-issues@ietfa.amsl.com>; Thu, 10 Jan 2019 08:11:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level:
X-Spam-Status: No, score=-7.553 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 Ggp9gf4Vewa0 for <quic-issues@ietfa.amsl.com>; Thu, 10 Jan 2019 08:11:54 -0800 (PST)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187A9126CB6 for <quic-issues@ietf.org>; Thu, 10 Jan 2019 08:11:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=JhD+/npj6bEiOXhUjXAGdAeECps=; b=YXJFu8Eobrb3Rp/d DgrcratTM1mRtlNYTnqp+rM1Gt500jw9fvfdQjJHT98M9S/8WOWb01ppEoDmmcxa I07s69jNUDxMOdOrhAa0eaivZZ6ptfKHyxfJPjZV6ySoqcYghUh0ma+2eGwwEwhd eanFchTGLxbowRe6pVj6YtqhrA0=
Received: by filter1715p1mdw1.sendgrid.net with SMTP id filter1715p1mdw1-21576-5C376EC8-1B 2019-01-10 16:11:52.476356056 +0000 UTC m=+224823.497288493
Received: from github-lowworker-97d0962.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0036p1iad2.sendgrid.net (SG) with ESMTP id Cw1X0flTQKaKg3BDx9cpWw for <quic-issues@ietf.org>; Thu, 10 Jan 2019 16:11:52.574 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-97d0962.cp1-iad.github.net (Postfix) with ESMTP id 896C580050 for <quic-issues@ietf.org>; Thu, 10 Jan 2019 08:11:52 -0800 (PST)
Date: Thu, 10 Jan 2019 16:11:52 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1203c0efbb4c09ad6a5f724e17af4d19836f108992cf00000001184f30c892a169ce178a377a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2280/c453152955@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2280@github.com>
References: <quicwg/base-drafts/pull/2280@github.com>
Subject: Re: [quicwg/base-drafts] Clarify Actions on nonzero Reserved Bits (#2280)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c376ec887d07_16803fc8a92d45b8240223"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0zsDGRXScq6ZIT3KQFqYQ8z73jtu/XYFdMs/ p7WIoc00CzPOUKgz97Gd6GtmyzzK96yF3D9Pli+/KxfeNG0QhKl+EJZhs2XRPAd7cuO+A4zHsQ7955 YgBx+Nl3IFTFVAnkkU5YxK8A64sFgxZ065eh+crXPms50zRWXtn9kK/fbkR5sx/O6ueF5qZjaiiEbL g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7jLF-rYEuxuy5y5xZVF9oSsi44w>
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, 10 Jan 2019 16:11:56 -0000

@ianswett My previous reply was too glib. One problem with applying the check right after removing header protection is that the consequences are a connection error -- so a garbage packet has a 3 in 4 chance of taking down the connection.

There are three equilbria here:
1) Simply discard the packet after header protection. As @marten-seemann pointed out, it's not clear why this would provide any sort of intelligence to an attacker, as there is no response.
2) After packet protection, it's a PROTOCOL_VIOLATION. This is the current state of the draft with this PR serving to clarify a bit.
3) Not having any requirement for the reserved bits. There is a difference in opinion over whether this is a side channel issue or not, or if this should be done only with some sort of negotiation. I'm not the one to articulate this positon.

Which is all to say that I should have taken @martinthomson 's advice a week ago and filed and 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/pull/2280#issuecomment-453152955

v2.23.0 | Report a Bug | By Email