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

Tom Herbert <tom@herbertland.com> Thu, 18 May 2023 14:29 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 9A0D5C13AE3C for <ipv6@ietfa.amsl.com>; Thu, 18 May 2023 07:29:00 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 P9k980KCB-9K for <ipv6@ietfa.amsl.com>; Thu, 18 May 2023 07:28:56 -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 01A14C13AE43 for <6man@ietf.org>; Thu, 18 May 2023 07:27:39 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-510e419d701so1690871a12.1 for <6man@ietf.org>; Thu, 18 May 2023 07:27:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1684420058; x=1687012058; 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=pynMpHtjOGbrbQ4QeY/ZVt1wO14724QixGWEja9eRtQ=; b=ew1K8y01dlO8xB20QQEW2JwHqbEUsrUj8DP1EnWq97TJH24Sjj1qXSJvddSPxLdp/5 P749dhh865ydhHuDt0cDvzjP1Obrb9jxhJPRlAbEOugYuQhP9m85OahuLWmrUU239uF9 dLrD8LO4Z5oHWv/OqszEenWN/X0oNola58LoNIHYr/zs/GI4Nd/XmuZfuyb3e8udnLbQ s2ggOtWaHYKPVUFkgmwIxmpVvH0mP614SG5WP/K1p8GaE2MYc1LgTNaVYqM9qN6i1Qo3 3tfqkr5nPugb0gS2DCQN8dJPxpOy7jnLqORbdXcC2c6PGj6meIuNVHS576aU7kq7Y76j d9GA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684420058; x=1687012058; 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=pynMpHtjOGbrbQ4QeY/ZVt1wO14724QixGWEja9eRtQ=; b=exnxvT58bq5WSvbaxtg64qYB+fq0Pxw7urdo7P+qJmuA81MX6WfEckumEIONxHuTKE jaGY2YeFfDhISkitUapXbmGePgjpQjlzHMcRu6Ft+lAIVJD4+7vVqROUkrMpR9hzZU0g ZO47e2YPnYSJ2W1chKgqWg72zkBKHP/mJmpmP9Px7abqeAmCVqIQQoyjFSfa16oIek51 Ss6kjfEGEVscPLd72ZSqHGb53Mt51izYn/VcD5hF9J9/MpA+/l8d8ftXkeCZkdS3EnFV xVzzjLOc/GlX0igiqM8kvfLRx0Qi38NLD7IoOLDzoBCOfqpjQe3sCDRBgvdI54+iOtA7 w24g==
X-Gm-Message-State: AC+VfDwfKrVlWcPhYft4uccWOCD/OfmCOLsARX83sxJsIJRtcrZdHLHd mdlhv+QuepHGRFcaTZ8VyLd+SrIi6naHBdZkYjQOlQ==
X-Google-Smtp-Source: ACHHUZ4ogfAUM1iL0lv6Nj4P4RuGXpSFroVHrZyyAmSYGhBuSgedhahMxTlg1M40myf2UNutO/cEpkQLVa0gtMQI1Ao=
X-Received: by 2002:aa7:da45:0:b0:50b:d863:30ea with SMTP id w5-20020aa7da45000000b0050bd86330eamr5912460eds.0.1684420057948; Thu, 18 May 2023 07:27:37 -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>
In-Reply-To: <a087b963-1e12-66bf-b93e-5190ce09914b@si6networks.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 18 May 2023 07:27:25 -0700
Message-ID: <CALx6S349nNA8L5+_1hrbWayqp8GfTYypWy_SP57c_Xxams=csg@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: David Farmer <farmer@umn.edu>, 6man@ietf.org, V6 Ops List <v6ops@ietf.org>, opsec WG <opsec@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Ka2ANbB7-5phf7f6LAl_YN1LC9Y>
Subject: Re: [IPv6] 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, 18 May 2023 14:29:00 -0000

On Thu, May 18, 2023 at 6:17 AM Fernando Gont <fgont@si6networks.com> wrote:
>
> Hi, David,
>
> On 18/5/23 02:14, David Farmer wrote:
> >
> >
> > On Wed, May 17, 2023 at 13:57 Tom Herbert
> > <tom=40herbertland.com@dmarc.ietf.org
> > <mailto:40herbertland.com@dmarc.ietf.org>> wrote:
> [...]
> >
> > Maximum security is rarely the objective, I by no means have maximum
> > security at my home. However, I don’t live in the country where some
> > people still don’t even lock there doors. I live in a a city, I have
> > decent deadbolt locks and I use them.
> >
> [....]
> >
> > So, I’m not really happy with the all or nothing approach the two of you
> > seem to be offering for IPv6 extension headers, is there something in
> > between? If not, then maybe that is what we need to be working towards.
>
> FWIW, I[m not arguing for a blank "block all", but rather "just allow
> the ones you really need" -- which is a no brainer.

Fernando,

I'm not sure how that's a no brainer, who decides "the ones you really
need"? If everyone independently makes that decision then we wind up
with an Internet that can't evolve and is perpetually stuck in the
status quo.

> The list you need
> is, maybe Frag and, say, IPsec at the global level? (from the pov of
> most orgs).
>
> (yeah... HbH and the like are mostly fine for the local link (e.g. MLD).
>
It might be productive if you suggested a more concrete direction
here. Maybe a proposed BCP suggesting the EHs that you believe should
be universally blocked and the rationalization for that and why the
problems with them can't be fixed.

Tom

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