1. Lemonade IETF 67 Eric Burger eburger@cantata.com Glenn Parsons (In Æther) gparsons@nortel.com gparsons@nortel.com

2. 7 and 9 November 2006IETF 67 - San Diego, CA, USA2 Remote Logistics mp3 Feed: SPEAK INTO THE MICROPHONE!!! –Tuesday: http://videolab.uoregon.edu/events/ietf/ietf675.m3u http://videolab.uoregon.edu/events/ietf/ietf675.m3u –Thursday: http://videolab.uoregon.edu/events/ietf/ietf673.m3u http://videolab.uoregon.edu/events/ietf/ietf673.m3u Jabber –Server: jabber.ietf.org –Room: lemonade –Logs: http://www.ietf.org/meetings/ietf-logs/lemonade/ http://www.ietf.org/meetings/ietf-logs/lemonade/ Meeting Materials (Presentations, Agenda, etc.) –https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=67https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=67

3. Scribes and Transcribes ?? For Tuesday ?? For Thursday

4. 7 and 9 November 2006IETF 67 - San Diego, CA, USA4 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 RFC 3978 (updated by RFC 4748) and RFC 3979. 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 RFC 3978 (and RFC 4748) for details.

5. 7 and 9 November 2006IETF 67 - San Diego, CA, USA5 Agenda Day 1 Agenda Bashing Status of Documents Interop Event Document Discussion Inter-Plenary Work Plan for Profile Milestones Day 2 Agenda Bashing Work On Discovered Interop Issues Work On Documents –Convert –Search-Within –VFOLDER –Profile bis Review Milestones

6. 7 and 9 November 2006IETF 67 - San Diego, CA, USA6 Document Status: Out of Our Hands Published –draft-ietf-lemonade-profile-07 RFC 4550 –draft-ietf-lemonade-urlauth-08RFC 4467 –draft-ietf-lemonade-burl-04RFC 4468 –draft-ietf-lemonade-catenate-05 RFC 4469 –draft-ietf-lemonade-mms-mapping-06RFC 4356 –draft-ietf-lemonade-goals-05 RFC 4416 RFC Editor Queue –draft-melnikov-imap-search-ret-03AUTH48 IETF last call –draft-melnikov-imap-expunged-01Revision Needed –draft-vaudreuil-futuredelivery-04IESG Approved

7. 7 and 9 November 2006IETF 67 - San Diego, CA, USA7 Document Status: In Our Control WG Last Call Finished –draft-ietf-lemonade-deployments –draft-ietf-lemonade-reconnect-client –draft-ietf-lemonade-compress WG Last Call –draft-ietf-lemonade-convert-05 –draft-ietf-lemonade-search-within-02 IETF Last Call –draft-daboo-imap-annotatemore-10 Didn’t happen after Montreal Cyrus Would Like IMAP-EXT Expert Review First

8. 7 and 9 November 2006IETF 67 - San Diego, CA, USA8 Documents to Discuss Views –draft-ietf-lemonade-vfolder-01 –draft-cridland-imap-context-00 Other Bis Components –draft-maes-lemonade-xencrypted- 02 –draft-maes-lemonade-tcp- challenged-environments-01 –draft-ietf-lemonade-2192bis-02 Reconnect (Server) –draft-ietf-lemonade-reconnect-07 Notifications –draft-ietf-lemonade-msgevent-00 –draft-ietf-lemonade-notifications-03 –draft-ietf-lemonade-notification- protocol-00 –draft-melnikov-lemonade-imap- events-00 –draft-ietf-lemonade-imap-sieve-01 Streaming Media –draft-ietf-lemonade-streaming-00 –draft-burger-lemonade-streamctrls-00 Profile-bis –draft-ietf-lemonade-profile-bis-04

9. 7 and 9 November 2006IETF 67 - San Diego, CA, USA9 LEMONADE Interop Reasons for Interop Marketing Proving viability of IETF I-D –Before RFC publication Moving to IETF Draft standard –from Proposed standard status Compliance –Conformance PICS –Interop test suite Input to OMA IOP Venue opportunities Private testing –London, UK –Oct 23-27, 2006 –DONE Telecom 2006 –LEMONADE interop –Hong Kong - Dec 4-8 3GSM 2007 –Proposed OMA MEM interop? –Barcelona - Feb 12-15

10. 7 and 9 November 2006IETF 67 - San Diego, CA, USA10 Summary from Private Testing 6 Corporate Entities, 3 Universities Established 4 Test Servers Tested RFC 4550 (LEMONADE Profile) Components and Scenarios –IMAP Features (NAMESPACE, LITERAL+, pipelining) –IDLE –CONDSTORE –SMTP Features (ENHANCEDSETATUSCODES, pipelining, BINARYMIME, SIZE, AUTH) –Forward Without Download (CATENATE, UIDPLUS, URLAUTH, BURL) –Additional Features (BINARY, LIST-EXTENEDED)

11. 7 and 9 November 2006IETF 67 - San Diego, CA, USA11 Results Lots of Stuff Worked As Advertised Some Specifications Need Clarification –Not Wrong, But Can Be Misinterpreted –IMAP URL, CATENATE, URLAUTH, CONDSTORE, IDLE Details and Discussion on Thursday

12. Document Discussion Alexey Melnikov

