XMPP Council - 2013-03-27


  1. Tobias

    council metting in 2h?

  2. Kev

    Yep.

  3. Kev

    Ding.

  4. Tobias

    Dong.

  5. Tobias

    The witch is dead.

  6. Kev

    Oh no!

  7. Kev

    I have poked the Ralph.

  8. Tobias

    ralph seems to be idle

  9. MattJ wonders what the time is

  10. MattJ

    and what time the meeting is

  11. Tobias

    hammer time

  12. Kev

    Bat time.

  13. MattJ

    Did the clocks change?

  14. Kev

    1) Roll call.

  15. Kev

    I am here.

  16. Kev

    MattJ: Not in Europe yet.

  17. MattJ

    I'm also here

  18. Kev

    Although they will before the next meeting.

  19. Tobias

    As am I

  20. MattJ

    Ok, so my client is just lying to me

  21. Tobias

    MattJ, the night of this sat/sun

  22. Kev

    m&m?

  23. Kev

    Just the three of us then, by the look of it.

  24. Kev

    2) http://xmpp.org/extensions/inbox/sensor-network-provisioning.html Accept as Experimental?

  25. Kanchil

    Kev: http://xmpp.org/extensions/inbox/sensor-network-provisioning.html: XEP-xxxx: XEP - Sensor Networks - Provisioning

  26. Tobias

    got till 3.12 but could tell you my comments so far

  27. Kev

    Go for it.

  28. Kev

    I'm at the not-blocking-but-bits-of-it-are-a-bit-weird stage.

  29. Tobias

    Editorial: - images in-line as SVG or Base64ed PNG - glossary could use definition list syntax instead of table Formal: - Example 1: 'get' and 'response' in node names is a bit redundant. The info is already available in the IQ-type. - Example 2..: Similiar redundant info in names. Isn't that important when compressed but still unclean in my opinion. Technical: - Out of scope probably: Are the sensor nodes use standard XMPP C2S connections over TCP/IP + TLS?

  30. Kev

    I was quite uneasy about building a new layer of identity over the top of XMPP, personally.

  31. Tobias

    you mean their authentication part?

  32. Kev

    Yeah.

  33. MattJ

    I need to read it more thorougly and post on-list, I have only been able to skim it

  34. Kev

    I found it very very hard going.

  35. MattJ

    Yes

  36. MattJ

    The question is whether it needs to be

  37. Kev

    But in any case - Tobias: Was that an opinion expressed, or going to be on list?

  38. MattJ

    I suspect not

  39. Kev

    MattJ: Yes, lots seems like it should be simplifiable.

  40. Kev

    Or more XMPPish.

  41. Tobias

    Kev, i'll probably reply on list when i've read it completely...seems more sensible at least

  42. Kev

    OK.

  43. Kev

    3) Date of next meeting?

  44. jabberjocke

    permission to speak?

  45. Tobias

    hi Peter Waher

  46. Kev

    Yeah, go for it.

  47. jabberjocke

    the work is very ongoing and we would

  48. jabberjocke

    like to have thorough discussions on the lists

  49. jabberjocke

    peters had alot of experiens in the sensor field

  50. jabberjocke

    so the provisioning "third party"

  51. Tobias

    that's good...because we probably have not so much :)

  52. jabberjocke

    is needed when using sensors from different suppliers and defineing who should

  53. jabberjocke

    descide ion the access

  54. jabberjocke

    simplification is most welcome

  55. Kev

    OK, thanks.

  56. MattJ

    I'll read it with that in mind when I read it, then :)

  57. jabberjocke

    (y)

  58. Kev

    I think there's lots of work that would benefit on the list (ideally in chunks small enough that they can be processed without setting aside hours at a time, as has happened before with big specs).

  59. jabberjocke

    throw questions any time

  60. Kev

    It's where the XMPP experts live :)

  61. Kev

    Ta.

  62. Kev

    So, I think we're on to 3) Next date?

  63. Kev

    SBTSBC?

  64. Tobias

    wfm

  65. MattJ

    wfm

  66. Kev

    4) AOB?

  67. Tobias

    none here

  68. Kev

    MattJ: ?

  69. Kev

    I'll take that as a no :)

  70. Kev

    Right, so I think we're done.

  71. Kev

    Thanks all

  72. Kev bangs the gavel.

  73. m&m

    gadammit

  74. m&m

    ok, I'll review the notes, and respond accordingly

  75. MattJ

    No AOB

  76. Kev

    Ta.

  77. stpeter

    (sorry that I have been in a Cisco meeting this morning)

  78. stpeter

    people are expecting me to do internal work these days... ;-)

  79. MattJ

    stpeter, we need the apology from Cisco :)

  80. Tobias

    and a signed letter from your mom

  81. m&m

    heh

  82. m&m

    2) no objections

  83. m&m

    3) I am on holiday next week, so will not be able to make it

  84. m&m

    4) irrelevant at this point

  85. Kev

    Would you like us to delay (3)?

  86. m&m

    I can respond on the list, if anything comes up next week

  87. m&m

    so, no, you don't need to delay on my part

  88. stpeter

    I'll review the log when I'm done here in ~15 minutes (I hope)

  89. Kev

    (I note that with the DST change, SBTSBC is different in UTC)

  90. Kev

    And that's super-efficient Council minutes out.

  91. Tobias

    i'll update the entry in the calendar

  92. Kev

    Ta.

  93. stpeter

    Kev: noted, you are a model for us all ;-)

  94. stpeter

    bbiaf