IETF Logo Mail Archive

Re: [quicwg/base-drafts] Why does stateless reset have to be checked after MAC failure (#2152)

ekr <notifications@github.com> Thu, 13 December 2018 21:05 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 7B55E130E9A for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 13:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Level:
X-Spam-Status: No, score=-4.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 ZhlvIWtCJXfd for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 13:05:40 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 2A4D1130E95 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 13:05:40 -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=lka2RGgONB7dt49CnlQHAqlbT8k=; b=f9JNPBsL+wp6zTSo hexMdqvGDEE66EeSQsGXtrW+g6abFsvUToiEhC7kaBsueH3wogSeffRQHvGdbCvC o6qJRgCrDfKI0qLgTK9UWZegnMmGKLCZcaXM3tI3MwYR+/X+sGaT1NarICr6Ehry EY6Bg7d8jxfXuJV+zpxm69VMVgw=
Received: by filter0534p1iad2.sendgrid.net with SMTP id filter0534p1iad2-10513-5C12C9A1-33 2018-12-13 21:05:37.968627292 +0000 UTC m=+250552.635062953
Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0031p1iad2.sendgrid.net (SG) with ESMTP id NFyXp2UnR5qxlTRkxYZJDQ for <quic-issues@ietf.org>; Thu, 13 Dec 2018 21:05:37.962 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id E0BB0C00D3 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 13:05:37 -0800 (PST)
Date: Thu, 13 Dec 2018 21:05:38 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab49e23124d35187dbcdc556e02cf98aa20616269d92cf00000001182a8ba192a169ce174b967d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2152/447120346@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2152@github.com>
References: <quicwg/base-drafts/issues/2152@github.com>
Subject: Re: [quicwg/base-drafts] Why does stateless reset have to be checked after MAC failure (#2152)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12c9a1dc701_5c613ff2036d45b855422"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3Aa+ieJTJhytwXDNCf/DGUhwE9CncRJMHW1B f1BM7OZf+mzrbcA1uyKY9hOqAkrALzHnu2nfT0aHD4FhxiLtthNqUy0XlhwwEqyk3J9Y32/nR2L1i7 D6R098n6vDx+7WJ42Oqa1zeXm38gnEVUq7sM9cY9Rj+tbfyn0G5qoOs4aw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/M3zrSl5_3--P3Ck1E_w5VY6hHzg>
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, 13 Dec 2018 21:05:42 -0000

Sure, but I have to get my other issues from my read-through in first.

On Thu, Dec 13, 2018 at 12:16 PM Mike Bishop <notifications@github.com>
wrote:

> I'm not sure the order is (intended to be) normative. An SR looks like a
> junk packet that you would otherwise drop, either because it doesn't match
> a known connection by CID, or because it happens to match a known CID
> (zero-length helps) but gives a whacko packet number compared to the
> connection state, or because the packet number looks reasonable but the MAC
> is bad.
>
> In those situations, you then have to decide whether it's just junk or
> actually a SR. So the order is what we expect a logical implementation
> would do, but not necessarily required. Can you propose better explanatory
> text for that?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/2152#issuecomment-447106218>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1oc052jJJFKds92ObK9YEXS8-ZQ84ks5u4rWwgaJpZM4ZSSuW>
> .
>


-- 
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/2152#issuecomment-447120346

v2.23.0 | Report a Bug | By Email