Re: The end of the Internet as we now it

Toerless Eckert <tte@cs.fau.de> Thu, 15 October 2020 22:37 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 15A213A0B16 for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 15:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 lDn7mf3C8uvD for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 15:37:12 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 560153A0B17 for <ietf@ietf.org>; Thu, 15 Oct 2020 15:37:12 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DA485548068; Fri, 16 Oct 2020 00:37:06 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D22F0440059; Fri, 16 Oct 2020 00:37:06 +0200 (CEST)
Date: Fri, 16 Oct 2020 00:37:06 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Christian Huitema <huitema@huitema.net>
Cc: Michael Thomas <mike@mtcc.com>, ietf@ietf.org
Subject: Re: The end of the Internet as we now it
Message-ID: <20201015223706.GA37210@faui48f.informatik.uni-erlangen.de>
References: <1245BFD6-1178-40D2-A475-838687A26A6F@puck.nether.net> <6626EED3-1CC1-4B40-879C-C68425A41B78@gmail.com> <8119d23c-5db5-060e-34e9-895d50c6eb4b@huitema.net> <8686EA57-4A60-4B56-98E1-503344C86627@mnot.net> <648fcb28-688e-0a37-cac6-9eb6821002ce@huitema.net> <8e8a52dd-9c02-ab9e-69e5-161d5042efd8@mtcc.com> <9d753c44-9846-23a3-6b2e-6f140bcc757b@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9d753c44-9846-23a3-6b2e-6f140bcc757b@huitema.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DFrfDcsDv8eawH5ehrp1eVkVNwA>
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: Thu, 15 Oct 2020 22:37:14 -0000

On Thu, Oct 15, 2020 at 12:26:50PM -0700, Christian Huitema wrote:
> I know that my choice of subject line was a bit over the top, but maybe
> it is not so wrong after all. Even sophisticated web site operators like
> our tools team have difficulties dealing with spikes of traffic and with
> attacks, and they have only blunt instruments at their disposal. So,
> yes, the Internet is not working as it used too.

In the past i had similar blocks for other web services, but at least
i did get web page replies that explicitly said that my IP addres
was blocked for he service due to abuse (i think back when comcast was
using dynamically reassigned ip addresses). Would be great if this
diagnosis could be fashioned also for ietf tool services
so users don't have to guess or get hold of the ietf tools admin.

Wasn't there something with IETF using cloudflare or the like ? I
don't know exactly what they offer, but a hardened web page saying as
much (your address is blocked due to abuse, resolve problem...)
to which a redirect at network level could be done should be possible.

Aka: Just ACL filtering is not nice to the users, but i am only
guessing how its set up - your initial info wasn't fully conclusive
in between "access denied" and "no packets coming back".

Cheer
    toerless