IETF Logo Mail Archive

[ietf-822] Fwd: [Ietf-dkim] Fwd: WG Action: Formed Mail Maintenance (mailmaint)

Dave Crocker <dhc@dcrocker.net> Fri, 10 May 2024 21:36 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848ABC16941E for <ietf-822@ietfa.amsl.com>; Fri, 10 May 2024 14:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 XL-vRMRvnxvo for <ietf-822@ietfa.amsl.com>; Fri, 10 May 2024 14:36:50 -0700 (PDT)
Received: from donkey.ash.relay.mailchannels.net (donkey.ash.relay.mailchannels.net [23.83.222.49]) (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 F316BC1840DB for <ietf-822@ietf.org>; Fri, 10 May 2024 14:36:49 -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 696C294183F for <ietf-822@ietf.org>; Fri, 10 May 2024 21:36:49 +0000 (UTC)
Received: from fr-int-smtpout4.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 9799B942EB9 for <ietf-822@ietf.org>; Fri, 10 May 2024 21:36:48 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1715377009; a=rsa-sha256; cv=none; b=jK1dneYNGe5MGgOcHdwp47sa+h0gDezfwry6bjOyRpiNYm6LnvUwdT0x5f2uAhOp4c1lXF IccQAJawlO4njGuNE+oWW9IvXQASQ+dI+jVjJwttPMFgxDFnxxS/TcszLGh01fmHrAe5y5 SRZFNdZKCEHOtutT8gpLAkZFvOYZvifnAdiUr0AjQaX8DaJtcA+Ygw5avXRLNKu23YCjC8 vElUAXEPeQLQNEax1zePTHCq71r3jiZSI4l8B4eXbLyvWSWbyf24v3QHUi1PBW8CVt6WUk IRT9ICU9BxaxXV0r4Y1vtPfynlTwjP8qCk/h5WSDniMdnh3mXSF51KN0uF1FEA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1715377009; 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=3as/FW52OO89eqr+ao1Uhi5BFf2LGM158EDS7eCIEbE=; b=ompiGsW8m2OoRbNK9JTSEHryo7tH2SBKBqC3OOL79NUOllrVp+/lV0IBpFu+qkiHVSyhzT CxL2WJw69Ivn4aQJI6qGpN5HXU5Eoer7tcAkZvYta4bRfPkuB5qskFeonNfhQpMZntWVQw yxPd5hoLeVJ0Io5ItlEtMhOZlyJgvmEBc/1RdZZTtlsR9STdocmsZN2XP+V4AjoGKnH0E9 0Z7inkCGGEAKSa56uglTRKGLYeSug+APhJ5dH9/c3woDPVWHvRwie23kNChXqonaQv6/bG 6etveDreqTWc02p2PL4MNZbgp1XI8AO4dIl9elIpnuPXDNlHf9hIROSEut6t6Q==
ARC-Authentication-Results: i=1; rspamd-5d55749bb4-j2rvd; 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-Average-Reaction: 6ae3164041c85e1d_1715377009318_285734733
X-MC-Loop-Signature: 1715377009318:992737305
X-MC-Ingress-Time: 1715377009318
Received: from fr-int-smtpout4.hostinger.io (fr-int-smtpout4.hostinger.io [89.116.146.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.111.87.15 (trex/6.9.2); Fri, 10 May 2024 21:36:49 +0000
Content-Type: multipart/alternative; boundary="------------6HuSKUB4YPNDZ0NsDAf5pECQ"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1715377006; 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=3as/FW52OO89eqr+ao1Uhi5BFf2LGM158EDS7eCIEbE=; b=c4tmIfECGB4mbmjHfRWgD2wWRWVf5hsGnsSnYrIZJTir5aTKZEZct151yfN+GzwZXwNL4B bCiQ0zSRNn84yCiQADfwCHe0h+3zs6FM2sk93JNz+EfM667pC2omRecusnVJdyRj8KZzYc lWFEVFbQTr+3vafFIvsnkuB0QASIYPzhh8AfItgAg/et8YmxsiOnHDMLaaCHVodKRJFbcH rQJqN/4CLc10kMR7GVA1RMojHWRCSRKSFG2j+f2ZZUy/qHSp9my8G05qTrO+rnSvE+uT5S 1n3Z+JjVOrOi/fzeH6vCMGYItTd+m+sd7nY0vS5S+t1rs2nFBMiythhORTC/iw==
Message-ID: <658ef616-54f7-4b07-88bf-28f5af0e80b1@dcrocker.net>
Date: Fri, 10 May 2024 14:36:45 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
References: <45c24966-832f-45a7-b173-88d9784e28b4@dcrocker.net>
From: Dave Crocker <dhc@dcrocker.net>
To: EmailCore WG <emailcore@ietf.org>, ietf-smtp <ietf-smtp@ietf.org>, ietf-822@ietf.org
Organization: Brandenburg InternetWorking
In-Reply-To: <45c24966-832f-45a7-b173-88d9784e28b4@dcrocker.net>
X-Forwarded-Message-Id: <45c24966-832f-45a7-b173-88d9784e28b4@dcrocker.net>
X-CM-Analysis: v=2.4 cv=YbPv5BRf c=1 sm=1 tr=0 ts=663e936e a=f+oD5hTMMv8HtluUlp4ziA==:117 a=f+oD5hTMMv8HtluUlp4ziA==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=b8OvNEjoAAAA:8 a=k7Ga1wGzAAAA:8 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=ZJhYsbITfc6HW6ocYUQA:9 a=QEXdDO2ut3YA:10 a=UTqBxFjiNI4A:10 a=iEzoSfX0PJ2zsFPHJpAA:9 a=LKcySoTZdltW2NgK:21 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10 a=xfJ8-ueq0pyqlCF7aVox:22 a=ijMaxGghyylP-n2pFjDB:22 a=w1C3t2QeGrPiZgrLijVG:22
X-CM-Envelope: MS4xfO8sOAO0UPeKcs5txKL8No8OyFii7ZfttCGd55cns1jw8c1kH8kwmKsx8Iiq5iVQ5TuDTCbjHHjEdwGwmudbVCM4MAyZn3vIjNB1B5H6pPeOpAqmrGTc GbA9JCIwkly47A3N+TXvENNjhMgKKcRqxwMO4tcLvybnnzbFSekIfRhCDanJ0TweIqiG4KDL585bWRsNYP3C9FnOvJr6v9BGc9HICVdwMWFYVAgOFMEKqA/X vVoYwVBo0vOO8PHFK6VjWg==
X-AuthUser: dhc@dcrocker.net
Message-ID-Hash: PKZ3KLLBAMYZIXECBNQODXC67577I66W
X-Message-ID-Hash: PKZ3KLLBAMYZIXECBNQODXC67577I66W
X-MailFrom: dhc@dcrocker.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-822.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Reply-To: dcrocker@bbiw.net
Subject: [ietf-822] Fwd: [Ietf-dkim] Fwd: WG Action: Formed Mail Maintenance (mailmaint)
List-Id: "Discussion of issues related to Internet Message Format [RFC 822, RFC 2822, RFC 5322]" <ietf-822.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/PNfsNtHbd5bodDD-aPXwLmUJ1K8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-822-owner@ietf.org>
List-Post: <mailto:ietf-822@ietf.org>
List-Subscribe: <mailto:ietf-822-join@ietf.org>
List-Unsubscribe: <mailto:ietf-822-leave@ietf.org>

FYI



-------- Forwarded Message --------
Subject: 	Re: [Ietf-dkim] Fwd: WG Action: Formed Mail Maintenance 
(mailmaint)
Date: 	Fri, 10 May 2024 14:33:06 -0700
From: 	Dave Crocker <dhc@dcrocker.net>
Reply-To: 	dcrocker@bbiw.net
Organization: 	Brandenburg InternetWorking
To: 	Murray S. Kucherawy <superuser@gmail.com>
CC: 	Ietf-dkim@ietf.org, IETF general list <ietf@ietf.org>



On 5/10/2024 10:54 AM, Murray S. Kucherawy wrote:
> * Prior to accepting any Standards Track document for development, 
> there must
> be a commitment to implement the resulting proposed standard from at least
> two independent parties, as recorded on a related IETF mailing list.
>
> * When deciding to send any Standards Track work to the IESG, there must
> first be produced a report documenting at least two (preferably more)
> independent implementations with at least partial interoperation based 
> on the
> developed specification.


This imposes two, formal requirements for Standards Track that are 
dramatically higher barriers than is typical for IETF Standards Track 
specification.

What is the justification for this deviation from IETF norm?

And, obviously, if it is reasonable here, why is is not universally 
reasonable, as a basic barrier for all specifications going on Standards 
Track?

d/

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

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

v2.37.1 | Report a Bug | By Email | System Status