Re: [Standards] Proposed XMPP Extension: Incident Reporting

2009-04-27 Thread Philipp Hancke
Title: Incident Reporting Abstract: This specification defines methods for incident reporting among XMPP server deployments. URL: http://www.xmpp.org/extensions/inbox/incident-reporting.html the purpose is to enhance the information flow so that attack patterns become visible earlier? I some

Re: [Standards] UPDATED: XEP-0237 (Roster Versioning)

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/27/09 5:27 PM, Jiří Zárevúcký wrote: > I've noticed change in this part: > >> the server MUST consider the item to have been modified and >> therefore MUST send the item to the client (typically via a roster >> push as described below). > > You

[Standards] Proposed XMPP Extension: Incident Reporting

2009-04-27 Thread XMPP Extensions Editor
The XMPP Extensions Editor has received a proposal for a new XEP. Title: Incident Reporting Abstract: This specification defines methods for incident reporting among XMPP server deployments. URL: http://www.xmpp.org/extensions/inbox/incident-reporting.html The XMPP Council will decide at its n

Re: [Standards] Unclarified behavior in XEP-0047 (in-band bytestreams)

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/25/09 4:01 PM, Jiří Zárevúcký wrote: > "Upon receiving notice that a data packet is cannot be processed by > the recipient, the sender SHOULD consider the bytestream to be closed > and invalid but MAY attempt to correct the error and re-send the >

Re: [Standards] UPDATED: XEP-0237 (Roster Versioning)

2009-04-27 Thread Jiří Zárevúcký
I've noticed change in this part: > the server MUST consider the item to have been modified and therefore MUST > send the item to the client (typically via a roster push as described below). You changed the MUSTs to MAY, which again introduces several possible problems. You can find reasons in o

[Standards] s2s discussion

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We will hold a special meeting about server-to-server improvements next Tuesday, May 5, at 20:00 UTC in the j...@conference.jabber.org room. If you have ideas about requirements, spec fixes, problems, solutions, etc., please join the meeting next week.

Re: [Standards] XEP-0816 (Invisible Command) mandates ridiculous UI

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/25/09 2:28 PM, Jiří Zárevúcký wrote: > 2009/4/25 Will Thompson : >> Obviously the client should try not to expose the user without them >> doing something that obviously exposes them, so prompting them if they >> wouldn't expect to be exposed is r

Re: [Standards] XEP-0816 (Invisible Command) mandates ridiculous UI

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/25/09 11:42 AM, Jiří Zárevúcký wrote: > 2009/4/25 Paul Aurich : >> I think it's critical to distinguish user-generated traffic from >> client-generated outgoing stanzas. I agree with Will that, for the former, >> this is a really frustrating UI a

[Standards] UPDATED: XEP-0237 (Roster Versioning)

2009-04-27 Thread XMPP Extensions Editor
Version 0.10 of XEP-0237 (Roster Versioning) has been released. Abstract: This specification defines a proposed modification to the XMPP roster protocol that enables versioning of rosters such that the server will not send the roster to the client if the roster has not been modified, thus saving

Re: [Standards] XEP-0237: version == sequence number?

2009-04-27 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/24/09 5:27 AM, Matthew Wild wrote: > On Fri, Apr 24, 2009 at 10:22 AM, Dave Cridland wrote: >> On Thu Apr 23 19:30:29 2009, Matthew Wild wrote: >>> We would need to decide what to do where we currently set ver='0' though. >> We just need to stick