Lemonade IETF 65.5

LemonadeIETF 65.5

Eric [email protected]

Glenn [email protected]

mailto:[email protected]

mailto:[email protected]

May 31 & June 1, 2006 IETF 65.5 - Ottawa, ON, Canada 2

Note WellAny 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.

Scribes and Transcribes

Eric For Wednesday

Eric For Thursday


Remote Logistics• Audio conference

– Bridge: +1-613-765-0170 Password: 3937582#

• Centra– URL: https://centra.nortel.com/main/

Event ID: SFJ922013 Event Password: IETF

• iChat & Timbuktu• Jabber

– Server: jabber.ietf.org– Room: lemonade– Logs: http://www3.ietf.org/meetings/ietf-logs/[email protected]/

https://centra.nortel.com/main/



http://www3.ietf.org/meetings/ietf-logs/%[email protected]/

http://www3.ietf.org/meetings/ietf-logs/%[email protected]/


Chair’s Agenda

• Agenda Bashing• Meeting goals• Status of documents• OMA liaison• Issue Discussion

– Revised Documents Open Issues

• Milestones• Interoperability testing


Documents to Discuss• draft-ietf-lemonade-futuredelivery -> draft-vaudreuil-futuredelivery • draft-ietf-lemonade-reconnect • draft-ietf-lemonade-rfc2192bis • draft-ietf-lemonade-convert • draft-ietf-lemonade-compress ->

draft-ietf-lemonade-convert • draft-ietf-lemonade-search-within • draft-ietf-lemonade-vfolder

• draft-ietf-lemonade-notifications • draft-ietf-lemonade-deployments • draft-ietf-lemonade-firewall-binding ->

draft-maes-lemonade-tcp-challenged-environments• draft-ietf-lemonade-streaming-convert ->

draft-cook-lemonade-streaming• draft-ietf-lemonade-profile-bis• draft-ietf-lemonade-imap-sieve


Meeting Goals

• Air outstanding issues on Profile-bis and all related documents before WG Last Call

• Meeting Updates to Drafts by June 19

• WGLC Starting as documents posted


Document Status

• RFC-Editor's Queue:– draft-ietf-lemonade-profile-07 RFC 4550 (AUTH48)

• Published:– draft-ietf-lemonade-burl-04 RFC 4468 – draft-ietf-lemonade-catenate-05 RFC 4469– draft-ietf-lemonade-urlauth-08 RFC 4467– draft-ietf-lemonade-mms-mapping-06 RFC 4356– draft-ietf-lemonade-goals-05 RFC 4416

trio


OMA MEM liaison

• OMA document status– MEM Architecture in review– MEM Technical Specification initiated

• Official dependency on Profile-bis

• Have not started subsetting STI• Response

– Update on new RFCs– Overview of OMA use of LEMONADE?

Document Issues

Reconnect

Alexey MelnikovCorby Wilson

draft-ietf-lemonade-reconnect-06


Changes since the last revision (1/2)

• Fixed some formatting issues.• Clarified what state is to be associated with a

session.• Clarified interaction with IMAP ACL extension.• Clarified that creation of a new session when there is

an active one makes the older one inactive.• Added DELETEDSID response in order to convey

this information.• Clarified that the server can still return NO if per-user

limit on number of sessions is reached and all of them are active.


Changes since the last revision (2/2)

• Added paragraph clarifying that any session can only be active on a single TCP connection at a time.

• Clarified that if (on session resumption) UIDVALIDITY provided by the client doesn't match the server's value, than the mailbox is selected in the same read-write mode as it was originally selected, but all other state must be forgotten.

• Specified that the second (and subsequent) request to create a new session is treated as the first one. (Behavior change from -05)

• Added the DELETESID command that allows to terminate a no longer needed resumable session without the need to close the connection.


Open Issues/ToDo

• Do we need server side quick reconnect?

• Decide on minimum mandatory to implement number of resumable sessions per-user

• Make LOGOUT parameters consistent with IMAP ABNF (RFC 4466)

IMAP URL

Chris NewmanAlexey MelnikovStéphane Maes

draft-ietf-lemonade-rfc2192bis-02


Changes

• Clarified ";AUTH=" handling in IMAP URLs• Added [most of the] text from URLAUTH• Clarified why encoded SEARCH doesn't allow

for synchronizing literals.• Added example of a SEARCH containing

Russian text represented in UTF-8.• Updated references and split them into

Normative and Informative.


Open Issues/ToDo (1/3)

• Make the trailing '/' in "server reference" optional, i.e. allow for: imap://imap.isode.com

• Separate consideration for configuration ("stored") versa publicly exchanged URL (?)

• Text about mailbox naming scope still needs polishing [please review and give your comments]

• Section about listing content of an IMAP server need more text on suggested client behavior



• Need a lot of work on decided which URLAUTH text belongs to the document [Need help from Mark]

• Add URLAUTH example(s)• Need to decide about the best way to

represent "rump URL" (before URLAUTH signing) and full URLAUTH URLs

• Check if IANA URI registration template is correct and complete



• Make sure that the example code is still correct regarding permitted characters, etc.

• Decide on other extensions that are needed:– Allow for BINARY URLFETCH URLs?– Search return options? (draft-melnikov-imap-

search-ret-xx.txt)– Extended LIST selection options? (draft-ietf-

imapext-list-extensions-xx.txt)

LEMONADE Profile

Stéphane Maes

Alexey Melnikov


Profile MUST implement

IMAP• STARTTLS • CATENATE • URLAUTH• UIDPLUS • POSTADDRESS • LITERAL+• CONDSTORE• IDLE• NAMESPACE

ESMTP• AUTH • PIPELINING • 8BITMIME • CHUNKING • BINARYMIME • DSN • SIZE• ENHANCEDSTATUSCODES• BURL• STARTTLS


Phase bis - MUST implementIMAP/ESMTP

All of Profile Notifications• Content Transformation

√ Static– Streaming

Filters (e.g., SIEVE) Filter management Reconnect• Compression

– Coded for TLS is gzip– Compress

• BINARY APPEND• Allow Partial URLs

Others

• Firewall issues (deployment)• TCP challenged

environments• Proxies• Object encryption• Notification encryption

DraftComments to the list


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

• Telecom 2006– LEMONADE interop– Hong Kong - Dec 4-8

• 3GSM 2007– Proposed

OMA MEM interop?– Barcelona - Feb 12-15


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

Done Submit 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

Charter Discussion


Thanks!• Mail List:

– General Discussion: [email protected]

– To Subscribe: [email protected]

– 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/

http://flyingfox.cantata.com/i-d/lemonade

Lemonade IETF 65.5

Documents

Transcript of Lemonade IETF 65.5