Re: [ietf-smtp] Endless debate on IP literals

Dave Crocker <dhc@dcrocker.net> Thu, 02 January 2020 18:07 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9753912009E for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 10:07:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 gkCTqqAgEXr6 for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 10:07:08 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 4BF38120090 for <ietf-smtp@ietf.org>; Thu, 2 Jan 2020 10:07:08 -0800 (PST)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 002I80dL023193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 Jan 2020 10:08:01 -0800
To: John R Levine <johnl@taugh.com>
Cc: ietf-smtp@ietf.org
References: <alpine.BSF.2.21.99999.352.2001011101090.45428@gal.iecc.com> <f0f15437-8315-8e5e-e402-c3e8b0688261@dcrocker.net> <25cabd85-681c-28d4-64e3-97f1ec170911@dcrocker.net> <alpine.OSX.2.21.99999.374.2001011126340.52164@ary.qy> <c3fcf56a-e9b9-e979-16b0-cbec677dd2f2@dcrocker.net> <alpine.OSX.2.21.99999.374.2001021202330.56444@ary.qy>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <794462ec-e54b-ca8d-76f6-490384f4b051@dcrocker.net>
Date: Thu, 02 Jan 2020 10:07:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.99999.374.2001021202330.56444@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/CVI5XX1mvAV_ABE_VYjaJPJEtGQ>
Subject: Re: [ietf-smtp] Endless debate on IP literals
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2020 18:07:10 -0000

On 1/2/2020 9:03 AM, John R Levine wrote:
> Agreed.  I do think there's a few things like STARTTLS that need to move 
> into the mandatory core, but not many.


To beat this point into the ground, just to make sure there is no 
confusion:  since starttls isn't in rfc5321...

The target documents would be:

    1) Astreamlined rfc5321bis

    2) A document specifying requirements for Exterior MTAs, which would 
include mandating rfc5321bis, starttls, ...

    3) Possibly a document specifying requirements for Interior MTAs?


My impression is that there's some amount of desire to restrict use of 
IP literals in EHLO [*] to interior mtas, and prohibiting them from 
exterior mtas.

If that assessment is roughly correct, it would mean that rfc5321bis 
would specify /only/ support for domain names in the EHLO command, with 
an Interior MTA document specifying an enhancement to the command, to 
allow use of IP literals.


d/

[*] whether and where to deprecate HELO is a separate issue needing 
similar consideration for scope of use.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net