108
edits
Line 20: | Line 20: | ||
* Advance [http://www.xmpp.org/internet-drafts/ rfc3920bis] and [http://www.xmpp.org/internet-drafts/ rfc3921bis] to RFC status in the IETF. | * Advance [http://www.xmpp.org/internet-drafts/ rfc3920bis] and [http://www.xmpp.org/internet-drafts/ rfc3921bis] to RFC status in the IETF. | ||
* Make serious progress in improving the security profile of XMPP technologies through work on end-to-end encryption, TLS deployment via the [https://www.xmpp.net/ XMPP ICA], and spam-prevention technologies. | * Make serious progress in improving the security profile of XMPP technologies through work on end-to-end encryption, TLS deployment via the [https://www.xmpp.net/ XMPP ICA], and spam-prevention technologies. | ||
* Develop a file transfer approach that will solve the NAT traversal problem and be 99% reliable (probably including HTTP upload/download with IBB as a fallback for smaller files, negotiated via Jingle). | |||
* Lay the groundwork for shared editing (e.g., whiteboarding) over XMPP. | * Lay the groundwork for shared editing (e.g., whiteboarding) over XMPP. | ||
* Push more specs from Draft to Final (see [http://mail.jabber.org/pipermail/standards/2007-August/016477.html post]) | * Push more specs from Draft to Final (see [http://mail.jabber.org/pipermail/standards/2007-August/016477.html post]) |
edits