Re: [v6ops] draft-van-beijnum-multi-mtu-05

Nick Hilliard <nick@foobar.org> Thu, 07 April 2016 22:39 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA11512D755 for <v6ops@ietfa.amsl.com>; Thu, 7 Apr 2016 15:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 v4iquCz4mwGm for <v6ops@ietfa.amsl.com>; Thu, 7 Apr 2016 15:39:03 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC9F812D73D for <v6ops@ietf.org>; Thu, 7 Apr 2016 15:39:01 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.foobar.org (089-101-070076.ntlworld.ie [89.101.70.76] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.14.9) with ESMTPSA id u37Mcvjt042611 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 23:38:58 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070076.ntlworld.ie [89.101.70.76] (may be forged) claimed to be cupcake.foobar.org
Message-ID: <5706E181.50208@foobar.org>
Date: Thu, 07 Apr 2016 23:38:57 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Philip Homburg <pch-v6ops-4@u-1.phicoh.com>
References: <alpine.DEB.2.02.1604042335570.31096@uplift.swm.pp.se> <5703ABF9.2000907@foobar.org> <20160406153142.GU56633@Space.Net> <570534CC.3020603@foobar.org> <m1ao8bQ-0000EdC@stereo.hq.phicoh.net>
In-Reply-To: <m1ao8bQ-0000EdC@stereo.hq.phicoh.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/xF2r4nKI0bH1KrLrr5lL3XHUJD4>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-van-beijnum-multi-mtu-05
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 22:39:05 -0000

Philip Homburg wrote:
> Assuming two nodes (hosts or routers) have announced such a larger MTU. And
> they have verified (using ICMP, or whatever) that is is actually possible
> to exchange packets at a bigger MTU.
> 
> Then what problems do you expect in todays networks?

for starters, multicast and broken implementations.  If there are
routers doing this negotiation, then this may change the path mtu
mid-flight, which could cause problems if the path mtu drops
unexpectedly, which it might easily if lots of things are dynamically
negotiated.  Or if the MTU negotiation takes place at the first hop and
the endpoints are left thinking that they can handle an mtu of 9200
bytes while the intermediate path might only support 1500 and the
fragmenting router is already rate limiting icmp6 toobig responses.  Or
several of the situations mentioned in rfc2923.

The issue is that the use case is not sufficiently compelling to warrant
introducing low level changes in a protocol which has been around for 20
years and has a wide deployment, where operational experience tells us
that problems relating to MTU path mismatches are a huge headache which
are difficult to debug.

Nick