RE: [lemonade] Lemonade Kicker Design Team Proposal

["Douglas Paul-APD028" <paul.douglas at motorola.com>]

OMA EMN is in S60, see http://www.nokia.com/A4297065

IMAP IDLE is in UIQ 3.1 as well. I have a Motorola Z8 in my hand.

Cheers,

/Paul.

-----Original Message-----
From: Ben Last [mailto:Ben.Last at emccsoft.com] 
Sent: 26 July 2007 11:19
To: lemonade at ietf.org
Subject: RE: [lemonade] Lemonade Kicker Design Team Proposal

>From: Randall Gellens [mailto:randy at qualcomm.com]
>Subject: [lemonade] Lemonade Kicker Design Team Proposal

>5.4.2.  Out-of-IMAP Notifications
>Today, a number of email vendors include facilities to send SMS or 
>other simple non-stream messages to clients on handsets when new mail 
>arrives.  OMA has published a mechanism that uses WAP PUSH to send a
basic message containing a URL [OMA-EMN].  The IETF is investigating
ways to standardize enhanced functionality in this area.
>A "push email" user experience can be achieved using any number of 
>techniques, ranging from always-on TCP connectivity to the server and 
>the NOTIFY extension described above, to OMA EMN, or even a
non-standard trigger message over SMS.  In any technique, the client
learns of the existence of new mail, and decides to fetch information
about it, some part of it, or all of it, and then presents this to the
user.

An implementation note, for client-side, relevant to the above, on
Symbian.

EMN handling (over SMS) functionality is part of the UIQ 3.2 platform,
not Symbian as a whole.  It doesn't appear as though there is an S60
equivalent (Zoltan - can you clarify?) There is currently nothing in the
platform that can provide third-party applications with EMN
notification.  It's all handled internally, and there is no way to
register a third-party client as a handler for EMN notifications.

There appears to be a potential conflict if a third party client handles
the same protocol as a built-in client (for example, a Lemonade client
is an IMAP client, and so is the built-in Symbian IMAP client).  The
"mailat" scheme is not well-suited to client implementation because the
email address is not necessarily stored in a standard location that the
platform can use to identify the correct client.

In summary: the use of EMN requires a significant level of platform
support, since OMA messages are usually handled directly by the
platform.  There appears to be an assumption that "the client" is one
entity; this does not adequately cover the question of third-party
clients installed on existing devices.

Regards
Ben

--
Ben Last
R&D Manager
EMCC Software


_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade