The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Group Chat Reporting
Abstract:
This specification describes how a client can report abuse and spam in
a MUC or other group chat context.
URL: https://xmpp.org/extensions/inbox/xep-gc-reporting.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
Good Morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, April 7
2026 at 15:30 UTC in xmpp:council@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* Proposed XMPP Extension: Message Archive Management: Trim Command
* Proposed XMPP Extension: Group Chat Reporting
* Proposed XMPP Extension: Occupant Mute Synchronization
* UPDATED: XEP-0384 (OMEMO Encryption)
* UPDATED: XEP-0413 (Order-By)
* UPDATED: XEP-0509 (Initial Authentication Pipelining)
4) Items for voting
a) Proposed XMPP Extension: Message Archive Management: Trim Command
https://xmpp.org/extensions/inbox/xep-mam-trimming.html
b) Proposed XMPP Extension: Group Chat Reporting
https://xmpp.org/extensions/inbox/xep-gc-reporting.html
c) Proposed XMPP Extension: Occupant Mute Synchronization
https://xmpp.org/extensions/inbox/xep-occupant-mute-sync.html
5) Pending votes
Daniel on XEP-0045: Add clarification regarding unsetting reserved nicknames
See the spreadsheet of doom:
https://docs.google.com/spreadsheets/d/14gy_nhuTnqlktakJfLZ2Mc-jblSaG0na0Kh…
6) Date of Next
7) AOB
8) Close
Version 0.2.0 of XEP-0509 (Initial Authentication Pipelining) has been
released.
Abstract:
This specification defines a protocol for discovering if the SASL2
<authenticate> can be pipelined safely along with the stream open, and
if so allows the client to perform this pipelining safely.
Changelog:
Updates based on implementation (dwd)
URL: https://xmpp.org/extensions/xep-0509.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.2.1 of XEP-0413 (Order-By) has been released.
Abstract:
This specification allows to change order of items retrieval in a
Pubsub or MAM query
Changelog:
Replace old namespace use in examples. (jp)
URL: https://xmpp.org/extensions/xep-0413.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.9.1 of XEP-0384 (OMEMO Encryption) has been released.
Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.
Changelog:
Fix using id=0 in examples. Spec requires positive numbers. (XEP
Editor: dg)
URL: https://xmpp.org/extensions/xep-0384.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.
Dear Council Members,
For years now we have two competing standards https://xmpp.org/extensions/xep-0447.html and https://xmpp.org/extensions/xep-0385.html and it leads to confusion and additional work for new implementers and prevents in some cases implementations at all.
According to the xmpp.org page both XEPs have each 6 implementations.
I would suggest to issue a last call to gather feedback.
After all feedback is addressed council should advances only one.
Regards
Philipp
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Explicit Mentions
Abstract:
This specification defines a way to explicitly mention a person or
groups of people.
URL: https://xmpp.org/extensions/inbox/explicit-mentions.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
Hi all,
At the recent Summit, we had a long and nuanced discussion about the state
of the XMPP RFCs and whether there is value in updating parts of them,
potentially through the IETF, to better reflect how XMPP is actually
implemented and used today.
To be clear upfront: This is not a proposal to start an IETF working group,
nor a commitment to produce new RFCs. The discussion at the Summit surfaced
enough open questions that it seems worthwhile to first have a focused
scoping and feasibility discussion.
Some of the motivations that were raised:
- The current RFCs do not describe a baseline that results in
interoperable modern implementations
- Discoverability for new implementers is difficult (knowing which XEPs
are "essential")
- The IM landscape has changed significantly since the original RFCs
- External review and feedback could be valuable
- There may be marketing and positioning benefits, but these are
secondary
At the same time, many concerns were raised:
- The sheer amount of work required, and whether we realistically have
the manpower
- Risk of scope creep (e.g., baking too much into RFCs)
- Loss of flexibility compared to the XEP process
- Fear of starting something we cannot finish
- Unclear interaction with compliance suites and the "living standard"
nature of XMPP
- Potential pushback or distraction from other IETF efforts (e.g., MIMI)
Questions that seem worth discussing at this stage:
- Is it useful to think about updating some RFCs (e.g., core, IM), while
leaving the rest to XEPs?
- What would be clearly in-scope vs out-of-scope?
- Is there enough interest and capacity to justify exploring this
further?
- What would be a sensible first step that does not overcommit us?
If you were at the Summit and felt strongly one way or the other, it would
be great to hear your perspective here. If you weren't, fresh viewpoints
are equally welcome.
The goal of this thread is simply to assess whether this topic is worth
pursuing further, and if so, in what very limited and realistic form.
Kind regards,
Guus
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Message Archive Management: Trim Command
Abstract:
This specification describes how a client can request "trimming" of an
archive
URL: https://xmpp.org/extensions/inbox/xep-mam-trimming.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
Version 0.1.0 of XEP-0513 (Explicit Mentions) has been released.
Abstract:
This specification defines a way to explicitly mention a person or
groups of people.
Changelog:
Accepted as Experimental by council vote on 2026-03-31 (dg)
URL: https://xmpp.org/extensions/xep-0513.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.