[spec] List of proposed clarifications

[Stephane Bortzmeyer]

On Sun, Feb 28, 2021 at 10:23:12AM -0500,
 Adnan Maolood <me at adnano.co> wrote 
 a message of 10 lines which said:

> I'd like to keep track of proposed clarifications to the Gemini
> specification, since they seem to get buried in the mailing list. So
> I've made a list and published them on my capsule:
> 
> => gemini://adnano.co/gemini-spec-proposals/

Now that we have an issue tracker to follow the work on the final
specification <https://gitlab.com/gemini-specification>, you may want
to turn this page into tickets at this issue tracker and/or to add
ticket numbers and links in your page.

>From your list:

=> https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify that META cannot be empty
=> https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify that META cannot contain LF before the final CRLF
=> TODO Clarify that Gemini URL queries MUST (not SHOULD) use %20 instead of +
=> https://gitlab.com/gemini-specification/protocol/-/issues/2 Clarify that servers MUST send TLS close notify before closing the connection
=> TODO Clarify that clients MUST NOT send fragments to the server [IMHO, RFC 3986, section 3.5 is clear enough]
=> TODO Clarify the purpose of alt text