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

Stewart Bryant <stewart.bryant@gmail.com> Wed, 09 June 2021 11:48 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 5AD303A110B; Wed, 9 Jun 2021 04:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 evuNuQirg61l; Wed, 9 Jun 2021 04:48:27 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 6B7773A1107; Wed, 9 Jun 2021 04:48:27 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id r9so8438312wrz.10; Wed, 09 Jun 2021 04:48:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=221UgPhfV+ulso1hzm3N4e/JkZMFoDsba2qLoOY6FZM=; b=lHMmZCmZN45vLhT8zHvXYjQsxOyFt7AbawDVQt/krIX1Xm7smLrU/hGWUso9WgNXjk 5sKIG3k3fDYn+i24OPOnF/1L1o0QhZO35QlfLe5EWMlzWQ6SLMfgF5bz+nOpAXRZ4C2+ YOwM4rmhYsibwBlIQULvmuhHYXiLIcj3w61wziWdEHAANT1/Vhxj/oFlLmra8u8A+zMe iawFEoVjqNE74H/0XSTUDN3Hrz9JyeqtUww0JFUv0kCl5XkyByut6yA35WjPaeFlf9CH Ga6nPsE4swZMco1LHALYKqF1+FSVE0YMpGnZ6f5BVLr+6fqfXFivQBI4SE5LtLzWTc5K ccxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=221UgPhfV+ulso1hzm3N4e/JkZMFoDsba2qLoOY6FZM=; b=INvrAF1tkQ5zoKogLyKXutop/H0hp2kl7eZhyg4VgYIPNVqeov2DP2KxjOB9zI8ZQV IavqFi0MdMxpeOioLaMXCk9VJn2khvO1lYx/tKxJQH2xdu2RVb8FOTNJWtEO538vyhwe QfQqrhBuRfLCbuTawWUUt5QBqDmt57zFTN3tov5up9NikC9UwOhfT7YovoyX3berMUWE WaP954tOEUvOjpNIMSH2OCrcJP6IV/QGerbe6gnHx/0tec3kJT4kXXf/tD70p+HYPPpC UgAObAaf+k8FC5UylrIGtpBIlRBA+TMX9qvtf4gkWKFmWx0DDdCYE81hOPhK1qWZ9EJ7 mOgQ==
X-Gm-Message-State: AOAM530Lm1hs6eaumgnF/+Ce9jf4/16QX1H25vpniBm/NqYBv56J/HQ4 P735yrP4oP2M/EFfvYJfY5Q=
X-Google-Smtp-Source: ABdhPJzYBxKHsHIgRVyobq7U+111lkU5IfLWODxqdd/6UevMTUoWgu0LMDfC65PprjCfsuzO4+mpBg==
X-Received: by 2002:a5d:4ac5:: with SMTP id y5mr28255912wrs.18.1623239304413; Wed, 09 Jun 2021 04:48:24 -0700 (PDT)
Received: from [192.168.8.171] ([85.255.233.46]) by smtp.gmail.com with ESMTPSA id c2sm6367471wmf.24.2021.06.09.04.48.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jun 2021 04:48:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <YMCj2P4AlqlpeXdV@clarinet.employees.org>
Date: Wed, 09 Jun 2021 12:48:22 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, "Andrew G. Malis" <agmalis@gmail.com>, mark@townsley.net, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Ignacio Goyret <ignacio.goyret@nokia.com>, intarea IETF list <int-area@ietf.org>, pals@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC1A1D29-EF8D-4480-A950-3BA2AD16033F@gmail.com>
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>
To: Derek Fawcus <dfawcus+lists-int-area@employees.org>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/nHtAUkszaj2GT5vBNOtoE6jkg0Y>
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 11:48:33 -0000


> On 9 Jun 2021, at 12:19, Derek Fawcus <dfawcus+lists-int-area@employees.org> wrote:
> 
> On Wed, Jun 09, 2021 at 11:23:00AM +0100, Stewart Bryant wrote:
>> 
>> I doubt that there is much L2TP still out there. It was in its prime with dialup modems.
> 
> Stewart,
> 
> Isn't the BT wholesale ADSL product still using it?
> 
> Someone recently pointed to their SIN 472, which reference RFC 2661 not 3931.
> I don't know what other countries are doing for ADSL service,
> and in how many ADSL is a live vs legacy product.
> 
> Certainly my ISP describes how one can connect to them using L2TP mainly because
> they have the backend available for supporting the various 'broadband' access
> facilities.  They also offer ADSL access via another provider, so maybe they're
> also using L2TP?
> 
> So maybe the UK deployment doesn't count a 'much’.
> 
> DF

I suppose the ADSL product may be using it. I thought that it was all MPLS-PW.

We need someone from Openreach to tell us what they are doing.

In any case hopefully the last of the xDSL will soon be confined to the scrap bin it should have been in years ago as part of the plan to replace copper with FTTP/5G/LEO.

- Stewart