Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv 6 extension headers? (Episode 1000 and counting) (Linux DoS)

Tom Herbert <tom@herbertland.com> Fri, 26 May 2023 16:01 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C32DC151707 for <ipv6@ietfa.amsl.com>; Fri, 26 May 2023 09:01:49 -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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maWfO55alAvM for <ipv6@ietfa.amsl.com>; Fri, 26 May 2023 09:01:45 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7E09C151071 for <ipv6@ietf.org>; Fri, 26 May 2023 09:01:45 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-517ab9a4a13so811932a12.1 for <ipv6@ietf.org>; Fri, 26 May 2023 09:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1685116905; x=1687708905; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=+onLLO54/cEJ3ivTrjjvkda9Y+3UkG77wF3bX2qt8A8=; b=UGuXZVW9w5agwsyvQ48CnOkBgcYRWvjHpGRa24DoICSjBxGYQiyJNeD3WFRVqDETMr FrIAMzyzKvCIY7kojYqvb4rC6u6ItrqjZKj7M5QsDtM3padqIvWfX54JKlIhb25iWNJz 2FGPffq7Xybpocq828vsA/ge/ijtU+HPFrHwkNxAWsWTqnLdVS7mV+yli2TJDG58ItYj 4DWdLt4X8PIzPTMKvCjhgzus+u65Wd5whoU5tezIyEsBDHMB8Ykt6fdMqvnysEYbPUhH 3UCLOp1nh3Ny9vm371izwFvTZ/5TPuF1lUL8AO8UyVGSCbRwowWXPHwisbClm1fLCXTu lTOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685116905; x=1687708905; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+onLLO54/cEJ3ivTrjjvkda9Y+3UkG77wF3bX2qt8A8=; b=VJRmRHq/I0wMN9VQSH3ToA4MadMGvEBYuqzCvfaIkAXllBxEtoicHBSG4q9fzNKHkP qN9yRDSMO3RR3EFtSeQHylE1DjpiXun5pNNFVlC3OXEOnbFjYrP4UUl6vxgchY4XS69C 600Q/pMZAcum3KpA77clyz0LTk+FkcRxZIiXjcXFHAYtARt3Z1q4JYcDn33dYL10M9a6 +VSheqM27qRGak09OT0nxjW1N1JzaNJxeZKHHWYK9FGJLFmiH31DzhVCpgWueLb2FcGs MyZh/ZMi3/vCPZN0Qby4KKUqtg/S6cQdeNoCHG0KReioExbY9d2zw9Gwx6rf2HNqvtVR SOPA==
X-Gm-Message-State: AC+VfDy2nCIot2NH6bUJ04RGjCJj/rBeHwN5/5ML7ZAD56TIoPTpcdzy j2iZAk9DG9JpV1+GQDowmRqeDarSbFUkmublWHGo7A==
X-Google-Smtp-Source: ACHHUZ7K9imWiKCFVs5c7I3gGqrk/pphcIoi2ZzPYCC+psh2jB9SZzVWl0J6epAo1i6dd0XJMrcNvWSH0UvMgPAXdy4=
X-Received: by 2002:a17:903:1209:b0:1a6:82ac:f277 with SMTP id l9-20020a170903120900b001a682acf277mr3883217plh.14.1685116905040; Fri, 26 May 2023 09:01:45 -0700 (PDT)
MIME-Version: 1.0
References: <11087a11-476c-5fb8-2ede-e1b3b6e95e48@si6networks.com> <CALx6S343f_FPXVxuZuXB4j=nY-SuTEYrnxb3O5OQ3fv5uPwT8g@mail.gmail.com> <CAN-Dau1pTVr6ak9rc9x7irg+aLhq0N8_WOyySqx5Syt74HMX=g@mail.gmail.com> <a087b963-1e12-66bf-b93e-5190ce09914b@si6networks.com> <CALx6S349nNA8L5+_1hrbWayqp8GfTYypWy_SP57c_Xxams=csg@mail.gmail.com> <51a066b3-4b4c-d573-ffbe-d6b44a4f193f@gont.com.ar> <a411a1b0-c521-c456-3d44-d99a1cc0975b@gmail.com> <CWXP265MB5153E4687BE45480DBC5A531C2439@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM> <27d28224-0cb0-eec2-8d54-f0d175596c85@gmail.com> <f5758380-9967-b67b-744d-dc36b7b599ab@si6networks.com> <4FCF75B585A1D068+7D9B99BB-B24B-4FE8-A3FD-54877C7C1131@cfiec.net> <375ea678-b05f-7bb6-5ae2-43c54cd271f4@si6networks.com>
In-Reply-To: <375ea678-b05f-7bb6-5ae2-43c54cd271f4@si6networks.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 26 May 2023 09:01:33 -0700
Message-ID: <CALx6S34u5=2UxEz3zeApv+_-W=PTj0PzMRHS1UC=zRchqVCDyQ@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: "Haisheng Yu (Johnson)" <hsyu@cfiec.net>, "v6ops@ietf.org" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "andrew.campling@419.consulting" <andrew.campling@419.consulting>, "opsec@ietf.org" <opsec@ietf.org>, "fernando@gont.com.ar" <fernando@gont.com.ar>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HumNXHP6akH0MZP0zL7YuDtuOZw>
Subject: Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv 6 extension headers? (Episode 1000 and counting) (Linux DoS)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2023 16:01:49 -0000

On Fri, May 26, 2023 at 8:12 AM Fernando Gont <fgont@si6networks.com> wrote:
>
> Hi, Haisheng Yu,
>
> On 26/5/23 06:14, Haisheng Yu (Johnson) wrote:
> [....]
> >
> > The essence of the extension header issue is determined by the
> > competition between operators and equipment vendors.For most internet
> > users, they rely on the default configurations provided by the operators
> > or equipment vendors. Operators always want devices from vendors that
> > offer powerful features (e.g., in SRv6, equipment vendors aim to support
> > as many layers of Segment Routing lists as possible). However, during
> > actual deployment, only a portion of these features is used due to
> > security concerns. Equipment vendors are motivated to innovate as they
> > seek to outperform their competitors and gain profits in the market.
> >
> > The extension headers in IPv6 provide a significant advantage beyond the
> > address space of IPv4, enabling flexible and programmable network
> > transmissions. Looking at the current applications of IPv6 extension
> > headers, notable achievements have been made (such as SRv6). Perhaps
> > it's time to consider reducing restrictions on extension headers and
> > allow for more innovation and application.
>
> I'm super fine with folks that have a use for EHs, to use them. -- And I
> agree that for vendors it's an interesting source fo revenue.
>
> That said, I'm not that fine if invited to a party where, if anything, I
> will only pay the bills. So, I block everything that I don't use. e.g.,
> I have no use for EHs in any of my servers, except the pentesting boxes
> that I use to send weird packets to others.

Fernando,

If you're making that decision as the operator of a public network
then you are not making that decision for yourself, but you're making
a "big brother" decision for others and preventing permissionless
innovation as Brian stated nicely. I don't believe it could be claimed
that this is for "the good of the Internet".

Tom

>
> Cheers,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------