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

Haisheng Yu <hsyu@cfiec.net> Fri, 26 May 2023 04:15 UTC

Return-Path: <hsyu@cfiec.net>
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 6C61DC16951B; Thu, 25 May 2023 21:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.782
X-Spam-Level:
X-Spam-Status: No, score=-1.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 Oyo0NojhvG6C; Thu, 25 May 2023 21:15:47 -0700 (PDT)
Received: from smtpbgjp3.qq.com (smtpbgjp3.qq.com [54.92.39.34]) (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 2B722C14CE4C; Thu, 25 May 2023 21:15:45 -0700 (PDT)
X-QQ-mid: bizesmtp84t1685074484t21r4lzf
Received: from DESKTOP-3U2VLEE ( [60.247.14.2]) by bizesmtp.qq.com (ESMTP) with id ; Fri, 26 May 2023 12:14:40 +0800 (CST)
X-QQ-SSF: 00400000000000C0Z000000A0000000
X-QQ-FEAT: HPkwb3INVpB7JSLjnc4mXUsU6qeRAqZ5TMZL4WcPHd14lXLF45OUOuF3nfZtz joOetD2gu8s11zOArrigMZMnrPS21SvbcASdA+sued1HzIrhmcfapNe0cGTpR2hKO3iRk/b YB0iI+t1U1QANxNJ37j/WlV1K5azQlH+1DLDGjLj+V8fWKcmXgoM1R6Fj829wY+w7Q9kgj3 CIxifAhTWrN8j9Jjb3tL6/XjVbbjYkvBS1uaqwR/Vpb3c/K0h8J+XkBC4RMRUwgb7rc1FKJ HbsgsreRJhjcssrnL8WGCWjefJauZ69rjGimamB66NILGusO+bzoFzfqkoeY89/7L5WIEbF 7A7KGLOAlneY79X6qxhotM0H8ocvHxx7VbzDjZK9JqVg1leAtAg795NCYyD2zLqkaJAVuP2 5MsxzMO8VBXZ0bR1wW5UVA==
X-QQ-GoodBg: 2
X-BIZMAIL-ID: 17315564817489890643
Date: Fri, 26 May 2023 12:14:38 +0800
From: Haisheng Yu <hsyu@cfiec.net>
To: "fgont@si6networks.com" <fgont@si6networks.com>
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>
Message-ID: <4FCF75B585A1D068+7D9B99BB-B24B-4FE8-A3FD-54877C7C1131@cfiec.net>
In-Reply-To: <f5758380-9967-b67b-744d-dc36b7b599ab@si6networks.com>
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>
X-Mailer: MailMasterPC/4.17.9.1009 (Win10 19H2)
X-CUSTOM-MAIL-MASTER-SENT-ID: 82FB1B92-D3C1-4642-B546-98D7B31EB091
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:cfiec.net:qybglogicsvrgz:qybglogicsvrgz6a-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G3N4OMvS_Vce6PjLFPTgBCkgfGE>
Subject: Re: [v6ops] [OPSEC] [IPv6] Why folks are blocking IPv6 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 04:15:51 -0000

Hi, Fernando 

I guess it all depends on the TV? e.g., I for one I'm not planning to throw it out just because Sony decided to quit pushing updates (which were never automatic for my set).

I don't have a Sony TV, so I have a slightly different perspective.

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.

Johnson Yu



---- Replied Message ----
Hi, Brian,

On 23/5/23 00:41, Brian E Carpenter wrote:
[...]

That depends where you choose to apply the zero trust model. As Steve
Bellovin argued many years ago in his distributed firewalls paper,
distributing the trust model to the end systems is best, because you no
longer have to trust any intermediate systems.

Given the amount of things that get connected to the Net (smart bulbs,
refrigerators, etc.) -- and that will super-likely never receive
security updates, you may have to rely on your own network.

For instance, I wouldn't have my smart TV "defend itself".

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

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops
ÿ