What ever you do please don’t rename the and
elements. Proceed should continue to be the 'main' element that tells
the initiator to proceed with the jingle handshake. Anything else will
just be a nightmare to talk about because you would always have to
specific if you are talking about version
Am Mittwoch, 25. Januar 2023, 17:12:06 CET schrieb Daniel Gultsch:
> I'd get rid of instead of
>
> Only put into the stanza. Don’t send at all.
>
> Stops you from having to put two elements in the message.
>
> What in the :0 version was will just quietly go away. (In
> favor of wording
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: XMPP Compliance Suites 2023
Abstract:
This document defines XMPP application categories for different use
cases (Core, Web, IM, and Mobile), and specifies the required XEPs
that client and server software needs to implement
Version 0.2.0 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:
* Add description of attack model
* Add section defining IETF interaction
Version 0.2.0 of XEP-0461 (Message Replies) has been released.
Abstract:
This document defines a way to indicate that a message is a reply to a
previous message.
Changelog:
Fix example character counting. Add disco feature. Relax the 'to'
attribute constraints. (nc)
URL:
Version 0.1.1 of XEP-0444 (Message Reactions) has been released.
Abstract:
This specification defines a way for adding reactions to a message.
Changelog:
Add the XML Schema (egp)
URL: https://xmpp.org/extensions/xep-0444.html
Note: The information in the XEP list at
Version 0.3.0 of XEP-0426 (Character counting in message bodies) has
been released.
Abstract:
This document describes how to correctly count characters in message
bodies. This is required when referencing a position in the body.
Changelog:
Added section about subsequences. (lmw)
URL:
Version 0.5.0 of XEP-0353 (Jingle Message Initiation) has been
released.
Abstract:
This specification provides a way for the initiator of a Jingle
session to propose sending an invitation in an XMPP message stanza,
thus taking advantage of message delivery semantics instead of sending
IQ stanzas
I'd get rid of instead of
Only put into the stanza. Don’t send at all.
Stops you from having to put two elements in the message.
What in the :0 version was will just quietly go away. (In
favor of wording around proceed being carbon copied)
On Wed, Jan 25, 2023 at 3:49 AM Thilo Molitor
Hi folks,
I'd like to request that the council reconsiders its previous
decision[1] not to advance XEP-0334.
Rationale: It has many implementations, and other further-advanced
XEPs already make use of it - e.g. XEP-0280, XEP-0353, XEP-0424 (this
may be an incomplete list). From this I believe
10 matches
Mail list logo
