- From: Rahul Gupta <cxres@protonmail.com>
- Date: Tue, 01 Aug 2023 22:14:52 +0000
- To: "dispatch@ietf.org" <dispatch@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
- 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->
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. > > >
Attachments
- application/pgp-keys attachment: publickey_-_cxres_protonmail.com_-_0x0CEC7748.asc
Received on Tuesday, 1 August 2023 22:15:18 UTC