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

Arnaud Taddei <arnaud.taddei@broadcom.com> Thu, 25 May 2023 05:12 UTC

Return-Path: <arnaud.taddei@broadcom.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 39735C151090 for <ipv6@ietfa.amsl.com>; Wed, 24 May 2023 22:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_NONE=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 (1024-bit key) header.d=broadcom.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 FvR7trNtGKOD for <ipv6@ietfa.amsl.com>; Wed, 24 May 2023 22:12:23 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 571F9C151091 for <ipv6@ietf.org>; Wed, 24 May 2023 22:12:22 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-51440706e59so404003a12.3 for <ipv6@ietf.org>; Wed, 24 May 2023 22:12:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1684991541; x=1687583541; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NlHnuIvPUSR8nlCXvhpzVMTgv9QInH2I/XfRLkKuftU=; b=CBH38WZ0xuPmMLP+qdZnNkuzUOQ1P6k1fkjhc+GBnaUC2fZ+67/aEcbMd3i0QatY7m C1pW6xyuRcyOppSihfmqj/PmuVA+EhmzajliHhiRVpART0lcIXWQlR+aGFO+WoSu1A8e MGoZ93CXCMavlHgFd6tfe56IhIg/koN1ZUYKM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684991541; x=1687583541; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NlHnuIvPUSR8nlCXvhpzVMTgv9QInH2I/XfRLkKuftU=; b=PCh/g8zBvVc5sUV071kA2Uz+qus2aLe8e7WgiiMGskaiXk+Y8UbcESuKWG+p38lF84 I8XTsdXKHUayMOBHq44WT5J73iTFpoPJf8yEi7GefPyILJmmq8oNf1aXKFL+dMEUuV0+ lfLaByfkuV6ozWk3T3bNYRYv7Eg60sDwLpjI33Cyb1hxfzGkersHrcU+KZtiJYKfZ9fQ G1Oymrd5O9o0ECXe2g9rsc+l5NMby0mqonhCf58BEHteHHJZWNJIQQVeipmwAyAXfARO JxeCaxQVbJS40a7eJ07mDqWxeYXK8MKVm6TO5+RcxBP0VWrKGMJ65AtOo9Hj7pPmLm25 vjTQ==
X-Gm-Message-State: AC+VfDzpIfO2xEY7PZ+zz1STOrBVV8mnhmQNJx9HygRtA7co0x1siaEv pUlTrnoIsO7/OWzBLqmKmT6DMa0vGE8/Kl2T6V6qir7nPUS3uahTdIKOAxAxGmJBoHTDeJc=
X-Google-Smtp-Source: ACHHUZ6xAxne5txUBXsX2YPUnNNhsv5sq4Fe4ZTR7YainWr6A8lQL9MmmdtFWliWciLuirZqMpBZBA==
X-Received: by 2002:aa7:d8c3:0:b0:514:272f:7083 with SMTP id k3-20020aa7d8c3000000b00514272f7083mr2648571eds.24.1684991540727; Wed, 24 May 2023 22:12:20 -0700 (PDT)
Received: from smtpclient.apple ([178.197.198.212]) by smtp.gmail.com with ESMTPSA id h25-20020aa7c619000000b0050bd245d39esm168040edq.6.2023.05.24.22.12.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 May 2023 22:12:19 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
In-Reply-To: <1cf9c93b-32db-6d30-9ea9-951172587a9a@si6networks.com>
Date: Thu, 25 May 2023 07:12:05 +0200
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, IPv6 Operations <v6ops@ietf.org>, 6man <ipv6@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Message-Id: <588C62B7-0FA1-4C3F-8EE2-1CB58A667407@broadcom.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> <72784f8e65f34bcc9f5652c0a553c70c@boeing.com> <1cf9c93b-32db-6d30-9ea9-951172587a9a@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3731.500.231)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000422b2505fc7daaa1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ptNxjRCDA_UqmQ0O-g-xRQDhs_k>
Subject: Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why folks are blocking IPv6 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: Thu, 25 May 2023 05:12:28 -0000

Would like to support Fernando again, and not just because I have a Sony TV too. 

Cybersecurity is in such a bad state that I can only plea for a sense of realism and pragmatism vs dogmatism to get real solutions at hand to the defenders practitioners

If not I will ask people here to consider spending a week in a Security Operation Center when there is a Ransomware breaking up 

Fernando’s paper intentions will be appreciated by the defenders  



> On 25 May 2023, at 03:07, Fernando Gont <fgont@si6networks.com> wrote:
> 
> 
> 
> On 25/5/23 02:01, Manfredi (US), Albert E wrote:
>> -----Original Message-----
>> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Fernando Gont
>>> 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".
>> Agreed, "on your own network." From the viewpoint of a household, whatever network defense has to be behind that household's router, for it to be credible, and preferably right in each host. Yeah, some IoT devices may not be updated regularly.
> 
> So, that's why people block them at the edge.
> 
> (just the messenger)
> 
> 
> 
>> The ISP has to worry about protecting that ISP's own network. 
> 
> That's e.g. where RFC9098 comes in, with notes on why they are dropped in places other than the edge network.
> 
> 
> 
>> Households have to be responsible for protecting their household's network. (And connected TVs do get regular software updates, as a matter of fact.)
> 
> 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).
> 
> Thanks,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
> 
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.google.com/url?q=https://www.ietf.org/mailman/listinfo/opsec&source=gmail-imap&ust=1685581681000000&usg=AOvVaw2CR1KLp2V-YO9ZOvhwrWtn


-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.