Re: Accurate history [Re: "professional" in an IETF context]

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 08 November 2021 14:13 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E69743A0C2A for <ietf@ietfa.amsl.com>; Mon, 8 Nov 2021 06:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.228
X-Spam-Level:
X-Spam-Status: No, score=-5.228 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_NONE=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 mSyxDFQh5SSm for <ietf@ietfa.amsl.com>; Mon, 8 Nov 2021 06:13:35 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 805583A0C5B for <ietf@ietf.org>; Mon, 8 Nov 2021 06:13:33 -0800 (PST)
Received: (qmail 17130 invoked from network); 8 Nov 2021 14:11:06 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 8 Nov 2021 14:11:06 -0000
Message-ID: <8f8c3279-22e8-72d7-5262-d1c93d891f71@necom830.hpcl.titech.ac.jp>
Date: Mon, 08 Nov 2021 23:13:31 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Subject: Re: Accurate history [Re: "professional" in an IETF context]
Content-Language: en-US
To: ietf@ietf.org
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <885e62bf-7d6a-4501-a48a-e7c2cbf20382@joelhalpern.com> <e59adb61-a55c-7f5f-a60a-40bf186c139d@necom830.hpcl.titech.ac.jp> <CAC8QAceMSrfkqGTYcMNr3JargO3gxJqTaEyf02LGHd-KVeUDHw@mail.gmail.com> <6286da3e-2beb-9556-089a-2e1951573b1e@gmail.com> <59c80b60-438f-b10f-ad61-ba839f6e4f95@necom830.hpcl.titech.ac.jp> <e834916e85ea47ef94fce07c23928d2b@huawei.com> <37b299c8-e821-07e5-6240-68fb9d1ca137@gmail.com> <23b450fb11eb4a51bb4ee837b5c52657@huawei.com> <a805b50d-3ccd-dd2a-4931-6c6dc9a8ede3@necom830.hpcl.titech.ac.jp> <CAC8QAceY1gtK5v3WGMd4OB0z826jDiDDw_g1LbjWef7MKTnrcg@mail.gmail.com> <7d6af5bc-9663-7e4e-26ba-23fb1e4dccbe@necom830.hpcl.titech.ac.jp> <7238184A-53D6-42C3-B9C3-E333513A8636@sobco.com> <513d8f63-78c6-50ca-9d11-ee128af0d202@foobar.org> <f6ecd8af8e0040869e152b086e041a42@huawei.com> <E285424F-7E21-47BF-8235-BF9710F1593C@gmail.com> <23408009-7933-d1ed-6347-13092ee3abc9@gmail.com> <a9d6ed638692428aa5b67f16f961a1cc@huawei.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <a9d6ed638692428aa5b67f16f961a1cc@huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8AAmhgiDdE8mjDpUZeY73Z2PjBo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2021 14:13:41 -0000

Vasilenko Eduard wrote:

> About ARP storm:

For the accurate history, ARP storm was a problem about 30 or 35
years ago, when some network managers were putting *thousands* of
hosts in a single broadcast domain. Then, as switch implementations
were too often buggy, broadcast storm was a rare but serious problem
of the managers and it was sometimes called ARP storm because
ARP is the major protocol to use broadcast.

Though IP people at that time were happy with small subnets
divided by routers following the CATENET model, the reasoning
to have large broadcast domain was that managing routers to
support multiple L3 protocols is painful, which is still so
for management of routers supporting both IPv4 and IPv6.

IIRC, Brian was a such manager.

But, as IPv4 became the only protocol worth supporting, Ethernet
broadcast domain became small divided by IPv4-only routers and
switch implementations became not so buggy, ARP storm is not a
problem today at all.

> ND has much bigger DoS capabilities because

Though many people who insists on IPv6 totally misunderstand,
broadcast ban by IPv6 is totally meaningless as requiring to
support all host multicast instead of broadcast is as bad (it
is actually not bad) as supporting broadcast.

Though I have found that, these days, some people says "ARP storm"
mean some compromised host generates a lot of broadcast ARP packets,
it is no worse than the host generates a lot of all-host-multicast
ND packets.

As such, ND is no better than ARP.

						Masataka Ohta