[dispatch] Fw: Enquiry about proposing a new specification at IETF
Rahul Gupta <cxres@protonmail.com> Tue, 01 August 2023 22:15 UTC
Return-Path: <cxres@protonmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB081C14CF18 for <dispatch@ietfa.amsl.com>; Tue, 1 Aug 2023 15:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dkN6FJ0V3Zo for <dispatch@ietfa.amsl.com>; Tue, 1 Aug 2023 15:15:12 -0700 (PDT)
Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch [185.70.40.141]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D75C14F75F for <dispatch@ietf.org>; Tue, 1 Aug 2023 15:15:11 -0700 (PDT)
Date: Tue, 01 Aug 2023 22:14:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1690928109; x=1691187309; bh=XbxByNZxym+g8vwtqzs6nlX04G4ooWu997DTu6ihDrM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=XA96gYe87/abIlKZRc9CFD0dxr3nDev6f3lOzSc3vFOcSLkVJHiy+c+d0Qn3GPT15 pXgMJALjkPP+1DMlp1IA+S2dfsoDxVJSEAlZ2laguedR8OhDXQ/Hmq3eXf1wSuyQrg Q6ahhXAK1WIxkdF01oCJjT1o57QwBOBQoCsP+beztnDci2k4adbtemM/J+/Jrgeflz JuhLAgh+qWTH8oIJ3w6p6YP9z0h7yOzjcXVVGxAUQwN+4/k1dvdoQvFvmgphxX2/Xy WnnzoUVwx9ax2AsqxefiYoiDAaqZpmiNkWCOI8XLS+GUvFE98m69zrvPD4Dgkj59CQ VYG/AdeL61ewQ==
To: "dispatch@ietf.org" <dispatch@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
From: Rahul Gupta <cxres@protonmail.com>
Cc: "pengshuping@huawei.com" <pengshuping@huawei.com>, "fenton@bluepopcorn.net" <fenton@bluepopcorn.net>, "mnot@mnot.net" <mnot@mnot.net>, "tpauly@apple.com" <tpauly@apple.com>
Message-ID: <KJoGNM6fXdWpXLabB4MuKj05RKSiRfZ_rNTTnBVdzF7bd1hVfQdlTrmnxPnb0w0jDiT4FMdk1TJi4P-DmkBRcMnmzZovXHx993ua9SGHXqc=@protonmail.com>
In-Reply-To: <wpLX3CXt4u-gNXFwK_MojMeXY9RQO3o3cKOWhuCNLKu0jPAKt4GNB1gv7LhxN6R0np7X5VuYFil2n8zVwihzry-zzhmF49N9vQVLihsntng=@protonmail.com>
References: <wpLX3CXt4u-gNXFwK_MojMeXY9RQO3o3cKOWhuCNLKu0jPAKt4GNB1gv7LhxN6R0np7X5VuYFil2n8zVwihzry-zzhmF49N9vQVLihsntng=@protonmail.com>
Feedback-ID: 919445:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="------c44e877bff56c3330c18ac6ea28eeeba68c0d114eef30712169b4d94ea347890"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/j4L2_0f3hfhoS8ITDYza4ApbmP8>
X-Mailman-Approved-At: Tue, 01 Aug 2023 18:05:09 -0700
Subject: [dispatch] Fw: Enquiry about proposing a new specification at IETF
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2023 22:17:54 -0000
Dear HTTP and Dispatch Groups, I wish to propose a new protocol built on top of HTTP - Per Resource Events Protocol <https://cxres.github.io/per-resource-events/protocol> for standardization with the IETF. I am hoping someone in the Dispatch or HTTP groups might guide me how to proceed. I have already made a more detailed request introducing my proposal to the ART Area Director about a fortnight ago (attached below). I apologize about the spamming everyone, but I am hoping that at least one of you might respond. Yours truly, Rahul PS: Mark: I have read your blog post recently, and seen that you are interested in extending HTTP to build an event (pub/sub) protocol. I believe my proposal will be especially of interest to you. Sent with Proton Mail secure email. ------- Forwarded Message ------- From: Rahul Gupta <cxres@protonmail.com> Date: On Thursday, July 20th, 2023 at 7:23 PM Subject: Enquiry about proposing a new specification at IETF To: francesca.palombini@ericsson.com <francesca.palombini@ericsson.com> > Hi Francesca, > > I am writing to you in your capacity as Area Director of art at IETF. I am developing a new protocol for notifications on top of HTTP and exploring the option for its standardization at IETF. In this regard, I am hoping you might be able to guide me in the right direction. > > The protocol that I am proposing is called the Per Resource Events Protocol <https://cxres.github.io/per-resource-events/protocol>, which as the names suggests allows a server to add notification capability to any resource to provide updates about its own representation changes. > > > This specification is an offshoot of my contribution as a co-author on Solid Notification Protocol <https:/github.com/solid/notifications> which adds notification capabilities to Solid Pods (though SNP is universal in that it can be used by any other servers) as defined for the Solid Project <https://solidproject.org>. Per Resource Events address the similar use cases as Solid Notifications, but with a simpler but less comprehensive protocol that would be much easier to implement and to scale. There has already been a publicly expressed interest in implementation since I have uploaded my first draft on Github. > > > I would be really grateful if you can guide me through the steps that I need to undertake and/or people who I might need to contact directly for my proposal to be considered by IETF for standardization. > > > Thanks in advance, > > > Your truly, > Rahul Gupta > > > PS: Please forgive me for writing to you directly, but I am not sure how else to get IETF's attention. When I have previously written to the HTTP-WG mailing list with a question a few months ago, (despite multiple attempts) my e-mail was not listed. Nor did the postmaster provide an intimation for not listing the mail, as is the internal policy for the mailing list. > > >