The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Happy Eyeballs
Abstract:
When a server's IPv4 path and protocol are working, but the server's
IPv6 path and protocol are not working, a dual-stack application that
initiates a connect experiences significant connection delay compared
to an IPv4-only application. This is undesirable because it causes the
dual-stack initiating entity to have a worse user experience. This XEP
defines how IETF's 'Happy Eyeballs' algorithm requirements that reduce
this user-visible delay are applied to XMPP.
URL: https://xmpp.org/extensions/inbox/xep-happy-eyeballs.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
Good evening!
I would want to ask for friends to collaborate with me in writing an
XEP, or adding to a current XEP, a feature which would allow to attach
images to pubsub nodes.
By that, I mean, to attach an image per node.
This is useful for publishing systems, such as Movim.
Kind regards,
Schimon
Hi,
"XEP-0484: Fast Authentication Streamlining Tokens" is written without any
considerations for multiple devices.
With stuff like that "*For every client using FAST, have two token slots -
'current' and 'new'." *in it.
I am kinda confused how the XEP could be considered in 2024. The moment we
have two devices for the same user, the devices would start conflicting
with each other, by revoking tokens of each other.
The XEP should use namespaces (or be resource aware) for it to properly
work.
--
Best regards,
Uvarov Michael
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, September
24 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-0004 (Data Forms)
* UPDATED: XEP-0264 (Jingle Content Thumbnails)
* UPDATED: XEP-0313 (Message Archive Management)
* Proposed XMPP Extension: Happy Eyeballs
4) Items for voting
a) Proposed XMPP Extension: Happy Eyeballs
https://xmpp.org/extensions/inbox/xep-happy-eyeballs.html
b) XEP-0198: Clarify server enabling SM without requested resumption
https://github.com/xsf/xeps/pull/1376 (modified)
5) Pending votes
None
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
7) AOB
8) Close
Version 1.1.2 of XEP-0313 (Message Archive Management) has been
released.
Abstract:
This document defines a protocol to query and control an archive of
messages stored on a server.
Changelog:
* Fix JID and affiliation of the first two witches in the MUC example.
* Fix duplicated 'id' in MUC example.
* Fix indentation in examples. (egp)
URL: https://xmpp.org/extensions/xep-0313.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.2 of XEP-0264 (Jingle Content Thumbnails) has been
released.
Abstract:
This specification defines a way for a client to supply a preview
image for Jingle content.
Changelog:
Restrict 'width' and 'height' to the 0..65535 range, instead of being
unbounded integers. This is in accordance to XEP-0084 and XEP-0221
for instance. (egp)
URL: https://xmpp.org/extensions/xep-0264.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 2.13.2 of XEP-0004 (Data Forms) has been released.
Abstract:
This specification defines an XMPP protocol extension for data forms
that can be used in workflows such as service configuration as well as
for application-specific data description and reporting. The protocol
includes lightweight semantics for forms processing (such as request,
response, submit, and cancel), defines several common field types
(boolean, list options with single or multiple choice, text with
single line or multiple lines, single or multiple JabberIDs, hidden
fields, etc.), provides extensibility for future data types, and can
be embedded in a wide range of applications. The protocol is not
intended to provide complete forms-processing functionality as is
provided in the W3C XForms technology, but instead provides a basic
subset of such functionality for use by XMPP entities.
Changelog:
Add section on empty and absent values. (gk)
URL: https://xmpp.org/extensions/xep-0004.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.
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, September
17 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-0133 (Service Administration)
* UPDATED: XEP-0474 (SASL SCRAM Downgrade Protection)
* UPDATED: XEP-0045 (Multi-User Chat)
* UPDATED: XEP-0272 (Multiparty Jingle (Muji))
* NEW: XEP-0493 (OAuth Client Login)
* NEW: XEP-0494 (Client Access Management)
4) Items for voting
a) XEP-0004: Empty and absent values
https://github.com/xsf/xeps/pull/1387
b) XEP-0264: Restrict 'width' and 'height' to the 0..65535 range
https://github.com/xsf/xeps/pull/1366
c) XEP-0198: Clarify server enabling SM without requested resumption
https://github.com/xsf/xeps/pull/1376
d) XEP-0313: Fix MUC archive example
https://github.com/xsf/xeps/pull/1321
5) Pending votes
None
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
7) AOB
8) Close
