[ietf-smtp] Document updates and interactions with the ietf-smtp mailing list
John C Klensin <john-ietf@jck.com> Sun, 27 September 2020 15:41 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB073A0FCC; Sun, 27 Sep 2020 08:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 xa7KOs-ta6pA; Sun, 27 Sep 2020 08:41:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 844D83A044A; Sun, 27 Sep 2020 08:41:09 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kMYnU-000MIv-BU; Sun, 27 Sep 2020 11:41:08 -0400
Date: Sun, 27 Sep 2020 11:41:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: emailcore@ietf.org
cc: ietf-smtp@ietf.org
Message-ID: <B88A405ED8AD88DA790731AB@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/YUsPrrdIeFVUEAlv3ZqmDC98qGA>
Subject: [ietf-smtp] Document updates and interactions with the ietf-smtp mailing list
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2020 15:41:11 -0000
(ietf-smtp@ietf.org is copied for convenience in this note -- please do not include it in any replies.) Hi. Now that we have a WG and a separate mailing list... (1) The last several hours have included a discussion on ietf-smtp about domain validation and possible modifications to SMTP that would presumably go into 5321bis. If we are going to have a separate mailing list for this WG, threads that propose 5321 (or 5322) modifications should be on the emailcore list and, if we are going to avoid very confused editors and others, the emailcore list exclusively. I suggest that co-chairs either take on responsibility for enforcing that principle or that they find someone to do so. (2) draft-klensin-email-core-as-00 will expire this week. Unless someone (presumably including the co-chairs) provides a convincing argument for me to do otherwise, I do not intend to post an updated version of that document. I would be willing to post a version with a draft-ietf-emailcore... name, but that means that someone needs to initiate the process of designating it as a WG draft. And, as I have said several times before, I don't intend to be editor of that document as it evolves with WG discussion, so I hope the co-chairs have a volunteer to whom I can send the XML and notes and a plan. (3) Similarly, I do not expect there to be a draft-klensin-rfc5321bis-04, so, if and when people want to see an updated version of draft-klensin-rfc5321bis-03, there should be some action to authorize posting of what would presumably be draft-ietf-emailcore-rfc5321bis-00. best, john
- [ietf-smtp] Document updates and interactions wit… John C Klensin
- Re: [ietf-smtp] [Emailcore] Document updates and … Alexey Melnikov