XSF Discussion - 2013-11-07

tobias: http://www.heise.de/newsticker/meldung/IETF-Streit-um-sicheres-HTTP-2-0-neu-entbrannt-2041890.html -- we really need to explain monika to let us review her articles before publication

the jabber community is only holding up the "opportunistic tls" flag, not the "tls" flag

For service deployments: o require the use of TLS for both client-to-server and server-to-server connections

maybe she misinterpreted that as strong authenticated TLS connections via trusted certs

i suppose "use of TLS" isn't really well defined

Well, it is in 6120

does it imply which CAs are in your TA?

or define those

that's out of scope i think

well, 6120 says that one must check certificates

and opportunistic violates that because it (partially) ignores the results of the certificate check

does it define what check certificate means?

http://tools.ietf.org/html/rfc6120#section-13.7.2.1 does that

Observation: the XSF blog announced the start of voting, but not the close and results, and nothing about the summit either...

"board, get busy"? :-)

Just an observation, I said :)

we could ask peter for notes :-))))

yeah..let's put more load on his todo

mattj: +1, currently we lack a warning sign "don't shoot yourself in the foot"

*sigh* I knew there was something I forgot to do

Sorry bear :)

You need more minions

plenty of minions, just need focus

so getting reminded that things need to be done is helpful (well, for me that is)

fippo, I'm considering a mod_nothing_to_hide that echoes all your messages to a public MUC, pubsub or MAM archive

bear: can you draft one of your andyet minions to adulate lance @ http://xmpp.org/about-xmpp/xsf/xmpp-council/ :-)

fippo - sure can

whoever baptized me "Hornsby Cornflower" can surely do that

:)

:P

mattj: after you've reviewed mod_turncredentials that sounds like a good idea :-)

fippo, ah yes :)

on the matter of board activity, we actually have (german) press writing about the manifesto before the xsf has a press relase

otoh, it's not an xsf activity

technically.

i'd love for the XSF to have and publish opinions on things affecting the XMPP network / community though. It's rather expected of us by other communities

ah, you're not there the whole week?

no, just friday

I have created a quick manifesto post

fippo ^^

bear: ^5

https://www.loomio.org/discussions/3678?page=5 <-- if anyone wants to tell the diaspora people about xmpp (and webrtc)...

You already did a good job :)

yea, was reading to get context and see that fippo is already involved - nice work sir!

at some point i'll have to find a way to abandon strophe and use stanza.io

heh. you'll never be rid of strophe.jingle though :p

http://vancouver.conf.meetecho.com/WebLite/event.jsp?w=rtcweb btw

vp8 vs h.264

i just need to review what's needed for pranswer in jingle.js first..

who's winning?

lance: i'll see about refactoring my stuff and adding it to jingle.js

i need to update it for dtls support anyway

they are working thru the h.264 fud and also wondering why google doesn't do what cisco just did

not sure, they haven't unpacked the vuvuzelas, kazoos and trumpets yet

gah! i should have brought kazoos

my position on that is clearly "i don't care about the video codec..."

i'm just wondering how to get adobe to implement VP8 so i can sell an old rtmfp server for lots of money (-:

haha

"lets stop picking nits and arguing about points on the slide"... <-- must be new to IETF

"google's codec and the standard codec"

ted is great

"I offered him a hug" :)

fippo: what was left to implement in jitsi's video bridge?

lance: i just started to work on it this week. on the bridge side it's not yet capable of ice yet (supposed to land this week)

on the client side i don't understand how it's supposed to be used. but emil will explain that to me tomorrow hopefully

after that it's hunting down issues