XMPP Council - 2024-04-09

it's time

1) roll call

👋

hello!

Hi

2) Agenda Bashing

does anyone have something to add to the agenda?

I’m guessing not...

3) Editors update

* STABLE: XEP-0386 (Bind 2) * STABLE: XEP-0388 (Extensible SASL Profile) * UPDATED: XEP-0333 (Displayed Markers)

4) Items for voting

a) Move 'XEP-0334 (Message Processing Hints)' to stable

+1

+1

+1

+1

b) Move 'XEP-0333 (Displayed Markers)' to stable

+1

+1

+1

+1

c) XEP-0388: Fix typo https://github.com/xsf/xeps/pull/1338

+1

very very technically this is a breaking change. but it is also very clearly a typo

+1

+1, even though I couldn't work out the change in the first line of diff

+1, same, very hard to see but caught a comment pointing it out

dan.caseley: First diff is s/atrribute/attribute/, no idea why it's not properly highlighted by github.

yes one of those is actually a typo

Thanks!

5) Pending votes

none

6) Date of Next

+1w wfm

+1w wfm

+1w wfm

(but i’m away the two weeks after that)

+1w wfm

7) AOB

I actually have some AOB myself

(side note: I went to fix my calendar on thunderbird and it actually is set to 4pm UTC, so it shows the "correct" time of the meeting, which means my android calendar app has a bug, fun times fun times...)

I’m (partially with my editor hat on) are done with the first round of Last Calls but I want to start some more

I'm open for ideas (obviously we need to ping the authors)

personally i'm interested in calling occupant id as this is required for a lot of MUC stuff like reactions

also channel binding

i've tried to ping flow wrt channel binding. will do again

and marvin is on vacation (author of occupant id)

so yeah I guess feel free to either ping me or the respective authors to ask council to start a last call

end of my AOB

any other AOB?

channel binding needs some more in depth security considerations spelling out what it does and does not protect against, I've seen a lot of misconceptions lately, but nothing that can't be easily fixed, I can bring it up during last call :)

XEP-0359? Lots of other XEPs make use of stable stanza IDs.

yes... we may or may not have to remove origin-id

the stanza-id gets used a lot

the origin id has been controversial in the last last call

anyway. seems like there are no AOB

8) Close

thank you all. see you next week

Thanks Daniel!

thanks all

I thilk anything we need to get compliance suites made of only stable and above is good. I agree occupant id seems uncontroversial and is now widely deployed

I don't think we are super far of from that

Vcard conversion xep last call ends next week

I'll probably start working on a 2025 version in summer

That considers the old bookmarks phased out

And makes a couple of other changes

Anything from Council worth to communicate on our media channels?