Re: [dispatch] Fw: Enquiry about proposing a new specification at IETF

worley@ariadne.com Wed, 02 August 2023 15:51 UTC

From: worley@ariadne.com
To: Rahul Gupta <cxres=40protonmail.com@dmarc.ietf.org>
Cc: dispatch@ietf.org, ietf-http-wg@w3.org
In-Reply-To: <KJoGNM6fXdWpXLabB4MuKj05RKSiRfZ_rNTTnBVdzF7bd1hVfQdlTrmnxPnb0w0jDiT4FMdk1TJi4P-DmkBRcMnmzZovXHx993ua9SGHXqc=@protonmail.com> (cxres=40protonmail.com@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Wed, 02 Aug 2023 11:48:32 -0400
Message-ID: <87sf91sawf.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/GzwmF5nATo6iv4f8J1JF6Uo7Ndk>
Subject: Re: [dispatch] Fw: Enquiry about proposing a new specification at IETF
Precedence: list

Rahul Gupta <cxres=40protonmail.com@dmarc.ietf.org> writes:
> 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.

The dispatch mailing list is probably a good place to start.

Some things that would help advance your work:

- Make sure you can compare it to previous work and explain why it is
  better.  I'm not familiar with event subscription in HTTP (though I've
  done quite a bit with SIP) but a quick search reveals RFC 8030
  "Generic Event Delivery Using HTTP Push".  Make sure you can explain
  how your proposal does something valuable that RFC 8030 does not.

- Consider if your proposal might work as an addition to RFC 8030;
  extensions of existing standards are always favored over new work
  which partially duplicates what has gone before.

- If Mnot's blog explains needs that the proposal satisfies, see if your
  writeup can summarize those needs and explain how the proposal
  satisfies them. -- A common problem with first draft documents is that
  the writer forgets he is the expert in the subject and doesn't write
  down enough of the context information to make the document easily
  readable by non-experts.

- Are there other people involved in assembling the proposal?  Is there
  running code implementing the proposal, especially if it is used in a
  production situation.  All of these show there is widespread interest
  and value in this work.

- The goal of a first message about proposed work is to get people
  interested in it.  So it helps to write a few paragraphs explaining
  why the proposal is useful.  You can omit almost all of the technical
  details, as few people will be encouraged to spend time looking at the
  proposal because of the details.  But if you can describe a widely
  felt need that the proposal satisfies, you'll gain traction.

Dale

[dispatch] Fw: Enquiry about proposing a new spec… Rahul Gupta
Re: [dispatch] Fw: Enquiry about proposing a new … worley