fippokev: and dont forget the agenda item you missed last time ;-)
Peter Waherhas joined
fippoah wait, you did not.
fipponit for 0124: content-length in example 6 seems wrong
stpeterBTW we still need to form the UPnP Liaison Team, I received a ping about that again this morning
fippostpeter: kev has it on the agenda, forgot it last time
fippothe content-length in example 3 is wrong, too
fippoand the one in example 5
stpeterI admit that I haven't reviewed the latest and greatest
stpeterprobably I should since it has my name on it, eh? ;-)
stpeterin 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&mI thought that's what we all agreed to
m&mwell, XEP-0206 has some more work to be done then
stpeterwell 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.
Kev1) roll call.
KevLance sent apologies.
stpeteranyway, 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
KevSo, UPnP liasons.
KevI'd quite like to have either someone Council, or Council-esque on this. What do others think?
KevDo we have any volunteers from past/present Council or similar?
Kevstares at fippo.
m&mjust don't look at me, I cannot
Kevm&m: I'm not looking at you, for that reason.
stpeteryeah m&m is overbooked
KevThis is also the reason I'm not looking at me.
stpeterbut everyone is overbooked
m&mthat and conflict-of-interest issues
stpeternote also that we're likely to have 2 more liaison teams, so we'll need to spread the load
KevThere are likely to be Jinglish things involved here, I think? Which makes fippo seem like a good choice.
stpeternods to m&m I suppose
KevIf he'd like to volunteer.
m&mfippo sounds like a fine candidate
Tobiaswould be nice to have someone from the council on the team
KevTobias: Are you volunteering?
stpeterwell, I could do this as well since I've already been working with them
Kevfippo: Ah, excellent.
TobiasKev, i'm quite busy as it is this semester
fippoi can share with peter ;-)
Kevstpeter: Or that. Although my preference would not be for you to take on anything new :p
stpeterbut that's true (for me) of all the liaison discussions
Tobiasif no one else would come up i'd spring in..if it's not too much meeting work
Kevstpeter: Well, do you /want/ to be in on this?
stpeterKev: actually I would prefer that fippo not take on anything new ;-)
KevI have no idea what Fippo's workload is like :)
fippostpeter: I'll find things to drop ... like dialback :-)
Kevstpeter / fippo / Tobias: do you want to quickly decide between yourselves?
stpeterhow about fippo and I volunteer?
Peter WaherI also volunteer. UPnP are working with IoT-related things.
stpeterPeter Waher: yes, thanks
KevPeter Waher: Yes, thanks - you and Joachim both.
Tobiasstpeter, completely happy with that :)
stpeterI like this liaison kind of thing
KevYeah, I'd like to volunteer myself.
KevI'm just not going to.
KevHow big a team do we want here?
stpeterso me, fippo, Peter, and Joachim sounds fine
KevDoes four people seem appropriate, or do we need to select further?
stpeterI think we don't need more
KevIf four people is OK (not too many), I'd like to propose fippo, Joachim and Peter^2.
fippolet's see what the actual workload is and adapt if necessary.
Kevfippo / Tobias, +-1 please.
KevI'll take the proposal to the Board meeting in a minute, then.