Re: [quicwg/base-drafts] Do we need to define a maximum packet size? (#383)

ianswett <notifications@github.com> Mon, 13 March 2017 13:13 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 F0C3D1295F4 for <quic-issues@ietfa.amsl.com>; Mon, 13 Mar 2017 06:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.383
X-Spam-Level:
X-Spam-Status: No, score=-0.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 tRj9pYFcJr3d for <quic-issues@ietfa.amsl.com>; Mon, 13 Mar 2017 06:13:08 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91F161295FA for <quic-issues@ietf.org>; Mon, 13 Mar 2017 06:13:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=K18EISew/K2TcYDFZy4amBWa7EQ=; b=aT4MPCXRQWDFG8bL kEA+bWLTZo9ZvhZ9iO0MqJvLfGeL4wlroMogUCS6tdmml0NT18b9/tCk4qcEU352 BHypGtUTqhyI5AuPmEI8UeIrA8GcAGUfc94wtIqm5Q2YehK+TzXXdfKr+pTRBxKT Oau+lTn+w+tZK8PWkzkkJSssP78=
Received: by filter1111p1mdw1.sendgrid.net with SMTP id filter1111p1mdw1-12492-58C69AE2-25 2017-03-13 13:13:06.343104178 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id N1kJHXFPR9y9jRakZ-g4vA for <quic-issues@ietf.org>; Mon, 13 Mar 2017 13:13:06.272 +0000 (UTC)
Date: Mon, 13 Mar 2017 06:13:06 -0700
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/383/286102911@github.com>
In-Reply-To: <quicwg/base-drafts/issues/383@github.com>
References: <quicwg/base-drafts/issues/383@github.com>
Subject: Re: [quicwg/base-drafts] Do we need to define a maximum packet size? (#383)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58c69ae22a015_6da23fde4192dc2c369514"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0LZKCVkl55hNlfFwAeQUtkKRsJKh8XFbK5t0 84qdzDLlFgJ5rOWNnvr6+ECYxS2UORjqvtHZx10oqB/tFBtYiwQ6mMAOAu/oVDwgB8qD0T2r6P4xit 3BIf7aI2MiIvE3vb96nKBAviiInmHljxEvUEDbQ/CAog9Vmp1j+NazPd/jTQy/AAB4w+o2FeaQ5tPv Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eVKugbspCTydnKZthxMVUaPdeLk>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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, 13 Mar 2017 13:13:10 -0000

It may be nice to signal MSS, but this could only be the endpoint value, unless one of the peers had particularly good knowledge of the path.  So I'd suggest a handshake negotiated value, to the min of the two peers, since it's assume the max endpoint size is the same for sending and receiving.

-- 
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/383#issuecomment-286102911