got till 3.12 but could tell you my comments so far
Kev
Go for it.
Kev
I'm at the not-blocking-but-bits-of-it-are-a-bit-weird stage.
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?
Kev
I was quite uneasy about building a new layer of identity over the top of XMPP, personally.
Tobias
you mean their authentication part?
Kev
Yeah.
MattJ
I need to read it more thorougly and post on-list, I have only been able to skim it
Kev
I found it very very hard going.
MattJ
Yes
MattJ
The question is whether it needs to be
Kev
But in any case - Tobias: Was that an opinion expressed, or going to be on list?
MattJ
I suspect not
Kev
MattJ: Yes, lots seems like it should be simplifiable.
Kev
Or more XMPPish.
Tobias
Kev, i'll probably reply on list when i've read it completely...seems more sensible at least
Kev
OK.
Kev
3) Date of next meeting?
Peter Waherhas joined
jabberjocke
permission to speak?
Tobias
hi Peter Waher
Kev
Yeah, go for it.
jabberjocke
the work is very ongoing and we would
jabberjocke
like to have thorough discussions on the lists
jabberjocke
peters had alot of experiens in the sensor field
jabberjocke
so the provisioning "third party"
Tobias
that's good...because we probably have not so much :)
jabberjocke
is needed when using sensors from different suppliers and defineing who should
jabberjocke
descide ion the access
jabberjocke
simplification is most welcome
Kev
OK, thanks.
MattJ
I'll read it with that in mind when I read it, then :)
jabberjocke
(y)
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).
jabberjocke
throw questions any time
Kev
It's where the XMPP experts live :)
Kev
Ta.
Kev
So, I think we're on to
3) Next date?
Kev
SBTSBC?
Tobias
wfm
MattJ
wfm
Kev
4) AOB?
Tobias
none here
Kev
MattJ: ?
Kev
I'll take that as a no :)
Kev
Right, so I think we're done.
Kev
Thanks all
Kevbangs the gavel.
m&m
gadammit
m&m
ok, I'll review the notes, and respond accordingly
MattJ
No AOB
Kev
Ta.
stpeter
(sorry that I have been in a Cisco meeting this morning)
stpeter
people are expecting me to do internal work these days... ;-)
MattJ
stpeter, we need the apology from Cisco :)
Tobias
and a signed letter from your mom
m&m
heh
m&m
2) no objections
m&m
3) I am on holiday next week, so will not be able to make it
m&m
4) irrelevant at this point
Kev
Would you like us to delay (3)?
m&m
I can respond on the list, if anything comes up next week
m&m
so, no, you don't need to delay on my part
stpeter
I'll review the log when I'm done here in ~15 minutes (I hope)
Kev
(I note that with the DST change, SBTSBC is different in UTC)