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

Stewart Bryant <stewart.bryant@gmail.com> Wed, 09 June 2021 10:23 UTC

Return-Path: <stewart.bryant@gmail.com>
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 904AE3A0743; Wed, 9 Jun 2021 03:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UIgAINyi41JM; Wed, 9 Jun 2021 03:23:04 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 402E93A0766; Wed, 9 Jun 2021 03:23:04 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id r9so8162471wrz.10; Wed, 09 Jun 2021 03:23:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EeXRZySFhjmKJko/ZLCzT+5ohGL1YUOKA+TZ8eLLd+E=; b=dl1gVSkSTGPYFYt9mzwcihZDg+1P5foicwhsBsX2FK5ljCD8x65Nx1LLR8MWjnerTX 7hEExVz6pYvTrK7qVm9eqnpMLCsYQ4ZUmHgxV5pLp+nAQXNVTXuUuOJeNKai3r+T5V4B OL8dyviNCySSWlBhfaL0LNLGbYMw1duzhVbN4pYCW1Z5X29NICx4+r8oF98Tdd/X1ZRL WZxWoMJXRnIyLYlDO0V+6dawi8kaqnZ3KQtFOqrAK6+IqjngiyrRMEMmD659x7iEADCr koPi4hUk8qrX2fOQHF84qP6bRYL9wB9pi8EX2V2BHDikc1qNAH8PDOp+fv273O3xYsUy 6IAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EeXRZySFhjmKJko/ZLCzT+5ohGL1YUOKA+TZ8eLLd+E=; b=H7A0VdfWkZ/DzvGyg3LkdbC1WVQkNxul4qlMN0guD7REcPVpWD6tB2Y1NHT4fs/Xhz StUxV6JFNofRwemyG7nYRnirOzZWRqRL6Z3zxVZqhgZnDGn0Q5kUMhTry836kbowBb8m HzoqLXNttpFHHAFOP+EST6GZM0LoF78TEerlTd/pmn2hS58EUL4lYH4OiEvXwa79QC4I 5yjC67MkETiChKx+LCYZ9bLI40Hf9m75prfzLHEuP8BehxzlLMt0dwrh9fQ0f+QGn8jL T2yaM0Zm5aF+9QNHowpcnL8hiBjGZB2wUvHLa7+0cBUa2nMrb3w6ZU1e55nJYLbde7h6 LWTg==
X-Gm-Message-State: AOAM531r235qGtP32GYJnaMZ3zVMHZR2Jq4m08iF8SKsCnR93ZGVPfPp wMnT5dpCkeKPKz2mHHWYn2g=
X-Google-Smtp-Source: ABdhPJxxO/ggE6Q7aE/hp7OMn8JEgDhblG3ZIPIqf7UdE5LgSC5wTK2VKm2e8NFLY/RSq6Dn1Uzpxw==
X-Received: by 2002:a5d:4a4e:: with SMTP id v14mr27189013wrs.74.1623234182011; Wed, 09 Jun 2021 03:23:02 -0700 (PDT)
Received: from [192.168.8.162] ([85.255.233.46]) by smtp.gmail.com with ESMTPSA id u15sm5327839wmq.1.2021.06.09.03.23.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jun 2021 03:23:01 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <5E252602-F635-4DF0-8FAE-C80CF88293D9@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E2F4FD6B-4B30-4BEB-97AC-530027EA19A6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Date: Wed, 9 Jun 2021 11:23:00 +0100
In-Reply-To: <CAA=duU2o9YKF5Sfu6VTr5+bUr1JVgaGZh=X4+BQRbMu63FqVsg@mail.gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Derek Fawcus <dfawcus+lists-int-area@employees.org>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Ignacio Goyret <ignacio.goyret@nokia.com>, intarea IETF list <int-area@ietf.org>, pals@ietf.org
To: "Andrew G. Malis" <agmalis@gmail.com>, mark@townsley.net
References: <5c60cc79-1552-3f52-641f-e508780227ae@bobbriscoe.net> <YLuFLq7k9akVVHWS@clarinet.employees.org> <CAA=duU2o9YKF5Sfu6VTr5+bUr1JVgaGZh=X4+BQRbMu63FqVsg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/-twPKOg4PAAUJnyuVG1tUHCEmFc>
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: Wed, 09 Jun 2021 10:23:10 -0000

Sequence number checking in the forwarder is always a problem because it is stateful so I doubt that many high-scale or high-speed forwarders ever did this.

I think there is an undisclosed assumption that go up enough levels and its IP so sequence number checking in the transport network (as opposed to the transport layer) is not really needed.

I doubt that there is much L2TP still out there. It was in its prime with dialup modems. L2TPv3 which was intended to replace it became niche with, as Andy says, operators who did not want MPLS. Much of what L2TPv3 was intended for was actually done with PW over MPLS with some replacement with by Mac in Mac for cost reasons.

If Carlos does not know the answer, Mark T would be my next port of call.

Stewart



> On 8 Jun 2021, at 22:41, Andrew G. Malis <agmalis@gmail.com> wrote:
> 
> Bob,
> 
> In addition to the cases listed by Derek, L2TPv3 can also carry non-IP pseudowire data, such as Ethernet frames (see RFC 4719 for example). Even though 4719 says that sequencing is optional, I would certainly recommend it :-).
> 
> But I guess that's really not what you were asking about, since you specifically mentioned IP data. But it is a case where you would probably see sequencing in use.
> 
> Back in the day, Sprint made good use of Ethernet over L2TPv3, as they were in the anti-MPLS camp at the time. But that's water over the bridge, and I really don't know if this solution continues to be in active use. Mark Townsley might know.
> 
> Cheers,
> Andy
> 
> 
> On Sat, Jun 5, 2021 at 10:07 AM Derek Fawcus <dfawcus+lists-int-area@employees.org <mailto:dfawcus%2Blists-int-area@employees.org>> wrote:
> On Fri, Jun 04, 2021 at 03:13:15PM +0100, Bob Briscoe wrote:
> > The L2TP RFC says sequencing /can/ be disabled for IP data, but it 
> > doesn't say SHOULD or MUST. Is it possible that some operators enable 
> > L2TP sequencing for IP data? And if so, do you know why they would? 
> > Also, are you aware of any other types of tunnel that might try to keep 
> > IP data packets in sequence?
> 
> How many intermediate headers are you considering between L2TP and where
> a carried IP header may exist?
> 
> Maybe I'm getting the wrong end of the stick, but surely this engages
> the text from section 5.4 of RFC 2661:
> 
>   "For example, if the PPP session being tunneled is not
>    utilizing any stateful compression or encryption protocols and is
>    only carrying IP (as determined by the PPP NCPs that are
>    established), then the LNS might decide to disable sequencing as IP
>    is tolerant to datagram loss and reordering."
> 
> This would then suggest if L2TP is carrying PPP, the PPP session is not
> multi-link, and is making use of compression (including one of the
> versions of IP header compression) in some form for IP packets, then
> reordering will impact the ability to decompress.
> 
> So such an L2TP data session may well make use of sequence numbers to
> prevent reordering.
> 
> I guess similarly in L2TPv3 when the PW is for PPP, and possibly also
> the fragmentation scheme in RFC 4623 which requires sequence numbers;
> and such PWE3 links could ultimately be carrying IP packets.
> 
> 
> DF
> 
> (not an operator)
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org <mailto:Int-area@ietf.org>
> https://www.ietf.org/mailman/listinfo/int-area <https://www.ietf.org/mailman/listinfo/int-area>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area