Re: [Standards] XEP Versioning

Hi, I just wanted to throw into the discussion that breaking changes is not the only thing to consider. Often new features are added to XEPs which are not breaking but someone still wants to know if a client implements it. Example XEP: 0045 Version 1.30: Add 333 status code with OPTIONAL

Re: [Standards] XEP Versioning

Hi Dave, thanks for your explanation! What is the reason for having a state such as Stable or Final and a redundant state (major) version? In my opinion, it would make more sense to have a separate state and semantic versioning as specified by https://semver.org . Or, if for any reason the

Re: [Standards] NEW: XEP-0397 (Instant Stream Resumption)

On Wed, 24 Aug 2022 at 12:19, Matthew Wild wrote: > On Wed, 24 Aug 2022 at 07:56, Daniel Gultsch wrote: > > > > > And yes we are currently implementing it. That's why I’m providing > > feedback on the XEP. And yes we are using it with compression and yes > > we do terminate TLS early and can’t

Re: [Standards] XEP Versioning

Hi, I like that we're documenting the versioning mechanism we use for XEPs, so - to be clear - I don't object to this change at all. I'm not so sure on the rationale given, though: @horazont The reason for specifying that topic was that @wurstsalat3000

[Standards] XEP Versioning

Hi, I created a PR for precisely specifying the versioning of XEPs: https://github.com/xsf/xeps/pull/1200 Here is the reason: https://github.com/xsf/xeps/pull/1200#issuecomment-1225678948 Please let me know what you think. ___ Standards mailing list

Re: [Standards] NEW: XEP-0397 (Instant Stream Resumption)

On Wed, 24 Aug 2022 at 07:56, Daniel Gultsch wrote: > > And yes we are currently implementing it. That's why I’m providing > feedback on the XEP. And yes we are using it with compression and yes > we do terminate TLS early and can’t use HT-* and yes we use PLAIN for > regular logins too and

Re: [Standards] NEW: XEP-0397 (Instant Stream Resumption)

On Wed, 24 Aug 2022 at 07:56, Daniel Gultsch wrote: > I now realize that I get hung up on PLAIN at little bit in my previous > e-mail. But what I was really saying is that ISR should allow any SASL > mechanism with HT-* being just one possible (although good) choice. > Right. HT is great, it

Re: [Standards] NEW: XEP-0397 (Instant Stream Resumption)

Hi Flow, I now realize that I get hung up on PLAIN at little bit in my previous e-mail. But what I was really saying is that ISR should allow any SASL mechanism with HT-* being just one possible (although good) choice. And to be clear when I say PLAIN I mean username+password and not putting the

[Standards] XMPP Council Agenda 2022-08-24

Good morning Council members, the next XMPP Council Meeting will take place on Wednesday, August 24th 2022 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Editors update - UPDATED: XEP-0447 (Stateless file sharing) - STABLE: XEP-0215