Re: operational stoppers to > 1500 MTU deployment in real life (Re: Path MTU Hop-by-Hop Option)

George Michaelson <ggm@algebras.org> Thu, 18 October 2018 12:46 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFC80130D7A for <ipv6@ietfa.amsl.com>; Thu, 18 Oct 2018 05:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 62f81qp4zj6p for <ipv6@ietfa.amsl.com>; Thu, 18 Oct 2018 05:46:21 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 5A60912D4ED for <ipv6@ietf.org>; Thu, 18 Oct 2018 05:46:21 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id 189-v6so137560wmw.2 for <ipv6@ietf.org>; Thu, 18 Oct 2018 05:46:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fEXbW6uSgnRuNF8SFwjCi+ouhl6r7bQuHIKLBpjJjrA=; b=XmF3LTUCBI4Ge3M/+oG1LJlHQd+t78bU6VZzY3wnrAVHb8rOyx84za4agWFhY6nfHW Zij00i75FCZfRl7dyxzEgSK4kmuqwBPwrpwNG9EQQ0WNK/BVDh8zAh9HXW6vMlodBGBM SNOeGhOKz5QHJMBL2dwV2xGZntP/cvMDlUENaHzVHaVKGH+5Nu+2rysneMOijrBeuRgr baPJNdJIoDrUBzaLGkGMAwV522fC/OTfTNY9K55zKxlrjM9+628tmao/KDhyRs3PUPkh YkBZgpcuOOTbuiaf9tI74reb7eipzDk69HGQqzGWasW6UlrTmoXbaxfVnkMLMu03PrnE lMug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fEXbW6uSgnRuNF8SFwjCi+ouhl6r7bQuHIKLBpjJjrA=; b=fM7L+oEzldK9yLehDh7A2H18reuzizUWUj1+o6WybseqNXVh+foTFOzsmZXfsckpsS 7p4a8jz84X+4ViUQKjG6VF7rZevWjs5HHZUc8fYd0EI2AUoueKuepKT6CAaQ9LGkPlrg VvFUc63ejBLpzqMLiORa3zw/ifzFWLBUUJ434S9uEy7GHLdvVqI1sIc+XL7vHUqZf/k2 yPYYxMdpvMD6DzjpGZRViyNppaoO7R299+GHw+yFdj2q81SZ7aXOmft9Z+ULNBXUVGaN TsWzmy/DU5JNtmvhfT/R8PjBL0pKkVg5TCYyUnCvNhu6oCxFFzH0c/bZV+Sx/cOT0/zU kKDQ==
X-Gm-Message-State: ABuFfogFjTBs51MZTAjyCdObma+w0VsNZ4c4hSse9ZLMo78FSRN3kWgC /i/Sf00EvJcEC5yyuQLXS1nZ27Sd5hhTcIEB9PcC/z2e
X-Google-Smtp-Source: ACcGV616pz1gmbWNvUhfm7Z5xrSvIUvKrcmOHbn6uEi0gwVgGjwZaydNBh/a+ZwvffJTSMFXG7IN2P9n5dqafChM6NE=
X-Received: by 2002:a1c:b0b:: with SMTP id 11-v6mr133067wml.25.1539866779743; Thu, 18 Oct 2018 05:46:19 -0700 (PDT)
MIME-Version: 1.0
References: <153972960647.9465.12295361632444928551.idtracker@ietfa.amsl.com> <E97952C5-3E3C-4EC1-B414-BDA8717FD7DF@gmail.com> <CALx6S36jRregvTO45=-Y=Kk+fS8eK-CxZDLhGuqcCz9Fq285rA@mail.gmail.com> <48c45b83983340a6882547aebb02602e@usma1ex-dag1mb5.msg.corp.akamai.com> <29044.1539782917@localhost> <3C43A2B0-E3EC-4457-9B75-4493FD6BA493@isc.org> <alpine.DEB.2.20.1810171735500.17344@uplift.swm.pp.se> <CAKr6gn2aMiYdKMr09GfN_Jt=1SKN50z_M7f_jmmTvke2Q9Czrg@mail.gmail.com> <alpine.DEB.2.20.1810181428280.26856@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1810181428280.26856@uplift.swm.pp.se>
From: George Michaelson <ggm@algebras.org>
Date: Thu, 18 Oct 2018 14:46:08 +0200
Message-ID: <CAKr6gn1dPjMexaPNHS_noYZEgFnLuXeL5h5qT8VXg-OzFQDo_g@mail.gmail.com>
Subject: Re: operational stoppers to > 1500 MTU deployment in real life (Re: Path MTU Hop-by-Hop Option)
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: ipv6@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kEYdos6noZt-KNO-3LKmG0d50Ec>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2018 12:46:26 -0000

dreams become nightmares very quickly.

I will observe that moving to jumbo for a locally attached file-store
was painful, so I do know even in the purely local context I've hit
pain.

However, in constructing GPON common-bearer services (NZ, AU) the
issue of a layer-2 which can encompass 1500 end to end, with a mix of
different overlay provider mechanisms (PPPoE, PPPoATM, Native,
VLAN...) It also becomes clear, the engineers who run the fibre are
well aware they have technology in the wide, talking from CPE to ISP
router, which *could* do it. They have to. They are pretty much
obliged to handle 2k, to allow the interior to be encap/decap for
1500. Customrs still get 14xx but the actual back-end is now north of
that. I think it could be more north.

Its not the glass and the layer-2 won't do "big" any more, its how the
upper layers are configured in equipment which is the problem.

What worries me is the people who are going to chime in about chipsets
and SFP designs which *cannot* do it. I suspect there is far more
transmission equipment stuck in the past than I would like.

I'll shut up now. I just wish as an SDO we could segment this problem
off and get a rational conversation about pits and poles to fix this.

-G

On Thu, Oct 18, 2018 at 2:36 PM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Wed, 17 Oct 2018, George Michaelson wrote:
>
> > dreaming of a larger packet future...
>
> It's completely undeployable in real life without something like
> https://tools.ietf.org/html/draft-van-beijnum-multi-mtu-05
>
> It's not realistic to expect a whole lan of managed and unmanaged devices
> to show up at a LAN and communicate with each other on a large MTU LAN.
>
> Right now my only tools are to crank up the L2 switch to 9000 MTU and
> advertise MTU=9000 in RA. Ok, I show up with my device that only has 1500
> MTU/MRU, I see that RA and I'm like "well, I can't do higher than 1500
> anyway, so I'll continue doing that". I need to send a UDP packet to the
> other guy on the same LAN, that's fine, he has 9000 MRU/MTU. He then needs
> to send me 2000 bytes back, so he does that and because my MRU is only
> 1500, my NIC now silently drops that packet. No PMTUD, just silent drop.
> *poof* gone.
>
> There are LOTS of similar failure modes that can happen. We need
> per-destination PMTU both on/off-link. I need to be able to send RIO and
> say "ok, ::/0 has 1492 PMTU" while at the same time send PIO with
> "MTU 9000". Devices then need to understand if their neighbours actually
> can do 9000 or not.
>
> I've even seen hardware/software that will have interface MTU of 1500,
> take the RA MTU=9000, set it's IPv6 interface MTU to 9000, set MSS to
> 89xx, send a large packet (because it can), then it borks when a response
> comes back because it only has ~2000 in MRU.
>
> Yes, real life is that broken.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se