-
Neustradamus
has left
-
Tobias
has left
-
Tobias
has joined
-
Tobias
has left
-
Neustradamus
has left
-
Neustradamus
has left
-
m&m
has left
-
Tobias
has left
-
Tobias
has joined
-
Kev
has joined
-
jabberjocke
has joined
-
Tobias
has left
-
Tobias
has joined
-
Tobias
has left
-
Tobias
has joined
-
jabberjocke
has left
-
Tobias
has left
-
Tobias
has joined
-
m&m
has joined
-
jabberjocke
has joined
-
MattJ
has joined
-
m&m
ding?
-
m&m
or am I an hour early?
-
MattJ
Dong
-
MattJ
Nope
-
MattJ
Kev is... *gasp* late
-
MattJ
By 32 seconds
-
Kev
It is time.
-
m&m
dislikes Daylight Savings Time
-
MattJ
too
-
Kev
I've poked Ralph.
-
Kev
Did I miss anything, or is there nothing to discuss this week?
-
stpeter
has joined
-
Kev
1) Roll call.
-
Kev
I'm here.
-
m&m
presente (for once)
-
stpeter
howdy
-
MattJ
Here
-
Kev
Tobias:?
-
Tobias
here
-
Kev
Assuming I didn't miss anything and there's nothing for this week again...
-
Kev
3) Date of next meeting.
-
m&m
SBTSBC WFM
-
MattJ
Me too
-
Tobias
wfm
-
Kev
And for me.
-
stpeter
I still need to publish a few things from the inbox
-
Kev
But that's for next week?
-
Kev
4) AOB?
-
stpeter
no, just noting my action items :-)
-
m&m
none from me
-
stpeter
however, the last call for XEP-0152 finished
-
stpeter
so I suppose the Council can vote on it at some point
-
Kev
Did we have a sum total of no feedback on that one, or do I misremember?
-
stpeter
same for 288
-
stpeter
there was pre-LC feedback on 152
-
stpeter
from Lance, at least, IIRC
-
Kev
Fippo's comment on 288 suggested that there were (probably minor) changes still to come on that.
-
stpeter
and feedback from Zash on 288
-
Kev
I've poked Fippo to see if 288 changes are coming.
-
stpeter
I will review 288 this week
-
Kev
I'll try to dig out the feedback on 152, I didn't notice it.
-
stpeter
nod
-
stpeter
that's it from me
-
Kev
I've noted adding 288 and 152 to next Council.
-
stpeter
thanks!
-
Kev
I think we're done then.
-
Kev
Thanks all
-
Kev
bangs the gavel.
-
m&m
grazie
-
stpeter
notes to himself that he needs to issue a Last Call on XEP-0220, too
-
MattJ
Do you have to?
-
MattJ
Can't we just, you know... leave it as it is? :P
-
stpeter
:P
-
MattJ
I guess we need something to keep our mailing lists active
-
m&m
heh
-
stpeter
hey, it has been in use since ~October 2000 and was in a Proposed Standard RFC, I think it deserves to be something other than an Experimental XEP :P
-
m&m
you could always propose an alternative (-:
-
Kev
'backdial
-
m&m
fwdcall?
-
m&m
er…callfwd
-
stpeter
tunes out the banter and pays attention to his conference call :P
-
Tobias
so..AOB section done?
-
Kev
Meeting done.
-
Kev
7 minutes ago.
-
MattJ
wb Tobias :)
-
Tobias
ahh..overread that line
-
Tobias
MattJ, been there all the time...physically
-
MattJ
But mentally...?
-
Tobias
menta...what?
-
MattJ
Thought so. It's all the C++ you've been doing :)
-
m&m
ouch
-
Tobias
or the couple minutes lua i squeezed in a week ago
-
fippo
has joined
-
fippo
hah, the dialback alternative will of course be turbohalibut!
-
fippo
don't you read xmpp@ietf.org? ;-)
-
m&m
fippo: uhm … no
-
m&m
POSH actually is turbohalibut
-
m&m
are you sure *you* read xmpp@ietf.org? (-:
-
MattJ
Haha
-
m&m
hands fippo compress for the burn
-
fippo
goes digging the archives
-
fippo
well, POSH doesn't DER-encode, does it?
-
fippo
i'm pretty sure this step is crucial for turbohalibut
-
m&m
has left
-
m&m
has joined
-
m&m
has left
-
m&m
has joined
-
fippo
has left
-
Tobias
has left
-
jabberjocke
has left
-
Kev
User exists but hasn't yet implicitly created a roster by adding anything to it. Does the roster exist or not?
-
Kev
i.e. does the text saying that you MUST NOT return an error, or the text saying you MUST return an error apply?
-
Kev
( http://tools.ietf.org/html/rfc6121#section-2.1.4 )
-
Kanchil
Kev: http://tools.ietf.org/html/rfc6121#section-2.1.4:
RFC 6121 - Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
-
Tobias
has joined
-
MattJ
Kev, in Prosody no stored data == empty stored data
-
MattJ
so we treat it as an empty roster
-
Kev
Ta.
-
Kev
Anyone else?
-
Tobias
has joined
-
Neustradamus
has left
-
m&m
has left
-
m&m
has joined
-
m&m
Cisco products behave similarly
-
Kev
Merci.
-
m&m
for roster
-
MattJ
btw, we also actually load the roster when the user binds their resource
-
MattJ
and fail binding if it can't be loaded
-
m&m
has left
-
MattJ
(failure, as opposed to not existing)
-
MattJ
This was so we don't end up overwriting it, or confusing clients into thinking they have an empty or no roster
-
Kev
Yes, that's quite sensible.
-
m&m
has joined
-
m&m
has left
-
m&m
has joined
-
jabberjocke
has joined
-
m&m
has left
-
m&m
has joined
-
m&m
has left
-
m&m
has joined
-
stpeter
has left
-
m&m
has left