March 20, 2003IETF 56 - San Francisco, CA, USA1 lemonade Eric Burger Glenn Parsons

March 20, 2003IETF 56 - San Francisco, CA, USA2 Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, 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 Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions.

March 20, 2003IETF 56 - San Francisco, CA, USA3 Scribes and Transcribes JABBER details Room: lemonadeServer: conference.ietf.jabber.com Logs:

March 20, 2003IETF 56 - San Francisco, CA, USA4 Agenda Agenda Bashing (Chairs) 5 min Review of LEMONADE charter & WG status (Chairs) 10 min Requirements (Kue) 20 min Server-to-Server Requirements (Lisa)20 min SNAP (Eric) 5 min Media Size (Meir) 5 min IMAP Extensions (Pete/Eric/Greg) 20 min Mobile Messaging discussion (Alan/Milt) 20 min Next Steps15 min

March 20, 2003IETF 56 - San Francisco, CA, USA5 Charter Status Glenn, Eric & Ned

March 20, 2003IETF 56 - San Francisco, CA, USA6 WG Status Glenn, Eric & Ned

March 20, 2003IETF 56 - San Francisco, CA, USA7 Deliverables LEMONADE Requirements - draft-vaudreuil-um-issues-00.txt - draft-burger-um-reqts-00.txt - draft-wong-umcli-00.txt Server-to-Server Notification Protocol - draft-shapira-snap-04.txt IMAP4 extensions for VM playback - draft-burger-imap-chanuse-00.txt - draft-nerenberg-imap-channel-01.txt IMAP4 extensions for mobile devices - draft-neystadt-imap-status-counters-00.txt - draft-shveidel-mediasize-00.txt - draft-vaudreuil-futuredelivery-00.txt Translation to and from other messaging systems We are not doing IMAP5

March 20, 2003IETF 56 - San Francisco, CA, USA8 Requirements Draft Kue Wong Meir Mendelovich draft-wong-umcli-02

March 20, 2003IETF 56 - San Francisco, CA, USA9 Server-Server Requirements Lisa Dusseault draft-dusseault-s2s-event-reqs-00

March 20, 2003IETF 56 - San Francisco, CA, USA10 SNAP Eric Burger draft-shapira-snap-05

March 20, 2003IETF 56 - San Francisco, CA, USA11 Media Size Meir Mendelovich draft-shveidel-mediasize-02

March 20, 2003IETF 56 - San Francisco, CA, USA12 IMAP Channel & Use Eric Burger draft-nerenberg-imap-channel-02 draft-burger-imap-chanuse-01

March 20, 2003IETF 56 - San Francisco, CA, USA13 Future Delivery Greg Vaudreuil draft-vaudreuil-futuredelivery-00.txt

March 20, 2003IETF 56 - San Francisco, CA, USA14 Mobile Messaging Alan Stebbens Milt Roselinsky draft-stebrose-mmsarch-00.txt Not published

March 20, 2003IETF 56 - San Francisco, CA, USA15 Deliverables LEMONADE Requirements - draft-vaudreuil-um-issues-00.txt - draft-burger-um-reqts-00.txt - draft-wong-umcli-00.txt Server-to-Server Notification Protocol - draft-shapira-snap-04.txt IMAP4 extensions for VM playback - draft-burger-imap-chanuse-00.txt - draft-nerenberg-imap-channel-01.txt IMAP4 extensions for mobile devices - draft-neystadt-imap-status-counters-00.txt - draft-shveidel-mediasize-00.txt - draft-vaudreuil-futuredelivery-00.txt Translation to and from other messaging systems Translation Remote composition More drafts needed???

March 20, 2003IETF 56 - San Francisco, CA, USA16 Thanks! Mail List: –To subscribe, send the message "subscribe um" to –Public archive is –Will Become After Supplemental Draft Page

March 20, 2003IETF 56 - San Francisco, CA, USA17 Extra-Group Interactions Intra-IETF –SIPPING –OPES Inter-Body –3GPP TSG T WG2 SWG3 Messaging –W3C Mulitmodal interaction Activity –Open Mobile Alliance –3GPP2 TSG-P –3GPP2 TSG-N Are There Others?