Difference between revisions of "DevCon3Agenda"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
Here are some possible DevCon agenda items... | |||
COMPONENT PROTOCOL | ==COMPONENT PROTOCOL== | ||
* TLS + SASL | |||
* Bind | |||
* Route | |||
* Roster | |||
* Presence | |||
MUC STUFF | ==MUC STUFF== | ||
* MUCOL | |||
* MUCOM | |||
* Distributed MUC | |||
* Message moderation | |||
SECURITY | ==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 | ==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 | ==PUBSUB/PEP== | ||
* publish-options | |||
* persisting public data objects | |||
* private data storage | |||
SHARED EDITING / WHITEBOARDING | ==SHARED EDITING / WHITEBOARDING== | ||
* similaries to MUCOL (permissions / media sessions) | |||
OTHER OPPORTUNITIES | ==OTHER OPPORTUNITIES== | ||
* extended presence | |||
* more use cases beyond IM |
Revision as of 15:44, 23 July 2007
Here are some possible DevCon agenda items...
COMPONENT PROTOCOL
- TLS + SASL
- Bind
- Route
- Roster
- Presence
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