Re: [Emailcore] Publication has been requested for draft-ietf-emailcore-rfc5322bis-10

Dave Crocker <dhc@dcrocker.net> Tue, 19 March 2024 17:26 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 7F264C14F5F9 for <emailcore@ietfa.amsl.com>; Tue, 19 Mar 2024 10:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gOOwsW0E1Ls for <emailcore@ietfa.amsl.com>; Tue, 19 Mar 2024 10:26:06 -0700 (PDT)
Received: from rusty.tulip.relay.mailchannels.net (rusty.tulip.relay.mailchannels.net [23.83.218.252]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097C2C14F5E2 for <emailcore@ietf.org>; Tue, 19 Mar 2024 10:26:05 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 2B38C41250 for <emailcore@ietf.org>; Tue, 19 Mar 2024 17:26:05 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 2EED040ECC for <emailcore@ietf.org>; Tue, 19 Mar 2024 17:26:04 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1710869164; a=rsa-sha256; cv=none; b=NMEtI/Fssm1oAsFlK0/AA5ILQO5wDHnV43qPd58UKcoy1PfmtAfBYXCFPIib6ZaS4/8kgC s0KC55gvnF5US0T0U+h33pYSzPWOVfZ1OLoQLwnIHGFjabZDfx9C2HQG8/gpAyzgrHZedJ 1ohkMJsbkA+7IyaZVUYWI6QbxQwAqCAU1rBDJ4zm+DSepGJgtsLyBBAKmmzcWpTCUg7jrT miVBUWqwAw0BlSJLcarNQ/Q0dQivjaleWNKHpkCq7QNi/sCHnqOp9jPr8/6PTp9Me32+5P kx+VYjzTZylFhNpJFQdvkHv3YymAQPdMpNQPRZeNCs7prVep6kBgArkjCFPPPw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1710869164; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:dkim-signature; bh=ERdHMGq9BKQU0Uu2eD5keQRy3DeNr0YUL3PwqjkaKq8=; b=o2cP2OeywbgCduSNhUHzK7UP6kRbspzcat9n/6HBILfrQSxVjLTO4Kx/Q5TExMCE35wpB1 9FST2as/TreprZVy+vJsTnO+ke47hihSaOHDtm6l05p/9wrPzynkbh2/DU0Pk8030mUPLD fmAZR/xzm2wFOqndUKLQliS3Cyb3kwnD+5SGiazrivSeT6zhcgjBwnSh2ZFM57j+16oKmm zD4cGNM/+ogBrn/A9voL3LO57PImi405lzwEhk7oO7UNauXYrnFFmmbyi3ruiGp5UK4i+8 8kxFrrPBbixGRpPJWKKnDnQrVi5jRqTQQxQFrM8uAkC+tlP5TCLoCIJM2u7LWA==
ARC-Authentication-Results: i=1; rspamd-b46fcdc5-mkrn6; auth=pass smtp.auth=hostingeremail smtp.mailfrom=dhc@dcrocker.net
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authuser|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Troubled-Coil: 73f472576456cff2_1710869164830_2959438286
X-MC-Loop-Signature: 1710869164830:4195273744
X-MC-Ingress-Time: 1710869164830
Received: from nl-srv-smtpout2.hostinger.io (nl-srv-smtpout2.hostinger.io [145.14.150.88]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.99.130.139 (trex/6.9.2); Tue, 19 Mar 2024 17:26:04 +0000
Content-Type: multipart/alternative; boundary="------------lXCw3Pd7ISN3dvQSwd1BDhYI"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1710869161; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=ERdHMGq9BKQU0Uu2eD5keQRy3DeNr0YUL3PwqjkaKq8=; b=VljT6zr/UEzPkwP5WZyYbeVjWsgRJX+CNsCio8e3PelWyKg2qIUpJgPQLfpkfQGpwn77ip kf9Wer1pHoaJvVMcJ2c5yrFNmCour5j+7KsuDYRehMHUR/7xA4EdOPA0TVmLRGF1vmITRg ZMlZPxK79TSbcNV+xts7gHFRC+oHeuE/2BsuS7dvteCHLkDGt/2WyXfdkyOyPG4KqNX9pg s41n5GXGulRlKE3eECgdn4Va4esdBpx2VWupr2F9hxgQSf9gbx7FpEqkqow3BWqREVHCBd JsCYYSAdFrdT2xUGXKbVFJNKF/BXCii084uQChJuYx2ZrusGAgvWgalqMiOTeg==
Message-ID: <8743df1b-47c0-40cb-aed3-0b61279346ef@dcrocker.net>
Date: Tue, 19 Mar 2024 10:26:00 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Reply-To: dcrocker@bbiw.net
Content-Language: en-US
To: "Murray S. Kucherawy" <superuser@gmail.com>, emailcore@ietf.org
References: <170717045911.28761.2601519691688511415@ietfa.amsl.com> <CAL0qLwYuQhxJmyyX=EYwKS-cfMHT0+iPcwJwutm6vm0=DLJ9Dg@mail.gmail.com> <CAHej_8nSH6AbFBXPHQTKceab5Oi_hmMoA9d_whHi5pLegdtqTw@mail.gmail.com> <CAL0qLwb5E4nMM0cUhWvgjXU_QoXTQPz5zFPD36r5m_R5f-ryfA@mail.gmail.com> <CAL0qLwb9NK7XSYQn+nE+VXdGwRb_PQyEUSQWTwNqx7n7eLPV5w@mail.gmail.com> <CAL0qLwZ8=XzTu0eUNsBBRSFHOAgaY4DGaj9dAN9piPMj3sA2VQ@mail.gmail.com> <32B64A19-6003-4E33-97A6-432C66FDC87B@episteme.net> <CAL0qLwZ-EXB8jsR70RkaWEsTdQODNKiqdJp5dVuRMiRQ5NjMNQ@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <CAL0qLwZ-EXB8jsR70RkaWEsTdQODNKiqdJp5dVuRMiRQ5NjMNQ@mail.gmail.com>
X-CM-Envelope: MS4xfL6beRFR7lMKSYYALWh0j5kUon51tLG7lNORc2K4zrJHLDsU6KrH6vSZqgbfmoA/I3k15wTaais5ioLZc54Ib9mnCMdzD6qzQEgQ+ZRH5bnBFN3diXbn oV7OaWplo8kkk20SeUrugagzOY4uFcFAG4ez1AtkfjVor5jmeQRUaGIxGStKqPYPDxrCl44BhIScc+ddeeEIhopUqv4f1abiUyM=
X-CM-Analysis: v=2.4 cv=YaC75RRf c=1 sm=1 tr=0 ts=65f9caa9 a=f+oD5hTMMv8HtluUlp4ziA==:117 a=f+oD5hTMMv8HtluUlp4ziA==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=k7Ga1wGzAAAA:8 a=ghJXpJfynru6S1WfAjMA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=94RglalEbQttptUjORkA:9 a=ljsbjUvMQYbkAT5s:21 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10 a=ijMaxGghyylP-n2pFjDB:22
X-AuthUser: dhc@dcrocker.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/FcvtZ24cpbvSNL3DfTSYv8kO3gM>
Subject: Re: [Emailcore] Publication has been requested for draft-ietf-emailcore-rfc5322bis-10
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 19 Mar 2024 17:26:10 -0000

On 3/18/2024 9:49 PM, Murray S. Kucherawy wrote:
>
>
>     This is outside the context of this document obviously, but I'm
>     ambivalent about how to do this. I'm not sure a bunch of RFCs is a
>     good
>     idea, but I'm also not convinced about FCFS.
>
>
> Since I'm the troublemaker here, let me make a suggestion:
>
> For retroactive population of this flag for things already in the 
> registry, the IESG can be asked to approve such a request. At some 
> point we can announce to ietf-822 or other relevant lists that anyone 
> who thinks they have a favorite header field in need of this 
> annotation, someone has to bring it to our attention and request it.

 1. The question of what it means to be a trace field has been sitting
    like an indigestible dumpling in the stomach, for many years. The
    recent round of effort with this is, therefore, quite significant. 
    However it also has no track record of being used.
 2. As a body, the IESG does not seem all that apt for doing the basic
    work of making technical assessments about header fields, per se,
    given its lack of experience in the topic.
 3. For retroactive assessments, it makes sense to create some sort of
    (rough) consensus process among folk with (some) background in this
    space.

So I suggest creating a small group to make a collective recommendation 
for existing header field registrations. Documenting it as an RFC then 
permits a normal IESG approval process.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social