Re: [Emailcore] Ticket #8: Need a registry of header fields that are Ok to add after submission

John C Klensin <john-ietf@jck.com> Mon, 26 July 2021 02:06 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5123B3A1437 for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 19:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 EVUSioeRBhw5 for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 19:06:03 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-136.nh.cpe.atlanticbb.net [65.175.133.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3673A1435 for <emailcore@ietf.org>; Sun, 25 Jul 2021 19:06:03 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1m7pzm-000IY9-RN; Sun, 25 Jul 2021 22:05:30 -0400
Date: Sun, 25 Jul 2021 22:05:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, emailcore@ietf.org
Message-ID: <7B7704211E06466E4EDA7884@JcK-HP5>
In-Reply-To: <20210726012552.0D13C24FAA25@ary.qy>
References: <20210726012552.0D13C24FAA25@ary.qy>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/ufF9_fCkQWIHT_ptsUlbDAJYsZ4>
Subject: Re: [Emailcore] Ticket #8: Need a registry of header fields that are Ok to add after submission
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2021 02:06:09 -0000


--On Sunday, 25 July, 2021 21:25 -0400 John Levine
<johnl@taugh.com> wrote:

> It appears that John C Klensin  <john-ietf@jck.com> said:
>> Or you could convince the WG to tell me to go ahead and
>> create a normative reference to 5598 5598 to and use the
>> exception procedure, but I imagine some of us would argue
>> that would be tantamount to moving standards track and hence
>> out of charter.
> 
> Yikes. If we make this list of headers, it's not going to be
> normative, since we can't retroacively clean up 40 years of
> practice, and while 5598 is a useful model of the way mail
> systems work, there's a lot of places where theory and
> practice don't exactly match.\

Exactly.

> Many headers are ideally created by MUAs but in practice added
> by MSAs, so they get listed both places. There's also overlap
> between MTA and MDA depending on how a mail system is built.
> 
> I still don't understand what problem this exercise would be
> solving.

Speaking personally only, agreed.  For me that created a
situation in which IANA should insist on my precise definitions
to run even a piece of a registry and getting to those
definitions --with theory and practice matching-- is likely to
be sufficient trouble that the benefits and problem being solved
had best be _very_ clear.

best,
   john