Session Date/Time: 22 Jul 2024 22:30

emailcore

Summary

The emailcore working group met to discuss and resolve open issues on the applicability statement document, the last official charter deliverable. The primary focus was on addressing the remaining open issues and preparing the document for a working group last call, with the goal of completing the charter before the next IETF meeting. Discussions covered various topics including DSN SMTP extension, percent encoding of non-ASCII text, received headers, CNAME usage, and empty quoted strings.

Key Discussion Points

Issue 40 (DSN SMTP extension): Proposed removal of the DSN SMTP extension due to poor implementation. There was discussion about downgrading "must" to "may" and including a comment about the lack of general support. A new issue will be opened for bounce message format standardization.
Issue 78 (Percent encoding of non-ASCII text): Discussion of clarifying text regarding percent encoding, focusing on discouraging modification of the left-hand side of email addresses. Agreement to shorten and clarify the text.
Internationalization references: Discussion of adding references to internationalization RFCs.
Received headers: Review of proposed edits to received header text, particularly concerning disclosure of information and privacy concerns. Discussion on the proper balance between threat intelligence and user privacy, alongside considering legal requirements.
Trace header fields: Discussion on generalizing a comment about removing unwanted headers when using an existing message as a template. Discussion on the definition of "trace fields".
De facto format for receipt headers: Skepticism expressed about documenting a de facto format for received headers due to complexity and potential for frequent changes.
CNAME usage: Discussion about clarifying the text on verifying and expanding MX record authentication related to CNAMEs. John pointed out the DNS community doesn't have numerical limits for CNAMEs so maybe the mail world shouldn't either. A suggestion was made to discourage use of CNAMEs completely.
SMTPO auth: Discussion about whether or not to have a reference to SMTPO auth.
Empty quoted strings: Discussion to revise text related to empty quoted strings to broaden the advice.
Required TLS: Discussion on incorporating a text reference for required TLS.

Decisions and Action Items

Issue 40: Downgrade DSN SMTP extension from "must" to "may" and include a comment about lack of general support. ACTION: Post to the mailing list to verify. Todd to create new issue for bounce message format. Alexei to provide text.
Issue 78: John Levine will revise text regarding percent encoding to shorten sentences and clarify the example. ACTION: John to send revised text to the mailing list.
Internationalization references: Double check if the references are already there and either close the issue or add appropriate RFC references. ACTION: Unassigned - original issue assignee to check.
Received headers: Send revised text to the mailing list about disclosure to others of header contents. ACTION: Unassigned - original issue assignee to edit based on discussion. Kevin Cox to send text to the notes, perhaps?
Trace header fields: Generalize the comment about removing unwanted headers when using an existing message as a template. ACTION: Pete and (unnamed) to come up with text and do it this week
De facto format for receipt headers: Close this issue as "won't fix." or do nothing.
CNAME usage: Jod Clancy will suggest some text. If people want to propose do counter-proposal on the main list, then we should do that. ACTION: Jod Clancy suggest some text. All to propose alternatives on the mailing list.
SMTPO Auth: Alexei will either suggest text, or officially withdraw my comment. ACTION: Alexei will suggest some text, if I can, then I shut up and then.
Empty quoted strings: Action Incorporate double dot example as as another thing maybe well it's part of the blending of the two proposals yeah i'll post something to the list and see where it goes
Required TLS: Jim, raise that on a list and possibly throw some text with it

Next Steps

Document authors to incorporate agreed-upon changes.
Post updated text to the mailing list for further review.
Plan for working group last call in September, contingent on resolving remaining issues.
Co-chairs should consider appropriateness to drop inactive co-author.