HTTP version case sensitive?
===

In 2002, Roy Fielding states that HTTP version should be case sensitive ([source][1]):

> Personally, I never had any intention that the "HTTP" be
> case-insensitive, and I am not aware of any clients that send it
> lowercase, nor any server that would accept it as lowercase.  Doing so
> is a waste of cycles.  So, I'd like that paragraph above to say:
> 
> > The version of an HTTP message is indicated by an HTTP-Version field
> > in the first line of the message.  HTTP-Version is case-sensitive.

However, [RFC 2616][2] has not been updated to include his proposal. Does this mean that his proposal was rejected and HTTP version is now case insensitive?

In other words, can a HTTP client/server send the HTTP version as `hTtP/1.1` and still claim to be standards-compatible?

  [1]: http://lists.w3.org/Archives/Public/ietf-http-wg/2002JulSep/0066.html
  [2]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.1