[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [lemonade] some questions in draft-ietf-lemonade-notifications-03
Zoltan.Ordogh at nokia.com [mailto:Zoltan.Ordogh at nokia.com] wrote at 15
August 2006 11:49:
>Hi Ben,
>I meant the "PIMAP client".
>So, I guess You mean a client based on the proprietary P-IMAP draft,
right?
>http://tools.ietf.org/wg/lemonade/draft-maes-lemonade-p-imap-12.txt
>Because if You mean a LEMONADE-compliant client, then it cannot be
based on P-IMAP (well,
>not right anyway now at least because there are too many differences).
It makes no difference at all to the point I was making: whether it's a
client based on any particular draft of P-IMAP, or Lemonade compliant to
some level, the point is still true: a Symbian application doesn't need
to be concerned with the complexities of receiving an MMS or SMS; that's
all dealt with by the platform.
However, to address your point: the Workgroup status page
(http://tools.ietf.org/wg/lemonade/) references
http://tools.ietf.org/wg/lemonade/draft-maes-lemonade-p-imap-12.txt,
which is "a recommendation for interoperable intermediate
implementations awaiting draft-ietf-lemonade-profile-bis-xx.txt" and
"the P-IMAP specifications are expected to further converge towards the
profile". Right now, a feasible way to implement a client is to
implement it so that it supports P-IMAP, which overlaps with many parts
of the Lemonade profiles. The client can then track the implementation
of Lemonade compliance in commercial servers whilst also generating
revenue from the installed base of users of those existing P-IMAP
servers.
So yes, there are differences between Lemonade (as expressed in the
profile-bis-xx documents) and P-IMAP (as expressed in
draft-maes-lemonade-p-imap-xx), but there's more than enough overlap to
allow a client to progress towards supporting both. After all, a good
general-use client will follow the capabilities of the server, and
XPIMAPvX is just a way for a server to declare that it supports a
particular set of capabilities; for example, XPIMAPv1r2 means that the
server supports PIMAP version 1.2, which includes XPROVISION,
XSETPIMAPPREF, XGETPIMAPPREF, XDELIVER, XZIP, XCONVERT, XVFOLDER,
XENCRYPTED and BINARY and implies support for LITERAL+. We're working
on a good general-use client, whose first release will include support
for servers that speak P-IMAP. As implementations of other
Lemonade-originated features appear in servers, support for those will
be added (actually, it's usually already in the client, but until it's
been tested with a real commercial implementation, it doesn't count).
Anyway; P-IMAP isn't really proprietary, since the full details are
available and anyone could implement it!
Regards
Ben
EMCC Software Ltd
_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade