-
emus
Hello everyone, it's not just mid-week but also mid-month! If you have news of your projects or projects of interest please don't forget to bring it over to the XMPP Newsletter we draft here: https://github.com/xsf/xmpp.org/pull/730 Questions & help welcome!
- eta . o O ( maybe we should copy the Matrix folks and have TWIX: This Week In XMPP )
-
Daniel
😂
-
!XSF_Martin
🤤
-
Daniel
oh riot is now element
-
Daniel
that's easier to google…
-
goffi
they've also got a huge contract with German education apparently, I don't know if XMPP was on the table, but if it was not there is something going wrong.
-
Daniel
well there is nobody who could have put it on their table
-
goffi
I have no idea how this kind of things are negociated and who brings project proposition. Is it not supposed to be a call for bids or something like that?
-
Daniel
i guess. but 'XMPP' is not an entity that could put in a bid for something like that
-
Daniel
and as an individual freelancer you pratically (and probably rightfully) have no chance at winning that
-
eta
yeah, what they're selling is their hosting service
-
eta
apart from isode maybe nobody in the XMPPverse is really doing that
-
goffi
processone?
-
Daniel
they don’t have clients
-
Daniel
if you are buying this for the use in schools you want a solution and not building blocks
-
goffi
alright, makes sense.
-
eta
evil plan, write a matrix c2s to XMPP translation layer, then undercut element because server hosting won't be as resource intensive
-
emus
> eta . o O ( maybe we should copy the Matrix folks and have TWIX: This Week In XMPP ) I dont unterstand what you wanna say?
-
eta
emus: don't worry, I'm just joking
-
eta
emus: (by the way, I should probably submit my WhatsApp bridge to your newsletter!)
-
emus
Are you still making jokes? 😦
-
eta
nope, this actually exists
-
emus
Okay, yes then feel free
-
eevvoor
We have one strong supporter for XMPP in the German jouth authorities.
-
eevvoor
But where have you heard that German schools start to use Matrix? This is new to me.
-
pep.
https://sifted.eu/articles/element-germany-deal/
-
eevvoor
I know only of one district starting to use mailbox.org as mailserver which means additionally an XMPP-account.
-
eevvoor
> The deal announced on Wednesday will see the German states of Schleswig-Holstein and Hamburg deploy a Matrix-based solution for 500,000 users across public offices and education as part of its wider adoption of open source cloud strategy Project Phoenix being carried out by IT provider Dataport. Hm this is weird.
-
eevvoor
thx for the link pep.
-
pep.
Is there anything at the IETF saying the XSF has a specific role when it comes to XMPP?
-
pep.
6120 has multiple mentions of "XSF" but it all seems very informal and not exclusive
-
Zash
Does it need to?
-
pep.
I'm just curious to know the current state
-
eevvoor
would be better ...
-
eevvoor
... my guess
-
pep.
eevvoor, I'm not entirely sure, but that's not what I'm asking here anyway
-
eevvoor
do other protocols do that? pep.
-
pep.
do what exactly? Define a separate entity to take care of them?
-
eevvoor
yes
-
Zash
Other than the delegation of the `urn:xmpp` namespace, I don't think there's any need for anything special from anyhere.
-
pep.
eevvoor, don't know
-
pep.
Zash, again, not asking about needs
-
eevvoor
That would be interesting to check.
-
Zash
pep.: What are you asking?
-
pep.
The current state
-
pep.
"IS there anything at the IETF saying the XSF has a specific role when it comes to XMPP"✎ -
pep.
"Is there anything at the IETF saying the XSF has a specific role when it comes to XMPP" ✏
-
Zash
I don't think there is.
-
Zash
Anything special comes from actually publishing XEPs.
-
Holger
So I can just publish Holger's Extension Protocols and the IETF Police can do ... *nothing*.
-
Zash
Anyone could publish XMPP extensions, there is no requirement that it goes through the XSF.
-
Daniel
I don't think we are sanctioned be the ietf or anything if that's what you mean
-
moparisthebest
one could even publish XMPP extensions as google docs in russian, if one were so inclined
-
pep.
Daniel: Yeah that's what I was asking, and I didn't think either but I thought it might be good to confirm
-
Daniel
I also don't know of a lot of other extensible protocols that don't remain with the ietf
-
Daniel
For example IMAP extensions are still ietf
-
pep.
moparisthebest, imagine somebody publishing that on a random website (xmpp.org) in english :p
-
Zash
Google published a bunch of docs on their custom extensions.
-
Daniel
Or ietf working groups
-
Daniel
Which makes you wonder what lead to that decision
-
pep.
I'm curious why the XSF "had to" be a separate entity, I'd be interested to know the story behind this
-
pep.
that
-
Zash
Probably because it already existed before the inital RFCs were created.
-
Zash
You could ask the same about the IETF
-
pep.
I also wonder what made the XSF (or JSF at the time) decide to go through the IETF process for some but not all their specs
-
Zash
The IETF isn't even an organization AIUI, it's like an activity organized by some other organizations.
-
Holger
Kinda obvious that anyone is free to publish custom extensions. I guess the fun situation would be if someone forked the XSF and claimed to be THE XMPP standardization organization.
-
Zash
pep.: Roughly the same reasons you'd go to the XSF with XEPs.
-
pep.
(my question being somewhat similar to the one above, why is there a need for the XSF at all)
-
pep.
Zash, "legitimacy"? But then are other specs not legitimate? :p
-
Zash
No, review by other people.
-
pep.
And other specs don't need review? :P
-
pep.
Just thinking out loud, there is not specific point I'm trying to make
-
Zash
You know that someone (at least Council in our case) looked at a XEP and said "this isn't terrible"
-
pep.
I wonder if merging as an IETF working group has ever been considered during the less active years
-
pep.
(or at all)
-
Zash
That would probably have worked too.
-
Daniel
I don't think there are significant upsides or down sides of being a working group
-
eevvoor
can the XSF be both? Itsself and an IETF working group?
-
pep.
I'm not sure it would be "The XSF" being an IETF working group but the same members
-
Daniel
Meaning I don't think that would benefit anyone in 'less active years'
-
Daniel
Work either gets done or it doesn't
-
pep.
Daniel, maybe it's slightly more visible to IETF people? dunno. I'm not really familiar with IETF
-
eevvoor
so it would be a mirror pep. ;)
-
pep.
But also we could share stuff like the infra etc. (using their ML and maybe some more if there is?)
-
eevvoor
every xep to an rfc :D (disclaimer: really just a joke)
-
eevvoor
ML is what pep.?
-
Zash
Tradeoffs
-
pep.
eevvoor, Mailing List
-
eevvoor
ah :D
-
pep.
8800 RFCs.. I'm sure they can adopt another 400s :p
-
Zash
As always, some things are easier to do if you're independent. Other things are harder.
-
pep.
June 2020: JSON Canonicalization Scheme (RFC8785). Finally they get to it?
-
moparisthebest
then the XSF would simply exist to managed the Jabber trademark? (assuming it's still legally able to do so, still haven't seen proof of this)
-
Zash
A support group for XMPP developers?
-
moparisthebest
before someone links all the PDFs from xmpp.org they have all expired
-
flow
pep.> But also we could share stuff like the infra etc. (using their ML and maybe some more if there is?) there is already an XMPP ML for the concluded XMPP WG
-
pep.
flow, yeah I do remember that
-
flow
i think one could also try to get an xmpp extension published as rfc
-
flow
but without an working group adopting the I-D, I'd assume that will require some contacts within the ietf to actually happen (cf. xmpp grid)
-
pep.
Sure, just like IoT stuff is being/has been published at the IEEE
-
stpeter
Just catching up on the discussion. A few points: (1) the JSF predated our involvement with the IETF by a few years (2) the JSF was created to publish open documentation of the Jabber protocols and to add extensions in an open way too (3) we decided to formalize the core protocols at the IETF because we thought it would improve the quality/security of the core and also increase awareness / lead to more adoption especially by organizations that care about a more formal stamp of approval such as corporations and governments (4) there is no formal agreement in place between the IETF and the XSF about the division of responsibilities because we have a good working relationship with IETF folks and they prefer not to create formal agreements unless the working relationship isn't so healthy (5) yes, anyone can create and publish XMPP extensions but it's helpful to have a community of practice where we can review each other's work and therefore (we hope) produce better protocols for the sake of interoperability (6) I have sometimes considered the option of a separate RFC "stream" for XSF specs (there are already streams for IETF, IAB, IRTF, and "independent" documents) but I see no great reason to do that
-
pep.
Thanks for the clarifications
-
eevvoor
stpeter, sounds good
-
pep.
What's the "stream" thing exactly?
-
pep.
Also "lead to more adoption especially by organizations that care about a more formal stamp of approval" -> so yeah legitimacy
-
stpeter
Streams are input methods to the RFC publication process. They are described at https://www.rfc-editor.org/rfc/rfc4844
-
Zash
The IETF process is a bit more nuanced than one might think at first. Not just I-D → RFC
-
stpeter
Having published 45 RFCs, I can concur with that statement. :-)
-
stpeter
I think I'm in the top 1%: https://www.arkko.com/tools/rfcstats/authactdistr.html
-
stpeter
Not that it really matters.
- stpeter wanders off to his next $dayjob meeting