💾 Archived View for gemi.dev › gemini-mailing-list › 000673.gmi captured on 2024-05-26 at 16:28:04. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

RFC for Gemini

📧 Messages: 3
🗣️ Authors: 3
📅 First Message: 2021-02-09 10:53
📅 Last Message: 2021-02-09 12:39

1. Jason Evans (jsevans (a) mailfence.com)

📅 Sent: 2021-02-09 10:53
📧 Message 1 of 3

Hi all,

Are there any plans for submitting a standardized RFC for a Gemini standard?

Link to individual message.

2. Petite Abeille (petite.abeille (a) gmail.com)

📅 Sent: 2021-02-09 11:07
📧 Message 2 of 3



> On Feb 9, 2021, at 11:53, Jason Evans <jsevans at mailfence.com> wrote:
> 
> Are there any plans for submitting a standardized RFC for a Gemini standard?

gemini://gemi.dev/gemini-mailing-list/messages/004458.gmi

?0?

Link to individual message.

3. Stephane Bortzmeyer (stephane (a) sources.org)

📅 Sent: 2021-02-09 12:39
📧 Message 3 of 3

On Tue, Feb 09, 2021 at 11:53:58AM +0100,
 Jason Evans <jsevans at mailfence.com> wrote 
 a message of 3 lines which said:

> Are there any plans for submitting a standardized RFC for a Gemini standard?

"t this point, the [spec] topic of the mailing list will be retired,
and the project will transition to a new phase where the primary
ongoing technical activity is to translate that speculative
specification into a more precise and formal technical document, with
the goal that it might eventually be submitted to formal internet
standard organisations like IETF and IANA."

gemini://rawtext.club/~sloum/geminilist/004642.gmi

Link to individual message.

---

Previous Thread: [Spec] [rfc-editor@rfc-editor.org: RFC 8942 on HTTP Client Hints]

Next Thread: [ANN] New site with some really dodgy algorithmic poetry