Re: Space for Packet Metadata

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 28 February 2018 16:07 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5768912DB6B for <quic@ietfa.amsl.com>; Wed, 28 Feb 2018 08:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 ZkkhDWjus7L3 for <quic@ietfa.amsl.com>; Wed, 28 Feb 2018 08:07:25 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id B0B3D124B17 for <quic@ietf.org>; Wed, 28 Feb 2018 08:07:25 -0800 (PST)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 022CB1B00056; Wed, 28 Feb 2018 16:06:49 +0000 (GMT)
Message-ID: <5A96D399.4010300@erg.abdn.ac.uk>
Date: Wed, 28 Feb 2018 16:06:49 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Nick Banks <nibanks@microsoft.com>
CC: "Eggert, Lars" <lars@netapp.com>, =?UTF-8?B?TWlra2VsIEZhaG7DuGUgSsO4cg==?= =?UTF-8?B?Z2Vuc2Vu?= <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Space for Packet Metadata
References: <CAN1APdfx4Y4MUm5iAF99Vn1Svck5y2e6_qrNbozkwJWics17eQ@mail.gmail.com> <96577B0E-502B-4723-9A9B-63D8B365D5AA@netapp.com> <CAN1APddJJHrpKBjn+U=rYYzxnuwyRYvA3++0T_ZRMy15fCJgbQ@mail.gmail.com> <FC9963A9-F5B4-4A4B-8DE9-FB938B390BB0@netapp.com> <DM5PR2101MB09010484CA0782C13E43C2C4B3C70@DM5PR2101MB0901.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR2101MB09010484CA0782C13E43C2C4B3C70@DM5PR2101MB0901.namprd21.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/v-fM0_EQZWci9XOuF1eBW-zvW-0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2018 16:07:28 -0000

For IPv6 that may be fine.

The QUIC transport paper (*) Section 7.1 speaks of "Packet Size 
Consideration"- as far as I know this is just UDP traffic from google 
Chrome clients to google servers. They showed 3% unreachable for 1200 B 
payloads. Other networks could well be different.

We are in the midst of a large measurement campaign related to our work 
in TSVWG on path MTU discovery. I would expect a wide variety of Path 
MTUs - even though the current majority of paths will support 1280 
bytes, many IPv4 paths do not - there are also many paths that support 
much more.

Gorry

* 
http://delivery.acm.org/10.1145/3100000/3098842/p183-Langley.pdf?ip=212.159.18.54&id=3098842&acc=OA&key=4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E5945DC2EABF3343C&__acm__=1519833743_fa365ff0c9cc6c6e266add2dba8f385f

On 28/02/2018, 15:30, Nick Banks wrote:
> According to spec, QUIC requires at least 1280 (from 9.4):
>
> "QUIC depends on the network path supporting a MTU of at least 1280 octets. This is the IPv6 minimum MTU and therefore also supported by most modern IPv4 networks. An endpoint MUST NOT reduce its MTU below this number, even if it receives signals that indicate a smaller limit might exist.'
>
> - Nick
>
> -----Original Message-----
> From: QUIC<quic-bounces@ietf.org>  On Behalf Of Eggert, Lars
> Sent: Wednesday, February 28, 2018 7:12 AM
> To: Mikkel Fahnøe Jørgensen<mikkelfj@gmail.com>
> Cc: IETF QUIC WG<quic@ietf.org>
> Subject: Re: Space for Packet Metadata
>
> On 2018-2-28, at 16:03, Mikkel Fahnøe Jørgensen<mikkelfj@gmail.com>  wrote:
>> Yes, but can it go below 1200? It seems the handshake aims to squeeze up near the minimum guaranteed (required) PMTU and QUIC implementations would probably not expect to maintain a connection that drops below PMTU 1200.
> The minimum IPv4 MTU is 576, so I'd expect QUIC stacks to probe as least that low.
>
> Lars