Overview suggestions (scheme and IP address in authority)
Two things that I think could be improved in the spec:
- Overview states
1. the scheme used is "gemini";
My issue with this is that it isn't mentioned again ever in the document. I believe the Requests section should make a mention of this. Overview should be a subset of highlights of the spec and not contain information that I can only find there IMHO.
- Overview states
5. the use of an IP address in the authority section SHOULD NOT be used
This sparks several thoughts within me:
- On first inspection I would prefer if it said in the host subcomponent of the authority section
- However, my other thought is who are we recommending this to? and what should happen if an IP address is used?
Host vs authority can be easily disregarded as the original text is not really wrong, I just think it guides a little better when implementing a server (because if they were to check authority is not an API but not consider the fact that such authority in some cases may have a port, then the detection of an IP address may fail, even when the host is an IP).
But I am really wrestling with the SHOULD NOT on IP address. Because I can't really do much on the server. Maybe log a warning, is that even worth it?
-
What is a client to do if an IP address is given? Nothing out of the ordinary. What could it do?
-
What is the server to do if a request is made with an IP address? Nothing out of the ordinary. What could it do?
Using domains vs IP addresses at the end of the day seems a practical choice that most people will make. The recommendation to not use IP addresses seems aimed at regular people (the person behind the client) but by allowing it and not explaining the reason why seems off to me.
At least I don't understand why that is included in the spec if nothing is really done or recommended for the client or the server, and no clarification is given on why the people using the clients should prefer Domains vs IP addresses.
Curious to hear your thoughts, thanks for your time.