awclinfordwere there any actions taken following the push discussion?
Tobiaswhile you're together in a room you could also gather opinions on XMPP Compliance Suite 201x
KevNoted, thank you.
hildjjawclinford: bear took good notes
hildjjwe need to assign an action item to write a push XEP
Kevhildjj: I put that on the board.
LanceI'll take that one on hildjj. Already have been working on one
hildjjI'll sign up to review it, and get some folks on the Cisco Jabber team to look at it.
awclinfordi’ll keep my eyes peeled for it Lance. we’ll put an implementation together and feedback to the group
Ge0rGis it still possible to extend the agenda? a) client-to-client (end-to-end) encryption of realtime media and file transfers; b) a normative/informative XEP to specify client priority according to user state and presence, to support message routing with multiple online resources
paulwittyI think we all pretty much agreed on DTLS-SRTP for encryption within Jingle sessions yesterday
paulwittywith some debate about making it required
ZashWhat about file transfers over TCP / Proxy65
paulwittyfavoured using the WebRTC style data channel of SCTP over DTLS
Ge0rGpaulwitty: sorry, wasn't able to attend yesterday. DTLS-SRTP solves UDP-based streaming. what about TCP connections?
paulwittyno TCP connections
paulwittyuse Jingle to set up file transfers, use SCTP to give reliability over the UDP
paulwittyand maybe deprecate all other forms of file transfer
Ge0rGwhat about sharing files with a MUC?
Ge0rGpaulwitty: we are talking about SCTP, the transport-layer protocol which nobody yet implements?
paulwittydoing that in user space, yes
paulwittybecause it looks like that's the direction WebRTC is going
Ge0rGmaybe WebRTC is not quite the right approach for us. it's not like all XMPP client developers have the same resources available to them like Mozilla or Google....
paulwittyis there anything which will work well through all network topologies, is secure, and is easy to implement?
winfriedpaulwitty: that looks like the holy grail to me...
Ge0rGHTTP upload of encrypted files to a data storage server maybe
hildjjWebDAV-like things + e2e, for some value of "secure" that doesn't include server-side virus checking
Ge0rGpaulwitty: implementing a transport-layer protocol on top of an application-layer encryption protocol on top of UDP just looks like crazyness to me. I wouldn't be surprised if JSON is used in the negotiation process
ZashThink of the layers!
hildjjGe0rG: the right place to discuss that is at the rtcweb wg at the IETF
paulwittythe argument is that people who have done Jingle will at least have done the ICE and DTLS layers
lloyd.watkinBased on helping Simon with building the buddycloud XEP I've thrown this together, https://github.com/lloydwatkin/xep-builder , as a helper for building/writing XEPs. Would people find it useful? If not I'll consign it to the dustbin of code.
bearapologies if my take on compliance suite and/or testing irked anyone
Simonnever noticed irk
Michal Piotrowskihas left
bearI am approaching the end of my energy so I tend to be grumpy or combative
Michal Piotrowskihas joined
Philip Robertshas joined
Philip Roberts@bear putting in a vote for "you're fine, relax" :)