IETF Logo Mail Archive

Re: [Pals] [Int-area] L2TP sequencing: Commonly disabled for IP data? Or always?

Derek Fawcus <dfawcus+lists-int-area@employees.org> Mon, 28 June 2021 18:46 UTC

Return-Path: <dfawcus@employees.org>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE8A53A003D; Mon, 28 Jun 2021 11:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 o1SB6HfZNnJa; Mon, 28 Jun 2021 11:46:15 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAE253A0035; Mon, 28 Jun 2021 11:46:14 -0700 (PDT)
Received: by clarinet.employees.org (Postfix, from userid 1736) id A95004E11DAB; Mon, 28 Jun 2021 18:46:13 +0000 (UTC)
Date: Mon, 28 Jun 2021 19:46:13 +0100
From: Derek Fawcus <dfawcus+lists-int-area@employees.org>
To: pals@ietf.org, intarea IETF list <int-area@ietf.org>
Message-ID: <YNoY9RtM9XNOM7BF@clarinet.employees.org>
References: <5E252602-F635-4DF0-8FAE-C80CF88293D9@gmail.com> <YMCj2P4AlqlpeXdV@clarinet.employees.org> <EC1A1D29-EF8D-4480-A950-3BA2AD16033F@gmail.com> <881FF4F8-27BA-4B58-B54E-68F3811BE1D4@layerfree.net> <CAAWx_pWZt1RTHeCvghfNFyEB7E-6zDC89uexbDEdo=9=uVLcBA@mail.gmail.com> <YMDIrkR/ekhMZi2K@clarinet.employees.org> <CAAWx_pXPK7YfrcBZWk=hHRy+YqMbtq=bKfpa0iQBu4fX7iLekw@mail.gmail.com> <3421c34d-0fba-df94-89a3-64abdc325633@bobbriscoe.net> <CAAWx_pXnoZ6-LhZeTiZ8=eG+7JKRd9WV_Y8QxHZ_g6jB3qFqFg@mail.gmail.com> <e0ad92b0-49fd-022c-2478-1820ab7a506d@bobbriscoe.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <e0ad92b0-49fd-022c-2478-1820ab7a506d@bobbriscoe.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/uYwEys8DxvqA_xjAoVzprYtLM6M>
Subject: Re: [Pals] [Int-area] L2TP sequencing: Commonly disabled for IP data? Or always?
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2021 18:46:18 -0000

On Mon, Jun 28, 2021 at 09:39:34AM +0100, Bob Briscoe wrote:
> 
> My attempt to generalize this UK-specific knowledge: No-one is going to 
> add sequencing without a reason, and the only possible reason mentioned 
> so far would be stateful compression, which these days would just slow 
> things down more than the bandwidth saved.

I also mentioned PWE fragmentation - rfc4623 - it depends upon the sequence
numbers as a fragment identifier.  So depending upon how it is implemented,
it may implicitly turn on sequencing, without the user knowing.

So the related question then becomes, where is that fragmentation support
being used - if anywhere?

DF

v2.23.0 | Report a Bug | By Email