IETF Logo Mail Archive

Re: [arch-d] deprecating Postel's principle- considered harmful

Joe Touch <touch@strayalpha.com> Thu, 09 May 2019 02:25 UTC

Return-Path: <touch@strayalpha.com>
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 C7B7912024D for <ietf@ietfa.amsl.com>; Wed, 8 May 2019 19:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level:
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 cMuxZLheD4Vx for <ietf@ietfa.amsl.com>; Wed, 8 May 2019 19:25:14 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CAB6120266 for <ietf@ietf.org>; Wed, 8 May 2019 19:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=C+SAz3qzsSPWIbcU54wS54FEMl/oKmKUmqmwSy9EK7k=; b=F3UbogzqeLdibhxmt6zM9N+4D mXgIOodYVjDGNiKVmrHa/RavenjScZq8mxsd6hLv+2d39uMDOmQUKh7dRH3c2/y6e53IVH25dK8Ck 9AOee118DEIUVP1hiZ9oShewGg9BLAu1zeubsTY6KYaF3LTLZgUpSAe5d3RtQ1vP4iwfRPRwa/vcU B1WDljpBOrAJppgzmgF4e//UuLXRzJFGLZQqAtXD+hz4Ps0wEIr/cfdqzXaboj/zgI44KoZ94uGuD F3gA22aLxwpMItT15uINxx+3m9MF3Lsy3NaHxX3K6STyFa1/QqqScc46661MFUzM7iXTRay53qr3f TzCsgz7Cg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:55760 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1hOYk0-004AXM-Ku; Wed, 08 May 2019 22:25:05 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_C78ECB23-7291-40E0-8CC4-58ACDA86F42C"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [arch-d] deprecating Postel's principle- considered harmful
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <992ddb8c-449f-e480-5019-4c882a42ac16@cs.tcd.ie>
Date: Wed, 08 May 2019 19:24:59 -0700
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Message-Id: <346BD702-EA92-4D44-A64D-168720D8B81B@strayalpha.com>
References: <F64C10EAA68C8044B33656FA214632C89F024CD3@MISOUT7MSGUSRDE.ITServices.sbc.com> <CALaySJJDHg5j9Z7+noS=YXoNROqdsbJ6coEECtLtbJ6fWJ3xsQ@mail.gmail.com> <DBD4837F-299B-497C-8922-AFF858B06C0F@strayalpha.com> <EDB037CE-F16A-4392-B36C-F44E30F29753@tzi.org> <9b590e5f-907f-79bd-8aaa-86bf8a9dc446@kit.edu> <0D0CA9B6-2FBA-4281-953A-F21F0BF04398@strayalpha.com> <6583f36d-ff9a-49c6-2da9-857edd67f4b4@network-heretics.com> <5A1C28E9-376A-425F-B7BF-0ADAFB3A244F@strayalpha.com> <7763659b-c6d3-8ca9-b8ad-a801615845e0@network-heretics.com> <29A35F0F-E521-4DC8-8068-9DDC83BFE1AE@strayalpha.com> <992ddb8c-449f-e480-5019-4c882a42ac16@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9r81H8b9Fc1Xsa1l8Nl7kdkuVz0>
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, 09 May 2019 02:25:27 -0000


> On May 8, 2019, at 5:48 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> On 09/05/2019 01:04, Joe Touch wrote:
>> 
>> If you think you can manage the flood by inferring it was an attack,
>> all you will accomplish is not protecting yourself from an
>> accidentally flood.
> That seems to make no sense at all to me. I doubt anyone
> thinks they can manage DoS attacks by just "inferring."
> If they do, they deserve all they get:-)

My point is simple:

- if you’re running out of resources, do you care whether it’s a deliberate, malicious attack or just traffic that takes your site down?
- if you’re not running out of resources, what is really being attacked?

“attack” is irrelevant.

If you have resources you need to protect from over use or incorrect use, do so.

Stop trying to decide WHY; it’s enough to address HOW.

Joe

v2.23.0 | Report a Bug | By Email