Publication of the Mercure Protocol

Kévin Dunglas <> Wed, 08 July 2020 16:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E2C783A0F46 for <>; Wed, 8 Jul 2020 09:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ywfWOXNlilfw for <>; Wed, 8 Jul 2020 09:17:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FBF43A0F21 for <>; Wed, 8 Jul 2020 09:17:23 -0700 (PDT)
Received: from lists by with local (Exim 4.92) (envelope-from <>) id 1jtCiM-00056K-6J for; Wed, 08 Jul 2020 16:14:30 +0000
Resent-Date: Wed, 08 Jul 2020 16:14:30 +0000
Resent-Message-Id: <>
Received: from www-data by with local (Exim 4.92) (envelope-from <>) id 1jtCiK-00054c-JF for; Wed, 08 Jul 2020 16:14:28 +0000
Received: from ([]) by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1jtBJd-0006vD-B3 for; Wed, 08 Jul 2020 14:44:53 +0000
Received: from ([2607:f8b0:4864:20::12e]) by with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <>) id 1jtBJb-00037X-ET for; Wed, 08 Jul 2020 14:44:53 +0000
Received: by with SMTP id a11so31043699ilk.0 for <>; Wed, 08 Jul 2020 07:44:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=0VrRYeAh9DYP7O/mx7dDTRDlJMUNu/3659r9+OY/Ri0=; b=V/TUcPRvAlJIQA0qXtlCfzdvbObqZNtR3HRSizQTt/JFKVUz0UD8mieYc+7UJu17Pe RqqcrZhHLYqXWR2YPA5Hw+XF4H5DVdXdW2MWzm237PO7hVTSYCcygxHDPWFURCmLg6w1 cI3K+kFZTcvDhjFiTLZDYr8hQFP0V2Z56TOF1Zne3NzcedRQQEubnZBHax/lm7QMUQPl dc0OEDsUnGQ6Qh81PY0sFPxKRw9BunTiu7YwgrKj9dxum1RMgyMlaj6ucd3d1EtiUpuG gIiyCw1CpFkOlNLPsLzwY9jIm3bfOtE6TPFDl4gBIGEgShdr3Q/deKxJAPYPzxO7rqC/ PntQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0VrRYeAh9DYP7O/mx7dDTRDlJMUNu/3659r9+OY/Ri0=; b=ehLkckUgdz96gbgWJDYjVy50cAH/Rrp7ApnvCZPly7C9wL1V7D2xaNctiGI01Jiylt ZQ4HE0munhKeO7TTSDwCzKMQD/XmjOhBE3jM4zjnz8gG9TdcOfnRL9ZAgcmoTGv8BUXd U/DRhEolwZNM/D9q1VEMKF3BNFHPZO72EcZsz+CI0aBPwQjW1eCy06KJu0nRmtFVYCUv +OaW29eYdZRe6HXJs7YiuCqDfYnV/tzTWdi3AJNO5WhVY9RVtV2jRwf6dbYx5XNPre8U pxXdmkMubugIjBAOXiEwbAB82X0Clvi1yOg3JCY1Lng3LJjG4+coU4xdt9HXVGuGGaMv SEdg==
X-Gm-Message-State: AOAM530DUPAeo3WZXDA5jRVPyMF0a5Ffui6qpZPdnnx5nLOlOsTHIaUo kBt5F0v91pfPGuPWIkTZ0wZ3HASWwLgpjLJNdCSiqKkhs9uqAA==
X-Google-Smtp-Source: ABdhPJzikdMH/O8/CweJD6C0x6GIlSvWz9IAxLoH5M4MHE0XfE8osuTNTSawu6Uxzx1E8WdMjWA+5UG1+mATm1PtvQU=
X-Received: by 2002:a92:cece:: with SMTP id z14mr12292493ilq.120.1594219480149; Wed, 08 Jul 2020 07:44:40 -0700 (PDT)
MIME-Version: 1.0
From: =?UTF-8?Q?K=C3=A9vin_Dunglas?= <>
Date: Wed, 8 Jul 2020 16:44:29 +0200
Message-ID: <>
Content-Type: multipart/alternative; boundary="000000000000cf0c6d05a9ef25c7"
Received-SPF: none client-ip=2607:f8b0:4864:20::12e;;
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1jtBJb-00037X-ET cb0bb7dfa01fcfcb82e7434d63e1452e
X-caa-id: 14ea962b15
Subject: Publication of the Mercure Protocol
Archived-At: <>
X-Mailing-List: <> archive/latest/37858
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

Hi all,

Late 2018, I published an Internet-Draft specifying a protocol called


   Mercure is a protocol enabling the pushing of data updates to web
   browsers and other HTTP clients in a fast, reliable and battery-
   efficient way.  It is especially useful for publishing real-time
   updates of resources served through web APIs to web and mobile apps.

I just published the 7th version of the I-D. The protocol can now be
considered stable and feature complete. It is already widely implemented
and used, including by popular web frameworks such as Symfony. You can see
the full list of implementations in the "Implementation Status" section of
the I-D.
I would like to go one step further and propose it as a RFC.

I was wondering if the HTTPbis Working Group could host the work on this
protocol (this looks allowed by the "Other HTTP-Related Work" section of
the charter)?

Also, I tried to register the link relation ( and the
"well-known" URI ( used by
the protocol, but it's not possible yet because the I-D isn't on any stream..
I submitted a new version of the XML file with the following header:

<rfc version="3" ipr="trust200902" docName="draft-dunglas-mercure-07"
submissionType="IETF" category="std" xml:lang="en" xmlns:xi="" consensus="true">

But it looks like it hasn't been taken into account by the tracker (

I must admit that the process to propose a RFC is still a bit unclear to
me. Is this list the right place to propose and discuss this protocol?
Should I create a new submission for the draft or is it possible to
"update" the stream on the existing one?

Best regards,
Kévin Dunglas / @dunglas <>