On 1/24/2012 8:41 PM, Evgeniy Khramtsov wrote:
On 25.01.2012 09:30, Mike Wacker wrote:
I saw this in RFC 6120:
To reduce the possibility of a denial-of-service attack, (a) the
receiving entity SHOULD NOT close the stream with a see-other-host/
stream error until after the confidentiality and
On Wed Jan 25 04:41:29 2012, Evgeniy Khramtsov wrote:
On 25.01.2012 09:30, Mike Wacker wrote:
I saw this in RFC 6120:
To reduce the possibility of a denial-of-service attack, (a) the
receiving entity SHOULD NOT close the stream with a
see-other-host/ stream error until after the
On 2012-01-24 01:03, XMPP Extensions Editor wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: The 'xmpp.pubsub' URI Scheme
Abstract: This document defines the format of Uniform Resource Identifiers
(URIs) to identify nodes in the context of Publish-Subscribe
Version 2.4 of XEP-0077 (In-Band Registration) has been released.
Abstract: This specification defines an XMPP protocol extension for in-band
registration with XMPP-based instant messaging servers and other services
hosted on an XMPP network (such as groupchat rooms and gateways to non-XMPP IM
Version 1.6 of XEP-0114 (Jabber Component Protocol) has been released.
Abstract: This specification documents the existing protocol used for
communication between servers and external components over the Jabber network.
Changelog: [See revision history] (psa)
Diff:
Version 1.6 of XEP-0114 (Jabber Component Protocol) has been released.
Abstract: This specification documents the existing protocol used for
communication between servers and external components over the Jabber network.
Changelog: [See revision history] (psa)
Diff:
On Wed, Jan 25, 2012 at 2:26 AM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 1/24/12 11:14 AM, Peter Saint-Andre wrote:
After jabbering with Kev for a bit, here's a follow-up on the status
code 210 issue (originally raised by Waqas Hussain).
If the user's nickname is modified by the
On 1/25/12 4:04 PM, Peter Saint-Andre wrote:
It may make sense to extend 210 to (2)
and (3).
That's the path I took based on your feedback (however, I notice that I
didn't add anything about status code 210 to the section on
user-requested nick changes, which is another time when the
