IETF Logo Mail Archive

Re: [v6ops] IPv6 fragmentation experience

Ole Troan <otroan@employees.org> Fri, 23 March 2018 00:36 UTC

Return-Path: <otroan@employees.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 96AC5127136 for <v6ops@ietfa.amsl.com>; Thu, 22 Mar 2018 17:36:02 -0700 (PDT)
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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 GN1MugBQD_fZ for <v6ops@ietfa.amsl.com>; Thu, 22 Mar 2018 17:36:01 -0700 (PDT)
Received: from accordion.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B1EA1270AE for <v6ops@ietf.org>; Thu, 22 Mar 2018 17:36:01 -0700 (PDT)
Received: from [192.168.10.117] (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id D2EDD2D5064; Fri, 23 Mar 2018 00:36:00 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15D100)
In-Reply-To: <133d0300-7d11-133d-dec1-07aa7546f3df@strayalpha.com>
Date: Fri, 23 Mar 2018 01:35:58 +0100
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: <6265ABC4-73D9-4A6B-BA52-71F26483AAE7@employees.org>
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>
To: Joe Touch <touch@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/h92ZSFYieTb5uLy9dpMLhrDoCaw>
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 00:36:03 -0000

Joe,

It seems you are in denial about the consequences for IPv4 with ever increasing address sharing. 

Ole

> On 23 Mar 2018, at 01:28, Joe Touch <touch@strayalpha.com> wrote:
> 
> 
> 
>> On 3/22/2018 10:21 AM, Jen Linkova wrote:
>> The expectations need to be set and documented.
> 
> On that, I agree.
> 
> The expectation is that a device that inspects L4 will preserve L4
> semantics - which means that if it starts forwarding on L4, it had
> better keep doing so for the rest of the fragments for that L4.
> 
> Just saying "that's what everyone does" isn't an answer. Everyone (in
> general) disobeys speed limits; that doesn't mean we stop putting them
> up or stop enforcing them.
> 
> Joe
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email