Re: [v6ops] IPv6 fragmentation experience

Joe Touch <touch@strayalpha.com> Fri, 23 March 2018 14:05 UTC

Return-Path: <touch@strayalpha.com>
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 11C1D1243F6 for <v6ops@ietfa.amsl.com>; Fri, 23 Mar 2018 07:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 kpuqF_0aWe6F for <v6ops@ietfa.amsl.com>; Fri, 23 Mar 2018 07:05:07 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C41B1200F1 for <v6ops@ietf.org>; Fri, 23 Mar 2018 07:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=TG3PTAN86F1ni5PaNcO3dkiTOtIv8/9I2mtyt3BY4eU=; b=eqphu1+Flzw/3Ay+sU1OD85gm MtXkQScheKvsK4NHrtZQsi7a5oj181XpthvIc1yquxRyPS2YWirr2Ya4wmwL8j0SElKhVb9pAzs7Z TXy02xcm0XOmqa2JzZTvD7xohXa88+KztsZ6iTxnXxFAo9HpUJpofenSlP3pTeBeaEzJTTmrUKstX tVeselqp4+R5L0R/BJioFKo9HF5b3DQPFbLx+y8HA5kEreXWf3+zFkYSX9/uWuKdelXWBI9nra37N HBDtD2Wx92QUdcjw5n/0ME5RIUdCdt41PNc0y/5NZ+QEE4NrsPeNvKcBjyJJEzsjgPmk91aVVQNhr 2uCVaVbmg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:60958 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from <touch@strayalpha.com>) id 1ezNJB-003hlX-7k; Fri, 23 Mar 2018 10:04:46 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <53B81EAD-6AB9-4A2C-BEBC-2B80A10533BF@employees.org>
Date: Fri, 23 Mar 2018 07:04:32 -0700
Cc: Jen Linkova <furry13@gmail.com>, Tom Herbert <tom@herbertland.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9987C06-F2BD-4BA5-B10E-BD1121AB169F@strayalpha.com>
References: <84080e87-9ec6-a676-b535-088470e43923@asgard.org> <alpine.DEB.2.20.1803201208550.20609@uplift.swm.pp.se> <561690FD-9016-4EB0-B03C-CE2BFE4BE7A0@employees.org> <7456C389-0CB0-4E9D-8622-E3461FAA4375@steffann.nl> <5F05318A-0B2D-4B6F-8442-6A0C7E9581EF@gmail.com> <6cc086ed-f6b4-60a9-d181-1e3a6a41c563@strayalpha.com> <alpine.DEB.2.20.1803210918100.20609@uplift.swm.pp.se> <92BFD600-9948-4E2C-80A1-F5F2BD320A31@strayalpha.com> <20180321200444.GX89741@Space.Net> <0c57a669-7cad-e554-b637-a6d86e0e7a67@strayalpha.com> <20180322102010.GE89741@Space.Net> <CAFU7BAQU9NNL=B7YjdNxDH9fjv3cFk=LUsz-eG0Rxe2gA6X+8g@mail.gmail.com> <CALx6S36WA0hV5oa1Ab7D6nH=1B+SGRA=JVJgdYWRH7OH8wB_JQ@mail.gmail.com> <CAFU7BATfu2remSQTiLGpUDLhp020xFLLQdDBT-3iKsNhBmw+wg@mail.gmail.com> <133d0300-7d11-133d-dec1-07aa7546f3df@strayalpha.com> <6265ABC4-73D9-4A6B-BA52-71F26483AAE7@employees.org> <0519C8D2-BD94-45E5-B26A-CD5B96A8A27B@strayalpha.com> <53B81EAD-6AB9-4A2C-BEBC-2B80A10533BF@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3445.5.20)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mu3Vk2ZHd14vQBCXNT6SCr8tHIw>
Subject: Re: [v6ops] IPv6 fragmentation experience
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 23 Mar 2018 14:05:09 -0000


> On Mar 23, 2018, at 3:20 AM, Ole Troan <otroan@employees.org> wrote:
> 
> Joe,
> 
>>> It seems you are in denial about the consequences for IPv4 with ever increasing address sharing.
>> 
>> You are willing to pay money to be lied to. I am not
> 
> I am the one taking your money and implementing it, and trying not to lie to you in the process.

Here’s what you need to do to stop lying that you’re selling me an IP router (or A+P device):

1) if you look at L4, then you need to either reassemble the packet or cache the front fragment and use it as context for later fragment forwarding.

2) if you can’t keep up with #1, then you need to ignore L4 context for that packet and forward it using only L3

3) remember that ECMP still requires a valid P (path); if a “path” doesn’t go to a destination for a fragment, it’s not a path and should not be in your forwarding table

I’m doing what I can to help reduce the amount of #2 traffic here in the IETF (UDP options) and certainly everyone should be doing some sort of PLPMTUD too. Sure, we all should also try to move to IPv6.

But that doesn’t mean those who sell IPv4 devices get to lie.

We all need to be aware of implementation *errors* and fix them.

Joe