XMPP Council - 2014-03-19


  1. Lance

    i dont think i'll be able to make it for the meeting this afternoon. i'll vote on list

  2. Kev

    Thanks Lance.

  3. Kev

    BTW - things I have on for today are: http://xmpp.org/extensions/tmp/xep-0124-1.11rc3.html UPnP liasons.

  4. Kev

    http://xmpp.org/extensions/inbox/iot-discovery.html

  5. Kev

    (Although I hadn't noticed that one!)

  6. Kev

    m&m: Have I missed anything from the editor team?

  7. m&m

    that looks like the full list

  8. Kev

    Ta.

  9. Zash

    time?

  10. stpeter

    30 minutes from now, right?

  11. Tobias

    Zash, is your NTP broken?

  12. Tobias

    ;)

  13. Zash

    <iq type='get' id='so confuse'> <time xmlns='urn:xmpp:time'/> </iq>

  14. fippo

    kev: and dont forget the agenda item you missed last time ;-)

  15. fippo

    ah wait, you did not.

  16. fippo

    nit for 0124: content-length in example 6 seems wrong

  17. stpeter

    BTW we still need to form the UPnP Liaison Team, I received a ping about that again this morning

  18. fippo

    stpeter: kev has it on the agenda, forgot it last time

  19. fippo

    the content-length in example 3 is wrong, too

  20. fippo

    and the one in example 5

  21. stpeter

    hrmph

  22. stpeter

    I admit that I haven't reviewed the latest and greatest

  23. stpeter

    probably I should since it has my name on it, eh? ;-)

  24. m&m

    hrm

  25. 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?

  26. m&m

    I thought that's what we all agreed to

  27. m&m

    well, XEP-0206 has some more work to be done then

  28. 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

  29. Kev

    'tis time.

  30. Kev

    1) roll call.

  31. Kev

    Lance sent apologies.

  32. 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

  33. fippo

    here

  34. Kev

    Tobias? Mattj?

  35. Tobias

    there

  36. Kev

    So, UPnP liasons.

  37. Kev

    I'd quite like to have either someone Council, or Council-esque on this. What do others think?

  38. Kev

    Do we have any volunteers from past/present Council or similar?

  39. Kev stares at fippo.

  40. fippo hides

  41. m&m

    just don't look at me, I cannot

  42. Kev

    m&m: I'm not looking at you, for that reason.

  43. stpeter

    yeah m&m is overbooked

  44. Kev

    This is also the reason I'm not looking at me.

  45. stpeter

    but everyone is overbooked

  46. m&m

    that and conflict-of-interest issues

  47. stpeter

    note also that we're likely to have 2 more liaison teams, so we'll need to spread the load

  48. Kev

    There are likely to be Jinglish things involved here, I think? Which makes fippo seem like a good choice.

  49. stpeter nods to m&m I suppose

  50. Kev

    If he'd like to volunteer.

  51. m&m

    fippo sounds like a fine candidate

  52. stpeter

    heh

  53. Tobias

    would be nice to have someone from the council on the team

  54. fippo

    well, ok.

  55. Kev

    Tobias: Are you volunteering?

  56. stpeter

    well, I could do this as well since I've already been working with them

  57. Kev

    fippo: Ah, excellent.

  58. Tobias

    Kev, i'm quite busy as it is this semester

  59. fippo

    i can share with peter ;-)

  60. Kev

    stpeter: Or that. Although my preference would not be for you to take on anything new :p

  61. stpeter

    but that's true (for me) of all the liaison discussions

  62. Tobias

    if no one else would come up i'd spring in..if it's not too much meeting work

  63. Kev

    stpeter: Well, do you /want/ to be in on this?

  64. stpeter

    Kev: actually I would prefer that fippo not take on anything new ;-)

  65. Kev

    I have no idea what Fippo's workload is like :)

  66. fippo

    stpeter: I'll find things to drop ... like dialback :-)

  67. Kev

    stpeter / fippo / Tobias: do you want to quickly decide between yourselves?

  68. stpeter

    how about fippo and I volunteer?

  69. Peter Waher

    I also volunteer. UPnP are working with IoT-related things.

  70. stpeter

    Peter Waher: yes, thanks

  71. Kev

    Peter Waher: Yes, thanks - you and Joachim both.

  72. Tobias

    stpeter, completely happy with that :)

  73. Peter Waher

    (y)

  74. stpeter

    I like this liaison kind of thing

  75. Kev

    Yeah, I'd like to volunteer myself.

  76. Kev

    I'm just not going to.

  77. stpeter

    yep

  78. Kev

    How big a team do we want here?

  79. stpeter

    so me, fippo, Peter, and Joachim sounds fine

  80. Kev

    Does four people seem appropriate, or do we need to select further?

  81. stpeter

    I think we don't need more

  82. Kev

    If four people is OK (not too many), I'd like to propose fippo, Joachim and Peter^2.

  83. fippo

    let's see what the actual workload is and adapt if necessary.

  84. stpeter

    agreed

  85. Tobias

    great

  86. Kev

    fippo / Tobias, +-1 please.

  87. Tobias

    +1

  88. fippo

    '+1

  89. Kev

    Thanks

  90. Kev

    I'll take the proposal to the Board meeting in a minute, then.

  91. Kev

    3) http://xmpp.org/extensions/inbox/iot-discovery.html Accept?

  92. Kev

    I need to go on-list for this.

  93. Tobias

    i haven't gotten through this completely yet, so i'll vote on list

  94. fippo

    me too -- but i'd not that i am somewhat strongly opposed to have hardcoded user@domain names there

  95. stpeter

    I need to sit down and read then entire IoT "suite"

  96. Kev

    OK.

  97. Kev

    4) http://xmpp.org/extensions/tmp/xep-0124-1.11rc3.html Accept 1.11?

  98. Kev

    I, similarly, need to take this to the list.

  99. fippo

    look good. the content-lengths need to be checked/fixed so i'll vote on list too with more feedback.

  100. Tobias

    didn't have that one on the radar at all..will go through the diff this evening

  101. Kev

    Ta.

  102. Kev

    5) Date of next

  103. m&m

    editor notes the examples need to sanitized

  104. Kev

    16:00 UK time, Wednesday?

  105. Kev

    (I /think/ it's the end of next week Europe hits DST)

  106. Tobias

    Kev, right...in the night from 29/30

  107. fippo

    m&m: will send that feedback directly to editor.

  108. Tobias

    that time wfm

  109. fippo

    time wfm, too

  110. Kev

    6) AOB?

  111. Tobias

    none from my side

  112. m&m

    fippo: only if that feedback is patches (-: Otherwise substantive changes really ought to be sent it to council@

  113. Kev

    So I think that's no AOB from anyone?

  114. fippo

    none from me either

  115. Kev

    In which case... thanks all.

  116. Kev bangs the gavel.

  117. Tobias

    thank you

  118. MattJ

    Sigh, sorry

  119. stpeter

    hi MattJ

  120. MattJ

    Hey

  121. fippo

    m&m: sent. more work than I expected

  122. m&m

    ok

  123. m&m

    thank you for preserving the whitespace (-:

  124. m&m

    do the calculations assume the whitespace is present, or not present?

  125. fippo

    not present

  126. m&m

    thanks

  127. fippo

    i wasnt sure what i wanted example 6 to look like

  128. fippo

    so I left the whitespace there