[ietf-822] Fwd: WG Review: Mail Maintenance (mailmaint)
"Murray S. Kucherawy" <superuser@gmail.com> Fri, 19 April 2024 17:35 UTC
Return-Path: <superuser@gmail.com>
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 7E95BC14F6BE for <ietf-822@ietfa.amsl.com>; Fri, 19 Apr 2024 10:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=gmail.com
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 HTcKTIuMdO3J for <ietf-822@ietfa.amsl.com>; Fri, 19 Apr 2024 10:35:11 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 8A460C14F6BA for <ietf-822@ietf.org>; Fri, 19 Apr 2024 10:35:11 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-a553e26fb03so52538166b.1 for <ietf-822@ietf.org>; Fri, 19 Apr 2024 10:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713548109; x=1714152909; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=3ZgDeZPi8Y/KLcn6UPFZhlTgEr7ccyb8CsX+S8mRXxI=; b=EnOmZKOIF43eHSrLe8UY+9xt1o7176YcouMI8YdQoPyzis2QMiDzFJ3J0In0vp9FpZ wIapgBdkNVTBiP+3jNVIWP80A2VSzLLOGfXnMmX9Rhpz4lTme8NFmmamPqhN5G1o1mj7 HHvYunfWR+LH7NsB/3rEM9IowBJZ7s24LsFWr7f1k6Dv0/tZ+HLjTi7pSMmXuj4xgNjb l15ku2fOToXiLCg8PHaC6C6ygFuwYLWef8gLqbctqA6mzL6nvLZ4ULeh4eXJ90/UeJs0 BLq7431BIBEtjyirYFfRSLdleXDCGGPOQY/lRo0i67ppysXPdo72O/w1yG68tJ5JUfrx RcDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713548109; x=1714152909; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3ZgDeZPi8Y/KLcn6UPFZhlTgEr7ccyb8CsX+S8mRXxI=; b=qbYrREw0OPwuGRT07hSUZjRP4IsmgVJsXG+L0J0QM61C8fCaUOq9AA2+CuTqa2odNd zjG2E2MXDMw7vdFIlTfK0oMA0aDF4qFlx5GzYqaPajNU1GmPmz+e3k6+peRbFGFd9fhd jYnnDitbmHRR/HhGDNKtlYuTdEnILZMz23o0wFGQtdfDLon5quTJvbeDyb43xRKU/LQq MewD/NuA64mRyVFd1j51kIZRKLcxU6PiSIpAesXY4oyBTFRNmUu//b/pyCDVDkRcr3EO bT99UhJUVW3sAd11ngDZPAYsoNcbNB3r/dfJP2y1t7p0LNnCBKMscCOIH+74+DlZ73g3 ULUQ==
X-Gm-Message-State: AOJu0YyY3xWJRjqjIIOG55cGODlfd+Ck/DsfehuJ7xjQPmKS4gQ9e59n 7VeZbWf6KlZrkzgQhtYxNXZgvZDFhUjRWYS5CYTx6P3eI3OZVYFz1wP/2L2aICqRy08pSthM0Us L/CRkW1/bzEAJx/s9vteXseasxHFsL2AP
X-Google-Smtp-Source: AGHT+IHmCLYabsj86n6oMrXly8s5ltjDsheF9epjSfS2e6a9sbhp/Bu33r4IJJ/tEzZ5RDPhboAwcACW56UolamoFO4=
X-Received: by 2002:a17:906:2591:b0:a55:5b1f:52f3 with SMTP id m17-20020a170906259100b00a555b1f52f3mr2010476ejb.4.1713548108790; Fri, 19 Apr 2024 10:35:08 -0700 (PDT)
MIME-Version: 1.0
References: <171354751915.42440.9058103568713803636@ietfa.amsl.com>
In-Reply-To: <171354751915.42440.9058103568713803636@ietfa.amsl.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 19 Apr 2024 10:34:56 -0700
Message-ID: <CAL0qLwb_HEmHgw-LdF8CF=x+uk0c7xWNYGqU+=b8wewYtUyjxw@mail.gmail.com>
To: ietf-822@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005484ca06167682f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/8U5FUz6dk-ZWV1TvtMZp9LVdgTw>
Subject: [ietf-822] Fwd: WG Review: Mail Maintenance (mailmaint)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2024 17:35:12 -0000
FYI only. Please don't discuss this here; send feedback to me directly or to iesg@ietf.org. -MSK, ART AD ---------- Forwarded message --------- From: The IESG <iesg-secretary@ietf.org> Date: Fri, Apr 19, 2024 at 10:25 AM Subject: WG Review: Mail Maintenance (mailmaint) To: IETF-Announce <ietf-announce@ietf.org> A new IETF WG has been proposed in the Applications and Real-Time Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by 2024-04-29. Mail Maintenance (mailmaint) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: TBD Assigned Area Director: Murray Kucherawy <superuser@gmail.com> Applications and Real-Time Area Directors: Murray Kucherawy <superuser@gmail.com> Orie Steele <orie@transmute.industries> Mailing list: TBD Group page: https://datatracker.ietf.org/group/mailmaint/ Charter: https://datatracker.ietf.org/doc/charter-ietf-mailmaint/ Internet Messaging (“email”) is one of the oldest applications still supported by the IETF. It consists of numerous layers and extensions that support the robust construction, transport, retrieval, and interpretation of messages. (For the purposes of this charter, “email” starts in RFC 5321 which covers transport and RFC 5322 which covers message format, and extends into specifications based on those documents and their antecedents. It does not include extensions to related protocols such as IMAP.) >From time to time, new work in the email space is brought to the IETF for consideration and development. Where there is enough critical mass to create a working group to develop and publish the work, this is the preferred case. More often, however, a proposal is brought that lacks enough critical mass to independently support chartering of a working group, but would still be useful to publish as a standard. Such projects must then either seek the assent of an Area Director willing to sponsor it as a standards track document, or support via the Independent Stream Editor (ISE) without standards track status. The MAILMAINT (“Mail Maintenance”) working group will consider projects in the email space that are too small to warrant construction of a dedicated working group. This will take advantage of a common community to consider these proposals rather than forming a series of disparate but related communities. Work proposed for MAILMAINT may arrive via direct proposals, or it may be referred via one or more DISPATCH-style working groups. Calls for Adoption are required for all work proposals. Proponents of work that is not taken up within the IETF may, of course, decide to bring their proposal to the Independent Stream. The working group should discuss such proposals with the ISE and share the results of the working group’s consideration. Further, MAILMAINT will observe the following constraints when considering the adoption of new work directly: * 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. An interoperability demonstration will be preferred. * 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. * Chartering of a dedicated working group with a custom charter is strongly preferred when engaging any work that updates the base email documents (RFC 5321 and RFC 5322 and their successors). All work will be announced to appropriate non-WG lists such as ietf-822, ietf-smtp, ietf-dkim, etc., at the time a Call For Adoption or Working Group Last Call begins. Standards work being taken up by MAILMAINT should be checked with other relevant areas (mainly Security) to confirm appropriate oversight or possible assignment to that area. Milestones will be used to track all approved work, including during chartering and rechartering. Milestones: Jul 2024 - Call For Adoption of draft-dweekly-wrong-recipient _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
- [ietf-822] Fwd: WG Review: Mail Maintenance (mail… Murray S. Kucherawy