This message constitutes notice of a Last Call for comments on
XEP-0440.
Title: SASL Channel-Binding Type Capability
Abstract:
This specification allows servers to annouce their supported SASL
channel-binding types to clients.
URL: https://xmpp.org/extensions/xep-0440.html
This Last Call begins today and shall end at the close of business on
2024-05-20.
Please consider the following questions during this Last Call and send
your feedback to the standards(a)xmpp.org discussion list:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
2. Does the specification solve the problem stated in the introduction
and requirements?
3. Do you plan to implement this specification in your code? If not,
why not?
4. Do you have any security concerns related to this specification?
5. Is the specification accurate and clearly written?
Your feedback is appreciated!
[CC'ing standards@, as I'd like to engage the community regarding our
usage of Github]
On 07/08/2025 18.50, E.M. wrote:
> Dear all,
>
> hereby I will post on today's Board Meeting. Ref: https://wiki.xmpp.org/
> web/Board-Meeting-2025
>
> We have a two items to vote for, too. Please clearly indicate how (+1,
> 0, -1) and on what you are voting (topic).
>
> Furthermore, we are proposing to have another Board meeting in one week at
> Thursday, 14 Aug 2025
> Time: 16:00 UTC / 18:00 CEST
> (Can anyone update the calendar if we agree here?)
>
> Please comment if there are any other topics or input on the items.
>
> Cheers,
> Eddie
> _______________________________________________________________________
>
> * XEP-0001 and 0143 changes need approval from Board
> ** Call to provide you input to the changes and place a comment or review.
> Link 1: https://github.com/xsf/xeps/pull/1412
This contains some good changes, like the advise to read, understand,
and agree to our IPR. However, I find the the strong emphasis on Github
PRs very problematic. Especially the part where we tell people that if
they don't have a github account and are not willing to sign up for one,
they should find someone who has one.
The XSF should not require the usage of a propriety service for
contributions.
On the other side, I do acknowledge that using a CI-based system for
contributions has its advantage. Therefore, a change which mentions that
we also accept contributions via Github, outlining the existence of a CI
there, would be acceptable to me.
But it is my strong believe that we should always accept contributions
via mail.
Therefore -1, as is.
On a side note: We may also want to point out that it is possible to
validate changes locally. And we probably should look into codeforge
alternatives. But that is outside of the scope of this PR.
> Link 2: https://github.com/xsf/xeps/pull/1407
+1, thanks for writing this.
> Link 3: ?
Do we have this link by now?
> * Update on Fiscal Hosting
> ** Background: The platform we have been using for fiscal hosting is to
> begin moving to a new pricing structure in January, and this affects us.
> Details: https://pricing-2026.opencollective.com/
> *** Votes: The XSF Board votes to close the fiscal hosting offering via
> Open Collective without replacement and asks the community to suggest
> alternatives instead of publishing a survey.
+1, as per Matt's analysis, opencollective seems to be to expensive for us.
> * Confusion in protocol name (XMTP)
> ** Background: See Board mailing list
> ** Comment: We don't see that we can do much about it, as XMPP is not a
> trademark and they are already aware.
I think there is not much we can do after the fact.
> * Propose Gonzalo Nemmi (gnemmi) to become member of the XSF CommTeam
> ** Background: Gonzalo is publishing and providing great efforts along
> the team and work well with the XSF and Community. This deserves
> recognition.
> ** Votes: The XSF Board votes that if Gonzalo Nemmi (gnemmi) will be
> accepted as XSF member,
I don't think Board is the right body to approve new members.
> that Gonzalo Nemmi (gnemmi) can join the XSF
> CommTeam.
+1, assuming they fulfill the prerequisites (e.g., being an XSF member).
> ** Comment: Jcbrand will be unlisted after not responding but is always
> welcome to support and comeback.
Thanks for your work JC!
- Flow
Good day.
I realize that PEP is a form of PubSub for accounts.
I do want to know whether it is feasible for an account to create a PEP
node which other accounts can post items to it.
Please advise.
Kind regards,
Schimon
Version 1.2.3 of XEP-0167 (Jingle RTP Sessions) has been released.
Abstract:
This specification defines a Jingle application type for negotiating
one or more sessions that use the Real-time Transport Protocol (RTP)
to exchange media such as voice or video. The application type
includes a straightforward mapping to Session Description Protocol
(SDP) for interworking with SIP media endpoints.
Changelog:
Make 'ssrc' attribute 'xs:unsignedInt' (32-bit) instead of 'xs:string'
to match RFC3550. (lnj)
URL: https://xmpp.org/extensions/xep-0167.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 0.4.0 of XEP-0455 (Service Outage Status) has been released.
Abstract:
This document defines an XMPP protocol extension that enables server
administrators to communicate issues with the server to all users in a
semantic manner.
Changelog:
Remove leftover pubsub references, add accessibility considerations.
(mp)
URL: https://xmpp.org/extensions/xep-0455.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 1.0.4 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:
Schema should use all instead of sequence (dg)
URL: https://xmpp.org/extensions/xep-0388.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 0.3.0 of XEP-0317 (Hats) has been released.
Abstract:
This specification defines a more extensible model for roles and
affiliations in Multi-User Chat rooms.
Changelog:
Add hat creation and detruction flows; add hue optional parameter; add
chatroom presence hats broadcast; complete disco#info; clarify how the
service should broadcast updated hats; typos; standardize the form
fields; (tj)
URL: https://xmpp.org/extensions/xep-0317.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 1.6.3 of XEP-0198 (Stream Management) has been released.
Abstract:
This specification defines an XMPP protocol extension for active
management of an XML stream between two XMPP entities, including
features for stanza acknowledgements and stream resumption.
Changelog:
Remove leftover <optional/> and <required/> children in <sm/> element.
(egp)
URL: https://xmpp.org/extensions/xep-0198.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Hello Schimon (etl al)
> I am working on a news service for XMPP, which sends messages according
> to status.
>
> When JID is offline, service should stop.
Sounds like you would benefit from using PEP (XEP-0163) which accomplishes this. The publisher publishes a PEP event with its new service namespace, and only online entities with a presence subscription, and a corresponding service-detectable feature requesting PEP events with the corresponding news namespace, will receive the event. In this case, there's no need for the service to manually check subscribers and their current online presence.
Best regards,
Peter Waher
