Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP

Dave Crocker <dhc@dcrocker.net> Sun, 29 December 2019 22:29 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 544D51200C1; Sun, 29 Dec 2019 14:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 cFS9xQcNutyN; Sun, 29 Dec 2019 14:29:44 -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 5D68112006F; Sun, 29 Dec 2019 14:29:44 -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 xBTMUVgl007888 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 29 Dec 2019 14:30:31 -0800
To: Barry Leiba <barryleiba@computer.org>
Cc: ART ADs <art-ads@ietf.org>, ietf-smtp@ietf.org
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <CALaySJKn4M_O1eKTFWxtOF_VPpqDS8fPQVqmtVC6q8_pUxL9RA@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <702875b2-ed4d-cb85-e0cf-39bb759dfc8f@dcrocker.net>
Date: Sun, 29 Dec 2019 14:29:29 -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: <CALaySJKn4M_O1eKTFWxtOF_VPpqDS8fPQVqmtVC6q8_pUxL9RA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/0hNz3VbsLprZQg0mDx3VhD3SZDE>
Subject: Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP
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: Sun, 29 Dec 2019 22:29:45 -0000

On 12/29/2019 2:08 PM, Barry Leiba wrote:
> I'd like to see us keep to a plan of folding in errata, doing some
> sensible reorganization, otherwise minimizing changes, and
> republishing 5321 with a target of "Internet Standard", which it
> clearly is.
> 
> I'd like to see us then address some of these other issues in a
> separate document, which can go out as BCP or Proposed Standard
> (applicability statement) -- and there are other options as well --
> that would aim to give normative advice about these sorts of things
> but that is not part of the Internet-Standard level spec at this
> point.
> 
> Is there substantial objection to taking that approach?


It's difficult to assess the utility of some other document without 
having a clear idea of what it would be expected to cover and how it 
would be expected to get used.  (It also has never been clear to me how 
useful IETF applicability statements are; my general impression is: not 
very.)

That is, there seems to be an effort to do point-based work here without 
attending to any larger integrated system/architecture level issues.

If there were an urgent need for that point work, this might make sense 
but I haven't noticed that case being made.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net