On Sun, Dec 27, 2020 at 10:32 AM Petite Abeille <petite.abeille at gmail.com> wrote: > 1 ? RFC x1965 The Gemini Protocol: describes the over-the-wire protocol > itself > 1 ? RFC x1966 The Gemini Document:. describes the text/gemini document > forma > +1. Note, however, that creating standards-track RFCs (as I hope we will) implies the possibility that the IETF WG will make changes. If the present Gemini community doesn't want to give up change control, we can publish an informational RFC instead. Anyone with an email address can join an IETF WG, however, so we can still have influence, just not control. > 1 x RFC x1967 Gemini Implementation Recommendations: opinion piece about > what Gemini is meant to be, its philosophy, its origin story. Plus > practical bits and pieces. Not normative. > Typically documents like this are not RFCs nowadays. 1 x IANA Registration for URI scheme gemini://:1965 > 1 x IANA Registration for Media Type text/gemini > There is no reason not to merge the IANA registrations into the main documents. Separate RFCs have been used in the past when the protocol or media type was already in use but there was no existing URI scheme. John Cowan http://vrici.lojban.org/~cowan cowan at ccil.org Heh, heh: ... or three pairs of wheels? I wonder what would have happened if Ravna had just read a little further. In some weird way, Twirlip knows the Secret of the Riders. --Vernor Vinge, note 601 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201227/2a2a 7d46/attachment.htm>
---
Previous in thread (3 of 40): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)
Next in thread (5 of 40): 🗣️ Solderpunk (solderpunk (a) posteo.net)