Re: IETF Policy on dogfood consumption or avoidance - SMTP version

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 16 December 2019 16:32 UTC

Return-Path: <hallam@gmail.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 37C481201DB; Mon, 16 Dec 2019 08:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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 uCfbXAIk5ER7; Mon, 16 Dec 2019 08:32:34 -0800 (PST)
Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) (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 4F779120145; Mon, 16 Dec 2019 08:32:34 -0800 (PST)
Received: by mail-oi1-f179.google.com with SMTP id l136so3795959oig.1; Mon, 16 Dec 2019 08:32:34 -0800 (PST)
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=ZeoPMEZ4zdGWVw4KGSW3TXawbM1nJebLn69nD7PG8jo=; b=GgoOGA7iUYUfc1WfAHKQdeb+c4yvrAsMvbHd9IXN7TNihTIrOWFm+xvvzgCrPjJXlp hlE73nRPn6X7EWgYAW2yWvbqeHGlMb3wbvfmSflUYtJxn2EM0o3IkdP5yxe4n8txoaF9 4QWaYW2Ztsbj5aNVrt4XgLEyaBlnzvM3AeXVeKBALcsjMxtATWh5yHm4gX8xIqk3RSNO tZETveuWNCoGujZCyuH3zXh9PiwRuwUIgPXLNn7c2BK7I598C8yUc4bsK1fA9ypFpEzs OLdyIroLHdOOSrB0m3rR7ZTnYzhF5r3Zc9aRlO01DlgvpX5uDH89+ecPwsrSbN8ksIt2 MXjQ==
X-Gm-Message-State: APjAAAW0TE82hiO+4SR3raDt+twXJKHnZwSOIbnuVas6NQIIZ7yOQryc SHcEP7+bxSCVCGzjAmHIl7o8GBaBp865Bxnu5uxNCQ==
X-Google-Smtp-Source: APXvYqwvrKDrvQE3GRuhQ3dxzFFT6hhp+IioDud8rwyyBV1eAYFlQDG6CgeEIvGT4O941j5OgmGDk+o/VKbBnRnFVdY=
X-Received: by 2002:a05:6808:3a9:: with SMTP id n9mr9595226oie.31.1576513953472; Mon, 16 Dec 2019 08:32:33 -0800 (PST)
MIME-Version: 1.0
References: <8EE11B75E1F8A7E7105A1573@PSB> <m2a77ttff6.wl-randy@psg.com> <CABL0ig4Wz-0dk7bsRpaN6pni2rHEc-jPnygwed_Hygy+CiehQA@mail.gmail.com> <16306b3a-63bd-621e-636c-dd7626f74733@foobar.org>
In-Reply-To: <16306b3a-63bd-621e-636c-dd7626f74733@foobar.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 16 Dec 2019 11:32:24 -0500
Message-ID: <CAMm+Lwiq=2j1Wpp8-eLX7zMUv=GK3a5wYh4SAmTOb=c4FWQmjg@mail.gmail.com>
Subject: Re: IETF Policy on dogfood consumption or avoidance - SMTP version
To: Nick Hilliard <nick@foobar.org>
Cc: Glen <glen@amsl.com>, IETF Discussion Mailing List <ietf@ietf.org>, The IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e31250599d4c297"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TRN07loyC8l28x8DYyGKkB8dmcU>
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, 16 Dec 2019 16:32:35 -0000

On Mon, Dec 16, 2019 at 11:18 AM Nick Hilliard <nick@foobar.org> wrote:

> Glen wrote on 16/12/2019 16:11:
> > /^[0-9.]+$/             550 RFC2821 violation
> > /^\[[0-9.]+\]$/         550 RFC2821 violation
> >
> > In just seconds, I can easily change the messages, or remove the
> > rules, either with complete ease.
>
> s/RFC2821 violation/policy violation/
>
> + let's move on.
>

+1

Try as we may, a 40 year old protocol that was designed before we had any
of the technology required to mitigate abuse is not going to meet every
modern need.

What concerns me is not that the old protocols are failing but that the new
protocols that are being deployed are closed. Sure, the Signal spec is
open. But it is a closed system. You cannot connect to the Signal world
from the outside.

Millions of people are using non-SMTP and non-XMPP messaging systems every
day. Perhaps deployment isn't quite as impossible as some people imagine.