Re: [ietf-smtp] An Applicability Stateement for core email specifications - and request for AD advice/instructions

John C Klensin <john-ietf@jck.com> Tue, 17 March 2020 23:46 UTC

Return-Path: <john-ietf@jck.com>
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 046F13A0B29; Tue, 17 Mar 2020 16:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 E9Br5nKRiCnE; Tue, 17 Mar 2020 16:46:07 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C69C3A0B1F; Tue, 17 Mar 2020 16:46:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jELuI-000LqY-PI; Tue, 17 Mar 2020 19:45:58 -0400
Date: Tue, 17 Mar 2020 19:45:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
cc: ietf-smtp@ietf.org, art-ads@ietf.org, superuser@gmail.com
Message-ID: <3A16D7C89843E9BC7512F7B7@PSB>
In-Reply-To: <59CC395A-3630-4B48-A834-9338F7501888@fastmail.fm>
References: <AB1A97E4B60AFB6A17DDF756@JcK-HP5.jck.com> <59CC395A-3630-4B48-A834-9338F7501888@fastmail.fm>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/MXlgLSLEF7e84u_47l5HFf5pGpE>
Subject: Re: [ietf-smtp] An Applicability Stateement for core email specifications - and request for AD advice/instructions
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: Tue, 17 Mar 2020 23:46:18 -0000

Alexey,

Thanks for getting to this in the middle of all of the other
chaos.

Inline below.

--On Monday, March 16, 2020 11:40 +0000 Alexey Melnikov
<aamelnikov@fastmail.fm> wrote:

> Hi John,
> I am finally catching up with a few outstanding requests.
> 
>> On 8 Mar 2020, at 17:49, John C Klensin <john-ietf@jck.com>
>> wrote:
>> 
>> (personal opinion, not wearing any particular hat)
>> 
>> Hi.
>> 
>> Discussions on this (ietf-smtp) list since before IETF 106 and
>> the informal proposals to try to revise RFCs 5321 and 5322 and
>> get them done before now (!), have convinced me, and I think
>> at least some others, that an Applicability Statement or BCP
>> --one that can cover current advice for application and use of
>> provisions of the core protocols and related ones -- is going
>> to be key to an actual revision effort for 5322 and
>> (especially) 5321 being a matter of weeks or a few months
>> rather than years of work.
>> 
>> If we are going to continue discussions in anticipation of an
>> eventual WG, I think it would be helpful to get an outline of
>> what might be in, or evolved into, such an A/S or BCP posted
>> soon.  It could act, not only as a placeholder but a place to
>> keep (historically archival, because that might be important)
>> notes of what we expect to put there, partially so that we
>> could put pointers and references into 5321bis/5322bis.
> 
> I personally like this idea. So +1 from me.
>> 
>> Its presence as a placeholder could also help with
>> constructing a draft WG Charter.
>> 
>> I guess I am, reluctantly, willing to sign up to produce a
>> first cut at such an (-D or an outline of one (although
>> certainly not before tomorrow's posting deadline).
> 
> Please do!

Unfortunately, while I had a clear picture of how to put that
together when I wrote that note, the passage of time and general
disruptions cleared it from memory.   Will try to reconstruct
within the next several days, depending in part on how you
(collectively and Barry in particular would like me to
prioritize it relative to RFC-to-be 8753.
 
>> But my condition for doing
>> so would be a volunteer for co-author who would be willing to
>> take over the work and maintain the document.  That would be a
>> good opportunity for someone new at this work, possibly more
>> involved in day-to-day operations of large email systems, and
>> with a different perspective on things than I have.  So,
>> unless others object or the ADs have conflicting advice,
>> volunteers sought.
 
> I am willing to help out with this one, if you like someone
> not junior (in addition to a more junior person).

Especially since you presumably acquire free time next week,
that would be great.  As this moves forward, you (or Barry and
Murray) also need to find a WG Chair or co-chairs and being one
of the latter would also be a good learning opportunity for
someone who hadn't done it before (IMO, it would be wonderful if
you felt like taking the more senior role on because you have
the both the IETF expertise and the long-term email
perspective).   For this A/S document, I just don't want people
to depend on me longer-term as sole editor because I suspect I
will have my hands full with 5321bis.

>> On a similar note, I have been maintaining a list of possible
>> issues and changes to 5321 in Appendix G of 5321bis.  I'm
>> willing to continue to do that, but it may be that either a
>> formal tracker or an IETF-sanctioned Github repository would
>> be a better way to manage and facilitate discussion on those
>> topics and where they belong.  Other than a personal distaste
>> for trying to track long and complex discussions that I
>> cannot read in real time in Github, I have no preference
>> among the three options.  But I don't think setting something
>> up requires a WG or even a firm plan/ draft charter for one
>> and so, if others (particularly the ADs or or potential WG
>> chairs) have strong opinions, this would be, IMO, a good time
>> to get them posted.
> 
> While I don't particularly like GitHub interface (I love git
> itself), I think it is the more commonly used tool these days.
> (My next choice would be trac on tools.ietf.org)
> 
> I can set one up, if there is rough agreement to use GitHub.

I'm happy to leave this decision to others.  It is partially the
interface, or maybe a sign of advancing age, but I have found
GitHub almost impossible to follow and track for long,
multi-thread discussion.  In that respect, the advantage of trac
is precisely that it can keep an issues list but encourages the
action discussions to take place on a mailing list, while
GitHub, in practice, seems to discourage that.

Hope everyone is well and staying that way.

best regards,
   john