Changes

Jump to navigation Jump to search
47 bytes removed ,  22:52, 27 January 2010
m
no edit summary
Line 1: Line 1:  
Here are some possible DevCon agenda items...
 
Here are some possible DevCon agenda items...
   −
Room: devcon@conference.jabber.org (would be an xmpp: link if this wiki supported it)
+
Room: [xmpp:devcon@conference.jabber.org?join devcon@conference.jabber.org]
    
==XMPP-CORE==
 
==XMPP-CORE==
   −
[http://www.xmpp.org/extensions/xep-0198.html XEP-0198: Stanza Acknowledgements]
+
[http://xmpp.org/extensions/xep-0198.html XEP-0198: Stanza Acknowledgements]
 
* Justin to update the spec to reflect IRL discussion
 
* Justin to update the spec to reflect IRL discussion
   Line 23: Line 23:     
==COMPONENT PROTOCOL==
 
==COMPONENT PROTOCOL==
   
Consensus to solve the basics
 
Consensus to solve the basics
 
* TLS
 
* TLS
Line 81: Line 80:  
==MUC STUFF==
 
==MUC STUFF==
 
* [http://www.wimba.com/labs/mucol/ MUCOL] -- Bruno discussed on Day One
 
* [http://www.wimba.com/labs/mucol/ MUCOL] -- Bruno discussed on Day One
* [http://www.xmpp.org/extensions/inbox/distributedmuc.html Distributed MUC]
+
* [http://xmpp.org/extensions/inbox/distributedmuc.html Distributed MUC]
 
* Message moderation
 
* Message moderation
    
==SECURITY==
 
==SECURITY==
* Requirements, requirements, requirements ([http://www.xmpp.org/extensions/xep-0210.html XEP-0210])
+
* Requirements, requirements, requirements ([http://xmpp.org/extensions/xep-0210.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
Line 128: Line 127:     
Specs:
 
Specs:
* [http://www.xmpp.org/extensions/xep-0060 XEP-0060: Publish-Subscribe] (1.9)
+
* [http://xmpp.org/extensions/xep-0060 XEP-0060: Publish-Subscribe] (1.9)
* [http://www.xmpp.org/extensions/xep-0163.html XEP-0163: Personal Eventing] (1.0)
+
* [http://xmpp.org/extensions/xep-0163.html XEP-0163: Personal Eventing] (1.0)
    
Works in progress:
 
Works in progress:
* [http://www.xmpp.org/extensions/tmp/xep-0060-1.10.html XEP-0060 1.10 working draft]
+
* [http://xmpp.org/extensions/tmp/xep-0060-1.10.html XEP-0060 1.10 working draft]
* [http://www.xmpp.org/extensions/tmp/xep-0163-1.1.html XEP-0163 1.1 working draft]
+
* [http://xmpp.org/extensions/tmp/xep-0163-1.1.html XEP-0163 1.1 working draft]
    
IRL discussions:
 
IRL discussions:
 
* Come up with ~5 node types a la MUC room affiliations? -- all these node configuration options are too complicated and users will never be able to handle them! Here are some possibilities....
 
* Come up with ~5 node types a la MUC room affiliations? -- all these node configuration options are too complicated and users will never be able to handle them! Here are some possibilities....
* Private node: whitelist access model, only account owner on whitelist, persist data -- see [http://www.xmpp.org/extensions/inbox/pdp.html PDP]
+
* Private node: whitelist access model, only account owner on whitelist, persist data -- see [http://xmpp.org/extensions/inbox/pdp.html PDP]
 
* Public node: open access model, anyone may subscribe or get items
 
* Public node: open access model, anyone may subscribe or get items
 
* Eventing node: presence access model, filtered notifications
 
* Eventing node: presence access model, filtered notifications
* Data node: open access model (e.g., public keys / user profile), persist items -- see [http://www.xmpp.org/extensions/inbox/pop.html POP]
+
* Data node: open access model (e.g., public keys / user profile), persist items -- see [http://xmpp.org/extensions/inbox/pop.html POP]
    
==SHARED EDITING / WHITEBOARDING==
 
==SHARED EDITING / WHITEBOARDING==
190

edits

Navigation menu