[Standards] XEP-0255: Location Query

2009-02-12 Thread Helge Timenes
Just a heads up notice: As suggested by Stephen Pendleton I plan to add ip-address to the type of "beacons" that can be submitted in a location query. The justification being that in most cases an IP address can be associated with a particular country, region and city. Some items of concern in

Re: [Standards] UPDATED: XEP-0257 (Client Certificate Management for SASL EXTERNAL)

2009-02-12 Thread Peter Saint-Andre
Alexey Melnikov wrote: > Peter Saint-Andre wrote: > >> Alexey Melnikov wrote: >> >> >>> 2). In Section 3 the following text was added: >>> If the subjectAltName contains a full JID the server MUST force the client to use the given resource during resource binding. The client is

Re: [Standards] UPDATED: XEP-0257 (Client Certificate Management for SASL EXTERNAL)

2009-02-12 Thread Alexey Melnikov
Peter Saint-Andre wrote: Alexey Melnikov wrote: 2). In Section 3 the following text was added: If the subjectAltName contains a full JID the server MUST force the client to use the given resource during resource binding. The client is only allowed to use the provided resource name. If

Re: [Standards] UPDATED: XEP-0257 (Client Certificate Management for SASL EXTERNAL)

2009-02-12 Thread Peter Saint-Andre
Alexey Melnikov wrote: > 2). In Section 3 the following text was added: > >> If the subjectAltName contains a full JID the server MUST force the >> client to use the given resource during resource binding. The client >> is only allowed to use the provided resource name. If a client with >> the sa

Re: [Standards] UPDATED: XEP-0257 (Client Certificate Management for SASL EXTERNAL)

2009-02-12 Thread Alexey Melnikov
XMPP Extensions Editor wrote: Version 0.2 of XEP-0257 (Client Certificate Management for SASL EXTERNAL) has been released. Abstract: This specification defines a method to manage client certificates that can be used with SASL External to allow clients to log in without a password. Changelog

[Standards] UPDATED: XEP-0257 (Client Certificate Management for SASL EXTERNAL)

2009-02-12 Thread XMPP Extensions Editor
Version 0.2 of XEP-0257 (Client Certificate Management for SASL EXTERNAL) has been released. Abstract: This specification defines a method to manage client certificates that can be used with SASL External to allow clients to log in without a password. Changelog: [See revision history] (dm) Di

Re: [Standards] Section 2.3 of XEP-0107

2009-02-12 Thread Jonathan Schleifer
Am 11.02.2009 um 21:34 schrieb Ralph Meijer: If Gajim implements sending along moods in messages, for the sole purpose of replacing PEP, I would consider that a bug. It goes against the very reason we started to define our publish-subscribe specifications for. We had a few discussions abo

Re: [Standards] groupchat and error message routing

2009-02-12 Thread Waqas Hussain
On Thu, Feb 12, 2009 at 3:57 PM, Dave Cridland wrote: > On Wed Feb 11 18:27:03 2009, Jiří Zárevúcký wrote: >> >> I'm not entirely sure, but I think that nobody is ever supposed to >> send an error message to a bare JID. > > Not true - PEP nodes send from a bare jid, if these bounce they end up bac

Re: [Standards] Password protected rooms

2009-02-12 Thread Dave Cridland
On Wed Feb 11 15:08:41 2009, Matthew Wild wrote: On Wed, Feb 11, 2009 at 3:01 PM, Jonathan Schleifer wrote: > Just a reason NOT to require a PW for the owner: Some admin might have > changed it and now the owner can't join the room anymore or change it back. > That same admin could simply

Re: [Standards] Password protected rooms

2009-02-12 Thread Pavel Simerda
On Wed, 11 Feb 2009 10:45:34 -0800 Justin Karneges wrote: > On Wednesday 11 February 2009 05:06:24 Kevin Smith wrote: > > On Wed, Feb 11, 2009 at 12:58 PM, Kurt Zeilenga > > > wrote: > > > I'm thinking more about a non-comprised server case, but just the > > > case of poor administrative practi

Re: [Standards] Password protected rooms

2009-02-12 Thread Dave Cridland
On Wed Feb 11 18:45:34 2009, Justin Karneges wrote: There are quite many XMPP services (bots and such) that you authenticate with just by JID. Why would those things be okay, but MUC is somehow more secure and requires a password? Well, yes - in a perfect world, we'd sign stanzas with X.50

Re: [Standards] groupchat and error message routing

2009-02-12 Thread Dave Cridland
On Wed Feb 11 18:27:03 2009, Jiří Zárevúcký wrote: I'm not entirely sure, but I think that nobody is ever supposed to send an error message to a bare JID. Not true - PEP nodes send from a bare jid, if these bounce they end up back at a connected resource, much to the client's bewilderment,