[quicwg/base-drafts] Include max_udp_payload_size in packet size discussion (#3651)
Martin Thomson <notifications@github.com> Wed, 13 May 2020 00:51 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 6409A3A0B0F for <quic-issues@ietfa.amsl.com>; Tue, 12 May 2020 17:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.268
X-Spam-Level:
X-Spam-Status: No, score=-3.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.173, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 pEIzqdrgw0je for <quic-issues@ietfa.amsl.com>; Tue, 12 May 2020 17:51:57 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0358F3A0B0A for <quic-issues@ietf.org>; Tue, 12 May 2020 17:51:56 -0700 (PDT)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id 159D46A07E0 for <quic-issues@ietf.org>; Tue, 12 May 2020 17:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1589331116; bh=fr1Qd4rMpwMv/pBvoy+14S01AcfcsoekKmZFKLKmPUg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=EJMNSWhkRww5UdgI8G8CEEWu0h/rAEH/Jf/xJIE/qXSEY4kXsY7AHev2c1I9gw1vd UwjMTH+b84T1Nq0ORXTwHsgB7cnISeoVknVJ3iKtPVtUCFRLKk5cvXF4boqg2CDj4k t2WpNh+o5oQhdO7999D1oFujuMpyxgLO+UHX8McI=
Date: Tue, 12 May 2020 17:51:56 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ554AI4XE7JHM4JX54Y4S2ZEVBNHHCJR4Q6U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3651@github.com>
Subject: [quicwg/base-drafts] Include max_udp_payload_size in packet size discussion (#3651)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ebb44ac6ce1_49253fb7690cd9641582ad"; 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/_Tzqn-21NYe_gjeFhFHGQKYI36E>
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: Wed, 13 May 2020 00:51:58 -0000
This isn't a complete dissertation on how clients might choose to use larger packet sizes. In particular, it doesn't capture the whole discussion about starting at a higher size being a way to raise the 1280 to something higher, with the requisite cost being that you might have failures. Deciding to put that in would be much harder. What this does is just say that the transport parameter acts as a further limit on packet size and that you won't know that prior to knowing. That means that you are guessing about the network path AND your peer when you decide to send >1200 (to be fair, the former really only applies for IPv4, and it's not much of a guess). Closes #3638. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/3651 -- Commit Summary -- * Include max_udp_payload_size in packet size discussion -- File Changes -- M draft-ietf-quic-transport.md (28) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/3651.patch https://github.com/quicwg/base-drafts/pull/3651.diff -- 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/3651
- [quicwg/base-drafts] Include max_udp_payload_size… Martin Thomson
- Re: [quicwg/base-drafts] Include max_udp_payload_… ianswett
- Re: [quicwg/base-drafts] Include max_udp_payload_… Marten Seemann
- Re: [quicwg/base-drafts] Include max_udp_payload_… Jana Iyengar
- Re: [quicwg/base-drafts] Include max_udp_payload_… Jana Iyengar
- Re: [quicwg/base-drafts] Include max_udp_payload_… Jana Iyengar
- Re: [quicwg/base-drafts] Include max_udp_payload_… Martin Thomson
- Re: [quicwg/base-drafts] Include max_udp_payload_… Martin Thomson