Difference between revisions of "DevCon3Agenda"

From XMPP WIKI
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
* XEP-198
* [http://www.xmpp.org/extensions/xep-0198.html XEP-0198]
* Stanza size limitations
* Stanza size limitations


Line 19: Line 19:
* [http://www.wimba.com/labs/mucol/ MUCOL]
* [http://www.wimba.com/labs/mucol/ MUCOL]
* [http://www.wimba.com/labs/mucom/ MUCOM]
* [http://www.wimba.com/labs/mucom/ MUCOM]
* Distributed MUC
* [http://www.xmpp.org/extensions/inbox/distributedmuc.html Distributed MUC]
* Message moderation
* Message moderation


==SECURITY==
==SECURITY==
* Requirements, requirements, requirements (XEP-0210)
* Requirements, requirements, requirements ([http://www.xmpp.org/extensions/xep-0201.html XEP-0210])
* Stanza signing (broadcast and directed)
* 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
* Auth via PGP key? (IIRC there's a TLS method for this - see http://tools.ietf.org/html/draft-ietf-tls-openpgp-keys

Revision as of 17:18, 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 size limitations

COMPONENT PROTOCOL

  • Authentication (TLS + SASL)
  • Domain subscription
  • Namespace subscription
  • Presence subscription
  • Roster subscription and manipulation
  • Route

MUC STUFF

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