From 734d327ab0740a9c8ed826b62f9fec13f252e8b7 Mon Sep 17 00:00:00 2001 From: Linus Jahn Date: Sun, 28 Apr 2019 17:46:48 +0200 Subject: [PATCH 1/8] XEP-0380: Add OMEMO encryption method --- xep-0380.xml | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/xep-0380.xml b/xep-0380.xml index c5a811e4..e6ca897f 100644 --- a/xep-0380.xml +++ b/xep-0380.xml @@ -11,7 +11,7 @@ recipient can discover how to decrypt it. &LEGALNOTICE; 0380 - Deferred + Experimental Standards Track Standards Council @@ -24,6 +24,15 @@ EME &linkmauve; + + 0.3.0 + 2019-04-28 + lnj + +

Added OMEMO encryption namespace.

+

Made XEP experimental again.

+ + 0.2.0 2018-01-25 @@ -168,11 +177,11 @@ urn:xmpp:openpgp:0 &xep0373; - + eu.siacs.conversations.axolotl + &xep0384; + From fd92e3612760956ca35be5e07cb3d3a3f0ff9150 Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Thu, 2 Aug 2018 19:20:54 +0200 Subject: [PATCH 2/8] XEP-0184: Require the 'id' attribute in . There was no way to implement this specification while not using the 'id' attribute, this makes it explicit in both the text and the schema. --- xep-0184.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xep-0184.xml b/xep-0184.xml index c7ceb52c..dcd136cb 100644 --- a/xep-0184.xml +++ b/xep-0184.xml @@ -27,6 +27,12 @@ &stpeter; &hildjj; + + 1.4.0 + 2018-08-02 + egp +

Make the 'id' attribute required, this extension makes no sense otherwise.

 + 1.3.0 2019-05-15 @@ -209,7 +215,7 @@ ]]> -

When the recipient sends an ack message, it SHOULD ensure that the message stanza contains only one child element, namely the <received/> element qualified by the 'urn:xmpp:receipts' namespace. In addition, it SHOULD include an 'id' attribute that echoes the 'id' attribute of the content message. Naturally, intermediate entities might add other extension elements to the message when routing or delivering the receipt message, e.g., a <delay/> element as specified in &xep0203;.

+

When the recipient sends an ack message, it SHOULD ensure that the message stanza contains only one child element, namely the <received/> element qualified by the 'urn:xmpp:receipts' namespace, which MUST include an 'id' attribute that echoes the 'id' attribute of the content message. Naturally, intermediate entities might add other extension elements to the message when routing or delivering the receipt message, e.g., a <delay/> element as specified in &xep0203;.

Note: It is a good practice to use the same message type as the message that requested the receipt, however a client SHOULD also accept receipts with a different message type. When sending a Receipt for a type='groupchat' message (which is NOT RECOMMENDED), the Receipt must be sent to the bare JID of the room and not to the full JID of the sender.

@@ -248,7 +254,7 @@ - + From d36a6cadd759201c854f61795489107f69d567db Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Wed, 26 Jun 2019 16:49:35 +0200 Subject: [PATCH 3/8] xep-0371: fix gathering-complete text Fixes the text to use the correct element name which is used in the sample and the schema --- xep-0371.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0371.xml b/xep-0371.xml index c0ed18dc..a2d725ff 100644 --- a/xep-0371.xml +++ b/xep-0371.xml @@ -715,7 +715,7 @@ Romeo Gateway Juliet

Informational messages can be sent by either party within the context of Jingle to communicate the status of a Jingle ICE "session". The informational message MUST be an IQ-set containing a &JINGLE; element of type "transport-info", where the informational message is a payload element qualified by the 'urn:xmpp:jingle:transports:ice:info:0' namespace.

-

The only payload element defined so far is the <ice-gathering-complete/> element. This element is used only to signal that gathering of ICE candidates has been completed (i.e., to send an "end-of-candidates indication"), as in the following example.

+

The only payload element defined so far is the <gathering-complete/> element. This element is used only to signal that gathering of ICE candidates has been completed (i.e., to send an "end-of-candidates indication"), as in the following example.

