IETF Logo Mail Archive

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

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 09 August 2021 08:17 UTC

Return-Path: <vasilenko.eduard@huawei.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 0430F3A0877; Mon, 9 Aug 2021 01:17:55 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MMLAAvJRH7km; Mon, 9 Aug 2021 01:17:49 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99ABA3A0875; Mon, 9 Aug 2021 01:17:49 -0700 (PDT)
Received: from fraeml735-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Gjppg1ZRcz6D8Zm; Mon, 9 Aug 2021 16:17:15 +0800 (CST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by fraeml735-chm.china.huawei.com (10.206.15.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Mon, 9 Aug 2021 10:17:44 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml703-chm.china.huawei.com (10.219.141.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 9 Aug 2021 11:17:44 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2176.012; Mon, 9 Aug 2021 11:17:44 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Töma Gavrichenkov <ximaera@gmail.com>, David Farmer <farmer@umn.edu>
CC: Tom Herbert <tom@herbertland.com>, 6man WG <ipv6@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: RE: IPv6 Anycast has been killed by LINUX patch in 2016 - who cares?
Thread-Topic: IPv6 Anycast has been killed by LINUX patch in 2016 - who cares?
Thread-Index: AdeITEcEgFJ2cblRTf2jVtlvbXQCSf//1HuAgAAKBoCABbMDAIAAHJEAgADFrgCAAAXCAIAAJhUAgAAd7wCAAA2xgIAADq8AgAAI1wCAADD9AIAABIYAgAAUnoCAAFXlgIAAwpCAgAAG0AD//vbZkA==
Date: Mon, 09 Aug 2021 08:17:44 +0000
Message-ID: <aea499df6fce4a939e4803a7dd3cc3fe@huawei.com>
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> <CAN-Dau3+e=g-ujo30hKidXfbD0EJZ8-Y8iz7pu+ez3Yakmgzvw@mail.gmail.com> <CALZ3u+Yg89v2NgvTBRQtzJ0Yfyh8G3gio6H9DN7MG5dZV7MTJw@mail.gmail.com>
In-Reply-To: <CALZ3u+Yg89v2NgvTBRQtzJ0Yfyh8G3gio6H9DN7MG5dZV7MTJw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.207.136]
Content-Type: multipart/alternative; boundary="_000_aea499df6fce4a939e4803a7dd3cc3fehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ViH1gwswotnjDdunf745UzdBxrc>
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: Mon, 09 Aug 2021 08:17:55 -0000

Ø  I, too, believe the practical discussion rather belongs to LKML.
No. RFC 7094 permitted Linux people to do what they did.
They are fully compliant with this standard RFC.
They are not compliant with RFC 6437 but it is not their problem to sync RFCs.

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Töma Gavrichenkov
Sent: Sunday, August 8, 2021 10:28 PM
To: David Farmer <farmer@umn.edu>
Cc: Tom Herbert <tom@herbertland.com>; 6man WG <ipv6@ietf.org>; IETF discussion list <ietf@ietf.org>
Subject: Re: IPv6 Anycast has been killed by LINUX patch in 2016 - who cares?

Peace,
On Sun, Aug 8, 2021, 10:03 PM David Farmer <farmer@umn.edu<mailto:farmer@umn.edu>> wrote:
While I agree with you, anycast is an important capability in the Internet architecture

This is sort of an achievement already given some reckless claims on the IETF mailing list!  Thank you.


nevertheless it has many limitations, and is not the panacea you claim it to be, even for DDoS.

If you consider the client-server model, it *is* the panacea, fundamentally, but I agree that p2p and other models of communications might require something else.  My bad, didn't consider these before.


Furthermore, I’m not sure what you or the original reporter of this problem expect the IETF to do to fix the problem that was reported.

Honestly, I've just been answering the questions other people have, sharing my experience.

I, too, believe the practical discussion rather belongs to LKML.

--
Töma

v2.23.0 | Report a Bug | By Email