IETF Logo Mail Archive

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

James Bensley <jwbensley+pals@gmail.com> Wed, 09 June 2021 13:08 UTC

Return-Path: <jwbensley@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 3956B3A15B4; Wed, 9 Jun 2021 06:08:15 -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, RCVD_IN_DNSWL_BLOCKED=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 FV9T0krGe4id; Wed, 9 Jun 2021 06:08:10 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 2AB4B3A158C; Wed, 9 Jun 2021 06:08:09 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id p7so3856870lfg.4; Wed, 09 Jun 2021 06:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=Uq6FX530+uGOGOostrEosibGpF+PqdnXWeAnSPg1EcY=; b=da5NtT7HLJSc+BgmS+zVA89Gb/I95bVkQxPO+HuzBUSGvKL2h8GH2CzNxLkhejvAXw kNSXIXS+Jihr7gKxOb79hqFWJJO8gnAy5F0b7+BDsSPAAdJnzjiSrx5m7pwi0pkPH8s0 +ovCtfbkvAlPzXOxvn0Esl7L4KK9MxbGWMriB1qBbkb/kijwevbDt7UkEY46ovlMxBfy ZMsPuM408iJwbZi6bK0uPSB0SnHWe9GsRNfyXVpq1hpI9FSQacOUBwtdqO/o5pPc8Uum pLHa6T7hl+SOszQy9cOiEi//KF5vK9t9NRc50WnPNymijMAhh0b84SPt1kOvryVSkgCp 8Dig==
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:content-transfer-encoding; bh=Uq6FX530+uGOGOostrEosibGpF+PqdnXWeAnSPg1EcY=; b=mCZNcsII28JhuiPdmFqJj+0yRy51bqFnQ1I/BZeKjhaxXjxZQaeNS5s8YamlJ3sz27 oV7igH+DAj+4ZevoWjy81Jwujv1Kb/oLu0Bg9Ac/QW5vhYJfdMVVnwPqwe2ht9B9KsKj Lwj425BjZ6w5dqasoSTSEpVV/X/4Oy/BgKf5+q16mlo5kaF/mPur6WdGVX59c8udPLlh 2GPi/HJLnnd7/FiP1vWlErR2DKBVmun5Q4rPIB7AlELtStcgjY91rU3UbKpdo88TTC+6 yCTXbVaH8catL0j4hNEwbOuLe6NdcCGYp0CTX2pV/V3YQ12CyW9euR6TKEDwU0DCPW9l D69Q==
X-Gm-Message-State: AOAM531oa8+BrOSTmpNyDuetggyitDSqUyswFFGkWu2ETF/GaGiQQBY+ SCDOgzmbJFDCj9KbWDoSKvyePnxQoDgpVYOLjOjIkxXBVXu1Q0fF
X-Google-Smtp-Source: ABdhPJzR/FokOu3qh3aCSCbJ957x9DYWVmMzYzk7OZ+Jw/L2hJEM2E3/pMSmvfRs2vvhxAYHx1iyi+hJcegYm8msOVc=
X-Received: by 2002:a05:6512:218e:: with SMTP id b14mr5905356lft.658.1623244087286; Wed, 09 Jun 2021 06:08:07 -0700 (PDT)
MIME-Version: 1.0
References: <5c60cc79-1552-3f52-641f-e508780227ae@bobbriscoe.net> <YLuFLq7k9akVVHWS@clarinet.employees.org> <CAA=duU2o9YKF5Sfu6VTr5+bUr1JVgaGZh=X4+BQRbMu63FqVsg@mail.gmail.com> <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>
In-Reply-To: <881FF4F8-27BA-4B58-B54E-68F3811BE1D4@layerfree.net>
From: James Bensley <jwbensley+pals@gmail.com>
Date: Wed, 09 Jun 2021 15:07:41 +0200
Message-ID: <CAAWx_pWZt1RTHeCvghfNFyEB7E-6zDC89uexbDEdo=9=uVLcBA@mail.gmail.com>
To: pals@ietf.org, intarea IETF list <int-area@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/Bmndjayv9Rdj7gFMO07rcXfFpe0>
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 13:08:25 -0000

On Wed, 9 Jun 2021 at 14:05, Giles Heron <giles@layerfree.net> wrote:
> Re BT specifically (and again my info is outdated and may be mis-remembered) the 20C network used L2TP, and I think it’s an option on 21C for handoff to smaller ISPs.  Should all be in the SINs somewhere?

I work in the UK ISP sector. I can confirm that L2TP is in wide spread
use for wholesale services by all major ISPs (except Liberty). I think
the real question here (unless I've misunderstood) is not "is L2TP
being used" but "is L2TP being used AND sequencing is being used
and/or enforced?" - is that understanding correct?

Chers,
James.

v2.23.0 | Report a Bug | By Email