1 / 41

Lemonade IETF 65

Lemonade IETF 65. Eric Burger eburger@cantata.com Glenn Parsons gparsons@nortel.com. Note Well.

jillian-bernard
Download Presentation

Lemonade IETF 65

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. LemonadeIETF 65 Eric Burger eburger@cantata.com Glenn Parsonsgparsons@nortel.com

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of BCP 78 and BCP 79.Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult BCP 78 for details. IETF 65 - Dallas, TX, USA

  3. Scribes and Transcribes ??? For Monday ??? For Wednesday

  4. Remote Logistics • mp3 Feed • http://videolab.uoregon.edu/events/ietf/ietf657.m3u • Jabber • Server: rooms.jabber.ietf.org • Room: lemonade • Logs: http://www3.ietf.org/meetings/ietf-logs/lemonade@rooms.jabber.ietf.org/ IETF 65 - Dallas, TX, USA

  5. Chair’s Agenda • Agenda Bashing • Meeting goals • Status of documents • OMA liaison • Issue Discussion • Existing Document Open Issues • Operating in Environments Without TCP • Milestones • Charter Discussion IETF 65 - Dallas, TX, USA

  6. Documents to Discuss • draft-ietf-lemonade-notifications • draft-ietf-lemonade-convert • draft-ietf-lemonade-imap-sieve • draft-ietf-lemonade-search-within • draft-ietf-lemonade-vfolder • draft-gulbrandsen-imap-view • draft-ietf-lemonade-compress • draft-ietf-lemonade-reconnect • draft-ietf-lemonade-rfc2192bis • draft-ietf-lemonade-profile-bis • draft-ietf-lemonade-futuredelivery • draft-maes-lemonade-xencrypted • draft-ietf-lemonade-deployments • draft-ietf-lemonade-firewall-binding IETF 65 - Dallas, TX, USA

  7. Beijing • Goals • LEMONADE Profile bis and associated documents in IESG queue immediately after IETF 65 • Drafts before IETF 65 – Feb 27, 2006 • Post meeting updates - Apr 3, 2006 • Scorecard • Drafts: Of 13 Drafts to Do, Only 2 Not Done: • Message Event: Needs New Name; Anything Else? • Streaming Content: Where’s The Draft? Excuse Is Over… IETF 65 - Dallas, TX, USA

  8. Meeting Goals • Meeting Updates to 12 Drafts by April 3 • WGLC Starting April 10 (Staggered) • Content Streaming: Draft by April 10 IETF 65 - Dallas, TX, USA

  9. Document Status • IESG Processing: • draft-ietf-lemonade-notify-s2s-00 Revised ID NeededFold into Notifications • RFC-Editor's Queue: • draft-ietf-lemonade-profile-07RFC Ed Queue • draft-ietf-lemonade-burl-04 RFC Ed Queue • draft-ietf-lemonade-catenate-05 RFC Ed Queue • draft-ietf-lemonade-urlauth-08 RFC Ed Queue • Published: • draft-ietf-lemonade-mms-mapping-06   RFC 4356 • draft-ietf-lemonade-goals-05 RFC 4416 trio IETF 65 - Dallas, TX, USA

  10. OMA MEM liaison • Response to specific questions • will study the possibility of a shorter list that is mandatory for the MEM enabler for OMA STI. We will provide IETF LEMONADE an update on this after our next meeting. • only notification and send/receive roundtrip delay is of concern at this point. • message recall is still a requirement. Specifically, that the client be able to request a recall and that success/failure be indicated back. MWG-MEM will let IETF know if any further work is requested. • Response • Update on status • … IETF 65 - Dallas, TX, USA

  11. Document Issues

  12. Notifications • draft-ietf-lemonade-notifications • draft-newman-lemonade-msgevent IETF 65 - Dallas, TX, USA

  13. Content Transformation • draft-ietf-lemonade-convert IETF 65 - Dallas, TX, USA

  14. Filter • Sieve-Related • draft-ietf-lemonade-imap-sieve • draft-martin-managesieve • Views • draft-ietf-lemonade-vfolder • draft-gulbrandsen-imap-view • Time-Based Views • draft-ietf-lemonade-search-within • Spin-out from VFOLDER IETF 65 - Dallas, TX, USA

  15. Compression • Application Level versus Transport Level • Beijing:Application = MUST, Transport = MAY • draft-ietf-lemonade-compress • Do We Reopen This? • Data Showing Both Good and Bad • Only Looking at Size, Not CPU • One More Complex Than Other • Do We Need an Indicator, for Either, for On/Off? • How Can Client Possibly Know If Compression Is Valuable? IETF 65 - Dallas, TX, USA

  16. DAY 2 LemonadeIETF 65 Eric Burger eburger@cantata.com Glenn Parsonsgparsons@nortel.com

  17. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of BCP 78 and BCP 79.Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult BCP 78 for details. IETF 65 - Dallas, TX, USA

  18. Chair’s Agenda • Agenda Bashing • Meeting goals • Status of documents • OMA liaison: Inbound • Issue Discussion • Existing Document Open Issues • OMA liaison: Response • Finish Issue Discussions • Operating in Environments Without TCP • Milestones • Charter Discussion IETF 65 - Dallas, TX, USA

  19. OMA Response • STI Design Team Read-Out • Profile-bis Presentation for OMA IETF 65 - Dallas, TX, USA

  20. Proposed Mandatory list of Conversions to support for draft-ietf-lemonade-convert-xx • Proposal from Alexey / Chris / Stephane • HTML to Text: • Details to be worked out from STI doc etc… • HTML, XHTML, … • Doc structure • Tables… • Images: • image/gif, image/jpeg and image/png (un- / no more encumbered) • Parameters from STI: • Size limit (i.e. reduce quality), • width, • height, • resize directive (crop, stretch, aspect ratio) • Note: we have not considered depth, is this needed? IETF 65 - Dallas, TX, USA

  21. Proposed Mandatory list of Conversions to support for draft-ietf-lemonade-convert-xx Continued: • Audio: • Not considered because of lack of widely used unencumbered codecs • To be treated as others • Others: (including, proprietary document formats, audio, video, …) • To be described via MIME types and STI parameters • May not be supported by server => behavior described in draft • Should be validated with device manufacturers and operators IETF 65 - Dallas, TX, USA

  22. Additional thoughts for CONVERT Not part of the proposal from task force (two previous slides) • Add a compression transformation for object level compression based on discussions of Monday • Will take to the list IETF 65 - Dallas, TX, USA

  23. Documents to Discuss • draft-ietf-lemonade-notifications • draft-ietf-lemonade-convert • draft-ietf-lemonade-imap-sieve • draft-ietf-lemonade-search-within • draft-ietf-lemonade-vfolder • draft-gulbrandsen-imap-view • draft-ietf-lemonade-compress • draft-ietf-lemonade-reconnect • draft-ietf-lemonade-rfc2192bis • draft-maes-lemonade-xencrypted • draft-ietf-lemonade-profile-bis • draft-ietf-lemonade-futuredelivery • draft-ietf-lemonade-deployments • draft-ietf-lemonade-firewall-binding IETF 65 - Dallas, TX, USA

  24. Reconnect Status • Got New draft-05 • Did Not Last Call (Next Slide) • After Meeting • Depends on • CONDSTORE, expunged,… • Need implementations of 05 IETF 65 - Dallas, TX, USA

  25. Reconnect Issues • What state is to be saved by the server? • Address some edge cases, e.g. "SID, SID <session-id>, SID". Is the last operation "create new session", or should it be noop? • Figure out if RECONNECT should depend on EXPUNGED extension (extension to send a compressed list of expunged messages). • Is LOGOUT (PRESERVE) needed? • Do we need to add a new DELETESID command (i.e. a command to delete an existing session without logging out)? IETF 65 - Dallas, TX, USA

  26. RFC2192bis – IMAPURL Status • Updated text on mailbox naming scope field (section 3.1), more changes to this section needed. • Updated section 3.2 to describe anonymous logins and client behaviour if it sees LOGINDISABLED IMAP capability. • Reworked section 5 (listing IMAP server content) to talk about NAMESPACE command. • Removed references to Content-Base header, as it was obsoleted. Updated reference for Content-Location header to point to MHTML •  Allow for UTF-8 (as non-synchronizing literals) in Search criteria •  Clarified that IMAP usernames and Search criteria can contain UTF-8 data. •  Fixed error in ABNF for partial body range. •  Added IANA considerations section (more work is needed). •  Updated references IETF 65 - Dallas, TX, USA

  27. RFC2192bis Issues • Include URLAUTH IMAP URL extension into this draft? • Extend syntax to allow for BINARY, SEARCH return options (ESEARCH extensions), LIST-EXTENDED, etc.? (I think the answer to this question is yes, the question if we want to put all mentioned IMAP URL extensions in 2192bis) • ABNF Error Will Be Fixed in Next Version IETF 65 - Dallas, TX, USA

  28. Encryption • Secure Transport • Done: TLS • Secure End-to-End for Message Objects • Done: S/MIME • Object Encryption? • draft-maes-lemonade-xencrypted • Notification Encryption? • No proposal yet • Stéphane’s Presentation IETF 65 - Dallas, TX, USA

  29. LEMONADE Profile Stéphane Maes Alexey Melnikov

  30. IMAP STARTTLS CATENATE URLAUTH BURL UIDPLUS POSTADDRESS LITERAL+ CONDSTORE IDLE ESMTP AUTH PIPELINING 8BITMIME CHUNKING BINARYMIME DSN SIZE ENHANCEDSTATUSCODES Profile MUST implement IETF 65 - Dallas, TX, USA

  31. IMAP/ESMTP All of Profile Notifications Content Transformation Static Streaming Filters (e.g., SIEVE) Filter management Reconnect Compression Minimum codec for TLS as gzip Compress BINARY APPEND Allow Partial URLs Others Firewall traversal Proxies Object encryption Notification encryption Phase bis - MUST implement Draft -- Comments? IETF 65 - Dallas, TX, USA

  32. Future Release • WG Last Call Completed, Except: • Do we like semicolons or commas? • Waiting on revised draft from editor • Send for AD review • …then IETF last call IETF 65 - Dallas, TX, USA

  33. Operating in Environments Without TCP

  34. Firewall Traversal • Original Plan Was for Two Drafts • BCP On How to Properly Deploy a Network: • draft-ietf-lemonade-deployments • Informational On How to Deploy in TCP-Challenged Environments • draft-ietf-lemonade-firewall-binding • Chair Error on Charter IETF 65 - Dallas, TX, USA

  35. Moving Forward on TCP-Challenged Environments • Individual Informational Submission • Document Will Be Subject to Expert Review By the Work Group IETF 65 - Dallas, TX, USA

  36. Charter Dates Goals and Milestones: Done Submit LEMONADE goals and use-cases specification to the IESG Done Submit server to server notification requirements to the IESG Done Submit translation to other messaging systems to the IESG DoneSubmit IMAP/SUBMIT extensions for forward without download to IESG Done Submit IMAP4 profile for mobile devices to the IESG Jun 05 Submit IMAP4 extensions for streaming multimedia to the IESG Aug 05 Submit server to server notification protocol to the IESG IETF 65 - Dallas, TX, USA

  37. Charter Discussion

  38. Lemonade Charter Review • LEMONADE Goals • IMAP4 extensions for VM playback • IMAP4/SUBMIT extensions for forwarding • IMAP4 extensions & profile for diverse endpoints • Server-to-Server Notification Protocol • Translation to and from other messaging systems IETF 65 - Dallas, TX, USA

  39. LEMONADE Goals draft-ietf-lemonade-goals IMAP4 extensions for VM playback draft-ietf-lemonade-convert IMAP4 extensions for forwarding draft-ietf-lemonade-burl draft-ietf-lemonade-urlauth draft-ietf-lemonade-catenate IMAP4 extensions & profile for diverse endpoints draft-ietf-lemonade-reconnect draft-ietf-lemonade-futuredelivery draft-ietf-lemonade-profile draft-ietf-lemonade-rfc2192bis Server-to-Server Notification Protocol draft-ietf-lemonade-notify-s2s Translation to and from other messaging systems draft-ietf-lemonade-mms-mapping WG Deliverables IETF 65 - Dallas, TX, USA

  40. Next Steps • Meeting Updates to 11 Drafts by April 3 • WGLC Starting April 10 (Staggered) • Content Streaming: Draft by April 10 IETF 65 - Dallas, TX, USA

  41. Thanks! • Mail List: • General Discussion: lemonade@ietf.org • To Subscribe: lemonade-request@ietf.org • In Body: in body 'subscribe' • Archive: ftp://ftp.ietf.org/ietf-mail-archive/lemonade/ • Supplemental Work Group Page http://flyingfox.cantata.com/i-d/lemonade/ IETF 65 - Dallas, TX, USA

More Related