Re: [quicwg/base-drafts] Allow servers to omit version negotiation in response to 0-RTT packets. (#1758)

Mike Bishop <notifications@github.com> Tue, 25 September 2018 21:09 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 77EEA130DC6 for <quic-issues@ietfa.amsl.com>; Tue, 25 Sep 2018 14:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.455
X-Spam-Level:
X-Spam-Status: No, score=-8.455 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 Up7QY-bDeRcf for <quic-issues@ietfa.amsl.com>; Tue, 25 Sep 2018 14:09:41 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 832C2126BED for <quic-issues@ietf.org>; Tue, 25 Sep 2018 14:09:41 -0700 (PDT)
Date: Tue, 25 Sep 2018 14:09:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537909780; bh=2nt5T5tRkIKnp8dUHrXkzShVegdD5RmfKf2jKdmUhdQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QUFlSnvKoTAuXVyQwje9CL5L6urnuIIn/nb/l9BY5/pzDXcn9+c9CluXOZCH3vkGC 5glAlZBesMQ5iE13Of4MSvR1E2J++7VJ6Bi7/G+RLQNTC28rZZO24gWry9uVRCc7CW QiEQJQpLqi0/Im7r23sDR8dSfhpZUCFzbQnc9mvI=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfc9dbca1f54bdfab2d2fda655a3fc7c05788a27d92cf0000000117c2661492a169ce1584906c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1758/c424502413@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1758@github.com>
References: <quicwg/base-drafts/pull/1758@github.com>
Subject: Re: [quicwg/base-drafts] Allow servers to omit version negotiation in response to 0-RTT packets. (#1758)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5baaa41445c82_35653ff8710d45b8106376"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/46HvsEAsvLix3vbd3c2jcJeazNY>
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: Tue, 25 Sep 2018 21:09:44 -0000

This is a corner-case of a corner-case.  In the general case, if you don't recognize the client's proposed version, you have to send VN because you can't interpret anything about it and the spec says that you SHOULD NOT try.  But here, you know the version you've received well enough to know what packet types you don't want to send VN in response to, but you don't actually speak that version.  To me, that sounds like a version that's been deprecated for security reasons; outside of that, you either know a version or you don't.

I'd agree with Martin, the right framing here is that servers aren't required to send VN in response to every packet, but are allowed to use heuristics to limit the number they send.  That could be based on packet type if it knows but refuses to speak the version, or by having a short-lived cache of client IP/ports to which you've recently send VN packets, etc.

-- 
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/1758#issuecomment-424502413