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

Bob Briscoe <ietf@bobbriscoe.net> Tue, 29 June 2021 10:02 UTC

Return-Path: <ietf@bobbriscoe.net>
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 2489C3A2DDF; Tue, 29 Jun 2021 03:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.768
X-Spam-Level:
X-Spam-Status: No, score=-1.768 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, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 6LMBSzOnWMvs; Tue, 29 Jun 2021 03:02:12 -0700 (PDT)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD5643A2DC7; Tue, 29 Jun 2021 03:02:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4loFXTfG7kU/dhq4G2P1TRnFgnKt6nRUcvnHx3UNp0k=; b=4H+qjGdyvsBSn5ipebZdFybK10 4fpZzfQ+vnouVznsrf3eMURKyET9/lxrQbsvbdOhOtE74xWXhY5jH6Bre2seq9+N7dAIA86Sj9nyq 5+g10WmuDnUtpT2EtcOgLvXhyz1tD2tBJrjYjfh7xd099MS9pllRafZzvj9ssRi0qkJdhvE7r1hxg 95ohRRE3irM8IKeHgR+KuhlMP3nSjlBZ4aYVGJqEp55pyB/XifM2bCM3mEcIQQAziYFhjJlAIcWR2 zVGbgmg1U8eMXp0bvgxqlQRv8/X9dMKFiIKTqGD7XCTugpi/DZqvs6NQW9yQOj7xwoVVal/hhTqFR g/nAJl/g==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:43374 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1lyAZH-0001fJ-Hc; Tue, 29 Jun 2021 11:02:09 +0100
To: tom petch <ietfc@btconnect.com>, intarea IETF list <int-area@ietf.org>, "pals@ietf.org" <pals@ietf.org>
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> <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> <AM7PR07MB624889988773F3F3AFD0AB8CA0039@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <055fc148-ce81-d548-a5f6-90e4bc353171@bobbriscoe.net>
Date: Tue, 29 Jun 2021 11:02:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <AM7PR07MB624889988773F3F3AFD0AB8CA0039@AM7PR07MB6248.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/vn4AnNj57aIaehrJyzKcMlkeqbY>
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: Tue, 29 Jun 2021 10:02:19 -0000

Tom, see [BB2]

On 28/06/2021 09:41, tom petch wrote:
> <at the bottom tp>
>
> From: Int-area <int-area-bounces@ietf.org> on behalf of Bob Briscoe <ietf@bobbriscoe.net>
> Sent: 27 June 2021 22:22
>
> James,
>
> [First apologies to everyone for asking the question then not following
> up on the answers until now - I went off line for a while.]
> See inline tagged [BB]...
>
> On 10/06/2021 13:09, James Bensley wrote:
>> On Wed, 9 Jun 2021 at 15:57, Derek Fawcus
>> <dfawcus+lists-int-area@employees.org> wrote:
>>> On Wed, Jun 09, 2021 at 03:07:41PM +0200, James Bensley wrote:
>>>> 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?
>>> Yes.
>> In that case  - sequencing isn't used for BT Wholesale services.
> [BB] Thank you. It sounds like you have some reason for your certainty
> here. Can you elaborate on what makes you so certain sequencing isn't used?
>
> <tp>
>
> Perhaps  a coincidence or perhaps not, but an I-D has just been posted
> Author          : Yogesh Nautiyal
> Filename        : draft-nautiyal-l2tpext-tunnel-ka-control-channel-00.txt
> which uses L2TP sequencing,  I note the author has an affiliation of Juniper.

[BB] Thanks for pointing this out. It's quite normal and expected for 
L2TP to use its sequencing facility for a control channel. I'm not 
concerned about that. My original question was scoped to IP as data.

But thanks anyway. Cheers


Bob

>
> The draft would need a fair bit of work.
>
> Tom Petch
>
> Bob
>
>> Cheers,
>> James.
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
> --
> ________________________________________________________________
> Bob Briscoe                               http://bobbriscoe.net/
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/