Internet unified messaging requirements to support diverse clients
This presentation is the property of its rightful owner.
Sponsored Links
1 / 9

Internet Unified Messaging Requirements to Support Diverse Clients PowerPoint PPT Presentation


  • 56 Views
  • Uploaded on
  • Presentation posted in: General

Internet Unified Messaging Requirements to Support Diverse Clients. Lemonade BOF. IETF 55, Atlanta. E. Burger, SnowShore Networks G. Parsons, Nortel Networks G. Vaudreuil, Lucent Technologies J.K. Wong, Nortel Networks. Draft: draft-wong-umcli-01.txt

Download Presentation

Internet Unified Messaging Requirements to Support Diverse Clients

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Internet unified messaging requirements to support diverse clients

Internet Unified Messaging Requirements to Support Diverse Clients

Lemonade BOF

IETF 55, Atlanta

E. Burger, SnowShore Networks

G. Parsons, Nortel Networks

G. Vaudreuil, Lucent Technologies

J.K. Wong, Nortel Networks

Draft: draft-wong-umcli-01.txt

E. Burger, G. Parsons, G. Vaudreuil, J.K. Wong(Ed.)

[email protected]


Draft history

Draft History

  • compiled from:- draft-burger-um-reqts-00.txt- draft-vaudreuil-um-issues-00.txt- draft-wong-umcli-00.txt

  • 4 sections:

    • E-mail standards evolution survey

    • Client Models for E-mail profiles

    • General UM Design Principles

    • Detailed Requirements

[email protected]


E mail standards evolution survey

E-mail standards evolution survey

  • Evolutionary Mission

    • SMTP and MIME extensions

    • POP3 and IMAP4 clients

    • Client Submission profiles for VPIM/IVM

      • Web browsers -- 3rd party email clients

    • Client Retrieval profiles for VPIM/IVM

      • Web browsers -- Thin clients

      • Multi-modal -- Mobile

Issue: Have we neglected to cite other relevant contributions?

[email protected]


Internet messaging client models gui

GUI

Internet Messaging Client Models: GUI

(E)SMTP

(client-server)

(E)SMTP (server-server)

GUI

RFC-822/MIME

desktopclient

MTA

UA

MTA

MR

email server

MTA – Message Transfer Agent

UA – User Agent

MR – Message Store

envelope

and content

HTTP,POP3 or

IMAP4

[email protected]


Internet messaging client models tui

TUI

UM server

Internet Messaging Client Models: TUI

(E)SMTP

(client-server)

(E)SMTP (server-server)

TUI

voice messaging

system

RFC-822/MIME

MTA

UA

MTA

MR

MTA – Message Transfer Agent

UA – User Agent

MR – Message Store

proprietary

API

IETF

Protocol

[email protected]


Internet messaging client models wui

WUI

GUI

TUI

Internet Messaging Client Models: WUI

(E)SMTP

(client-server)

(E)SMTP (server-server)

WUI

voice messaging

system

RFC-822/MIME

MTA

UA

MTA

UM server

MR

MTA – Message Transfer Agent

UA – User Agent

MR – Message Store

UA

Handset display client

HTTP,POP3 or

IMAP4

[email protected]


General um design principles

General UM Design Principles

  • Reuse Existing Protocols

  • Maintain Protocol Integrity

  • Sensible Message Context

  • Preserve Internet Infrastructure

  • Meet Near-Real-Time Telephony Requirements

  • Be Scalable, esp. for Video

  • Provide user functionality as close as possible to that experienced using a separate traditional mode

Are there other UM design principles?

[email protected]


Detailed requirements summary

Performance Requirements in Retrieval

Real-time Playback

Avoid Base-64 Data inflation

Functional Limitations in Retrieval

Context in mailbox summary

Context in mailbox sort

Context in mailbox quota

Functional mailbox conventions& support

Inbox, sent items, deleted items, expired item

CLID Restriction indication / preservation

Committed delivery to full mailbox

Detailed Requirements Summary

  • Message Submission Limitations

    • Forward without download

    • Quota by context enforcement

    • Future Delivery Support

  • Notification

    • Message Store to Notification protocol

[email protected]


Internet unified messaging requirements to support diverse clients

Detailed Requirements Summary

  • Performance Requirements in Retrieval

    • Real-time Playback

    • Avoid Base-64 Data inflation

  • Functional Limitations in Retrieval

    • Context in mailbox summary

    • Context in mailbox sort

    • Context in mailbox quota

    • Functional mailbox conventions& support

      • Inbox, sent items, deleted items, expired item

    • CLID Restriction indication / preservation

    • Committed delivery to full mailbox

  • Message Submission Limitations

    • Forward without download

    • Quota by context enforcement

    • Future Delivery Support

  • Notification

    • Message Store to Notification protocol

Issue: Additional requirements, especially for WUI?

[email protected]


  • Login