Re: [quicwg/base-drafts] When to send Version Negotiation (#1038)
Martin Thomson <notifications@github.com> Mon, 08 January 2018 04:11 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 694091270A3 for <quic-issues@ietfa.amsl.com>; Sun, 7 Jan 2018 20:11:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 EN6P_-k4M3QZ for <quic-issues@ietfa.amsl.com>; Sun, 7 Jan 2018 20:11:04 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 94544126C83 for <quic-issues@ietf.org>; Sun, 7 Jan 2018 20:11:04 -0800 (PST)
Date: Sun, 07 Jan 2018 20:11:03 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1515384663; bh=OlYjzoy4xx19xv04+ygoIpd572I5BC/1cGKyUoKt9b0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZF6Ub8OM2Z3T+Ez9Ej5Iu6MVSJaePeXfMoSd709XWkx71awaLpWzNnKUoQy80zORv 31fjkcECxAukLgOj0FYoqnvV+MR2BQwap2wjrqGzWzgpAuV+q/yjur7kanpPp2DcxX rJ9bmmWQkZZQbBjZq33wolN6VaXvBZOIS5R4/EtQ=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2f5f1dfb96ccb4e97556ee69beb33f74bdb6ceab92cf00000001166ab15792a169ce1115b3ed@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1038/355881449@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1038@github.com>
References: <quicwg/base-drafts/issues/1038@github.com>
Subject: Re: [quicwg/base-drafts] When to send Version Negotiation (#1038)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a52ef57a6a9c_310a3f9e350faf3867101"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/FgcU7t0La3SkpW59sWo1Yx_i1GY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 08 Jan 2018 04:11:06 -0000
I think that I would rather not do the second option here. The text could be clearer, but the intent was to have Version Negotiation triggered by any packet that might initiate a new connection. What that packet looks like will vary between versions, so I don't think we can specify a single type. I prefer making this text from Section 7.1 clearer: > For servers, packets that aren’t associated with a connection potentially create a new connection. However, only packets that use the long packet header and that are at least the minimum size defined for the protocol version can be initial packets. That is, if the packet uses the long header AND it is at least big enough to initiate a connection with any version that the server supports, then Version Negotiation SHOULD be sent. I use "SHOULD" only because of the caveats regarding rate limiting. -- 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/1038#issuecomment-355881449
- [quicwg/base-drafts] When to send Version Negotia… martinduke
- Re: [quicwg/base-drafts] When to send Version Neg… Martin Thomson
- Re: [quicwg/base-drafts] When to send Version Neg… martinduke
- Re: [quicwg/base-drafts] When to send Version Neg… Martin Thomson