September 2024 - Standards

NEW: XEP-0494 (Client Access Management)

by Daniel Gultsch

Version 0.1.0 of XEP-0494 (Client Access Management) has been released. Abstract: This specification details how an XMPP account owner can view and control which applications and services have access to their account. Changelog: * Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0494.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.

2 months

1
0
0 0

NEW: XEP-0493 (OAuth Client Login)

by Daniel Gultsch

Version 0.1.0 of XEP-0493 (OAuth Client Login) has been released. Abstract: This specification details how a third-party can be securely granted access to an XMPP account without exposing the account credentials, using OAuth. Changelog: * Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0493.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.

2 months

1
0
0 0

UPDATED: XEP-0474 (SASL SCRAM Downgrade Protection)

by Daniel Gultsch

Version 0.3.1 of XEP-0474 (SASL SCRAM Downgrade Protection) has been released. Abstract: This specification provides a way to secure the SASL and SASL2 handshakes against method and channel-binding downgrades. Changelog: * Fix typos * Adapt attack-model section to new simplified protocol (tm) URL: https://xmpp.org/extensions/xep-0474.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.

2 months

1
0
0 0

UPDATED: XEP-0133 (Service Administration)

by Daniel Gultsch

Version 1.3.1 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: Fixed typo in example for Get User Last Login Time (dc) URL: https://xmpp.org/extensions/xep-0133.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.

2 months

1
0
0 0

XSF membership application period Q4 2024

by Alexander Gnauck

I have setup the membership application Wiki page for the application period Q4 2024 Applications are encouraged from developers and others who are actively involved in the Jabber/XMPP community. To apply, create a page about yourself on the Wiki at: https://wiki.xmpp.org/web/Membership_Applications_Q4_2024 If you don't have a wiki account, send your full name, preferred nickname and email address to me or one of the other Sysops: https://wiki.xmpp.org/web/Sysops Apply now!!! Thanks, Alex

2 months, 1 week

1
0
0 0

Atom Over XMPP (XEP-0277 and XEP-0472) classifying comments and reactions

by Schimon Jehudah

Good day! I am working on Rivista[1], which is a journal publisher for XMPP. I test instances of Libervia and Movim against Rivista. Most of the tests are conducted against the official instance of Movim. The matter of this message is concerning to Adding a Comment[2] (clause 3.2 to XEP-0277). I have noticed that "reactions" are manifested exactly the same as comments, inside element title. The couple of indications that a comment is a reaction are: 1) Element title has a single character; or 2) The character or character combination is included in the range of characters that are dedicated for reactions. I would suggest to use a classifier. 1) Use element title as a classifier of post type, either a comment or a reaction, and use element summary as a handler for the comment itself; or 2) Use element category (e.g. xmpp:comment and xmpp:reaction); or 3) Utilize "Extension Elements" (clause 6.4 to RFC 4287). I think that solution #3 would be the ideal solution. Current ------- <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <published>2008-05-08T18:39:02Z</published> </entry> Title as an indicator --------------------- <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>comment</title> <summary type='text'>She is so pretty!</summary> <published>2008-05-08T18:39:02Z</published> </entry> Category as an indicator ------------------------ <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <category term='xmpp:comment'/> <published>2008-05-08T18:39:02Z</published> </entry> A dedicated extension --------------------- <feed xmlns="http://www.w3.org/2005/Atom" xmlns:reactions="http://xmpp.org/2024/reactions"> For comments:  <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <reactions:reaction type="💡️"/> <reactions:reaction type="👍️"/> <published>2008-05-08T18:39:02Z</published> </entry> For posts:  <reactions:reaction type="✒️" count="10"/> <reactions:reaction type="💡️" count="2"/> <reactions:reaction type="👍️" count="5"/> Kind regards, Schimon [1]: https://git.xmpp-it.net/sch/Rivista [2]: https://xmpp.org/extensions/xep-0277.html#comment_add

2 months, 1 week

1
2
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 :)

2 months, 2 weeks

3
2
0 0

2024

2023

Standards September 2024

2024

2023

Standards September 2024 ----- 2024 ----- November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 ----- 2023 ----- December 2023

Standards September 2024