Re: IETF Policy on dogfood consumption or avoidance - SMTP version
"Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu> Sun, 22 December 2019 06:46 UTC
Return-Path: <valdis@vt.edu>
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 A469612008C for <ietf@ietfa.amsl.com>; Sat, 21 Dec 2019 22:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 2_M6d6Z4HeYg for <ietf@ietfa.amsl.com>; Sat, 21 Dec 2019 22:46:07 -0800 (PST)
Received: from omr2.cc.vt.edu (omr2.cc.ipv6.vt.edu [IPv6:2607:b400:92:8400:0:33:fb76:806e]) (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 D682212001E for <ietf@ietf.org>; Sat, 21 Dec 2019 22:46:06 -0800 (PST)
Received: from mr5.cc.vt.edu (smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id xBM6k5JT017076 for <ietf@ietf.org>; Sun, 22 Dec 2019 01:46:05 -0500
Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by mr5.cc.vt.edu (8.14.7/8.14.7) with ESMTP id xBM6k0oZ027701 for <ietf@ietf.org>; Sun, 22 Dec 2019 01:46:05 -0500
Received: by mail-qt1-f198.google.com with SMTP id x8so9022773qtq.14 for <ietf@ietf.org>; Sat, 21 Dec 2019 22:46:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=xS7JakofIuulBnAdw6ql+Do7YKW/J7OpQVwHGLjsmjY=; b=YTcLGoKHZKaNazf1ea19f+ubrBLxKIhxnPsbIZZVgCLNOOiUEFGCn5otPvSrtc5bDG mXd4VSWdI3uQDT59piDwDNGbm+Cib7Pwab0Z8jujFH4pjW/vw2Xw7ITTNuy3z6WS6kfh KbtGWNno+LkUQ0u2yputibQlZFmOGPYGV8Sip3DwBECUDU/BrRY8m3rvVWNCQVZ6HRuS FZu3kUmnAoxtBBjpKNbbc+T26K7f9Ce4heLtgJq3Cm+lmXktKksbw2DLzyzZV5WFPnU4 7TPsKDbgdUpO1ObRhP0RR1+VQWX92BjP2Dr9wre7ltlTS+GBcIJkX9yHt4uCYEbr2bR0 2rUQ==
X-Gm-Message-State: APjAAAXODTsbI1Gd32iqHq4Snj17cz/Rq8qmTUgjIIMBIdgQQKyuS+fI m+ra+XdNIZtMpsdOO/3sFBNd8CytwLYsAXkJJkffaeA1V381jheNvJOAoRhkPG1489eUTmfntxE TZ9d2iy/jq1a6wOA=
X-Received: by 2002:a05:6214:1745:: with SMTP id dc5mr18865855qvb.230.1576997159499; Sat, 21 Dec 2019 22:45:59 -0800 (PST)
X-Google-Smtp-Source: APXvYqyXwm/D36q5shy4UiSi/v3aQMyyfBBh//Hxluk51W+ODTdTs66ErxZx2XOKKOiZCnyNAk3WFA==
X-Received: by 2002:a05:6214:1745:: with SMTP id dc5mr18865840qvb.230.1576997159188; Sat, 21 Dec 2019 22:45:59 -0800 (PST)
Received: from turing-police ([2601:5c0:c001:c9e1::359]) by smtp.gmail.com with ESMTPSA id o6sm4522720qkk.53.2019.12.21.22.45.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Dec 2019 22:45:57 -0800 (PST)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: Valdis Kl=?utf-8?Q?=c4=93?=tnieks <valdis.kletnieks@vt.edu>
X-Google-Original-From: "Valdis Klētnieks" <Valdis.Kletnieks@vt.edu>
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev
To: hsantos@isdg.net
Cc: ietf@ietf.org
Subject: Re: IETF Policy on dogfood consumption or avoidance - SMTP version
In-Reply-To: <5DFBB0FD.2010902@isdg.net>
References: <8EE11B75E1F8A7E7105A1573@PSB> <m2a77ttff6.wl-randy@psg.com> <CABL0ig4Wz-0dk7bsRpaN6pni2rHEc-jPnygwed_Hygy+CiehQA@mail.gmail.com> <16306b3a-63bd-621e-636c-dd7626f74733@foobar.org> <4D7EEBF62E149D1F23BA6A32@PSB> <58595081-6F4F-45E2-9798-B691AC919D28@cisco.com> <15D46124EFC1486F3613EF01@PSB> <0D67643B-00ED-482A-BCE0-1CF5A513C61F@cisco.com> <1fdc9df2-b66b-26cc-0e83-e973d30b8ec0@tana.it> <E0C999A5-18A9-4164-814E-3B85034028D2@cisco.com> <5DFBB0FD.2010902@isdg.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1576997156_12604P"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 22 Dec 2019 01:45:56 -0500
Message-ID: <26902.1576997156@turing-police>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z5ladqBvMgadaifMO6WFv5qB0po>
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: Sun, 22 Dec 2019 06:46:08 -0000
On Thu, 19 Dec 2019 12:18:53 -0500, Hector Santos said: > But the SMTP specs also say, it MUST NOT reject on this basis and I > was part of the WG encouraging text that we now find in section 7.9 > because we had new situations where a "MUST NOT reject" rule was not As it turns out, it wasn't rejecting on that basis, it was rejecting on a "not having a FQDN is a very strong spam signal" policy basis and erroneously issuing the wrong message. Given that there were *two* rules involved, one of which *did* flag an actual protocol violation, I'm willing to accept it's just a cut-n-paste error that nobody actually noticed for a decade or so... And maybe it's time to let that "address literal" sail into the sunset. If you're an MUA on a DHCP'ed device, there's a good chance that you don't know your FQDN. But at that point, the reality is that you're probably talking to an MSA on port 587 rather than a full MTA on port 25, and the MSA is (or should be) going to be authenticating you far more strictly than checking your EHLO. And if you're a full MTA on the public internet today, and *don't* have a FQDN, you're going to have a really bad day in 2019, *totally notwithstanding what the RFCs say about how it's totally legal*. What consenting MTA's do inside a walled garden is, of course, totally up to the administrators involved. They can use X.400 for all the rest of the net cares. We passed the point of a significant divergence between "what works in a walled garden" and "what works in the wild" at least a decade ago. And at *some* point, that's a big pile of technical debt that's going to need to be paid back. At this point, the least bad option is probably producing an updated rfc5321/5322 that documents the protocol, and a BCP/guidance document of "but here's what you need to be doing to ensure you can survive in the wild".
- Re: IETF Policy on dogfood consumption or avoidan… Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- IETF Policy on dogfood consumption or avoidance -… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Randy Bush
- Re: IETF Policy on dogfood consumption or avoidan… John Levine
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Nick Hilliard
- Re: IETF Policy on dogfood consumption or avoidan… Keith Moore
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Salz, Rich
- Re: IETF Policy on dogfood consumption or avoidan… Keith Moore
- Re: IETF Policy on dogfood consumption or avoidan… Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- Re: IETF Policy on dogfood consumption or avoidan… John R Levine
- Re: IETF Policy on dogfood consumption or avoidan… Randy Bush
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Keith Moore
- Re: IETF Policy on dogfood consumption or avoidan… Nick Hilliard
- Re: IETF Policy on dogfood consumption or avoidan… S Moonesamy
- Re: IETF Policy on dogfood consumption or avoidan… Glen
- Re: IETF Policy on dogfood consumption or avoidan… Nick Hilliard
- Re: IETF Policy on dogfood consumption or avoidan… Phillip Hallam-Baker
- Re: IETF Policy on dogfood consumption or avoidan… Glen
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Andrew G. Malis
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Andrew G. Malis
- Re: IETF Policy on dogfood consumption or avoidan… Randy Bush
- Re: IETF Policy on dogfood consumption or avoidan… Jay Daley
- Re: IETF Policy on dogfood consumption or avoidan… Andrew G. Malis
- Re: IETF Policy on dogfood consumption or avoidan… Jay Daley
- Re: IETF Policy on dogfood consumption or avoidan… Rob Sayre
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Salz, Rich
- Re: IETF Policy on dogfood consumption or avoidan… Alissa Cooper
- Re: IETF Policy on dogfood consumption or avoidan… Jay Daley
- Re: IETF Policy on dogfood consumption or avoidan… Hector Santos
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Brian E Carpenter
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Hector Santos
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Salz, Rich
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Keith Moore
- Re: [ietf-smtp] the inedible parts of IETF dogfoo… John Levine
- Re: [ietf-smtp] the inedible parts of IETF dogfoo… Keith Moore
- Re: [ietf-smtp] the inedible parts of IETF dogfoo… George Michaelson
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Randy Bush
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Hector Santos
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Hector Santos
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Eliot Lear
- Re: IETF Policy on dogfood consumption or avoidan… Alissa Cooper
- Re: [ietf-smtp] epostage is still a bad idea, the… John R Levine
- Re: [ietf-smtp] IETF Policy on dogfood consumptio… Salz, Rich
- Re: [ietf-smtp] epostage is still a bad idea, the… Phillip Hallam-Baker
- Re: IETF Policy on dogfood consumption or avoidan… Keith Moore
- Re: IETF Policy on dogfood consumption or avoidan… Hector Santos
- Re: IETF Policy on dogfood consumption or avoidan… John C Klensin
- Re: IETF Policy on dogfood consumption or avoidan… Eliot Lear
- Re: IETF Policy on dogfood consumption or avoidan… Alessandro Vesely
- Re: IETF Policy on dogfood consumption or avoidan… Viktor Dukhovni
- Re: IETF Policy on dogfood consumption or avoidan… Eliot Lear
- Re: IETF Policy on dogfood consumption or avoidan… Hector Santos
- Re: [ietf-smtp] epostage is still a bad idea, the… Brandon Long
- Re: [ietf-smtp] epostage is still a bad idea, the… Phillip Hallam-Baker
- Re: IETF Policy on dogfood consumption or avoidan… Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- Re: IETF Policy on dogfood consumption or avoidan… Hector Santos
- The dogfood discussion (was: Re: IETF Policy on d… John C Klensin
- Re: The dogfood discussion (was: Re: IETF Policy … Viktor Dukhovni
- Re: The dogfood discussion (was: Re: IETF Policy … Eliot Lear (elear)