Revision of core Email specifications (emailcore) agenda for [virtual] Madrid. * Date: Wednesday, 29 July 2020 * Time: 11:00-12:40 UTC * Meetecho: https://meetings.conf.meetecho.com/ietf108/?group=emailcore&short=&item=1 ### * Jabber: emailcore@jabber.ietf.org * Notes: https://codimd.ietf.org/notes-ietf-108-emailcore Chairs: Alexey Melnikov alexey.melnikov@isode.com Seth Blank seth@valimail.com WEDNESDAY, July 29, 2020 (UTC) 11:00-12:40 (1 hour 40 mins) Agenda bashing, administrivia, note well (chairs) - 5 mins Problem statement (chairs) - 5 mins Review of proposed changes to "Internet Message Format" (RFC 5322) draft-resnick-rfc5322bis - 15 mins Issue with ABNF for "field": https://www.rfc-editor.org/errata/eid2950 Disallow empty quoted string: https://www.rfc-editor.org/errata/eid3135 Header field name length limit: https://www.rfc-editor.org/errata/eid5918 Triage of raised issues for "Simple Mail Transfer Protocol" (RFC 5321) draft-klensin-rfc5321bis - 10 mins Example topics (we tackle as many as we have time for) G.9. Revisiting Quoted Strings G.7.11. Bring back 1yz reply codes? Core Email Applicability Statement: - 35 mins Suggested SMTP Extensions: 8BITMIME PIPELINING G.8. Enhanced Reply Codes and DSNs SMTPUTF8 (a.k.a. EAI) Terminology: G.3. Meaning of "MTA" and Related Terminology G.7.2. SMTP Model, terminology, and relationship to RFC 5598 G.11. SMTP Clients, Servers, Senders, and Receivers G.1. IP Address Literals in EHLO, MAIL or RCPT G.7.3. Resolvable FQDNs and private domain names Proposed Charter Scope (chairs) - 5 mins Charter Review and discussion - 25 mins Documents: https://datatracker.ietf.org/doc/draft-resnick-rfc5322bis/?include_text=1 https://www.rfc-editor.org/errata_search.php?rfc=5322&rec_status=15&presentation=table https://datatracker.ietf.org/doc/draft-klensin-rfc5321bis/?include_text=1 https://www.rfc-editor.org/errata_search.php?rfc=5321&rec_status=15&presentation=table https://datatracker.ietf.org/doc/draft-klensin-email-core-as/?include_text=1 --------------- If we go too quickly through triage of some issues, here are some others that we can discuss: G.10. Internationalization Consideration section needed? G.5. Remove or deprecate the work-around from code 552 to 452 The suggestion in Section 4.5.3.1.10 may have outlived its usefulness and/or be inconsistent with current practice. Should it be removed and/or explicitly deprecated? G.7.1. Issues with 521, 554, and 556 codes See new Section 4.2.4.2. More text may be needed, there or elsewhere, about choices of codes in response to initial opening and to EHLO, especially to deal with selective policy rejections.