Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Joachim Lindborg
fixed that *Regards* Joachim Lindborg CTO, systems architect *Keynote speaker at GoGonet live IPv6 conferens 12-14 november * Sustainable Innovation AB Adress: Box 55998 102 16 Stockholm Besöksadress: Storgatan 31 (Malmgården) Email: joachim.lind

Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Ludovic BOCQUET
Comments after: Le 13/11/2013 19:09, Peter Waher a écrit : > type='normal' xml:lang='en'> > > Something happened. > > must be: > Something else happened. > > For be beautiful, all http://www.xmpp.org links must be http://xmpp.org. Exam

Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Steffen Larsen
No problem Peter, You did all the hard job.. I am just commenting. :-) /Steffen On 13 Nov 2013, at 19:09, Peter Waher wrote: > Hello Steffen > > Ok, I see. It might be, as you say, implementation specific. Our > implementation accepts any number of child elements. But that might not be > the

Re: [Standards] XEP-0321 (Remote Roster Management): we need something with less restrictions

2013-11-13 Thread Matthew Wild
On 13 November 2013 18:12, Goffi wrote: > So, is it possible to remove these restrictions from the XEP ? Or at least > to have an unsecure mode, and a secure mode with full access to roster ? This is related to something we discussed at the summit recently - privileged components. I have half an

[Standards] XEP-0321 (Remote Roster Management): we need something with less restrictions

2013-11-13 Thread Goffi
G'day, To implement experimental features ( http://www.goffi.org/post/2012/06/24/Fine-access-tuning-for-PubSub ) for my XMPP client ( http://sat.goffi.org ), I have started my own pubsub server as an external composant, based on Ralph Meijer's Idavoll ( http://repos.goffi.org/sat_pubsub/ and

Re: [Standards] Commenting: XEP-0277 and XEP-0303

2013-11-13 Thread Goffi
G'day, Sorry for the delay between my answers. I'm now working full time on my project ( http://sat.goffi.org ) which make intensive use of pubsub and microblogging (see the demo at http://www.libervia.org ). ok, now for the questions/remarks: First I'm implementing XHTML for microblogging

Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Steffen Larsen
Hi Peter, I was thinking the same, that you could put multiple log elements into the message.. But then client or component should in the other end always try to “read” multiple structures out of the message stanza. It should be possible, but on the other side how do we treat the other tags in

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Steffen Larsen
ha ha ha… :-) /Steffen On 13 Nov 2013, at 14:57, Thijs Alkemade wrote: > > On 13 nov. 2013, at 14:51, Philipp Hancke wrote: > >>> Ejabberd's default key: >>> C5:78:17:B1:34:90:54:D0:5A:16:A4:C6:71:80:6D:C3:F8:8B:F1:31:3D:64:BD:42:8F:1F:C5:D9:21:EB:99:BE >> >> That is the CN=ejabberd? Likely

Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Peter Waher
Hello Steffen Thanks for the feedback. It's a good point that you might want to send multiple events in the same message. But would that not be accomplished with the current structure, but with multiple elements? As so: Something happened. Something e

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Thijs Alkemade
On 13 nov. 2013, at 14:51, Philipp Hancke wrote: >> Ejabberd's default key: >> C5:78:17:B1:34:90:54:D0:5A:16:A4:C6:71:80:6D:C3:F8:8B:F1:31:3D:64:BD:42:8F:1F:C5:D9:21:EB:99:BE > > That is the CN=ejabberd? Likely the same one I saw back in > http://mail.jabber.org/pipermail/standards/2007-July/01

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Philipp Hancke
Ejabberd's default key: C5:78:17:B1:34:90:54:D0:5A:16:A4:C6:71:80:6D:C3:F8:8B:F1:31:3D:64:BD:42:8F:1F:C5:D9:21:EB:99:BE That is the CN=ejabberd? Likely the same one I saw back in http://mail.jabber.org/pipermail/standards/2007-July/016086.html

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Dave Cridland
On Wed, Nov 13, 2013 at 1:27 PM, Thijs Alkemade wrote: > > On 13 nov. 2013, at 12:56, Dave Cridland wrote: > > > Then there's the "same-cert" shortcut, where the receiver connects to > the authoritative server and compares certs. This is an interesting case, > because we're deriving identity (an

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Thijs Alkemade
On 13 nov. 2013, at 12:56, Dave Cridland wrote: > Then there's the "same-cert" shortcut, where the receiver connects to the > authoritative server and compares certs. This is an interesting case, because > we're deriving identity (and therefore authenticating) from the certificate, > but the

Re: [Standards] Dialback, authentication, and authorization

2013-11-13 Thread Philipp Hancke
On Wed, 13 Nov 2013, Dave Cridland wrote: I'm having an interesting conversation with Fippo on the nature of dialback with respect to authorization and authentication - in particular, which parts of the protocol authenticate, and which authorize, and how. Here's what we'ev been discussing:

[Standards] Dialback, authentication, and authorization

2013-11-13 Thread Dave Cridland
I'm having an interesting conversation with Fippo on the nature of dialback with respect to authorization and authentication - in particular, which parts of the protocol authenticate, and which authorize, and how. Here's what we'ev been discussing: To recap, in authentication, one side asserts an

Re: [Standards] Updated: Event logging over XMPP

2013-11-13 Thread Steffen Larsen
Hi, I really think we have made some progress on this one. So cool Peter! :-) Just want to add a small thing: I have some logging like this already on my clients, and when the information is not that important I sometime piggy back the event log into one message stanza. So what I really would li