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

Fernando Gont <fgont@si6networks.com> Fri, 26 May 2023 15:11 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742BEC14CE46; Fri, 26 May 2023 08:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 w5nngzcKiBBT; Fri, 26 May 2023 08:11:41 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 E1467C387FFE; Fri, 26 May 2023 08:10:38 -0700 (PDT)
Received: from [10.89.9.171] (unknown [91.90.189.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 4DD572800EE; Fri, 26 May 2023 12:10:36 -0300 (-03)
Message-ID: <375ea678-b05f-7bb6-5ae2-43c54cd271f4@si6networks.com>
Date: Fri, 26 May 2023 17:10:35 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: "Haisheng Yu (Johnson)" <hsyu@cfiec.net>
Cc: "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>, "andrew.campling@419.consulting" <andrew.campling@419.consulting>, "fernando@gont.com.ar" <fernando@gont.com.ar>, "v6ops@ietf.org" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
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>
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
In-Reply-To: <4FCF75B585A1D068+7D9B99BB-B24B-4FE8-A3FD-54877C7C1131@cfiec.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3WIhz-wDSxl5d1ZkVnWfm8cNDfQ>
Subject: Re: [v6ops] [OPSEC] [IPv6] Why folks are blocking IPv 6 extension headers? (Episode 1000 and counting) (Linux DoS)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2023 15:11:47 -0000

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.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494