XSF logo XMPP Council - 2010-12-15


  1. Tobias has joined
  2. Tobias has left
  3. Tobias has joined
  4. Tobias has left
  5. Tobias has joined
  6. Tobias has left
  7. Tobias has joined
  8. Tobias has left
  9. Tobias has joined
  10. Tobias has left
  11. Tobias has joined
  12. linuxwolf has joined
  13. linuxwolf has left
  14. linuxwolf has joined
  15. Fritzy has joined
  16. linuxwolf wow, I'm early for once
  17. Fritzy :)
  18. linuxwolf And a Fritzy has appeared!
  19. linuxwolf (-:
  20. remko has joined
  21. Kev Three down.
  22. Kev Matt is joining.
  23. MattJ has joined
  24. Kev Ralph has also been poked, but not responded.
  25. Kev So, shall we start?
  26. Kev 1) Roll call
  27. linuxwolf present
  28. Fritzy present
  29. MattJ waves
  30. Fritzy presents!
  31. Kev Righty.
  32. Kev 2) Agenda bashing.
  33. Fritzy nope
  34. MattJ ditto
  35. linuxwolf a note at the end from me
  36. Kev Ok.
  37. Kev 3) Interop summary.
  38. Kev So, the interop event happened.
  39. dwd has joined
  40. Kev It started badly without much of a plan, I appointed myself 'in charge of stuff', there was a plan, it went very well.
  41. MattJ +1
  42. Fritzy I read the thread on it. Sounds like you made it productive.
  43. Kev We learned a bit about what we need to do next time, and discussion is starting to happen about this on the interop list.
  44. Fritzy any interesting results?
  45. Kev There's a report on the XSF blog.
  46. dwd I'd note from the floor that the interop testing done on SCRAM-SHA-1-PLUS was of quite some importance outside the XSF.
  47. ralphm has joined
  48. Kev Fritzy: Well, at the end of the week, everyone participating was more conformant than at the start.
  49. Kev Which is quite a result, relaly.
  50. Kev *really
  51. linuxwolf /nod
  52. Fritzy sounds good to me!
  53. dwd I'd also note that another interop event I've been invoved in increased its setup time to an entire week for the third event, so our spending two days on that is a *small* amount of time, relatively speaking.
  54. Kev It was surprising to me that the general standard of TLS handling was so high.
  55. Fritzy between servers
  56. Fritzy ?
  57. Kev So it does seem, largely, a deployment issue these days that s2s is often insecure.
  58. Kev Yes, s2s.
  59. MattJ Agreed
  60. Kev The only client that did the scripted testing was Swift.
  61. Kev There've been suggestions that the next interop should look at other low level stuff, with internationalisation seeming a sensible choice.
  62. dwd That's not to say that was the only client involved, though - a few used parts of the test network for various things.
  63. MattJ which is fine
  64. Kev dwd: Yes, I'm assuming everyone can read the report.
  65. Fritzy Will do.
  66. dwd Kev, It's on the new-fangled web thing, I didn't know everyone had it.
  67. Kev I don't think there's much more to say about it, but I think Council could consider whether it has a roll in the test plan for next time.
  68. dwd (Or even a role)
  69. Kev Maybe it doesn't, but it would seem to me that of the various XSF bodies, Council are the ones most likely to be thinking about interoperability requirements.
  70. Fritzy that makes sense.
  71. MattJ Indeed
  72. dwd There was also the suggestion concerning the server and client lists and the relationship with the interops.
  73. MattJ Next time I think perhaps council should draw up the tests
  74. MattJ and make them known further in advance of the interop
  75. Kev Yes, there was also discussion that clients and servers shouldn't be listed on xmpp.org unless they participate in the interop events, but that doesn't sound Councilish.
  76. Kev MattJ: Yep.
  77. Kev Righty, I think that's the interop done.
  78. ralphm Kev: agreed
  79. Kev linuxwolf: What did you want to add to the agenda
  80. ralphm I could imagine some interopmatrix
  81. Kev ?
  82. dwd I certainly think that indicating on those lists which ones *did* participate seems sensible.
  83. Fritzy Also, test preparation can be an open thing a week ahead of time -- something people are available to help with before testing is expected to start -- in muc and everything.
  84. remko dwd: *nod* It's a plus if you do, not a bad thing if you don't
  85. linuxwolf some upcoming items of work
  86. Kev Go for it.
  87. Kev Fritzy: Yes, this is all good. Jump on the interop list and discuss :)
  88. Kev linuxwolf: ... which are?
  89. linuxwolf so, we're working out some issues and their solutions regarding multiple resources
  90. Kev Ah.
  91. Kev http://doomsong.co.uk/extensions/render/multiple-clients.html ?
  92. linuxwolf plus a refresh of vcard
  93. ralphm linuxwolf: refresh?
  94. linuxwolf well, since an XML vcard specification is actually going to make it out of WG discussion, some of us feel it's time to also update (-:
  95. Kev linuxwolf: I did poke Joe about some updates I wanted to do to Mine a few months back, but he never replied.
  96. linuxwolf Kev: he's busy, and that brings me to the next piece
  97. Kev linuxwolf: That sounds new-fangled and exciting.
  98. ralphm linuxwolf: sounds nice, but any indication when?
  99. linuxwolf ralphm: it's an IETF WG, so that's still unknown (-:
  100. ralphm (also, does it include some way to indicate a JID?)
  101. ralphm linuxwolf: it seems this is kinda pending since 2000
  102. linuxwolf most of what we're doing with multiple resources is best practices, plus a bias toward message carbons
  103. linuxwolf ralphm: yes, but now there's actually consensus
  104. linuxwolf it's truly amazing to me (-:
  105. linuxwolf I'm trying to find the people who will actual work on these specs, but it looks like most of them will be moi
  106. ralphm not holding my breath C-:
  107. dwd http://tools.ietf.org/html/draft-ietf-vcarddav-vcardxml-06
  108. linuxwolf ^^
  109. Kev linuxwolf: Have you seen protoxep-multiple-clients?
  110. linuxwolf Kev: yes…since you just sent it to me
  111. linuxwolf (-:
  112. remko dwd: that looks even more verbose than the vcard before, nice
  113. dwd PSA's the responsible AD. Plus we could kick off an experimental XEP referencing the draft.
  114. ralphm it seems extensible, so hooray
  115. linuxwolf dwd: the XEP is started…just needs to get submitted
  116. Kev linuxwolf: Ok, I was trying to solve the same problems (I think) that you're trying to solve with carbons et al (It was carbons I wanted to update, not Mine, my bad).
  117. dwd remko, "It'll compress well"™
  118. linuxwolf Kev: no worries…let's you and I talk more about that
  119. Kev Sounds like a plan.
  120. linuxwolf I think I'll be taking authorship of a couple of these
  121. linuxwolf resource locking best practices, carbons, mine-ing
  122. stpeter has joined
  123. Kev And we'll wait to see the third vcard XEP proposal :)
  124. stpeter sigh
  125. stpeter got stuck in a massive traffic jam
  126. linuxwolf Kev: heh…at least #3 will actually use a vCard spec
  127. Fritzy stpeter: shitty
  128. Kev stpeter: I'm about to, which is why I'm keen to keep Council short.
  129. stpeter nod
  130. linuxwolf if we're counting infobits as #2
  131. MattJ stpeter, should have walked like I did :)
  132. Kev At least dwd is driving this time.
  133. dwd stpeter, You need to use better congestion control.
  134. Kev Right, so, that's probably us doneish on that.
  135. ralphm linuxwolf: aaaarghhh
  136. stpeter forgot his phone at home, otherwise would've contacted linuxwolf
  137. linuxwolf or a better routing algorithm (-
  138. Kev Next item: Next meeting.
  139. Kev We're halfway through December, I suggest we skip meeting until the new year.
  140. stpeter looks at the calendar
  141. linuxwolf /agreed
  142. stpeter yeah
  143. Fritzy 22nd shouldn't be a big deal though?
  144. Kev 5th Jan sounds good to me.
  145. MattJ That would give me a chance to get some XEPs submitted :)
  146. linuxwolf I'm <presence type='unavailable'/> until 01/03 anyway
  147. Fritzy ok
  148. stpeter I might be able to get some protoXEPs and edits done before the next meeting
  149. linuxwolf what stpeter said (-:
  150. dwd linuxwolf, That's not an RFC 3339 compliant date format, naughty.
  151. Kev MattJ: I intend to submit the 136bis related stuff once you're ready to submit 136bis.
  152. stpeter (protoxep for muc error elements)
  153. ralphm For the record: no -1 on publishing remote-auth
  154. Fritzy +1 for Jan 5th
  155. linuxwolf dwd: 20110103T08:00:00-07:00
  156. stpeter adds January 5 to the calendar
  157. remko linuxwolf: thanks. Now us europeans can understand what you mean
  158. Fritzy ralphm: would be interested in reading your critique
  159. Kev linuxwolf: I think that's an hour off.
  160. MattJ Kev, excellent
  161. ralphm Fritzy: 'no -1'
  162. Fritzy oh right
  163. Fritzy lack of veto
  164. Fritzy :)
  165. Kev 9am for -7, isn't it?
  166. Kev 1600 Real Time.
  167. ralphm Kev: did you catch that for the tally?
  168. stpeter it's 9 AM in Denver, 8 AM for Fritzy
  169. linuxwolf Kev: noting when I can be expected back online, not the next meeting (-:
  170. Fritzy yup
  171. Kev ralphm: I did, ta.
  172. Kev linuxwolf: sneaky.
  173. linuxwolf (-;
  174. linuxwolf it's sinister…just like my handedness
  175. Kev Ok, so, next meeting 5th Jan 1600GMT.
  176. Kev Any other Business?
  177. linuxwolf oh, FOSDEM
  178. dwd linuxwolf, Latin gags. I imagine your and PSA's classics-related humour has them rolling on the floor in Cisco.
  179. linuxwolf who from this council is thinking of attending
  180. linuxwolf ?
  181. MattJ <--
  182. dwd Kev will be.
  183. Kev linuxwolf: I'm assuming I will be.
  184. linuxwolf hehe
  185. dwd Kev, You are attending.
  186. stpeter heh
  187. Kev Jolly good.
  188. Fritzy Wish I could make it this year, but since I'll be in Italy shortly after, it isn't in the budget.
  189. remko dwd: you?
  190. linuxwolf dwd: "Good to be the King" (-:
  191. dwd Kev, I forgot to mention.
  192. stpeter and we know how much Kev loves Brussels
  193. dwd remko, I am, too. \o/
  194. MattJ :)
  195. stpeter but at least he has a few good memories of the place :)
  196. ralphm I'm attending of course
  197. Kev About || this much.
  198. remko dwd: \o/
  199. Fritzy they have good beer
  200. linuxwolf I need to find business justification before I can commit to being at FOSDEM
  201. Kev And I caught this awful 'having a wife' illness there, too.
  202. Kev But yes.
  203. ralphm linuxwolf: does "meeting ralphm" count?
  204. Kev linuxwolf: I'll be there :)
  205. linuxwolf (-:
  206. Kev Job done.
  207. linuxwolf if we have an "official council meeting", that can help (-:
  208. Fritzy aw man
  209. ralphm linuxwolf: done deal
  210. stpeter linuxwolf: we can find some customers for you to meet with :)
  211. dwd linuxwolf, Kurt wants to discuss digsig in XMPP, which is relevant.
  212. linuxwolf I'm working on my list…but every little thing helps
  213. Kev I expect there to be some informal interop, but I'm not sure if it'll be formal.
  214. linuxwolf stpeter: the good thing about Cisco is, it's global, so I can always find someone I need to talk with
  215. Kev Right.
  216. Fritzy we did Jingle interop the year before last
  217. ralphm linuxwolf: is being-council-member considered part of your job?
  218. linuxwolf ralphm: I believe it is, yes (-:
  219. ralphm ralphm: well, there you go
  220. linuxwolf heh
  221. Kev Or here you come, or something.
  222. Kev Anyway.
  223. Kev Any other any other business?
  224. linuxwolf I'm done...really!
  225. Fritzy no sir
  226. ralphm 5 min. to spare. nice
  227. Kev There are advantages to having a Chair with the attention span of a
  228. Kev oooh, butterflies.
  229. Kev Right!
  230. linuxwolf SQUIRREL!
  231. Kev I'll write up some meetings of the minute tomorrow morning.
  232. linuxwolf /nod
  233. Kev Thanks all
  234. Kev gavels the bang.
  235. linuxwolf Kev: and I'll begin the out-of-band discussion shortly
  236. MattJ Merci
  237. linuxwolf ¡gracias!
  238. Kev linuxwolf: Thanks. I like multiple-clients, but don't have an implementation yet, so it's not too late to change my mind :)
  239. Kev Anyway, there is a road to be hit.
  240. Kev gn all.
  241. Kev has left
  242. stpeter bye!
  243. linuxwolf ttfn
  244. dwd has left
  245. linuxwolf has left
  246. ralphm Kev: I want it in my n900
  247. stpeter checks the logs to see what he missed
  248. Fritzy has left
  249. remko has left
  250. Tobias has left
  251. MattJ has left
  252. ralphm has left
  253. Tobias has joined
  254. Tobias has left
  255. Tobias has joined
  256. bear has joined
  257. mlundblad has joined
  258. stpeter has left
  259. Tobias has left
  260. mlundblad has left