Date: Fri, 28 Jun 2019 08:32:28 +0200 Subject: [PATCH 4/8] MUC Self-Ping (XEP-0410): Clarify the feature string Although the example shows the correct string, the normative text potentially leaves the impression that the feature string is only 'self-ping-optimization', i.e. without the 'http://jabber.org/protocol/muc#' prefix. --- xep-0410.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0410.xml b/xep-0410.xml index 03518c61..d864a743 100644 --- a/xep-0410.xml +++ b/xep-0410.xml @@ -199,7 +199,7 @@ to a occupant's Ping request to the occupant's own nickname, as opposed to routing it to any of the occupant's clients. A service implementing this optimization needs to advertise the - self-ping-optimization feature in the &xep0030; response on + http://jabber.org/protocol/muc#self-ping-optimization feature in the &xep0030; disco#info response on the individual MUC room JIDs, and it MUST respond to a self-ping request as follows:

    From 2d09017fd9c20918fe35ec53d2cc200084f9630b Mon Sep 17 00:00:00 2001 From: Guus der Kinderen Date: Mon, 1 Jul 2019 14:37:15 +0200 Subject: [PATCH 5/8] XEP-0128: Remove 'unlikely' statement. With various XEPs (XEP-0157, XEP-0232, XEP-0363) depending on Service Discovery Extensions, it is no longer 'unlikely' that more than one extension is added. --- xep-0128.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0128.xml b/xep-0128.xml index 51ed03e9..842ea710 100644 --- a/xep-0128.xml +++ b/xep-0128.xml @@ -156,7 +156,7 @@ -

    In general, the XMPP Standards Foundation may choose to define at most one FORM_TYPE for each service discovery identity (category+type) registered with the XMPP Registrar. In addition, particular applications may define application-specific FORM_TYPEs as well, and one entity may have multiple service discovery identities (e.g., an XMPP server might also function as a publish-subscribe service). Therefore, it is possible (and allowed) for a single service discovery result to contain multiple service discovery extension elements (potentially up to two elements for each identity). However, in practice it is unlikely that any given service discovery result will contain more than one service discovery extension element.

    +

    In general, the XMPP Standards Foundation may choose to define at most one FORM_TYPE for each service discovery identity (category+type) registered with the XMPP Registrar. In addition, particular applications may define application-specific FORM_TYPEs as well, and one entity may have multiple service discovery identities (e.g., an XMPP server might also function as a publish-subscribe service). Therefore, it is possible (and allowed) for a single service discovery result to contain multiple service discovery extension elements (potentially up to two elements for each identity).

    Applications SHOULD ensure that information disclosed in a disco extension is appropriate for discovery by any entity on the network.

    From a5453db422353a7da06ca65ec934466b176b2888 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 30 Jul 2019 16:51:20 +0200 Subject: [PATCH 6/8] XEP-0371: add revision block --- xep-0371.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0371.xml b/xep-0371.xml index a2d725ff..e97c86e5 100644 --- a/xep-0371.xml +++ b/xep-0371.xml @@ -27,6 +27,12 @@ jingle-ice &stpeter; + + 0.2.1 + 2019-07-30 + fippo + Fix reference to gathering-complete element in text. + 0.2 2017-09-11 From 074cc95880fadd67f5b0964dbd8331a41beeb7cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 30 Jul 2019 16:52:53 +0200 Subject: [PATCH 7/8] XEP-0410: add revision block --- xep-0410.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0410.xml b/xep-0410.xml index d864a743..fe8b9a58 100644 --- a/xep-0410.xml +++ b/xep-0410.xml @@ -29,6 +29,12 @@ georg@op-co.de georg@yax.im + + 1.0.1 + 2019-07-30 + fs + Make feature string reference more clear + 1.0.0 2019-06-27 From fe9c14437fa69f0fc320a249d662e3b131d48f7e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 30 Jul 2019 16:55:08 +0200 Subject: [PATCH 8/8] XEP-0128: add revision block --- xep-0128.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0128.xml b/xep-0128.xml index 842ea710..213c84ef 100644 --- a/xep-0128.xml +++ b/xep-0128.xml @@ -23,6 +23,12 @@ N/A &stpeter; + + 1.0.1 + 2019-07-30 + gdk + Remove now-incorrect informational statement about the likelihood of multiple forms in a single disco#info reply. + 1.0 2004-10-20