[Standards] Re: XEP-0440 and tls-server-end-point

[Travis Burtrum]

On 1/11/24 10:37, Dave Cridland wrote:



On Thu, 11 Jan 2024 at 12:39, Holger Weiß > wrote:


* Simon Josefsson mailto:si...@josefsson.org>>
[2024-01-11 13:10]:
 >I believe tls-server-end-point is generally best left unimplemented to
 >guide efforts towards supporting the stronger tls-exporter.

One use case I see for tls-server-end-point is that it allows for
supporting channel binding by setups where TLS is terminated by some
reverse proxy, thereby protecting against _some_ but not all attack
vectors that tls-exporter protects against.


I'm pretty sure this was a key reason we picked the approach. If TLS is 
terminated before the server ever sees it, the server can still be 
configured to handle tls-server-end-point.


Also the TLS terminating proxy can pass the required secrets for "real 
channel binding" to the backend XMPP server via extensions to the PROXY 
protocol.  I plan on adding support for this to xmpp-proxy soon.


___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org

[Standards] Escape characters in XEP-0393: Message Styling

[Werner Kroneman]

Hello,

first of all, this is my first attempted contribution to an Internet 
standard, so I do apologize if the form is a bit off.


That said, I was implementing a parser for "XEP-0393: Message Styling", 
and I ran into the issue that not much is defined in the way of escape 
characters.


In Gajim, for instance, the sequence

*hello*

becomes bold, the sequence

\*hello*

does not, but the sequence

\\*hello*

also does not.

In many applications, preceding a \ with another \ escapes the latter \, 
making it so that the escape character itself is escaped, and therefore 
the * that creates the emphasis span would not be.


However, the standard does not mention any rule regarding this (and 
Gajim does not do what I expect), so it is perhaps a good idea to add a 
note about this before making it final.


Kind regards,

Werner

___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org

[Standards] Proposed XMPP Extension: PubSub Server Information

[kevin . smith]

The XMPP Extensions Editor has received a proposal for a new XEP.

Title: PubSub Server Information
Abstract:
This document defines a data format whereby basic information of an
XMPP domain can be expressed and exposed over pub-sub.

URL: https://xmpp.org/extensions/inbox/pubsub-server-info.html

The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org

[Standards] UPDATED: XEP-0483 (HTTP Online Meetings)

[kevin . smith]

Version 0.2.0 of XEP-0483 (HTTP Online Meetings) has been released.

Abstract:
This specification defines a protocol extension to request URLs from
an external HTTP entity usable to initiate and invite participants to
an online meeting.

Changelog:
* Use XEP-0482 to send the meeting link to another party (do)

URL: https://xmpp.org/extensions/xep-0483.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.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org

[Standards] ACTIVE: XEP-0458 (Community Code of Conduct)

[kevin . smith]

Version 1.0.0 of XEP-0458 (Community Code of Conduct) has been
released.

Abstract:
This document describes the XMPP Standard Foundation's Code of
Conduct.

Changelog:
Changed status to Active per Board vote on 2024-01-05. (psa)

URL: https://xmpp.org/extensions/xep-0458.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.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org