kev: and dont forget the agenda item you missed last time ;-)
Peter Waherhas joined
fippo
ah wait, you did not.
fippo
nit for 0124: content-length in example 6 seems wrong
stpeter
BTW we still need to form the UPnP Liaison Team, I received a ping about that again this morning
fippo
stpeter: kev has it on the agenda, forgot it last time
fippo
the content-length in example 3 is wrong, too
fippo
and the one in example 5
stpeter
hrmph
stpeter
I admit that I haven't reviewed the latest and greatest
stpeter
probably I should since it has my name on it, eh? ;-)
m&m
hrm
stpeter
in XEP-0206, I wonder if the text about TLS really makes sense - perhaps better to say "MUST NOT" do TLS at the BOSH layer?
m&m
I thought that's what we all agreed to
m&m
well, XEP-0206 has some more work to be done then
stpeter
well it says:
Note: Inclusion of TLS negotiation elements is allowed but is NOT RECOMMENDED. The definition of how TLS might be implemented over BOSH is currently beyond the scope of this document. Instead, channel encryption SHOULD be completed at the HTTP (transport) layer, not the XMPP (application) layer.
http://xmpp.org/extensions/tmp/xep-0206-1.4.html
Kev
'tis time.
Kev
1) roll call.
Kev
Lance sent apologies.
stpeter
anyway, I think I'll take some time for a decent review and also look at this in relation to XMPP over WebSocket so that they're in alignment
fippo
here
Zashhas joined
Kev
Tobias? Mattj?
Tobias
there
Kev
So, UPnP liasons.
Kev
I'd quite like to have either someone Council, or Council-esque on this. What do others think?
Kev
Do we have any volunteers from past/present Council or similar?
Kevstares at fippo.
fippohides
m&m
just don't look at me, I cannot
Kev
m&m: I'm not looking at you, for that reason.
stpeter
yeah m&m is overbooked
Kev
This is also the reason I'm not looking at me.
stpeter
but everyone is overbooked
m&m
that and conflict-of-interest issues
stpeter
note also that we're likely to have 2 more liaison teams, so we'll need to spread the load
Kev
There are likely to be Jinglish things involved here, I think? Which makes fippo seem like a good choice.
stpeternods to m&m I suppose
Kev
If he'd like to volunteer.
m&m
fippo sounds like a fine candidate
stpeter
heh
Tobias
would be nice to have someone from the council on the team
fippo
well, ok.
Kev
Tobias: Are you volunteering?
stpeter
well, I could do this as well since I've already been working with them
Kev
fippo: Ah, excellent.
Tobias
Kev, i'm quite busy as it is this semester
fippo
i can share with peter ;-)
Kev
stpeter: Or that. Although my preference would not be for you to take on anything new :p
stpeter
but that's true (for me) of all the liaison discussions
Tobias
if no one else would come up i'd spring in..if it's not too much meeting work
Kev
stpeter: Well, do you /want/ to be in on this?
stpeter
Kev: actually I would prefer that fippo not take on anything new ;-)
Kev
I have no idea what Fippo's workload is like :)
fippo
stpeter: I'll find things to drop ... like dialback :-)
Kev
stpeter / fippo / Tobias: do you want to quickly decide between yourselves?
stpeter
how about fippo and I volunteer?
Peter Waher
I also volunteer. UPnP are working with IoT-related things.
stpeter
Peter Waher: yes, thanks
Kev
Peter Waher: Yes, thanks - you and Joachim both.
Tobias
stpeter, completely happy with that :)
Peter Waher
(y)
stpeter
I like this liaison kind of thing
Kev
Yeah, I'd like to volunteer myself.
Kev
I'm just not going to.
stpeter
yep
Kev
How big a team do we want here?
stpeter
so me, fippo, Peter, and Joachim sounds fine
Kev
Does four people seem appropriate, or do we need to select further?
stpeter
I think we don't need more
Kev
If four people is OK (not too many), I'd like to propose fippo, Joachim and Peter^2.
fippo
let's see what the actual workload is and adapt if necessary.
stpeter
agreed
Tobias
great
Kev
fippo / Tobias, +-1 please.
Tobias
+1
fippo
'+1
Kev
Thanks
Kev
I'll take the proposal to the Board meeting in a minute, then.