This is not an official RFC

[poizan42]

Steps to reproduce:

1. Go to https://ietf.org
2. Try to find this RFC
3. Notice that it's not an official RFC

Expected behaviour:

This should be an official RFC.

What we can do to solve this:

1. Format it according to the rules for RFC formatting, see https://tools.ietf.org/html/rfc6949.
2. Submit it to IETF for publication next coming April 1st.

There may be some questions about how to list the authors in an effort such as this, but this is probably something we can figure out. This can go down in history as the first crowdsourced RFC.

[joho]

This has been on my TODO list for god knows how long. I generally get stuck at investigating vim plugins to do it for me 😄

[joho]

[joho]

So, uh, I ran out of steam last march to do it. But maybe this march!

[harleyknd1]

[lyrixx]

Missed ?!

[ferm10n]

YOU CAN DO IT ✊

[Seluj78]

How about this year ?

[komfluent]

this needs to happen!!!

[foxt]

Oh well, there's always this year

[ConnorBaxter]

Today is your chance

[joho]

Nah.

1. The IETF want a fair amount of lead time in a submission
2. In this economy?

[Ammonix]

you lazy piece of a developer ^^

[ferm10n]

Is this project still maintained?? 😂 This issue has been open since 2017 and it'd be a shame if someone were to, say, idk, steal the RFC and submit it on behalf of the current maintainer with the request that if the IEFT accepts it that it only gets published next April 1st

[ferm10n]

Hello fellow hackers. If you would like to prevent me from appearing in your GitHub each year, please share a recommendation on how I can help get this submitted!

The notifications will continue until participation improves.

[yarooze]

This year? Please...