Difference between revisions of "DevCon3Agenda"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
==XMPP-CORE== | ==XMPP-CORE== | ||
* Mixed child elements in message/presence | * Mixed child elements in message/presence | ||
* [http://www.xmpp.org/extensions/xep-0198.html XEP-0198] | * [http://www.xmpp.org/extensions/xep-0198.html XEP-0198: Stanza Acknowledgements] | ||
* Stanza size limitations | * Stanza size limitations | ||
Revision as of 17:20, 23 July 2007
Here are some possible DevCon agenda items...
Room: devcon@conference.jabber.org (would be an xmpp: link if this wiki supported it)
XMPP-CORE
- Mixed child elements in message/presence
- XEP-0198: Stanza Acknowledgements
- Stanza size limitations
COMPONENT PROTOCOL
- Authentication (TLS + SASL)
- Domain subscription
- Namespace subscription
- Presence subscription
- Roster subscription and manipulation
- Route
MUC STUFF
- MUCOL
- MUCOM
- Distributed MUC
- Message moderation
SECURITY
- Requirements, requirements, requirements (XEP-0210)
- Stanza signing (broadcast and directed)
- Auth via PGP key? (IIRC there's a TLS method for this - see http://tools.ietf.org/html/draft-ietf-tls-openpgp-keys
- ESessions
- Justin's "JEP-Secure"
- Ubiquitous TLS on open network
- SPAM fighting / reporting
- CAPTCAs for user registration
- DDoS
- IP Hashes to reduce groupchat spam
- Server reputations
FILE TRANSFER
- Existing methods don't work well enough
- Requirement to send multiple files?
- Jingle to get reliable transport (e.g., ice-tcp)
- Then: HTTP? IQ?
PUBSUB/PEP
- publish-options
- persisting public data objects
- private data storage
SHARED EDITING / WHITEBOARDING
- similaries to MUCOL (permissions / media sessions)
OTHER OPPORTUNITIES
- extended presence
- more use cases beyond IM