Skip to main content

Minutes IETF122: emailcore: Thu 08:00
minutes-122-emailcore-202503200800-00

Meeting Minutes Revision of core Email specifications (emailcore) WG
Date and time 2025-03-20 08:00
Title Minutes IETF122: emailcore: Thu 08:00
State Active
Other versions markdown
Last updated 2025-03-31

minutes-122-emailcore-202503200800-00

IETF 122 - EMAILCORE WG

EMAILCORE Agenda
IETF 122 [hybrid] Bangkok

Thursday 20 March 2025
08:00 (UTC)/15:00 (Bangkok), 1.5 hours

Meetecho:
https://meetings.conf.meetecho.com/ietf122/?group=emailcore&short=&item=1

Notes: https://notes.ietf.org/notes-ietf-122-emailcore

Chairs: Alexey Melnikov, Todd Herr

Notes Taker: Hans-Joerg Happel

rfc5321bis-41

  • Removed from RFC editor queue right after the approval
  • Will be in very targeted IETF LC scoped to security considerations
    raised in the first IETF LC
  • This will not go back to IESG for review, assuming the second IETF
    LC is successful

A/S status

  • Applicability Statement for IETF Core Email Protocols
    (https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-as-15)
  • 6.7; last sentence

    • John Klensin questioning whether or not text requiring STARTTLS
      should be required for legacy system
    • Bron argueing for a more general wording about confidentiality
      (irrespective of whether or not this is TLS) than nitpicking on
      STARTTLS particularly
    • Pete R. will rewrite sentence to clarify text to mean
      opportunistic use of STARTTLS on receiving side
  • https://github.com/ietf-wg-emailcore/emailcore/issues/134

    • Ken to make it slightly more generic (adding DANE and
      requireTLS)
  • https://github.com/ietf-wg-emailcore/emailcore/issues/135

    • Barry L. to check if to add small clarification to text
  • Ken and Alexey will collaborate on two newly created issues (#137;
    other one to be created)

  • John K. requesting clarification for end-to-end vs. hop-by-hop
    confidentiality and authentication
    • Pete to create issue for it

SMTP IANA cleanup (Alexey)

  • Out of scope for this WG according to John K. This will be taken to
    MAILMAINT, where it was already presented this week.