Header spec is ambiguous about key format

The current header specification does not specify what is considered a valid format for keys. Looking at the most common networking protocols (http/http2) we see specifics as to what keys characters are allowed and their formatting. There is no equivalent definition in thrift. 

The thrift header spec should clarify things like case sensitivity, behavior for trailing whitespace and non-ascii characters.