- Standards

Moving XEP-0066 to Final (emitting Last Call?)
by Goffi 08 Jul '26

08 Jul '26

Hello, The Council talked about moving a couple of stable XEPs which have not been modified for years to "Final". As this process has not been done for a long time, we want to first try with XEP-0066 (Out of Band Data). Peter, would you be fine with moving this specification to "Final"? Please not that dwd suggested to get rid of section 6 first (XEP-0095 being deprecated). If Peter is fine with getting rid of the section and moving forward, we can emit a last call. Thanks. Goffi

3 3

LAST CALL: XEP-0424 (Message Retraction)
by Daniel Gultsch 03 Jul '26

03 Jul '26

This message constitutes notice of a Last Call for comments on XEP-0424. Title: Message Retraction Abstract: This specification defines a method for indicating that a message should be retracted. URL: https://xmpp.org/extensions/xep-0424.html This Last Call begins today and shall end at the close of business on 2025-01-06. 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!

9 27

NEW: XEP-0516 (XMPP Decentralized ID (XID))
by Daniel Gultsch 01 Jul '26

01 Jul '26

Version 0.1.0 of XEP-0516 (XMPP Decentralized ID (XID)) has been released. Abstract: XMPP Decentralized ID (XID) is a DNS independent XMPP entity identifier. This specification describes how to generate, use, and handle them. Changelog: Accepted as Experimental by council vote (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0516.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.

3 2

Update to Jingle User Location ProtoXEP: call-scoped XEP-0080 binding
by Edward Tie 01 Jul '26

01 Jul '26

Hello, I have updated the Jingle User Location ProtoXEP with clearer wording after the Council discussion. The updated draft is here: https://github.com/xsf/xeps/pull/1550 The main clarification is that this proposal does not replace XEP-0080. XEP-0080 remains the location payload. The problem this proposal tries to solve is the call/session binding: XEP-0080 tells where the user is, but it does not reliably tell for which active Jingle call that location was shared. PEP/PubSub is useful for general user-location publication, but for an active call it does not clearly answer: - which Jingle session / sid the location belongs to; - whether the location was explicitly shared for this call; - whether it is fresh, stale, one-time, or live; - when call-scoped location sharing stops; - whether a relay, accessibility assistant or future emergency gateway may treat it as the location for the active call. The revised direction is therefore narrower: A small Jingle binding for XEP-0080 during an active call. It reuses the existing XEP-0080 geoloc payload and adds Jingle session context, stop-sharing/expiry wording, fallback wording and privacy wording. It also explicitly avoids claiming to be an emergency-service protocol by itself. The reason I think this matters is accessibility and 112/911-readiness. A deaf or speech-impaired user may be in a Total Conversation call with audio, video, RTT, captions, relay/interpreter services or a future emergency gateway. In that situation the peer or gateway should not have to guess whether the latest XEP-0080/PEP item belongs to the current call. Feedback is welcome, especially on whether this narrower “Jingle binding for XEP-0080” direction is the right shape. Kind regards, Edward

1 0

Jingle user location
by Edward Tie 30 Jun '26

30 Jun '26

|Thank you for the feedback. Could you please clarify the main objection to the Jingle User Location proposal? I would like to understand what should be changed before revising it. Is the objection about the use of Jingle, the relation to XEP-0080, privacy/consent, emergency-use wording, scope, or something else? I do not want to assume the reason. If you can point to the specific part that is problematic, I can make the next revision more focused.| greetings, Edward Tie .

1 0

NEW: XEP-0517 (Jingle Synchronized Real-Time Text)
by Daniel Gultsch 30 Jun '26

30 Jun '26

Version 0.1.0 of XEP-0517 (Jingle Synchronized Real-Time Text) has been released. Abstract: This specification defines a Jingle application extension for negotiating real-time text as part of the same conversational session as audio and video. Changelog: Accepted as Experimental by council vote (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0517.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.

1 0

XMPP Council Agenda 2026-06-30
by Daniel Gultsch 30 Jun '26

30 Jun '26

Good Morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, June 30 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 • UPDATED: XEP-0420 (Stanza Content Encryption • UPDATED: XEP-0514 (Emoji Markup) • NEW: XEP-0515 (TLS Channel-Binding Downgrade Protection) 4) Items for voting a) Proposed XMPP Extension: Payment Required https://xmpp.org/extensions/inbox/payment-required.html 5) Pending votes none See the spreadsheet of doom: https://docs.google.com/spreadsheets/d/14gy_nhuTnqlktakJfLZ2Mc-jblSaG0na0Kh… 6) Date of Next 7) AOB 8) Close

1 0

NEW: XEP-0515 (TLS Channel-Binding Downgrade Protection)
by Daniel Gultsch 30 Jun '26

30 Jun '26

Version 0.1.0 of XEP-0515 (TLS Channel-Binding Downgrade Protection) has been released. Abstract: This specification provides a way to secure the SASL and SASL2 SCRAM handshakes against channel-binding downgrades through TLS version downgrades. Changelog: Accepted as Experimental by council vote (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0515.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.

1 0

UPDATED: XEP-0514 (Emoji Markup)
by Daniel Gultsch 30 Jun '26

30 Jun '26

Version 0.1.1 of XEP-0514 (Emoji Markup) has been released. Abstract: This specification leverages Message Markup (XEP-0394) and Stateless file sharing (XEP-0447) (or Stateless Inline Media Sharing (XEP-0385)) to send custom emojis Changelog: Remove outdated reference to BoB (techmetx11) URL: https://xmpp.org/extensions/xep-0514.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.

1 0

UPDATED: XEP-0420 (Stanza Content Encryption)
by Daniel Gultsch 30 Jun '26

30 Jun '26

Version 0.5.0 of XEP-0420 (Stanza Content Encryption) has been released. Abstract: The Stanza Content Encryption (SCE) protocol is intended as a way to allow clients to securely exchange arbitrary extension elements using different end-to-end encryption schemes. Changelog: The time affix uses the DateTime profile of XEP-0082 Longer rpads MUST NOT be rejected Add a minimum size target for random padding to add resistance against potential correlation attacks in case of short content and 0-length rpad Removed unhelpful Implementation Note warning about injection of decrypted stanzas Clarify fallback body policy Fix descriptions to apply to all stanzas instead of just messages Remove questionable SHOULD in the time affix handling and clarify the affix'es verification Request the registrar to provide a list of exclusively server- processed elements List XEP dependencies Add XML schema (syndace) URL: https://xmpp.org/extensions/xep-0420.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.

1 0