Forty years ago, 21 people gathered for the first meeting of what became the Internet Engineering Task Force or #IETF . Every day billions of people use the open standards and technologies developed in the IETF. And nearly 8000 volunteer IETF participants from around the world collaborate in more than 100 working groups evolving those open standards and making the Internet work better!
"Jabber—or XMPP, as it became known after standardization through the #IETF—remains the only truly vendor-independent, federated instant messaging platform."
The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community.
On January 4, 1999, Jabber was first announced to the public¹.
Twenty-seven years later, Jabber—or XMPP, as it became known after standardization through the #IETF—remains the only truly vendor-independent, federated instant messaging platform.
In almost three decades, XMPP has never stopped evolving and remains our best tool for digital independence.
Jeremie writes
"Jabber is a new
project I recently started to create a complete open-source
platform for Instant Messaging with transparent communication
to other IM systems(ICQ, AIM, etc).
This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe and idempotent manner and then respond with the result of that processing.
@giacomo @lorenzo I did not review that particular spec, but for those I do, I'd raise hell before publication as #IETF if such problems were unaddressed, and know many other reviewers who would do the same.
#IETF124 was, of course, great, but I also enjoyed Montreal a lot. My flight home is only this afternoon so I went for a walk to grab some bagels and check out Habitat 67.
Day 2 of the Hackathon went great. Marvin (@larma) helped me implement an opt-in feature in #Conversations_im which routes all P2P sessions (calls and files transfers) via the users home server (similar to the feature found in Signal).
I went on a nice walk to a viewpoint on Mount Royal afterwards.
This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe/idempotent manner and then respond with the result of that processing.
The EU is mandating messaging apps be compatible with each other, but the current plan is looking less like #federation and more like "register your chat app with Meta, send them all your data, and link with their prescribed APIs that they may decide to change any day"
At the risk of preaching to the converted, here's @guusdk advocating for *real* interoperability between messaging apps, using an existing, battle-tested, #IETF-backed standard: #XMPP!
When I explain to others what I do for a living, I often ask why it is that we are not surprised that one can use a Gmail account to send an email to someone who uses an Outlook account, yet many people fully accept that you can’t send a message to s…
This document defines a method for JSON Meta Application Protocol (JMAP) servers to advertise their
capability to authenticate Web Push notifications using the Voluntary
Application Server Identification (VAPID) protocol.
NLnet Labs celebrates twenty-five years as an independent, non-profit foundation working on #opensource and #openstandards. Our mission remains to make the core of the Internet a better, safer place by developing open-source software, through applied research and by promoting and contributing to open standards. Have you been along for the ride as a user of our #DNS or #routing software, worked with us on #IETF standardisation, applied research or policy advocacy? Share your story!
This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP pr…
Thank you to everyone has supported and contributed to this over the past almost nine years since the initial seeds were planted during discussions at a TLS 1.3 interim meeting.
SVCB has potential to have substantial impact across a wide range of Internet protocols. I'm thrilled to see how many drafts are already building on it.
This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR)
types to facilitate the lookup of information needed to make connections
to network services, such as for HTTP origins.
