August 2024 - Standards

LAST CALL: XEP-0440 (SASL Channel-Binding Type Capability)

by Daniel Gultsch

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!

2 weeks, 4 days

9
30
0 0

Proposed XMPP Extension: PubSub Server Information

by kevin.smith＠isode.com

The XMPP Extensions Editor has received a proposal for a new XEP. Title: PubSub Server Information Abstract: This document defines a data format whereby basic information of an XMPP domain can be expressed and exposed over pub-sub. URL: https://xmpp.org/extensions/inbox/pubsub-server-info.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

5 months

3
3
0 0

XEP-0077: In-Band Registration - Account creation via XMPP and HTTP

by Melvin Keskin

Hi, At the moment, it is not recommended to provide a web registration URL if the server supports account creation via IBR. I created https://github.com/xsf/xeps/pull/1299 to provide a web registration URL in addition to account creation via IBR. The client or user can decide which one to choose. Please let me know what you think about it. To the Council: 1. What exactly do you mean by *The language is weird*? 2. I tried to describe the use case. Could you please explain your doubts? 3. Why would such a change be problematic for a final XEP? 4. Where should I add that change instead? Thanks in advance :)

1 year, 2 months

3
2
0 0

UPDATED: XEP-0402 (PEP Native Bookmarks)

by Daniel Gultsch

Version 1.2.0 of XEP-0402 (PEP Native Bookmarks) has been released. Abstract: This specification defines a syntax and storage profile for keeping a list of chatroom bookmarks on the server. Changelog: Encourage clients to immediately leave the room if they receive a bookmark notification with autojoin set to false (mye) URL: https://xmpp.org/extensions/xep-0402.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 year, 2 months

7
14
0 0

Bibliography and PubSub

by Schimon Jehudah

Greetings XSF! Thanks to Mr. Timothée Jaussoin (alias "edhelas") who is responsible for "XEP-0472: Pubsub Social Feed" I am interested and investigate about developing and utilizing XMPP PubSub. I am working on a couple of XMPP chat bots to which I will integrate support for PubSub. * Slixfeed (integrated) Slixfeed is a news bot of which PubSub support is almost done. It will use of affiliation='publisher' as defined in XEP-0060 to post news items to PubSub nodes https://git.xmpp-it.net/sch/Slixfeed * BukuBot (not yet integrated) BukuBot is a new chat bot which I contemplate on adding PubSub support in order to make link directories sharable, yet I do not think it would be wise to utilize node `urn:xmpp:links:0` for this purpose. Because of this, I would like to discuss of a new XEP which probably would be similar to XEP-0277 and XEP-0472, yet it would be specifically aimed at bibliography management. Such XEP would be utilized to share Book and Scholar citations, URLs (Gemini, Gopher, HTTP, XMPP), and other type of references over XMPP PubSub. I would be thankful for you to help and share your thoughts on this matter. Kind regards, Schimon

1 year, 2 months

3
12
0 0

XMPP Council Agenda 2024-08-27

by Daniel Gultsch

Good morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, August 27 2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Editors update * UPDATED: XEP-0045 (Multi-User Chat) * UPDATED: XEP-0388 (Extensible SASL Profile) * Proposed XMPP Extension: OAuth Client Login (https://xmpp.org/extensions/inbox/xep-oauth-client-login.html) * Proposed XMPP Extension: Client Access Management (https://xmpp.org/extensions/inbox/xep-client-access-management.html) 4) Items for voting a) Proposed XMPP Extension: OAuth Client Login https://xmpp.org/extensions/inbox/xep-oauth-client-login.html b) Proposed XMPP Extension: Client Access Management https://xmpp.org/extensions/inbox/xep-client-access-management.html c) XEP-0045: Add explicit error definition when non-owners attempt to use owner-specific functionality https://github.com/xsf/xeps/pull/1370 5) Pending votes None See the spreadsheet of Doom: https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa… 6) Date of Next 7) AOB 8) Close

1 year, 2 months

1
0
0 0

XEP-0444: fallback mechanisms?

by Marcin Mielniczuk

Hi, I noticed that, in the current implementations of XEP-0444 are not really backwards-compatible. Non-compliant clients completely miss the emoji reactions and the users are completely unaware that the reaction has been sent. One idea would be to provide the following as a fallback: > Content of the original message 😀 in a similar way to how message replies are currently shown on non-compliant clients. Similarly, when an OMEMO-incompliant client receives an OMEMO- encrypted message, it still receives some placeholder message indicating that the message is OMEMO-encrypted but the client does not support it. Is there any reason why there is currently no fallback mechanism in XEP-0444? Regards, Marcin

1 year, 2 months

2
2
0 0

Proposed XMPP Extension: Jingle Audio/Video Conferences

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Jingle Audio/Video Conferences Abstract: This specification defines a way to hold multiparty conferences with an SFU via Jingle. URL: https://xmpp.org/extensions/inbox/av_conferences.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year, 2 months

5
9
0 0

Proposed XMPP Extension: Client Access Management

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Client Access Management Abstract: This specification details how an XMPP account owner can view and control which applications and services have access to their account. URL: https://xmpp.org/extensions/inbox/xep-client-access- management.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year, 2 months

1
0
0 0

Proposed XMPP Extension: OAuth Client Login

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: OAuth Client Login Abstract: This specification details how a third-party can be securely granted access to an XMPP account without exposing the account credentials, using OAuth. URL: https://xmpp.org/extensions/inbox/xep-oauth-client-login.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year, 2 months

1
0
0 0

2025

2024

2023

Standards August 2024