IETF Logo Mail Archive

Re: [quicwg/base-drafts] Change max_packet_size to max_datagram_size (#3471)

martinduke <notifications@github.com> Fri, 21 February 2020 17:24 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 05269120147 for <quic-issues@ietfa.amsl.com>; Fri, 21 Feb 2020 09:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 6WAWiKRmGdw7 for <quic-issues@ietfa.amsl.com>; Fri, 21 Feb 2020 09:24:44 -0800 (PST)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D0D1200CC for <quic-issues@ietf.org>; Fri, 21 Feb 2020 09:24:44 -0800 (PST)
Received: from github-lowworker-5fb2734.va3-iad.github.net (github-lowworker-5fb2734.va3-iad.github.net [10.48.19.27]) by smtp.github.com (Postfix) with ESMTP id 553392806E2 for <quic-issues@ietf.org>; Fri, 21 Feb 2020 09:24:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582305883; bh=Z8WmundcmIv8HkC7bq39y+PZkgBmOfL8NPvUHuHgBdQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R7al9eH814dxMrEN2FY3eOrfOCyv45jDFwozSw7AZj/4YGog8RRCTW0GW05P3D95U J8NAgsYXehRjtQY0Njifyd1lUcPZagXLtIRk3Mv2F4P2QVC1pI1v5o6aJ1DQzHAjgO Z7kPkT5GyShu++brUAXLydffmZqAeeUowE+0xe9g=
Date: Fri, 21 Feb 2020 09:24:43 -0800
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3WYO5S5WRBHO4I2H54LVCNXEVBNHHCDYABKU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3471/589751586@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3471@github.com>
References: <quicwg/base-drafts/issues/3471@github.com>
Subject: Re: [quicwg/base-drafts] Change max_packet_size to max_datagram_size (#3471)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e50125b45578_1f333f9ca84cd964128262"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/BO6z-ku2ivVZe9wicuP1zbUNj3s>
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: Fri, 21 Feb 2020 17:24:46 -0000

@martinthomson I always assumed this was the equivalent of the TCP MSS option, rather than something to do with AEAD. Even if we decide to do nothing else, we should probably add some more text about what this is communicating and how to set it. But now the last sentence about unprotected packets make sense, so thanks for the insight.

But it seems we're converging on a TCP MSS-like purpose instead.

-- 
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/3471#issuecomment-589751586

v2.23.0 | Report a Bug | By Email