Sometimes content producers also should read RFCs

It turs out there is a centralized place for all things gopher after
all. As unexpected (for me) as it was the gopher RFC contains
answers for all my questions as a gopher content producer, as oposed
to a gopher implementor.

I'm used to RFCs describing much more complex network protocols in
great detail. Those usually are geared toward server and client
implementors.