lemonade ietf 64
Post on 02-Jan-2016
43 Views
Preview:
DESCRIPTION
TRANSCRIPT
November 7 & 9, 2005 IETF 64 - Vancouver, BC 1
LemonadeIETF 64
Eric Burgereburger@brooktrout.com
Glenn Parsonsgparsons@nortel.com
November 7 & 9, 2005 IETF 64 - Vancouver, BC 3
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.
November 7 & 9, 2005 IETF 64 - Vancouver, BC 4
Scribes and Transcribes
Eric For Monday??? For Wednesday
JABBER detailsRoom: lemonade Server: ietf.xmpp.orgLogs: http://www.xmpp.org/ietf-logs/lemonade@ietf.xmpp.org/
November 7 & 9, 2005 IETF 64 - Vancouver, BC 5
Chair’s Agenda
• Meeting Goals• Status of documents• Profile – phase 1
– WGLC issues
• Reconnect et al• OMA liaison• Profile – phase 2
– in vs. out
November 7 & 9, 2005 IETF 64 - Vancouver, BC 6
Document list
Session 1 - Mon, Nov 7, 1510h: • Agenda bashing• Status review
draft-ietf-lemonade-goals draft-ietf-lemonade-notify-s2s draft-ietf-lemonade-mms-mapping draft-ietf-lemonade-futuredelivery draft-ietf-lemonade-burl draft-ietf-lemonade-catenate draft-ietf-lemonade-urlauth draft-ietf-lemonade-profile
• Profile draft-ietf-lemonade-reconnect draft-ietf-lemonade-rfc2192bis draft-ietf-lemonade-convert
Session 2 - Wed, Nov 9, 0900h: • OMA liaison• OMA MEM AD discussion• Profile proposals
draft-maes-lemonade-notifications-filters-how-to draft-maes-lemonade-notifications-server-to-client draft-maes-lemonade-vfolder draft-newman-lemonade-msgevent draft-maes-lemonade-lzip draft-maes-lemonade-mobile-email draft-maes-lemonade-deliver draft-maes-lemonade-http-binding
November 7 & 9, 2005 IETF 64 - Vancouver, BC 7
Meeting Goals
• LEMONADE Profile phase 1 and all associated documents in RFC Editor queue right after Vancouver.
• LEMONADE Profile phase 2 and associated documents in IESG queue by December 15.
November 7 & 9, 2005 IETF 64 - Vancouver, BC 9
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
November 7 & 9, 2005 IETF 64 - Vancouver, BC 10
WG Deliverables• LEMONADE Goals
draft-ietf-lemonade-goals
• IMAP4 extensions for VM playback
draft-ietf-lemonade-convert
• IMAP4 extensions for forwarding
draft-ietf-lemonade-burldraft-ietf-lemonade-urlauthdraft-ietf-lemonade-catenate
• IMAP4 extensions & profile for diverse endpoints
draft-ietf-lemonade-reconnectdraft-ietf-lemonade-futuredeliverydraft-ietf-lemonade-profiledraft-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
November 7 & 9, 2005 IETF 64 - Vancouver, BC 11
WGLC Status• Goals
– RFC Editor Queue• Server-to-Server Notification Requirements
– IETF LC Closed, Informational, Needs update– New author? Abandon?
• MMS Mapping– IESG approved, appeal, rescinded– IETF last call re-initiated
• All previous issues resolved• One new potential issue raised
– IESG review Dec 1
November 7 & 9, 2005 IETF 64 - Vancouver, BC 12
Trio (URLauth, Catenate, BURL)
• IESG review comments to be resolved• CATENATE
– RFC Editor note proposed to resolve syntax ‘discuss’• BURL
– BURL missing mandatory auth mechanism ‘discuss’ addressed
– New draft-03• URLAUTH
– New draft-08– New discuss – Sam Hartman– Passing of credentials: SUBMIT -> IMAP
• Are IMAP server & SUBMIT server always in the same administrative domain
• Is this a reasonable restriction?
November 7 & 9, 2005 IETF 64 - Vancouver, BC 13
Future Delivery
• All issues resolved?
• Send for AD review
• …then IETF last call
November 7 & 9, 2005 IETF 64 - Vancouver, BC 15
Profile – open issues
1. Add IMAP IDLE - yes.2. Add IMAP BINARY - yes.3. Add description of the $Forwarded IMAP
keyword - yes.4. Explain how to address FCC problem
• add an extension to NAMESPACE command• yes, but in profile rev 2 (?)
5. Clarify text about ways to assemble messages
November 7 & 9, 2005 IETF 64 - Vancouver, BC 16
MUST implement
IMAP• STARTTLS • CATENATE • URLAUTH• BURL• UIDPLUS • POSTADDRESS • LITERAL+• CONDSTORE• IDLE
ESMTP• AUTH • PIPELINING • 8BITMIME • CHUNKING • BINARYMIME • DSN • SIZE• ENHANCEDSTATUSCOD
ES
November 7 & 9, 2005 IETF 64 - Vancouver, BC 17
Reconnect
• New draft-05 expected– Split function for resume in authentication
and login
• …then WG last call• Depends on
– CONDSTORE, SORT, I18N, expunged, ANNOTATE,…
• Need implementations of 05
November 7 & 9, 2005 IETF 64 - Vancouver, BC 18
RFC2192bis - IMAPURL
• Updated boilerplate, list of editor's, etc.• Updated references.• Updated ABNF not to use _, to use SP instead of SPACE.• Updated example domains to use example.org.• Fixed ABNF error in "imessagelist" non-terminal.• Updated ABNF, due to changes in RFC 3501, IMAPABNF and
RFC 3986.• Renamed "iuserauth" non-terminal to "iuserinfo".• Clarified that the userinfo component describes both
authorization• identity and mailbox naming scope.• Added "ipartial" specifier that denotes a partial fetch.
November 7 & 9, 2005 IETF 64 - Vancouver, BC 20
OMA MEM liaison
• Received– Requirements document approved– Appreciation for participation at joint workshop
• Architecture document– Architecture document for review and mapping of
a LEMONADE realization
• Response– Liaison?– Realization of OMA MEM AD
• Publish as Internet Draft before next OMA
November 7 & 9, 2005 IETF 64 - Vancouver, BC 21
Profile – Phase 2
• What is Profile Phase 2?– Meets balance of OMA requirements
• Contents– Current profile– Notifications– Content Transformation– Reconnect– …
November 7 & 9, 2005 IETF 64 - Vancouver, BC 22
Detailed proposals• Filter / Notifications
SIEVE WG draft-maes-lemonade-notifications-filters-how-todraft-maes-lemonade-notifications-server-to-clientdraft-newman-lemonade-msgeventdraft-maes-lemonade-vfolder
• Content Transformation draft-ietf-lemonade-channel derivatives for streaming
• Submission & remote compose draft-maes-lemonade-deliver
• Application Compression draft-maes-lemonade-lzip
• Firewallsdraft-maes-lemonade-http-binding
November 7 & 9, 2005 IETF 64 - Vancouver, BC 23
Phase 2 - MUST implement
IMAP• All of Phase 1 • Notifications• Content Transformation• UID• SIEVE• Compression• Firewall traversal
ESMTP• All of Phase 1 • SIEVE
Draft -- Comments?
November 7 & 9, 2005 IETF 64 - Vancouver, BC 24
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
Apr 05 Submit IMAP/SUBMIT extensions for forward without download to IESG
Apr 05 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
November 7 & 9, 2005 IETF 64 - Vancouver, BC 25
Next Steps
• We need documents…
• Ongoing coordination with OMA
• Interim meeting?– Last week of January– Options?
• Default - Boston hosted by Excel• California?• Asia?
November 7 & 9, 2005 IETF 64 - Vancouver, BC 26
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.snowshore.com/i-d/lemonade/
top related