[Kroupware] Kroupware RFC (follow-up)

[Bo Thorsen]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 19 March 2003 12:34, Stephan Buys wrote:
> Hi all,
>
> In an effort to start the process going I have come up with some areas
> where I need some feedback and some help clarifying/filling-in/editing:
>
> The breakdown is as follows:
>
> Kolab Server:
>
>    IMAP, POP3, LDAP
>
>    Sieve         RFC 3028
>
>       Vacation funtionality
>
> Kolab Client:
>
>     MIME         RFC 2045, 2046
>
>     iCalendar    RFC 2445
>
>     iTIP           RFC 2446
>
>        Scheduling Events, BusyTime, To-dos and Journal Entries
>
> Kolab TODO:
>
>    Calendar Attributes for vCard and LDAP (RFC 2739)
>
>    Groupware IMAP Folders (Proposed RFC to describe the process used by
> Kolab and Bynari)
>
> Recommended Reading:
>
>    RFC 3283 - Guide to Internet Calendaring
>
>    CAP (Calendar Access Protocol) - This is a work in progress. See the
> IETF calsch working group.

Nice list. I can add a few IMAP related to it:

IMAP RFC (2060) and IMAP URL Scheme RFC (2192), plus
http://imap.org/papers/docs/disc.html and
http://imap.org/papers/docs/disc-status.html (the two papers describing
disconnected IMAP).

Bo.

=2D --=20

     Bo Thorsen                 |   Praestevejen 4
     Senior Software Engineer   |   5290 Marslev
     Klar=E4lvdalens Datakonsult  |   Denmark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+gDo0mT99lwfUS5IRAjKmAJ9nCk/RZHOsFYCz33stcGweSLvO0wCgzqGj
yeuUCrLPYulUOQ38DmrG3TU=3D
=3DdMto
=2D----END PGP SIGNATURE-----