W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Questions in draft-09

From: Shigeki Ohtsu <ohtsu@iij.ad.jp>
Date: Wed, 08 Jan 2014 01:15:18 +0900
Message-ID: <52CC2816.2030300@iij.ad.jp>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi, I have a few questions on draft-09.

They are trivial and not serious but need to be clarified
in the draft for implementation.

1. Synchronization of HTTP2-Settings
 HTTP Upgrade is still in the spec.
 Are the values of HTTP2-Settings is acked and synchronized at
 the time of 101 response?  There is no need for endpoints to
 send and wait for a SETTINGS-ACK of HTTP2-Settings Header.

2. How to refuse a large SETTINGS_HEADER_TABLE_SIZE
 When an endpoint received a large SETTINGS_HEADER_TABLE_SIZE
  and do not want it, what to do it?

 a) The endpoint does not send SEETINGS-ACK, but it may cause
    a SETTINGS_TIMEOUT error.
 b) The endpoint sends SETTINGS-ACK but does not allocate a large
    header table and use only LiteralHeaderWithoutIndexing in
    encoding instead.
 c) others?

3. Header Ordering(8.1.3.3) and Cookie Compressing(8.1.3.4)
 An encoded cookie header can contain 0x0 in its value though it is
 not comma-separated lists and its ordering is not significant.
 In this case, is the cookie value splited and joined with '; '
 into a single cookie header?

Regards,
Received on Tuesday, 7 January 2014 16:15:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC