EMAILCORE Interim, November 2023

• Date: Wednesday, November 29th, 2023 (1-1.5 hour)
• Time: 15:00-16:30 (UTC)
• Meetecho:
  https://meetings.conf.meetecho.com/interim/?group=2750f35c-c527-411f-a667-3fa9c4049f36
• Notes:
  https://notes.ietf.org/notes-ietf-interim-2023-emailcore-02-emailcore

Chairs

• Alexey Melnikov alexey.melnikov@isode.com
• Todd Herr todd.herr@valimail.com

Scribe

• Pete scribing with the help of others

Attendees

Alexey Melnikov, Todd Herr, Barry Leiba, John Levine, John Klensin, Ken
Murchison, Laura Atkins, Pete Resnick

Minutes

No agenda bashes

WG Status - -22 ready for LC, -21 is close

Review of -21 recent changes

• 1.2 changes - no objections stated; bring to ML if you have any

• Suggested changes to 7.9. Is new text OK?

  • JK: A little nervous it could be seen as normative, but
    generally fine
  • AM: Discussed, not much objection, sounds good. JK will
    implement the change.

• Change 8.1.1.2 regarding IANA registry. Objections? Nope, sounds
  good.

• G.21 - Appendix B and 7.2
  • 7.2: Since it's non-normative, change seems fine. Even if it
    doesn't move to 6409bis, it could reasonably end up in A/S.
  • Appendix B has normative text, but is separate from the main
    protocol, so keeping it an appendix is a good thing.
  • AM: Doing 6409bis as an "Updates" with deltas only might be in
    scope. BL/JK: Disagree, still sounds out of charter. Charter
    explicitly disallows restructuring just for elegance.
  • Conclusion: Decided that changes to 6409 are out of charter
    scope and rechartering for it would be more trouble than it's
    worth; the best choice is to leave Appendix B where it is, and
    add some explanatory text as to why it's there. Changes to 7.2
    can be made.

Review of A/S issues:

• G.6 submission and TLS issues

  • AM: Sounds like acknowledge existence of port 465 and close the
    ticket
  • JK: But if this is about submission, does it even belong in the
    A/S?
  • Conclusion: Just put the mention of port 465 where you mention
    587

• Review of some A/S tickets

  • #38: Alexey will see if he can come up with examples; otherwise
    just close
  • #40: Went over the extensions in the list. Will discuss on the
    list whether we've covered the topic and then close if it does
  • #51: Take it to the list with suggestion to close the ticket
  • #66: Take it to the list with suggestion to close the ticket as
    covered in 5322
  • #78: Text was added to 4.2 to capture this issue. JL suggests
    also adding "don't punycode it either".
  • #79: PR/JL: Pointers to other documents should be sufficient to
    address.

Conclusions will be brought to the list, document WGLCs will be coming
soon.