Re: [quicwg/base-drafts] Client that does not PAD does not negotiate? (#4021)

Gorry Fairhurst <notifications@github.com> Tue, 25 August 2020 09:27 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 06DFD3A0BCB for <quic-issues@ietfa.amsl.com>; Tue, 25 Aug 2020 02:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.081
X-Spam-Level:
X-Spam-Status: No, score=0.081 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 FXykc5A2l5Nx for <quic-issues@ietfa.amsl.com>; Tue, 25 Aug 2020 02:27:17 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6B173A08FB for <quic-issues@ietf.org>; Tue, 25 Aug 2020 02:27:17 -0700 (PDT)
Received: from github-lowworker-5825cd4.ac4-iad.github.net (github-lowworker-5825cd4.ac4-iad.github.net [10.52.22.68]) by smtp.github.com (Postfix) with ESMTP id B2B415E01F3 for <quic-issues@ietf.org>; Tue, 25 Aug 2020 02:27:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1598347636; bh=ILwutyREbkGq5zyH2AtLjkMawSyDBp35We7cw7kWezA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CtSNR0yC45LeDFSOZamIiNNSplonGhWRYbt/dR+IcpI0MRBHxoC4YSgTn7Xk/9S2N wXS/RhLrF4dyqCy+Qw3n/f/gMiaIoEvegw/Z9zgnGfJCi+835Vy1lr+R/RkRRlA8uC 7IGKxU5PgjdijoZQRy0nQ9BtkZmlcuhU4zeqZmzM=
Date: Tue, 25 Aug 2020 02:27:16 -0700
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4GXMZSB5HKCUXZRQ55KC5HJEVBNHHCRJGOKE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4021/679913680@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4021@github.com>
References: <quicwg/base-drafts/issues/4021@github.com>
Subject: Re: [quicwg/base-drafts] Client that does not PAD does not negotiate? (#4021)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f44d974a360f_57f81964490ba"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
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/DlglF5tBYQ-DrZQZe1Eur3TWMFQ>
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 Aug 2020 09:27:19 -0000

So if this confused me (a little), I am assuming it could confuse others, so one way to make this clear is add a sentence (albeit a little long) after the SHOULD in section 6 that says what happens and explicitly includes a forward ref to Section 14.1 i.e.

AFTER THIS CURRENT TEXT:
   “The size of the first packet sent by a client will determine whether
   a server sends a Version Negotiation packet.  Clients that support
   multiple QUIC versions SHOULD pad the first packet they send to the
   largest of the minimum packet sizes across all versions they support.
   This ensures that the server responds if there is a mutually
   supported version.”


ADD SOMETHING LIKE:
    "If a client sends an Initial packet (see section 14.1) less than the smallest allowed
 packet size for the version of QUIC supported at the server 
(e.g., when this size is not permitted by the local interface), 
the server would not reply with a Version Negotiation packet and the connection attempt will time out.



-- 
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/4021#issuecomment-679913680