13. 7 and 9 November 2006IETF 67 - San Diego, CA, USA13 Changes to Profile bis Replaced RECONNECT (server side quick reconnect) with QRESYNC (client side quick reconnect) Added WITHIN and LIST-EXTENDED to the list of IMAP extensions Moved IDLE extension to a separate section. Added requirement for clients to use Format=flowed. Clarified interaction of SMTP SIZE and SMTP BURL (Thanks to Randy) Updated references

14. 7 and 9 November 2006IETF 67 - San Diego, CA, USA14 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) Input from Private Testing Event ABNF Error Will Be Fixed in Next Version

15. 7 and 9 November 2006IETF 67 - San Diego, CA, USA15 Notifications Architecture In-Band (IDLE)

16. Next Steps

17. 7 and 9 November 2006IETF 67 - San Diego, CA, USA17 Interim Progress Face-to-Face Unnecessary (?) –Monthly Jabber Chats to Push Documents Forward –Consensus?

18. 7 and 9 November 2006IETF 67 - San Diego, CA, USA18 Documents on Deck for WGLC 2192bis Multiple Conversions in Convert, then Re-WGLC draft-ietf-lemonade-msgevent-00 draft-ietf-lemonade-notifications-03 draft-melnikov-lemonade-imap-events-00 draft-ietf-lemonade-notification-protocol-00 draft-ietf-lemonade-imap-sieve-01

19. 7 and 9 November 2006IETF 67 - San Diego, CA, USA19 Profile Plans Components for Profile bis Complete, Except –Notifications –Views –Streaming Everything Was Supposed to be Done Now Publish Profile bis With Whatever of Notifications, Views, or Streaming is Ready Publish Profile ter With Rest of Feature Set OR Wait to Do Everything at Once?

20. 7 and 9 November 2006IETF 67 - San Diego, CA, USA20 Milestone Dates Goals and Milestones: DoneSubmit LEMONADE goals and use-cases specification to the IESG DoneSubmit server to server notification requirements to the IESG DoneSubmit translation to other messaging systems to the IESG Done Submit IMAP/SUBMIT extensions for forward without download to IESG Done Submit IMAP4 profile for mobile devices to the IESG Jun 05Submit IMAP4 extensions for streaming multimedia to the IESG Aug 05Submit server to server notification protocol to the IESG

21. 7 and 9 November 2006IETF 67 - San Diego, CA, USA21 Proposed Milestone dates Charter items Dec 2006 - CONVERT Dec 2006 - IMAP Search extension Dec 2006 - Deployment Dec 2006 - Reconnect (the chosen one) Dec 2006 - COMPRESSION Dec 2006 - IMAP URL Jan 2007 - LEMONADE profile bis Feb 2007 - Filtered views Feb 2007 - Notifications format Mar 2007 - Notifications protocol Mar 2007 - IMAP SIEVE Apr 2007 - LEMONADE profile ter Non charter items* Jun 2006 - Future delivery Nov 2006 - Extended search Nov 2006 - Annotatemore Jan 2007 - TCP challenged Feb 2007 - Streaming * Not tracked by WG, but tracked as “interesting”     Again 

22. Lemonade IETF 67 Day 2 Eric Burger eburger@cantata.com Glenn Parsons (In Æther) gparsons@nortel.com gparsons@nortel.com

23. 7 and 9 November 2006IETF 67 - San Diego, CA, USA23 Remote Logistics mp3 Feed: SPEAK INTO THE MICROPHONE!!! –Tuesday: http://videolab.uoregon.edu/events/ietf/ietf675.m3u http://videolab.uoregon.edu/events/ietf/ietf675.m3u –Thursday: http://videolab.uoregon.edu/events/ietf/ietf673.m3u http://videolab.uoregon.edu/events/ietf/ietf673.m3u Jabber –Server: jabber.ietf.org –Room: lemonade –Logs: http://www.ietf.org/meetings/ietf-logs/lemonade/ http://www.ietf.org/meetings/ietf-logs/lemonade/ Meeting Materials (Presentations, Agenda, etc.) –https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=67https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=67

24. Scribes and Transcribes ?? For Tuesday ?? For Thursday

25. 7 and 9 November 2006IETF 67 - San Diego, CA, USA25 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 RFC 3978 (updated by RFC 4748) and RFC 3979. 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 RFC 3978 (and RFC 4748) for details.

26. 7 and 9 November 2006IETF 67 - San Diego, CA, USA26 Agenda: Day 2 Agenda Bashing Work On Discovered Interop Issues Work On Documents –Convert –Search-Within –Filtered Views –Notifications –Profile bis Review Milestones

27. 7 and 9 November 2006IETF 67 - San Diego, CA, USA27 Proposed Milestone dates Charter items Dec 2006 - CONVERT Dec 2006 - IMAP Search extension Dec 2006 - Deployment Dec 2006 - Reconnect (the chosen one) Dec 2006 - COMPRESSION Dec 2006 - IMAP URL Jan 2007 - LEMONADE profile bis Feb 2007 - Filtered views Feb 2007 - Notifications format Mar 2007 - Notifications protocol Mar 2007 - IMAP SIEVE Apr 2007 - LEMONADE profile ter Non charter items* Jun 2006 - Future delivery Nov 2006 - Extended search Nov 2006 - Annotatemore Jan 2007 - TCP challenged Feb 2007 - Streaming * Not tracked by WG, but tracked as “interesting”

28. 7 and 9 November 2006IETF 67 - San Diego, CA, USA28 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/lemonadehttp://flyingfox.cantata.com/i-d/lemonade/