IETF Logo Mail Archive

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

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Fri, 26 May 2023 23:26 UTC

Return-Path: <albert.e.manfredi@boeing.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 B933CC14CF1C; Fri, 26 May 2023 16:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=boeing.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 0onFDa2RhPTg; Fri, 26 May 2023 16:26:17 -0700 (PDT)
Received: from ewa-mbsout-02.mbs.boeing.net (ewa-mbsout-02.mbs.boeing.net [130.76.20.195]) (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 DDED3C14CF15; Fri, 26 May 2023 16:26:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 34QNQFnx053387; Fri, 26 May 2023 16:26:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1685143575; bh=CxcRD7qkONXxBj0EP//yUPwmvz/pollVY7u84AtXphQ=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=G06Rt9ogma21PaShutvAVWsSE6pY8rXR7N/FjW/75AvWmF4rPti1v+P0+mBT95+JP aQx+S05hha7LPvuAwayTaoOWdC3fgw/ByMFG/2eT2TseLAMWwk2gx1RELN8WCtO/yn T5FCCyOtK8w7aWBXFrqAlGMuW/MDDdsgpiwg1NISuxjxh7mM/aD8DHEiwsJUDhUUSZ LFR3hi/T5x4aNkHw2iGV3gd3o53Lu77DN0+LmkkdSJ36GQlFRthS1fwUuB7Y9/xQb6 GI4MxyMRJtoXStNyhRqPXWcFozjagdMOGADc05FbpspYs6xwTlYw0wow4lsfJvU6wE ivr/seOHDik/g==
Received: from XCH16-08-01.nos.boeing.com (xch16-08-01.nos.boeing.com [137.137.111.40]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 34QNQ4FY053291 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 26 May 2023 16:26:04 -0700
Received: from XCH16-08-01.nos.boeing.com (137.137.111.40) by XCH16-08-01.nos.boeing.com (137.137.111.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.17; Fri, 26 May 2023 16:26:02 -0700
Received: from XCH16-08-01.nos.boeing.com ([fe80::e4ad:46fa:7f1a:20e4]) by XCH16-08-01.nos.boeing.com ([fe80::e4ad:46fa:7f1a:20e4%10]) with mapi id 15.01.2507.017; Fri, 26 May 2023 16:26:02 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Thread-Topic: [EXTERNAL] Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv 6 extension headers? (Episode 1000 and counting) (Linux DoS)
Thread-Index: AQHZj+txfXFBIdickkiF/1PMPMcXtK9tez4AgAAOsgD//6PyoA==
Date: Fri, 26 May 2023 23:26:02 +0000
Message-ID: <2a02905427604fa6a4c95e2eaa1dd165@boeing.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> <4FCF75B585A1D068+7D9B99BB-B24B-4FE8-A3FD-54877C7C1131@cfiec.net> <375ea678-b05f-7bb6-5ae2-43c54cd271f4@si6networks.com> <CALx6S34u5=2UxEz3zeApv+_-W=PTj0PzMRHS1UC=zRchqVCDyQ@mail.gmail.com> <882610dc-cf8f-e08d-8d9e-0e786097f520@si6networks.com> <CALx6S34AnMaVyEVQxaO0b1JGbQetQvDC+xDHk6aH5vbXM-KT7A@mail.gmail.com>
In-Reply-To: <CALx6S34AnMaVyEVQxaO0b1JGbQetQvDC+xDHk6aH5vbXM-KT7A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 14668D37ECC32E8E51A1C5773CD92E549E07B1D795A0281121FB5EB8885DDBE32000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/i8prhe1D5-F4BczLML-PmOSssL8>
Subject: Re: [IPv6] [EXTERNAL] Re: [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 23:26:20 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Tom Herbert

> And IETF exists for the good of the Internet and the world's population, not so your company can make money!

Ouch, Tom, let's not devolve the conversation here.

"Making money," legally of course, is nothing more than proof the system works. The IETF exists because many companies around the world see a great benefit in having such a communications tool available to them. These companies pay some of their people to participate. IETF participants are not typically just independently wealthy free agents. Each of these guys fits in some category of participant (equipment vendor, network provider, application designers) and each has a responsibility to see that their interests are met, not ignored.

If the communications tool introduces vulnerabilities that would potentially detract from their businesses, the IETF participants have the responsibility to bring that to light. We can’t expect some nebulous "greater good," however each of us defines that, to cause damage to users of the Internet. Besides which, ideas of what constitutes an actual "the greater good" are probably as varied as are the IETF participants.

Bert

v2.23.0 | Report a Bug | By Email