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

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 23 July 2021 12:43 UTC

Return-Path: <alexey.melnikov@isode.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 43C2D3A1953 for <emailcore@ietfa.amsl.com>; Fri, 23 Jul 2021 05:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 gLNRBTFOfYnb for <emailcore@ietfa.amsl.com>; Fri, 23 Jul 2021 05:43:17 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 2A29D3A1983 for <emailcore@ietf.org>; Fri, 23 Jul 2021 05:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1627044196; d=isode.com; s=june2016; i=@isode.com; bh=G+Kp/zqWhdMoO4wRHmkADPnsMhY3zyrLP1myTH2EzdI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=hO2x/HT6pLPlK54+uYDZ3Qt7CvSjKhXJor1fGVVWF9CME8ZrX7YgUQVOOCneECuhmoDaCw rLhynjTKh2+gKmoMPY9OwE7nmgOdgwK9DcRhJ6KYtqWnozhV6c5MrEMfKT8PBw8jWIa/xP fofavBRRgae2OuJE42O0qkDC+1aYRS8=;
Received: from [192.168.1.222] (host5-81-100-7.range5-81.btcentralplus.com [5.81.100.7]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YPq5YwAX7pz=@waldorf.isode.com>; Fri, 23 Jul 2021 13:43:15 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: emailcore@ietf.org
References: <e64e5ab8-fe18-7708-f8bf-6c5ee60658b6@isode.com> <13fcea10-e071-5707-a83d-38a2a92e1ac7@isode.com>
Message-ID: <d41f2824-6937-9ca9-a5a7-1ed31eece408@isode.com>
Date: Fri, 23 Jul 2021 13:43:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
In-Reply-To: <13fcea10-e071-5707-a83d-38a2a92e1ac7@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/gL6VGULlwe-j580obaNT-Rf9WSc>
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: Fri, 23 Jul 2021 12:43:22 -0000

On 23/07/2021 13:21, Alexey Melnikov wrote:

> Dear WG participants,
>
> I would like to get closure on this ticket, which was briefly 
> discussed on the mailing list and also during IETF 109 & 110. Below is 
> a updated strawman text:
>
> ===============
>
> Add to the IANA Considerations of rfc5321bis:
>
> IANA is requested to create a new subregistry for email header fields 
> that can be added to a message header section by a MSA/MTA/MDA. The 
> new subregistry would show whether a header field can be added by a 
> "message submission", “relay”, “delivery” system or some combination 
> of them. Headers appearing in this subregistry SHOULD also be 
> registered in 
> <https://www.iana.org/assignments/message-headers/message-headers.xhtml 
> <https://www.iana.org/assignments/message-headers/message-headers.xhtml>> 
> (whether it is registered as a Permanent Message Header Field Name or 
> as a Provisional Message Header Field Name). The registration template 
> has the following fields:
>
> 1) Name of the header field name
>
> 2) Can be added by an MSA?
>
> 3) Can be added by an MTA?
>
> 4) Can be added by an MDA?
>
> 5) Optional reference field that points to one or more document 
> describing the header field.
>
> 6) Optional comment
>
> Registration policy for this new subregistry is “Expert Review”. 
> Designated Experts should only check correctness of the information in 
> the registration template without passing any judgement on usuability 
> of a specific header field being registered.
>
> Updates to existing entries undergo the same process as registration 
> of new header fields.
>
> ===============
>
> Let me know your thoughts.
Speaking as a participant: I am happy with this text in rfc5321bis or A/S.