Re: IPv6 Anycast has been killed by LINUX patch in 2016 - who cares?

Tom Herbert <tom@herbertland.com> Sun, 08 August 2021 14:40 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 A52663A2DED for <ipv6@ietfa.amsl.com>; Sun, 8 Aug 2021 07:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P2lJhuQBK-cx for <ipv6@ietfa.amsl.com>; Sun, 8 Aug 2021 07:40:24 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8BD13A2DEE for <ipv6@ietf.org>; Sun, 8 Aug 2021 07:40:23 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id x90so20607310ede.8 for <ipv6@ietf.org>; Sun, 08 Aug 2021 07:40:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6yhgNGEzRtcYMPBcu+1lik2scD4FGv0UxxuojVeYdtQ=; b=SCFjD2WymOmA/Xi8kkhMaimeBZTQvNLutjHaUQ6nX6CZJBBX32ff6PnN7aDXfwGaXG BYu25TDRIVhIJhEGpr4IzzlMGfl7nF3r4VF6q4DNgzPj0BfCG0XH2mBBVMbeo+MUi0Tf D9L8by9t3pM8mMnO5ORSy0SoZI39E12rw8zG1DAD29JhKmwcJLU0VkJe23uk9zY2OUW3 tDHVURe2hqBH9sQgHkpWqj5SSDC0bSJEphS5nGYXYfr4j1VIEZcoxahe6LqJSpof53FV gu4i6vfuwtD6G5wEoHK9TmXMuoJwL8VlBljI02/5eA1efeP9KhnYdThpMLZAJMtBqGgj xQlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6yhgNGEzRtcYMPBcu+1lik2scD4FGv0UxxuojVeYdtQ=; b=q+VY3dLqbFPIBuyTDjJv/dwLu9CG11o+LKZi/CMDqluwslGpC7kvGan/Y7emDZ0ONL yLhroETl5aJsCYTqS/TdmJUguQeFFGFd3sYJ9Yt3CfBfjsL7VskdOLvMnbtDu9hpmwwl QLhSab/PMpP44/wpedllsPtFzk2vd9c6ye/bwpkJZizqV4XvCw2R2pEE5XoZyHz+7ymy VDI4mwz+9USBm214xrB+peDZX+thBfcZ3o2KM6NLbSpLXPYZqgDGDwlvjq5AG4CaSt4b /Wje8XLgQEorVUfmoP3qwCElYIReuQ4zlV+4aeZSLv76wpbl4r2RlytjXoLCqxYhZEuC qMFA==
X-Gm-Message-State: AOAM531Ue35dCOu7UekaOhDWocBvgQs+55ulSSXO3sR/AM8q30Yr83Vu zDxpmi03OXE3vYO+v3weavJ33RnVEn9U7P/7ve+tvw==
X-Google-Smtp-Source: ABdhPJwcev7+V37SxLfFSxnEIyqWayMHq6smft17BDst9vZdcPqg8ZRXiWmN68UwCw3OFbKx3FfRuJstHztTly/CgGA=
X-Received: by 2002:aa7:d3ca:: with SMTP id o10mr24295867edr.383.1628433620270; Sun, 08 Aug 2021 07:40:20 -0700 (PDT)
MIME-Version: 1.0
References: <db8c1a5534e9412ebcfa37682d75f862@huawei.com> <C23D7023-B5B7-47C6-8AC5-65A98822A724@lurchi.franken.de> <CANMZLAZGawUjRhSSE_rA8AyqMx=mx1WFeJ_tZq0KVEXJd2XBfQ@mail.gmail.com> <20210807014730.GA28901@faui48f.informatik.uni-erlangen.de> <CAO42Z2yezZh5-B0PwCuNt2FUMAW-FjMK8QZ8uL4TsPhs26zziw@mail.gmail.com> <20210807151716.GA3098@faui48f.informatik.uni-erlangen.de> <CALZ3u+a_7XQ+R8mV+9KzwRwxa0riP-QD_2R69ycV0NL9jy_S3Q@mail.gmail.com> <20210807175410.GA63079@faui48f.informatik.uni-erlangen.de> <CALx6S36b33LD_hNFvptOJuny4g98=dhq3RtKsGeLx3ks-yYjFg@mail.gmail.com> <6F63D7FE-8768-4BD8-846E-61E50E44228F@lurchi.franken.de> <CALx6S36pbw2angEmDpu5DnX2nix9KgxFs7ExU17x+JXQFs23TA@mail.gmail.com> <CALZ3u+Yt2X3faSVW7K0eaxmaQy6iA6p4=f0c4E_F4CP0tfjHYw@mail.gmail.com> <CALx6S343sL0=5wUTRSXMnhSamjTTZU=DzA9Y+dbJ4NRTu0_83w@mail.gmail.com> <CALZ3u+ad6Cecp4T+wfuKVJ4ZmnQvaCSX2njFPCN8DuctrU6uew@mail.gmail.com> <CALx6S37u=y1wX8+6d8aX-6=N1MFEqO9RwxQN5zhZnS4DLM8DcA@mail.gmail.com> <CALZ3u+bHbsdzQsHOHx-6nEe6yQBbHMDhH9_PWB=WHTchB8tj5w@mail.gmail.com>
In-Reply-To: <CALZ3u+bHbsdzQsHOHx-6nEe6yQBbHMDhH9_PWB=WHTchB8tj5w@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Sun, 08 Aug 2021 07:40:07 -0700
Message-ID: <CALx6S36MpCOh2mR+cfM__ASTdn9c4CuhxUrCnUgEv1WhORLyRg@mail.gmail.com>
Subject: Re: IPv6 Anycast has been killed by LINUX patch in 2016 - who cares?
To: Töma Gavrichenkov <ximaera@gmail.com>
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, 6man WG <ipv6@ietf.org>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007a116505c90d3f38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0qiB0VtWV1e9mX_s3-KaO8aBeDo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 08 Aug 2021 14:40:29 -0000

On Sun, Aug 8, 2021, 12:27 AM Töma Gavrichenkov <ximaera@gmail.com> wrote:

> Peace,
>
> On Sun, Aug 8, 2021, 5:20 AM Tom Herbert <tom@herbertland.com> wrote:
>
>> I don't see DDOS mentioned in this thread.
>
>
> You might have some serious procmail configuration...
> Check out the archives: https://mailarchive.ietf.org/arch/browse/ietf/
>
> If the concern is that an
>> attacker could DDOS an individual address then I'd point out that all
>> unicast addresses are susceptible to that anyway.
>
>
> Exactly my point.
>
> Using anycast as a
>> mitigation to DDoS doesn't seem like a great idea considering the
>> problems being discussed here.
>>
>
> It's quite the opposite: using anycast to mitigate DDoS is the only proper
> way to do it, because, basically, DDoS traffic, generated in thousands of
> locations on the globe, cannot be handled when accumulated in one place.
>
> Either you have multiple traffic termination points on the net (a.k.a.
> anycast), each as close to some traffic generation point as possible, or
> you'll end up having capacity overload around your last mile.  This is the
> equation fundamental to the Internet, while the implementation issues
> discussed here are hardly more than just typical software engineering tasks.
>

Yes, a service needs multiple points of entry, but anycast isn't the only
way to do that. For instance, DNS can return different addresses to users
in different geographic regions, mirrors have long been used for file
download.

Tom


> --
> Töma
>
>>