1 / 12

EAI WG Agenda

EAI WG Agenda. IETF 67, Thursday, Nov 9, 1300-1500. Agenda. 1300: Welcome, scribes, blue sheet, agenda bashing 1310: Last Call resolutions, Framework 1315: Open issues, -smtpext 1330: Open issues, -utf8headers and -downgrade 1415: Open issues, end-system operations POP, IMAP, mailing lists

bfolkerts
Download Presentation

EAI WG Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EAI WG Agenda IETF 67, Thursday, Nov 9, 1300-1500

  2. Agenda • 1300: Welcome, scribes, blue sheet, agenda bashing • 1310: Last Call resolutions, Framework • 1315: Open issues, -smtpext • 1330: Open issues, -utf8headers and -downgrade • 1415: Open issues, end-system operations • POP, IMAP, mailing lists • 1430: Related issues, other documents • Encapsulation • Mailto • Scenarios • 1445: Summary of decisions and action items • 1500: End of meeting

  3. Status of work • Framework finished WG Last Call • Core documents in discussion • SMTP, Header, Downgrade • Supporting documents drafted • IMAP, POP, Mailing list • DSN coming soon • Encapsulation, mailto: drafts exist • Implementation tests have started • CDNC EAI testing

  4. Framework – issues list (1) • Issue tracker: https://rt.psg.com/ • #1387 1.3 - i18mail user clarification • Editorial, accepted • #1388 -3 - Missing MIME considerations • Note that –headers needs to address MIME issues • #1389 4.1 - term "bounce" vs "reject” • Remove term ”bounce”. Exact term to use debated. • #1390 4.1 - "POP“ • Editorial, accepted • #1391 5 - delivery to final delivery MTA • Being wordsmithed • #1392 6 - delete i18n section • Accepted

  5. Framework – issues list (2) • #1393 7 - missing local part abuses as label • Resolution not clear; non-EAI issues involved • #1394 10 - too long security section • Wordsmithing, but no changes • #1395 13 – nits • Editorial, accepted • #1396 7.1 - title change IRI -> URI • Accepted • #1397 10 - UTF-8 • Resolution not clear

  6. Framework document – next steps • -03 version after meeting • Chairs will issue a WG Last Call on issue resolution • NO NEW ISSUES AT THIS TIME • If necessary, -04 will be issued • Chairs will pass this to IESG for approval

  7. SMTP extension • Resolved issues: • Identifier: UTF8SMTP • Open issues: • DSN extensions (new document?)

  8. Headers • Resolved issues: • Marker exists – UTF8SMTP: UTF8 • I18mail address always has angle brackets • Open issues: • Alt-addr representation: <utf8@utf8 <ascii@ascii>>? • UTF-8 in MIME headers • Please add

  9. Downgrade • Resolved issues: • Conversion is used. Main target is ASCII mail users. • Open issues: • Downgrade: headers for storage of pre-conv • Representation of utf8 address after conversion • Bounce vs leave out when addresses in header don’t have alt-address • Handling of 2047/2231 in headers • MIME body part headers • Please add

  10. End-system documents • These documents depend on the 3 first • POP • Open issues: • IMAP • Wait on IMAP ENABLE draft • Open issues: • Mailing lists • Open issues: • Are all the issues addressed?

  11. Other documents/concerns • Forward as attachment: In scope? • Both to UTF8SMTP users and to ASCII users • Issue may be outside have-to-solve core • Encapsulation • Needed for DSN content return • Adopt as WG document? • Mailto: URI • Wait until core set published? • Scenarios • Polish and publish?

  12. Summary, decisions, action items • Will be filled out during meeting

More Related