IETF Logo Mail Archive

[quicwg/base-drafts] Actions to take when Reserved Bits are not Zero (#2329)

martinduke <notifications@github.com> Thu, 10 January 2019 16:20 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 B9F1B130E6D for <quic-issues@ietfa.amsl.com>; Thu, 10 Jan 2019 08:20:00 -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 Gs9pi3KEFJ1O for <quic-issues@ietfa.amsl.com>; Thu, 10 Jan 2019 08:19:59 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 9A0DD130E6B for <quic-issues@ietf.org>; Thu, 10 Jan 2019 08:19:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Pn7Ncc3D53lPQyHqUC5aXMRW/JA=; b=kx0/2fJPtqMLs6ve wOtoc2yWWL81OwJtOb8rrlzJ6azSXcHA/nf2eIzMvxrstWG+bWF03n4rTWzZFr4a n0XxbeJv0/JMpuEGdL/cbEC+J5roD28G9T39mpjvSjRO42MWQ4u8bP0L4KL72qOT Opvx/9SDUYz4Q01mNtoLn4x77lo=
Received: by filter1660p1mdw1.sendgrid.net with SMTP id filter1660p1mdw1-12116-5C3770AD-20 2019-01-10 16:19:57.614779882 +0000 UTC m=+225642.821352627
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0031p1iad1.sendgrid.net (SG) with ESMTP id lZh98PyOQRSdysK42ctmNA for <quic-issues@ietf.org>; Thu, 10 Jan 2019 16:19:57.633 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id 875F72C0D4D for <quic-issues@ietf.org>; Thu, 10 Jan 2019 08:19:57 -0800 (PST)
Date: Thu, 10 Jan 2019 16:19:57 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab92be49c0f773cde7dc589bf25bc4794565daa67892cf00000001184f32ad92a169ce17b7938d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2329@github.com>
Subject: [quicwg/base-drafts] Actions to take when Reserved Bits are not Zero (#2329)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3770ad85c81_7c673f84160d45c4255787"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0BYyiurNjVL62eL9hhwWS27OhblTHxa8+fud JEJKYqcnt6apUQbQ+0hX0ZMDWFd+H+10yVZeApEUmWcelQ0IkvX7MDpsbYcFyUr3tIql9D1oVcqy5u WhSEVNVIy0U19tepMeQ3rF/4hMvOwcx5GRTv2dvjQQjvmVOIn++WjM0TsKmTUE4NUxFr1PRKzrcslu 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8VOUlhPf_qVgst3q96TveW4u8DE>
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:20:01 -0000

A few weeks ago I filed PR #2280 to clarify things a bit. The discussion suggests there is not much consensus. There are three possible equilibria for how to handle nonzero reserved bits:

1) The spec currently says it's a PROTOCOL_VIOLATION. This must occur only after packer protection is removed; after only header protection, 3 out of 4 garbage packets would meet the condition to take down the connection.
2) Alternatively, we could discard the packet after header protection. This is computationally cheaper. There is some concern about consistent decryption time, but as @marten-seemann pointed out if we simply discard there is no response for the attacker to measure.
3) The other choice is to allow senders to do anything with these bits, but that possibility was decisively rejected in #2022 and we shouldn't reopen settled issues in the absence of new information.

-- 
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/2329

v2.23.0 | Report a Bug | By Email