Tweaks from a doc readthrough

Mostly minor stuff from a readthrough.  Of particular note:

 - Regarding headers, "name-value pair" implies only one value; either it's a pair, and collections may have multiple instances with the same name; or it's a name with a collection of associated values.  Either is reasonable, but both is confusing.
 - Adjusting phrasing in SETTINGS_HEADER_TABLE_SIZE to better reflect that HPACK now lets the encoder change the table size at will.
 - Removing suggestion that a GOAWAY frame can get "lost", which can't happen in TCP; actual issue is that recipient may have acted on the previous GOAWAY and retried the requests the server says it didn't process.
Well, requires the client to open a new connection for any additional requests.  The point is that we have text describing how a client behaves when it runs out of streams, but if a server pushes frequently, the server side is going to run out before the client does.  The server then has the choice between becoming unable to push even though both sides are willing for it to do so, or sending a GOAWAY.

(If you do take something like it, though, fix my typo – GOAWAY, not GOWAY.)

From: Martin Thomson [mailto:notifications@github.com]
Sent: Friday, June 13, 2014 2:11 PM
To: http2/http2-spec
Cc: Mike Bishop
Subject: Re: [http2-spec] Tweaks from a doc readthrough (#524)


In draft-ietf-httpbis-http2.xml:

> @@ -1036,6 +1036,8 @@ HTTP2-Settings    = token68

>              Stream identifiers cannot be reused.  Long-lived connections can result in an endpoint

>              exhausting the available range of stream identifiers.  A client that is unable to

>              establish a new stream identifier can establish a new connection for new streams.

> +            A server that is unable to establish a new stream identifier may send a

> +            <x:ref>GOWAY</x:ref> frame to require the client to establish a new connection.

Not sure about this one. It doesn't quite work though, because the client isn't forced to open a new connection, it just means that the client will need a new connection for any new requests. I think that distinction is important enough to make. I'm leaning toward not including anything in this regard, honestly.

—
Reply to this email directly or view it on GitHub<https://github.com/http2/http2-spec/pull/524/files#r13771816>.