[Standards] UPDATED: XEP-0357 (Push Notifications)

Version 0.3 of XEP-0357 (Push Notifications) has been released. Abstract: This specification defines a way for an XMPP servers to deliver information for use in push notifications to mobile and other devices. Changelog: (see in-document revision history) URL:

[Standards] UPDATED: XEP-0060 (Publish-Subscribe)

Version 1.13.7 of XEP-0060 (Publish-Subscribe) has been released. Abstract: This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an

Re: [Standards] Proposed XMPP Extension: Atomically Compare-And-Publish PubSub Items

I'm not seeing what the compare part of this proposal actually is. Unless I misunderstand, it simply publishes the item only if it will update an existing one. If that is the case, I would propose a small change to the existing spec to add an attribute to the element that enables this

[Standards] TOTP and enforced password changes in SASL2

Folks, Now that an update to XEP-0388 has been published, I thought I'd share what I've been trying to do with it. I'll be tidying up some actual code this morning and making a PR into Openfire, but the general idea is to use the tasks that can be required by a in SASL2 in order to provide two

[Standards] Proposed XMPP Extension: Jingle Encrypted Transports

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Jingle Encrypted Transports Abstract: This specification defines a method that allows to use established encryption schemes like OpenPGP or OMEMO for end-to-end encryption of Jingle transports. URL:

[Standards] UPDATED: XEP-0234 (Jingle File Transfer)

Version 0.18.3 of XEP-0234 (Jingle File Transfer) has been released. Abstract: This specification defines a Jingle application type for transferring a file from one entity to another. The protocol provides a modular framework that enables the exchange of information about the file to be

[Standards] UPDATED: XEP-0133 (Service Administration)

Version 1.2 of XEP-0133 (Service Administration) has been released. Abstract: This document defines recommended best practices for service-level administration of servers and components using Ad-Hoc Commands. Changelog: Fix broken node value in example. (XEP Editor: ssw) URL:

[Standards] UPDATED: XEP-0300 (Use of Cryptographic Hash Functions in XMPP)

Version 0.5.2 of XEP-0300 (Use of Cryptographic Hash Functions in XMPP) has been released. Abstract: This document provides recommendations for the use of cryptographic hash functions in XMPP protocol extensions. Changelog: Add hash-used element (ps) URL:

Re: [Standards] TOTP and enforced password changes in SASL2

On Donnerstag, 24. August 2017 12:59:56 CEST Dave Cridland wrote: > Now that an update to XEP-0388 has been published, I thought I'd > share what I've been trying to do with it. > > […] > All of this sounds in general sensible. I was first a bit confused as to why you didn’t use the term

[Standards] UPDATED: XEP-0045 (Multi-User Chat)

Version 1.28 of XEP-0045 (Multi-User Chat) has been released. Abstract: This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to

[Standards] UPDATED: XEP-0234 (Jingle File Transfer)

Version 0.18.2 of XEP-0234 (Jingle File Transfer) has been released. Abstract: This specification defines a Jingle application type for transferring a file from one entity to another. The protocol provides a modular framework that enables the exchange of information about the file to be

[Standards] UPDATED: XEP-0369 (Mediated Information eXchange (MIX))

Version 0.9.3 of XEP-0369 (Mediated Information eXchange (MIX)) has been released. Abstract: This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple users through a mediating service. The protocol can be used to provide

[Standards] UPDATED: XEP-0388 (Extensible SASL Profile)

Version 0.2.0 of XEP-0388 (Extensible SASL Profile) has been released. Abstract: This document describes a replacement for the SASL profile documented in RFC 6120 which allows for greater extensibility. Changelog: (see in-document revision history) URL: https://xmpp.org/extensions/xep-0388.html

[Standards] UPDATED: XEP-0060 (Publish-Subscribe)

Version 1.13.6 of XEP-0060 (Publish-Subscribe) has been released. Abstract: This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an

[Standards] UPDATED: XEP-0390 (Entity Capabilities 2.0)

Version 0.2 of XEP-0390 (Entity Capabilities 2.0) has been released. Abstract: This document overhauls the XMPP protocol extension Entity Capabilities (XEP-0115). It defines an XMPP protocol extension for broadcasting and dynamically discovering client, device, or generic entity capabilities. In

[Standards] Proposed XMPP Extension: Atomically Compare-And-Publish PubSub Items

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Atomically Compare-And-Publish PubSub Items Abstract: This specification provides a mechanism to atomically Compare-And- Publish items to a PubSub node. URL: https://xmpp.org/extensions/inbox/cap.html The Council will

Re: [Standards] TOTP and enforced password changes in SASL2

On 24 Aug 2017, at 16:56, Dave Cridland wrote: > Moreover, SASL2 is designed to handle a lot more than just TOTP etc - > we can merge in resource binding without any additional round-trips, > for example, if I can ever persuade Kev to see things my way. So it's > more

Re: [Standards] TOTP and enforced password changes in SASL2

On 24 August 2017 at 17:02, Kevin Smith wrote: > On 24 Aug 2017, at 16:56, Dave Cridland wrote: >> Moreover, SASL2 is designed to handle a lot more than just TOTP etc - >> we can merge in resource binding without any additional round-trips, >> for