From 284f83bcf63f15a15405ef6d60252a10c0bc6217 Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Fri, 2 Aug 2024 20:49:49 +0200 Subject: [PATCH] XEP-0478: Add the XML Schema, and make both children optional --- xep-0478.xml | 78 ++++++++++++++++++++++++++++++++++++++++------------ 1 file changed, 60 insertions(+), 18 deletions(-) diff --git a/xep-0478.xml b/xep-0478.xml index 8df0c509..e72cbbbe 100644 --- a/xep-0478.xml +++ b/xep-0478.xml @@ -27,6 +27,18 @@ zash@zash.se &mwild; + + 0.2.0 + 2024-08-02 + egp + +
    +
  • Add the XML Schema.
    • +
  • Clarify that both children can be optional.
    • +
  • Fix indentation and one typo.
    • +
+ + 0.1.0 2023-05-04 @@ -46,7 +58,7 @@

This documents describes a mechanism for communicating limits, such as stanza size limits that is in effect on a particular stream, in order to allow the sending party to avoid reaching those limits.

Where stanza size limits have been deployed, very often this leads to problems with large stanzas causing connection outages, most often &xep0084; and &xep0053; result stanzas, which can be very large due to embedded images.

-

If stanza size limit violations are met with stream errors then this may lead to temporary connection outage, which may a few seconds to recover from.

+

If stanza size limit violations are met with stream errors then this may lead to temporary connection outage, which may take a few seconds to recover from.

 @@ -58,19 +70,19 @@ -

For any XMPP stream, there is an "initiating entity" (a client or server) and a "responding entity" that they are connecting to. The responding entity advertises its limits in the <stream:features/> element that it sends at the start of the stream.

-

The limits are enclosed in a <limits/> element qualified by the 'urn:xmpp:stream-limits:0' namespace. This element SHOULD contain the following child elements:

-
- -
<max-bytes/>
-
Contains an integer representing the maximum size of any first-level stream elements (including stanzas), in bytes the announcing entity is willing to accept. Guidance on acceptable limits is provided in &rfc6120; section 13.12.
- - -
<idle-seconds/>
-
Contains an integer representing the number of seconds without any traffic from the iniating entity after which the server may consider the stream idle, and either perform liveness checks (using e.g. &xep0198; or &xep0199;) or terminate the stream. Guidance on handling idle connections is provided in &rfc6120; section 4.6.
- -
- For any XMPP stream, there is an "initiating entity" (a client or server) and a "responding entity" that they are connecting to. The responding entity advertises its limits in the <stream:features/> element that it sends at the start of the stream.

+

The limits are enclosed in a <limits/> element qualified by the 'urn:xmpp:stream-limits:0' namespace. This element MAY contain the following child elements:

+
+ +
<max-bytes/>
+
Contains an integer representing the maximum size of any first-level stream elements (including stanzas), in bytes the announcing entity is willing to accept. Guidance on acceptable limits is provided in &rfc6120; section 13.12. If the responding entity is unable to determine its limits, this child can be absent.
+ + +
<idle-seconds/>
+
Contains an integer representing the number of seconds without any traffic from the iniating entity after which the server may consider the stream idle, and either perform liveness checks (using e.g. &xep0198; or &xep0199;) or terminate the stream. Guidance on handling idle connections is provided in &rfc6120; section 4.6. If the responding entity is unable to determine its limits, this child can be absent.
+ +
+ SCRAM-SHA-1 @@ -81,18 +93,18 @@ 1800 - ]]> +]]>

Servers using &xep0288; to establish a bidirectional stream with another server do not get an opportunity to send <stream:features/> to the responding entity. For a server to advertise the limits about what it is willing to accept on such a stream, the <limits/> element can be included in the <bidi/> element.

- 10000 1800 - ]]> +]]> @@ -129,6 +141,36 @@

The ability for a client to announce limits on what it will receive on a client-to-server stream is deliberately not provided by this specification. This vastly simplifies discovery of the maximum limits between any two JIDs, and it avoids situations where the server is unable to deliver incoming stanzas to some or all of an account's connected clients. Clients will already be protected from denial-of-service through excessive stanza sizes due to the server's own limits.

 -

TBD.

+ + + + + + + The protocol documented by this schema is defined in + XEP-0478: https://xmpp.org/extensions/xep-0478.html + + + + + + + + + + + + + + + + + +]]>