IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Sun, 25 July 2021 23:42 UTC

Return-Path: <dhc@dcrocker.net>
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 386E43A0E7D for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 16:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.753
X-Spam-Level:
X-Spam-Status: No, score=-0.753 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, RCVD_IN_BL_SPAMCOP_NET=1.347, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
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 GVUET0rQvA-b for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 16:42:23 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (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 36A403A0E83 for <emailcore@ietf.org>; Sun, 25 Jul 2021 16:42:23 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 231444020CB; Sun, 25 Jul 2021 23:42:22 +0000 (UTC)
Received: from gcp-us-central1-a-smtpout2.hostinger.io (100-96-17-89.trex.outbound.svc.cluster.local [100.96.17.89]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 64F97401F90; Sun, 25 Jul 2021 23:42:21 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from gcp-us-central1-a-smtpout2.hostinger.io (35.45.192.35.bc.googleusercontent.com [35.192.45.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.96.17.89 (trex/6.3.3); Sun, 25 Jul 2021 23:42:21 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Wipe-Decisive: 46916be86c543f97_1627256541852_3074901710
X-MC-Loop-Signature: 1627256541851:1598866931
X-MC-Ingress-Time: 1627256541851
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (Authenticated sender: dhc@dcrocker.net) by smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 89BF430B5560; Sun, 25 Jul 2021 23:42:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1627256540; bh=ftqaB9fBXOD5F+kZnCk6E1n4bXWWYX7oYOKmKXjoFUs=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=sPvmSsxUvvSYexldtGfpw+xefscKobH8H7UvS+BIHmS5ESFbzn9s9YX9Ih3QTF3NF G3eUNWNVwb+/KoBP1xrCtO2VRfc0/tbWgq092UYftCS1mnRq0Ux9VG+ZbrZ5lL6ZAc vUiAT95u18+IxPKf/mfpz97YzZgQC79TWS08pTW3R/Dyv9HTuuWLSfqyedGSMAaYpv VCC2tnEmAFf+Z9W20QpQnRFB7rrrJ8v5I6MqL9TW7sNsVgp2cWrM93gRdWza3qBtUq YcmD4pZMA2ELrT/l0AnzApqQmkT6+SAINU3SRjLjgnDAkt9phAocoJlMY0+ydZpxeL 65tnvxTwddCPw==
Reply-To: dcrocker@bbiw.net
To: John C Klensin <john-ietf@jck.com>
Cc: emailcore@ietf.org
References: <e64e5ab8-fe18-7708-f8bf-6c5ee60658b6@isode.com> <13fcea10-e071-5707-a83d-38a2a92e1ac7@isode.com> <C371882359676271873A6904@JcK-HP5>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <daf7b953-2bb0-ec3d-935c-52142e3fb910@dcrocker.net>
Date: Sun, 25 Jul 2021 16:42:19 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <C371882359676271873A6904@JcK-HP5>
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/emailcore/yqU8XJ0CvFe96Py0zED1m6ARrPw>
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: Sun, 25 Jul 2021 23:42:28 -0000

On 7/25/2021 4:30 PM, John C Klensin wrote:
> Personal opinion and opinion as co-author of RFC 6409: Much of
> the reason for creating a separate Message Submission
> specification was to make it clear that the MSA was allowed to
> do things that, in a more abstract world, we expected MUAs to do
> and discouraged MTAs from doing.  In other words, the boundary
> between MUA and SMA is deliberately unclear; the MUA could
> incorporate MSA functions (or not) or could communicate with the
> MSA using just about whatever protocol or API the two agreed on,
> etc.


You appear to be saying that Sections 4.2.1 and 4.3.1 of RFC 5598 are 
not sufficiently clear or complete.

Please elaborate with particulars.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email