IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Thu, 19 December 2019 10:07 UTC

Return-Path: <lear@cisco.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 50348120113 for <ietf@ietfa.amsl.com>; Thu, 19 Dec 2019 02:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 pAQ-GH64CmRJ for <ietf@ietfa.amsl.com>; Thu, 19 Dec 2019 02:07:15 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F0E312009E for <ietf@ietf.org>; Thu, 19 Dec 2019 02:07:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3994; q=dns/txt; s=iport; t=1576750035; x=1577959635; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=d6yXOFd8q0S0UnS4mM4YNsdijwPlshGkSW5sTtbNqPM=; b=lrnptPXrRJRHbXLLyBtfbjFGQx3vsb9WYP6ijgYFRZOBoCjXqZVWOuaq Wz9yEPh/uGpjzl4Cw+L9vcVfwz16WE0alBDi2t/LzB4nxWKnIRiEbdFNK MYWZ+WryIFF9I3oCmbpkSy8MnB0vf8Q6/I4wqY9Q6duWT5M9NNHX/etgA k=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BcAAAzS/td/xbLJq1kGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF8g2IBIBIqhAaJA4d0JZMmiAoCBwEBAQkDAQEvAQGEQAKCPzgTAgMNAQEEAQEBAgEFBG2FCwgwhV4BAQEBAgEjQhQFCwsEFCoCAlcGE4MiAYJXIKtadYEyhU+EdRCBNoFTimCCAIE4DBSBTlAuPoQiBwEBgy4ygiwElw6Xe4I/gkOBHJI1FAeCQ4wTi3uEQItUlWSDJwIEBgUCFYFpIoFYMxoIGxVlAYJBPhIYDYQUiQWOQEADMI5DDxeCGwEB
X-IronPort-AV: E=Sophos;i="5.69,331,1571702400"; d="asc'?scan'208,217";a="20576667"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Dec 2019 10:07:12 +0000
Received: from [10.61.197.159] ([10.61.197.159]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id xBJA7BAZ013079 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Dec 2019 10:07:11 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <E0C999A5-18A9-4164-814E-3B85034028D2@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2A262F4C-E5AE-4141-96DC-E56A24A8D8BC"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
Subject: Re: IETF Policy on dogfood consumption or avoidance - SMTP version
Date: Thu, 19 Dec 2019 11:07:10 +0100
In-Reply-To: <1fdc9df2-b66b-26cc-0e83-e973d30b8ec0@tana.it>
Cc: John C Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>
To: Alessandro Vesely <vesely@tana.it>
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>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
X-Outbound-SMTP-Client: 10.61.197.159, [10.61.197.159]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P7znMv4yKes_SizQJrH1nMSOAJc>
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, 19 Dec 2019 10:07:17 -0000


> On 19 Dec 2019, at 10:00, Alessandro Vesely <vesely@tana.it> wrote:
> 
> On Thu 19/Dec/2019 09:16:23 +0100 Eliot Lear wrote:
>> If you can’t manage to get a PTR into the DNS, there are a great many options
>> that include, but are not limited to using a free or pay-for mail service.  You
>> can still build your own, but you may have to use a data center that agrees to
>> update the PTR record for you (this is what I have done).  A mechanism even
>> exists to accomplish this with EC2 at very nominal prices (~USD $10/month)
> 
> 
> That's hardly acceptable.

Alessandro, I respect your opinion,  but we don’t get to decide that for others. The person who gets to decide whether a PTR is required is the MTA administrator and nobody else.  I take the point about market concentration, but that has to be balanced against other operational considerations, and it will likely lose every time.

Eliot

v2.23.0 | Report a Bug | By Email