Thanks to all who participated in this supplementary Last Call of draft-ietf-emailcore-rfc5321bis. The EMAILCORE working group produced this document within the constraints put upon it by IETF consensus through its charter. Within these constraints and the feedback from the first Last Call, changes were made to the Security Considerations to have a normative reference to the Applicability Statement to be forthcoming from EMAILCORE. As was stated by some in the Last Call, this is not ideal but it does allow the document to move forward under the constraints previously established. Based on this Last Call, there is IETF consensus to move forward with this normative reference along with the other changes provided in the referenced diff. Feedback from this Last Call has also provided guidance on the Applicability Statement to be delivered by EMAILCORE, which should include strong recommendations regarding transport security and the proper application of other email security mechanisms such as DKIM. Without these recommendations, the Applicability Statement is very unlikely to receive IETF consensus given the feedback received thus far. -andy, ART AD On 3/21/25 02:54, The IESG wrote:
This supplementary Last Call is for the sole purpose of verifying rough consensus exists for issues which were raised by and as a result of the SECDIR review of this document that have been addressed in version -42. The SECDIR review can be found here: https://datatracker.ietf.org/doc/review-ietf-emailcore-rfc5321bis-31-secdir-lc-eastlake-2024-10-11/ ...and the WG's response to it is a long thread that began here: https://mailarchive.ietf.org/arch/msg/emailcore/EHs584ejRsJ29M1X1RO1-zt5IV0/ ...and a diff between the SECDIR-reviewed version and the current version can be found here: https://author-tools.ietf.org/iddiff?url1=draft-ietf-emailcore-rfc5321bis-38&url2=draft-ietf-emailcore-rfc5321bis-42&difftype=--html Please limit your feedback to responding to this specific question. -- END -- The IESG has received a request from the Revision of core Email specifications WG (emailcore) to consider the following document: - 'Simple Mail Transfer Protocol' <draft-ietf-emailcore-rfc5321bis-42.txt> as Internet Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@xxxxxxxx mailing lists by 2025-04-04. Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document is a specification of the basic protocol for Internet electronic mail transport. It (including text carried forward from RFC 5321) consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. The document also provides information about use of SMTP for other than strict mail transport and delivery. This document replaces RFC 5321, the earlier version with the same title, and supersedes RFCs 1846, 7504, and 7505, incorporating all the relevant information in them. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc3463: Enhanced Mail System Status Codes (Draft Standard - Internet Engineering Task Force (IETF) stream) rfc3848: ESMTP and LMTP Transmission Types Registration (Draft Standard - Internet Engineering Task Force (IETF) stream) draft-ietf-emailcore-as: Applicability Statement for IETF Core Email Protocols (None - Internet Engineering Task Force (IETF) stream)
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
