[http-state] terminology: "request-host" and "request-uri"

[Julian Reschke <[e-mail]>]

Hi,

the spec currently has 
(<http://tools.ietf.org/html/draft-ietf-httpstate-cookie-09#section-2.3>):

    The terms request-host and request-uri refer to the values the user
    agent would send to the server as, respectively, the host (but not
    port) and the absoluteURI (http_URL) of the HTTP Request-Line.

First of all, it would be good if ABNF terms from RFC 2616 would be 
clearly introduced as such.

Such as

    This specification adopts the definition of "http_URL" from Section
    3.2.2 of [RFC2616].

(or something similar) -- this should be done for all terms/ABNF 
productions used from other spec.

Furthermore, there's a problem request-host, which, depending on the 
format of the HTTP Request-Line will *either* come from the Host header 
field, or from the Request-Line.

In HTTPbis, we have introduced the term "Effective Request URI", see 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-10.html#rfc.section.4.3>, 
based on which extracting thee host and the request path would be 
simpler. If you don't want to rely on that definition due to spec 
timing, you may want to consider to steal the spec text (originally 
introduced by Jeff for STS, btw).

Best regards, Julian