ietf-http-wg@w3.org from January to March 2013 by author

Adrien de Croy

• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)

Adrien W. de Croy

• Re: WGLC p6 4.2.1 (Thursday, 21 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• WGLC p6 4.2.1 (Sunday, 17 March)
• Re: Dealing with bad server chunking (Sunday, 17 March)
• Dealing with bad server chunking (Friday, 15 March)
• Re: [HTTP/1.1] method length and 501 Not Implemented (Tuesday, 12 March)
• Intercepting proxies - yet again (Thursday, 7 March)
• Re: HTTP/2 Header Encoding Status Update (Sunday, 3 March)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: A mechanism to encode HTTP version information in DNS (Saturday, 16 February)
• Re: A mechanism to encode HTTP version information in DNS (Friday, 15 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Wednesday, 6 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: #430 / #268 - definition of "public" (Wednesday, 30 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 19 January)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 19 January)
• Re: bohe and delta experimentation... (Saturday, 19 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: Heuristic caching without validators (Thursday, 17 January)
• Heuristic caching without validators (Thursday, 17 January)

Albert Lunde

• Re: The document's address (Friday, 8 March)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)

Alexander Dutton

• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)

Alexey Melnikov

• Proposed text for "Routing Data's relationship to headers" (Issue 23) (Wednesday, 13 March)

Amos Jeffries

• Re: p6: Returning the freshest response (Sunday, 31 March)
• Re: REFUSED_STREAM and CANCEL (Wednesday, 27 March)
• Re: Header compression: buffer management (Thursday, 21 March)
• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: [HTTP/1.1] method length and 501 Not Implemented (Wednesday, 13 March)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: SYN_REPLY (Thursday, 28 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Thursday, 28 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: WGLC issue: ambiguity in part 1 example (Wednesday, 27 February)
• Re: #41: Header Block field name length (Tuesday, 26 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Saturday, 23 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Saturday, 23 February)
• Re: Request Routing Information [was: Do we kill the (Saturday, 23 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: #430 / #268 - definition of "public" (Tuesday, 19 February)
• Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" (Monday, 18 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• WGLC issue: ambiguity in part 1 example (Sunday, 17 February)
• Re: A mechanism to encode HTTP version information in DNS (Saturday, 16 February)
• Re: How to determine server's decoding capability before sending entity? (Friday, 15 February)
• Re: http/2 prioritization/fairness bug with proxies (Friday, 15 February)
• Re: A mechanism to encode HTTP version information in DNS (Friday, 15 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: #430 / #268 - definition of "public" (Friday, 8 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Monday, 28 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Sunday, 27 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 19 January)
• Re: Cache-Cache and Binary Encoding (Saturday, 19 January)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 19 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)

Ashok Kumar

• Re: http/2 prioritization/fairness bug with proxies (Friday, 8 February)

Barry Leiba

• Re: Interim Meeting - next week (Monday, 21 January)
• Re: [editorial] awkward sentence for a MUST statement in section 6.3 Upgrade (Tuesday, 8 January)
• Re: draft-snell-http-prefer-17 feedback (Tuesday, 8 January)
• Re: draft-snell-http-prefer-17 feedback (Friday, 4 January)

Ben Niven-Jenkins

• Caching 412 responses (Saturday, 16 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)

Benjamin Carlyle

• Re: delta encoding and state management (Thursday, 24 January)

Bjoern Hoehrmann

• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Wednesday, 20 March)
• Re: WGLC issue: token68 in p7 (Wednesday, 20 March)
• Comments on draft-ietf-httpbis-p4-conditional-22 (Monday, 18 March)
• Comments on draft-ietf-httpbis-p5-range-22 (Monday, 18 March)
• Comments on draft-ietf-httpbis-p6-cache-22 (Monday, 18 March)
• Comments on draft-ietf-httpbis-p7-auth-22 (Monday, 18 March)
• Comments on draft-ietf-httpbis-method-registrations-11 (Monday, 18 March)
• Comments on draft-ietf-httpbis-authscheme-registrations-06 (Monday, 18 March)
• Re: Dealing with bad server chunking (Friday, 15 March)
• Re: [HTTP/1.1] method length and 501 Not Implemented (Tuesday, 12 March)
• Re: [HTTP/1.1] method length and 501 Not Implemented (Tuesday, 12 March)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: Status of 308 Status Code draft (Wednesday, 23 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)

Brian Pane

• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)

Brian Raymor (MS OPEN TECH)

• ALPN OpenSSL implementation (Friday, 15 March)
• Removing CREDENTIAL (Thursday, 21 February)
• HTTP 2.0 next steps and TLS next protocol negotiation (Tuesday, 12 February)
• New version of [TLS} Application Layer Protocol Negotiation (Thursday, 7 February)

Carsten Bormann

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)

Chris Elving

• Re: HTTP/2.0 Magic (Friday, 1 February)

Cyrus Daboo

• Re: Multi-GET, extreme compression? (Sunday, 17 February)
• Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)

Daniel Stenberg

• Re: Dealing with bad server chunking (Friday, 15 March)

Dave Thaler

• draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion (Thursday, 28 March)

David Kendal

• Re: Giving the Framing Layer a real name (Thursday, 7 March)

David Morris

• Re: Dealing with bad server chunking (Friday, 15 March)
• Re: HTTP/2.0 Magic (Friday, 22 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• Re: #430 / #268 - definition of "public" (Wednesday, 30 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)

Dr Robert Mattson

• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)

DRUTA, DAN

• RE: #40 - HTTP2 default value for client supported max_concurrent_streams (Wednesday, 6 March)

Eitan Adler

• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: The document's address (Friday, 8 March)

Eliezer Croitoru

• Re: Do we kill the "Host:" header in HTTP/2 ? (Sunday, 3 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)

Eliot Lear

• Re: DNS record support and draft-lear-httpbis-svcinfo-rr (Monday, 25 March)
• DNS record support and draft-lear-httpbis-svcinfo-rr (Monday, 25 March)
• Cisco Research looking for proposals to analyze HTTP 2.0 (Friday, 15 March)
• Re: HTTP/2 Header Encoding Status Update (Monday, 4 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Fwd: New Version Notification for draft-lear-httpbis-svcinfo-rr-01.txt (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Thursday, 21 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 19 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 12 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Monday, 11 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)

Eric J. Bowman

• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 14 February)
• Re: #428 Accept-Language ordering for identical qvalues (Wednesday, 13 February)
• Re: #428 Accept-Language ordering for identical qvalues (Wednesday, 13 February)

Fabian Keil

• Re: WGLC p6 4.2.1 (Monday, 18 March)

Fred Akalin

• Re: delta compression I-D 01 (Sunday, 17 March)
• Re: delta compression I-D 01 (Friday, 15 March)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)

Frédéric Kayser

• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Header compression: http1_huffman (Friday, 25 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 14 January)
• Re: Some general thought on CRIME and Compression and Headers (Saturday, 12 January)

Gabriel Montenegro

• RE: #40 - HTTP2 default value for client supported max_concurrent_streams (Wednesday, 27 February)
• RE: #40 - HTTP2 default value for client supported max_concurrent_streams (Tuesday, 26 February)
• RE: #40 - HTTP2 default value for client supported max_concurrent_streams (Sunday, 24 February)
• RE: #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• RE: Outstanding Action Items (Wednesday, 6 February)

Grahame Grieve

• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)

Greg Wilkins

• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)

Grzegorz Calkowski

• PUT, If-Match, 412 - over-constrained? (Friday, 22 February)

Gábor Molnár

• Re: Project idea (Monday, 25 March)
• Project idea (Thursday, 14 March)

Hasan Khalil

• Re: SYN_REPLY (Wednesday, 27 February)

Hassnaa Moustafa

• Re: Should Web Services be served by a different HTTP n+1? (Monday, 28 January)

Helge Hess

• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)

Helge Heß

• Re: Multi-GET, extreme compression? (Sunday, 17 February)

Herbert van de Sompel

• Memento Internet Draft, new version (Tuesday, 26 February)

Ilari Liusvaara

• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)

Ilya Grigorik

• Re: Project idea (Thursday, 14 March)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: FYI: Tools to evaluate header compression algorithms (Sunday, 6 January)

internet-drafts@ietf.org

• I-D Action: draft-ietf-httpbis-authscheme-registrations-06.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-method-registrations-11.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p2-semantics-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p1-messaging-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p7-auth-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p6-cache-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p5-range-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-p4-conditional-22.txt (Saturday, 23 February)
• I-D Action: draft-ietf-httpbis-http2-01.txt (Monday, 21 January)

James Cloos

• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: Delta Compression and UTF-8 Header Values (Tuesday, 12 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)

James M Snell

• Re: Choosing a header compression algorithm (Friday, 29 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: Header compression: header set diff (Monday, 25 March)
• Re: Header compression: header set diff (Friday, 22 March)
• Re: Header compression: header set diff (Thursday, 21 March)
• Re: Header compression: header set diff (Thursday, 21 March)
• Re: Choosing a header compression algorithm (Thursday, 21 March)
• Re: Header compression: buffer management (Thursday, 21 March)
• Delta I-D update feedback (Wednesday, 20 March)
• Re: delta compression I-D 01 (Wednesday, 13 March)
• Re: delta compression I-D 01 (Wednesday, 13 March)
• Fwd: New Version Notification for draft-snell-httpbis-mget-00.txt (Tuesday, 12 March)
• Re: Maximum Frame Size (Monday, 11 March)
• Re: HTTP/2 Header Encoding Status Update (Sunday, 3 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Friday, 1 March)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: #43: SYN_REPLY (Tuesday, 26 February)
• Re: Permitted characters for http keys (Monday, 25 February)
• Re: Permitted characters for http keys (Monday, 25 February)
• Re: Upgrade status for impl draft 1 (Thursday, 21 February)
• Fwd: New Version Notification for draft-snell-httpbis-bohe-03.txt (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Sunday, 17 February)
• Updated BOHE I-D... (Thursday, 14 February)
• Re: #428 Accept-Language ordering for identical qvalues (Wednesday, 13 February)
• HTTP Origin and Hop Hints and Prefer Header (Tuesday, 12 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: Next Steps for HTTP/2.0 (Tuesday, 5 February)
• Lucky 13 TLS Attack... (Tuesday, 5 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Header Stats (Wednesday, 23 January)
• Header Stats (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Sunday, 20 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Sunday, 20 January)
• Cache-Cache and Binary Encoding (Friday, 18 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Friday, 18 January)
• Set-Cookie and Cookie Optimized Binary Encoding (Friday, 18 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• delta encoding and state management (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe implementation for compression tests (Tuesday, 15 January)
• Re: bohe implementation for compression tests (Tuesday, 15 January)
• Re: bohe implementation for compression tests (Tuesday, 15 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 14 January)
• Re: HTTPS, proxying, and all that... (Monday, 14 January)
• Re: HTTPS, proxying, and all that... (Monday, 14 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 14 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 11 January)
• Some general thought on CRIME and Compression and Headers (Friday, 11 January)
• Re: bohe implementation for compression tests (Friday, 11 January)
• Re: bohe implementation for compression tests (Thursday, 10 January)
• bohe implementation for compression tests (Thursday, 10 January)
• Re: draft-snell-http-prefer-17 feedback (Monday, 7 January)

Jeff Pinner

• Re: Header field-name token and leading spaces (Sunday, 3 March)
• Re: SYN_REPLY (Thursday, 28 February)
• Re: Giving the Framing Layer a real name (Thursday, 28 February)

Julian Reschke

• Re: WGLC: p5 editorial nits (Sunday, 31 March)
• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 25 March)
• Re: Working Group Last Call on the HTTPbis document set (Thursday, 21 March)
• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• Re: WGLC: p7 editorial nits (Tuesday, 19 March)
• Re: WGLC issue: token68 in p7 (Tuesday, 19 March)
• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 18 March)
• draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 18 March)
• Re: Comments on draft-ietf-httpbis-p4-conditional-22 (Monday, 18 March)
• Re: Comments on draft-ietf-httpbis-p7-auth-22 (Monday, 18 March)
• Re: Comments on draft-ietf-httpbis-authscheme-registrations-06 (Monday, 18 March)
• Re: Dealing with bad server chunking (Friday, 15 March)
• Reminder: WG meeting today (Friday, 15 March)
• Re: The document's address (Friday, 8 March)
• Re: The document's address (Friday, 8 March)
• Re: Preference-Applied Response Header (Thursday, 7 March)
• Re: Preference-Applied Response Header (Thursday, 7 March)
• Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" (Wednesday, 6 March)
• draft-ietf-httpbis-http2-01, "4.2.3 Authentication" (Tuesday, 5 March)
• Re: Multi-GET, extreme compression? (Monday, 4 March)
• Re: Header field-name token and leading spaces (Sunday, 3 March)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• #433, was: WGLC issue: ambiguity in part 1 example (Tuesday, 19 February)
• #434: mention in header field considerations that leading/trailing WS is lossy (Tuesday, 19 February)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 16 February)
• Re: #431: URI path starting with "//" (Monday, 11 February)
• Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: #431: URI path starting with "//" (Sunday, 10 February)
• Re: #431: URI path starting with "//" (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Using Github for HTTP2 (Sunday, 10 February)
• Re: #431: URI path starting with "//" (Friday, 8 February)
• Re: #430 / #268 - definition of "public" (Sunday, 3 February)
• Re: [Technical Errata Reported] RFC6266 (3475) (Sunday, 3 February)
• #431: URI path starting with "//" (Saturday, 2 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Monday, 28 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Monday, 28 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Friday, 25 January)
• can a conditional header field put conditions on resources other than the target resource? (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 25 January)
• #96 Conditional GET text (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Types of Web Service (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• #428 Accept-Language ordering for identical qvalues (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: [editorial] awkward sentence for a MUST statement in section 6.3 Upgrade (Tuesday, 8 January)
• Re: WebDAV If header field and HTTP conditional precedence (Friday, 4 January)

Karl Dubost

• Re: [HTTP/1.1] method length and 501 Not Implemented (Tuesday, 12 March)
• [HTTP/1.1] method length and 501 Not Implemented (Tuesday, 12 March)
• Re: "In the wild" use case for Accept-Charset with parameters; musings on a modern alternative (Tuesday, 12 March)
• Re: Giving the Framing Layer a real name (Monday, 11 March)
• Re: Header field-name token and leading spaces (Sunday, 3 March)
• Header field-name token and leading spaces (Sunday, 3 March)
• HTML Form HTTP Extensions (Friday, 22 February)
• Re: URI path starting with "//" (Monday, 4 February)
• Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 29 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• [editorial] awkward sentence for a MUST statement in section 6.3 Upgrade (Tuesday, 8 January)

Ken Murchison

• WGLC: p4 304 (Not Modified) (Saturday, 30 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• WGLC: p5 editorial nits (Thursday, 28 March)
• WGLC: p4 editorial nits (Tuesday, 26 March)
• WGLC: p6 editorial nits (Monday, 25 March)
• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• WGLC: p1 editorial nits (Tuesday, 19 March)
• Re: WGLC issue: token68 in p7 (Tuesday, 19 March)
• WGLC: p7 editorial nits (Tuesday, 19 March)
• WGLC issue: token68 in p7 (Tuesday, 19 March)
• Re: Preference-Applied Response Header (Thursday, 7 March)
• Preference-Applied Response Header (Thursday, 7 March)

Larry Masinter

• RE: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)

Manger, James H

• Re: WGLC issue: token68 in p7 (Thursday, 21 March)
• RE: WGLC issue: token68 in p7 (Wednesday, 20 March)

Mark Baker

• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Saturday, 2 February)

Mark Nottingham

• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• p6: Returning the freshest response (Friday, 29 March)
• Re: Choosing a header compression algorithm (Monday, 25 March)
• Re: Choosing a header compression algorithm (Monday, 25 March)
• Re: Choosing a header compression algorithm (Friday, 22 March)
• Choosing a header compression algorithm (Thursday, 21 March)
• Re: WGLC p6 4.2.1 (Wednesday, 20 March)
• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 18 March)
• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 18 March)
• Planning for Future Meetings (Monday, 18 March)
• Working Group Last Call on the HTTPbis document set (Sunday, 17 March)
• Minutes from Orlando (Sunday, 17 March)
• Re: Project idea (Thursday, 14 March)
• Re: iwebpp.io announce - run peer/p2p web service with Node.js (Thursday, 14 March)
• Re: iwebpp.io announce - run peer/p2p web service with Node.js (Wednesday, 13 March)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Can't see error codes in HTML version of http://http2.github.com/http2-spec/#RST_STREAM (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Tuesday, 26 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Tuesday, 26 February)
• Re: Upgrade status for impl draft 1 (Tuesday, 26 February)
• #43: SYN_REPLY (Tuesday, 26 February)
• #41: Header Block field name length (Monday, 25 February)
• Re: Permitted characters for http keys (Monday, 25 February)
• Re: Permitted characters for http keys (Monday, 25 February)
• Draft agenda for Orlando (Monday, 25 February)
• Issues addressed in the -22 drafts (Monday, 25 February)
• Re: Using Github for HTTP2 (Monday, 25 February)
• Re: HTTP/2.0 Magic (Sunday, 24 February)
• Re: HTTP/2.0 Magic (Sunday, 24 February)
• Re: Using Github for HTTP2 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" (Friday, 22 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: Removing CREDENTIAL (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Upgrade status for impl draft 1 (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Tuesday, 19 February)
• Re: HTTP/2.0 Magic (Tuesday, 19 February)
• Re: HTTP/2.0 Magic (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: #430 / #268 - definition of "public" (Tuesday, 19 February)
• Re: HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items] (Monday, 18 February)
• Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Outstanding Action Items (Monday, 18 February)
• Re: Outstanding Action Items (Monday, 18 February)
• Re: Outstanding Action Items (Monday, 18 February)
• Re: WGLC issue: ambiguity in part 1 example (Monday, 18 February)
• Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" (Monday, 18 February)
• Re: #430 / #268 - definition of "public" (Monday, 18 February)
• Re: HTTP/1.1 #223: Allowing heuristic caching for new status codes (Monday, 18 February)
• Re: HTTP Origin and Hop Hints and Prefer Header (Tuesday, 12 February)
• Fwd: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" (Monday, 11 February)
• HTTP/1.1 #223: Allowing heuristic caching for new status codes (Monday, 11 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Using Github for HTTP2 (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Using Github for HTTP2 (Friday, 8 February)
• Re: httpbis - Requested session has been scheduled for IETF 86 (Thursday, 7 February)
• Fwd: httpbis - Requested session has been scheduled for IETF 86 (Thursday, 7 February)
• Re: Minutes from the Tokyo interim meeting (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: Outstanding Action Items (Tuesday, 5 February)
• Re: Next Steps for HTTP/2.0 (Tuesday, 5 February)
• Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Outstanding Action Items (Tuesday, 5 February)
• Next Steps for HTTP/2.0 (Tuesday, 5 February)
• Re: URI path starting with "//" (Tuesday, 5 February)
• Minutes from the Tokyo interim meeting (Tuesday, 5 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• #430 / #268 - definition of "public" (Wednesday, 30 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 28 January)
• Re: [httpbis] #223: Allowing heuristic caching for new status codes (Sunday, 27 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Thursday, 24 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 21 January)
• Interim Meeting - next week (Monday, 21 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: #409: is parsing OBS-FOLD mandatory? (Sunday, 20 January)
• Re: Lingering Close (Sunday, 20 January)
• #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Sunday, 20 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Sunday, 20 January)
• Re: #409: is parsing OBS-FOLD mandatory? (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Saturday, 19 January)
• Re: delta encoding and state management (Saturday, 19 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe implementation for compression tests (Friday, 18 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: Heuristic caching without validators (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: Heuristic caching without validators (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Draft agenda for Interim Meeting (Tuesday, 15 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 14 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 14 January)
• Re: #409: is parsing OBS-FOLD mandatory? (Wednesday, 9 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 7 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 7 January)
• Re: FYI: Tools to evaluate header compression algorithms (Sunday, 6 January)

Martin J. Dürst

• Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" (Monday, 25 March)
• Re: HTTP/2 Header Encoding Status Update (Thursday, 28 February)
• Re: Permitted characters for http keys (Monday, 25 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Wednesday, 6 February)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 28 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• Re: FYI: Tools to evaluate header compression algorithms (Sunday, 6 January)

Martin Nilsson

• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: FYI: Tools to evaluate header compression algorithms (Thursday, 10 January)

Martin Thomson

• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: p6: Returning the freshest response (Friday, 29 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: INVALID_STREAM and STREAM_ALREADY_CLOSED (Tuesday, 26 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• INVALID_STREAM and STREAM_ALREADY_CLOSED (Tuesday, 26 March)
• REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: Choosing a header compression algorithm (Friday, 22 March)
• Re: Maximum Frame Size (Monday, 11 March)
• Talking to yourself (Monday, 11 March)
• Complete Request Flow (Monday, 11 March)
• Re: The document's address (Friday, 8 March)
• Re: Maximum Frame Size (Tuesday, 5 March)
• Maximum Frame Size (Monday, 4 March)
• Re: SYN_REPLY (Thursday, 28 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Thursday, 28 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Thursday, 28 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: HTTP/2 Header Encoding Status Update (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Thursday, 21 February)
• Re: SYN_REPLY (Thursday, 21 February)
• SYN_REPLY (Thursday, 21 February)
• Streaming layer in HTTP/2.0 (Thursday, 21 February)
• Re: Upgrade status for impl draft 1 (Thursday, 21 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Interaction of WINDOW_UPDATE and SETTINGS for Flow Control (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: Permitted characters for http keys (Tuesday, 19 February)
• Re: HTTP/2.0 Magic (Tuesday, 19 February)
• Re: #428 Accept-Language ordering for identical qvalues (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• HTTP/2.0 Magic (Friday, 1 February)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• -01 posted (Monday, 21 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Friday, 18 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Friday, 18 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: Some general thought on CRIME and Compression and Headers (Thursday, 17 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 17 January)

Mike Belshe

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: http/2 prioritization/fairness bug with proxies (Sunday, 10 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Sunday, 10 February)
• Re: http/2 flow control (Monday, 28 January)

Nicholas Shanks

• "In the wild" use case for Accept-Charset with parameters; musings on a modern alternative (Tuesday, 12 March)
• Re: The document's address (Friday, 8 March)
• Re: The document's address (Friday, 8 March)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 16 February)
• Re: [apps-discuss] New Version Notification for draft-wilde-xml-patch-00.txt (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 21 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: The document's address (Friday, 18 January)

Nico Williams

• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Tuesday, 19 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 19 February)
• Re: http/2 prioritization/fairness bug with proxies (Thursday, 14 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 12 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: URI path starting with "//" (Saturday, 2 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: http/2 flow control (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: http/2 flow control (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Sunday, 20 January)
• Re: Set-Cookie and Cookie Optimized Binary Encoding (Sunday, 20 January)
• Re: #428 Accept-Language ordering for identical qvalues (Saturday, 19 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: HTTPS, proxying, and all that... (Monday, 14 January)
• Re: Some general thought on CRIME and Compression and Headers (Monday, 14 January)

Nicolas mailhot

• Re: Intercepting proxies - yet again (Thursday, 7 March)
• Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" (Wednesday, 6 March)
• Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" (Wednesday, 6 March)
• Re: HTTP/2 Header Encoding Status Update (Monday, 4 March)
• Re: HTTP/2 Header Encoding Status Update (Monday, 4 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Friday, 1 March)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: Multi-GET, extreme compression? (Wednesday, 27 February)
• Re: Request Routing Information [was: Do we kill the (Friday, 22 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 22 February)

Osama Mazahir

• RE: Dealing with bad server chunking (Thursday, 21 March)
• RE: Dealing with bad server chunking (Friday, 15 March)
• RE: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• RE: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• HTTP/2.0 Max Frame Size (Wednesday, 23 January)

Pablo

• The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)

Patrick McManus

• Re: DNS record support and draft-lear-httpbis-svcinfo-rr (Monday, 25 March)
• Re: Header compression: header set diff (Thursday, 21 March)
• Re: Maximum Frame Size (Tuesday, 5 March)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: Constant priotrity (Was: SYN_REPLY) (Saturday, 23 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Saturday, 23 February)
• Re: SYN_REPLY (Saturday, 23 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Tuesday, 12 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Sunday, 10 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: delta encoding and state management (Thursday, 24 January)
• Re: delta encoding and state management (Thursday, 24 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)

Phillip Hallam-Baker

• Re: Multi-GET, extreme compression? (Monday, 4 March)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Re: A mechanism to encode HTTP version information in DNS (Sunday, 17 February)
• Multi-GET, extreme compression? (Saturday, 16 February)
• Re: A mechanism to encode HTTP version information in DNS (Saturday, 16 February)
• A mechanism to encode HTTP version information in DNS (Thursday, 14 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Types of Web Service (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Types of Web Service (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Should Web Services be served by a different HTTP n+1? (Friday, 11 January)

Piotr Dobrogost

• Status of 308 Status Code draft (Wednesday, 23 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)

Poul-Henning Kamp

• Re: Header compression: buffer management (Friday, 22 March)
• Re: Header compression: buffer management (Friday, 22 March)
• Re: Header compression: buffer management (Thursday, 21 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: WGLC p6 4.2.1 (Monday, 18 March)
• Re: Proposed text for "Routing Data's relationship to headers" (Issue 23) (Wednesday, 13 March)
• Re: HTTP/2 Header Encoding Status Update (Monday, 4 March)
• Re: HTTP/2 Header Encoding Status Update (Monday, 4 March)
• Re: Header field-name token and leading spaces (Sunday, 3 March)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Some general thought on CRIME and Compression and Headers (Saturday, 12 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• HTTPS, proxying, and all that... (Friday, 11 January)

Robert Brewer

• RE: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)

Robert Collins

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)

Roberto Peon

• Re: Choosing a header compression algorithm (Friday, 29 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: Choosing a header compression algorithm (Thursday, 28 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: INVALID_STREAM and STREAM_ALREADY_CLOSED (Tuesday, 26 March)
• Re: Choosing a header compression algorithm (Tuesday, 26 March)
• Re: Choosing a header compression algorithm (Tuesday, 26 March)
• Re: Project idea (Monday, 25 March)
• Re: Choosing a header compression algorithm (Monday, 25 March)
• Re: Choosing a header compression algorithm (Saturday, 23 March)
• Re: Choosing a header compression algorithm (Friday, 22 March)
• Re: Choosing a header compression algorithm (Friday, 22 March)
• Re: Header compression: header set diff (Thursday, 21 March)
• Re: Choosing a header compression algorithm (Thursday, 21 March)
• Re: Header compression: buffer management (Thursday, 21 March)
• Re: Header compression: header set diff (Thursday, 21 March)
• Re: delta compression I-D 01 (Wednesday, 13 March)
• delta compression I-D 01 (Wednesday, 13 March)
• Re: Giving the Framing Layer a real name (Thursday, 28 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Thursday, 28 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Thursday, 28 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: #41: Header Block field name length (Tuesday, 26 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: HeaderDiff specification (Friday, 22 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: HeaderDiff specification (Friday, 22 February)
• Re: Constant priotrity (Was: SYN_REPLY) (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Friday, 22 February)
• Re: SYN_REPLY (Thursday, 21 February)
• Re: SYN_REPLY (Thursday, 21 February)
• Re: SYN_REPLY (Thursday, 21 February)
• Re: Streaming layer in HTTP/2.0 (Thursday, 21 February)
• Re: Removing CREDENTIAL (Thursday, 21 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Permitted characters for http keys (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Sunday, 17 February)
• Re: http/2 prioritization/fairness bug with proxies (Thursday, 14 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: Delta Compression and UTF-8 Header Values (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 12 February)
• Re: HTTP 2.0 next steps and TLS next protocol negotiation (Tuesday, 12 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Monday, 11 February)
• RE: proposed WINDOW_UPDATE text for session flow control windows (Monday, 11 February)
• Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) (Monday, 11 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Friday, 8 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: http/2 prioritization/fairness bug with proxies (Friday, 8 February)
• Re: Framing and control-frame continuations (Friday, 8 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Wednesday, 6 February)
• Re: Outstanding Action Items (Tuesday, 5 February)
• Framing and control-frame continuations (Tuesday, 5 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: Outstanding Action Items (Tuesday, 5 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Saturday, 2 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: Should Web Services be served by a different HTTP n+1? (Tuesday, 29 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: http/2 flow control (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• RE: bohe and delta experimentation... (Friday, 18 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: bohe implementation for compression tests (Thursday, 17 January)
• Re: bohe and delta experimentation... (Thursday, 17 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe and delta experimentation... (Wednesday, 16 January)
• Re: bohe implementation for compression tests (Tuesday, 15 January)
• Re: bohe implementation for compression tests (Tuesday, 15 January)
• Re: HTTPS, proxying, and all that... (Monday, 14 January)
• Re: Some general thought on CRIME and Compression and Headers (Saturday, 12 January)
• Re: bohe implementation for compression tests (Thursday, 10 January)
• Re: FYI: Tools to evaluate header compression algorithms (Monday, 7 January)
• Re: FYI: Tools to evaluate header compression algorithms (Sunday, 6 January)

Roland Zink

• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Framing and control-frame continuations (Wednesday, 6 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)

Roy T. Fielding

• Re: WGLC p6 4.2.1 (Tuesday, 19 March)
• Re: Host header with an empty value? (Tuesday, 19 March)
• Re: WGLC issue: ambiguity in part 1 example (Wednesday, 27 February)
• Re: WGLC issue: ambiguity in part 1 example (Tuesday, 26 February)
• Re: #428 Accept-Language ordering for identical qvalues (Wednesday, 13 February)
• Re: #430 / #268 - definition of "public" (Friday, 8 February)
• Re: URI path starting with "//" (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• Re: #430 / #268 - definition of "public" (Thursday, 31 January)
• Re: #430 / #268 - definition of "public" (Wednesday, 30 January)
• Re: [httpbis] #223: Allowing heuristic caching for new status codes (Monday, 28 January)
• Re: can a conditional header field put conditions on resources other than the target resource? (Friday, 25 January)
• Re: #96 Conditional GET text (Friday, 25 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 24 January)
• Re: #428 Accept-Language ordering for identical qvalues (Tuesday, 22 January)
• Re: #428 Accept-Language ordering for identical qvalues (Monday, 21 January)
• Re: #428 Accept-Language ordering for identical qvalues (Sunday, 20 January)
• Re: The document's address (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Friday, 18 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• Re: #428 Accept-Language ordering for identical qvalues (Thursday, 17 January)
• Re: Heuristic caching without validators (Thursday, 17 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: WGLC review of p2-semantics (editorial stuff) (Monday, 14 January)

RUELLAN Herve

• RE: Header compression: header set diff (Friday, 29 March)
• RE: Choosing a header compression algorithm (Friday, 29 March)
• RE: Choosing a header compression algorithm (Thursday, 28 March)
• RE: Choosing a header compression algorithm (Thursday, 28 March)
• RE: HeaderDiff specification (Tuesday, 26 March)
• RE: Choosing a header compression algorithm (Tuesday, 26 March)
• RE: Header compression: header set diff (Monday, 25 March)
• RE: Choosing a header compression algorithm (Monday, 25 March)
• Updated delta-encoding of values (Friday, 22 March)
• RE: Choosing a header compression algorithm (Friday, 22 March)
• RE: Header compression: buffer management (Friday, 22 March)
• RE: Header compression: buffer management (Friday, 22 March)
• RE: Header compression: header set diff (Friday, 22 March)
• RE: Header compression: header set diff (Friday, 22 March)
• RE: Choosing a header compression algorithm (Friday, 22 March)
• Header compression: buffer management (Thursday, 21 March)
• Header compression: header set diff (Thursday, 21 March)
• RE: Choosing a header compression algorithm (Thursday, 21 March)
• HeaderDiff draft (Monday, 18 March)
• RE: SYN_REPLY (Thursday, 28 February)
• RE: #41: Header Block field name length (Tuesday, 26 February)
• RE: HeaderDiff specification (Monday, 25 February)
• HeaderDiff specification (Friday, 22 February)
• RE: proposed WINDOW_UPDATE text for session flow control windows (Monday, 11 February)
• RE: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• RE: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• RE: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• RE: Header Stats (Wednesday, 23 January)
• RE: bohe and delta experimentation... (Monday, 21 January)
• RE: bohe and delta experimentation... (Friday, 18 January)
• RE: delta encoding and state management (Friday, 18 January)
• RE: bohe and delta experimentation... (Thursday, 17 January)
• RE: FYI: Tools to evaluate header compression algorithms (Wednesday, 16 January)

Scott Schmit

• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: HTTP/2.0 Magic (Saturday, 23 February)

Stefan Eissing

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• state management on connections (Wednesday, 23 January)

Stephane Bortzmeyer

• Re: HTTPS, proxying, and all that... (Monday, 14 January)

Stephen Farrell

• Re: Choosing a header compression algorithm (Thursday, 21 March)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)

Ted Hardie

• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Thursday, 28 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)

Thomas Maslen

• RE: Maximum Frame Size (Monday, 11 March)
• RE: Maximum Frame Size (Monday, 11 March)

Tim Bray

• Re: URI path starting with "//" (Friday, 1 February)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-02.txt (Saturday, 12 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 11 January)

Tim Williams

• httpbis (Thursday, 3 January)

tom

• Re: iwebpp.io announce - run peer/p2p web service with Node.js (Thursday, 14 March)
• Re: iwebpp.io announce - run peer/p2p web service with Node.js (Thursday, 14 March)
• iwebpp.io announce - run peer/p2p web service with Node.js (Wednesday, 13 March)

TZI

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)

Willy Tarreau

• Re: delta compression I-D 01 (Sunday, 17 March)
• Re: Host header with an empty value? (Saturday, 16 March)
• Re: Host header with an empty value? (Saturday, 16 March)
• Re: Dealing with bad server chunking (Friday, 15 March)
• Re: Dealing with bad server chunking (Friday, 15 March)
• Re: Giving the Framing Layer a real name (Thursday, 7 March)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Tuesday, 26 February)
• Re: Upgrade status for impl draft 1 (Tuesday, 26 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: Upgrade status for impl draft 1 (Friday, 22 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Thursday, 21 February)
• Re: HTTP/2.0 Magic (Tuesday, 19 February)
• Re: HTTP/2.0 Magic (Tuesday, 19 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Delta Compression and UTF-8 Header Values (Saturday, 9 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Friday, 1 February)
• Re: HTTP/2.0 Magic (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Wednesday, 30 January)
• Re: delta encoding and state management (Thursday, 24 January)
• Re: delta encoding and state management (Thursday, 24 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: #409: is parsing OBS-FOLD mandatory? (Sunday, 20 January)
• Re: Lingering Close (Sunday, 20 January)
• Re: #409: is parsing OBS-FOLD mandatory? (Sunday, 20 January)
• Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Sunday, 20 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: bohe and delta experimentation... (Friday, 18 January)
• Re: delta encoding and state management (Thursday, 17 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)

wrong string

• 答复: HeaderDiff specification (Tuesday, 26 March)

Yehia El-khatib

• Re: Giving the Framing Layer a real name (Wednesday, 27 February)

Yi, EungJun

• How to determine server's decoding capability before sending entity? (Friday, 15 February)

Yoav Nir

• Re: Giving the Framing Layer a real name (Thursday, 7 March)
• Re: HTTP/2 Header Encoding Status Update (Saturday, 2 March)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Constant priotrity (Was: SYN_REPLY) (Friday, 22 February)
• Re: HTTP 2.0 next steps and TLS next protocol negotiation (Tuesday, 12 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 12 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: Should Web Services be served by a different HTTP n+1? (Tuesday, 29 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Session Continuation at WebSec (Monday, 14 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)
• Re: HTTPS, proxying, and all that... (Friday, 11 January)

Yves Lafon

• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Monday, 7 January)

Zhong Yu

• Re: Host header with an empty value? (Tuesday, 19 March)
• Re: Host header with an empty value? (Saturday, 16 March)
• Host header with an empty value? (Saturday, 16 March)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: Delta Compression and UTF-8 Header Values (Sunday, 10 February)
• Re: #431: URI path starting with "//" (Sunday, 10 February)
• Re: #431: URI path starting with "//" (Friday, 8 February)
• Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] (Tuesday, 5 February)
• Re: URI path starting with "//" (Friday, 1 February)
• URI path starting with "//" (Friday, 1 February)
• Re: Do we kill the "Host:" header in HTTP/2 ? (Thursday, 31 January)
• Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" (Thursday, 24 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 16 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Tuesday, 15 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)
• Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? (Wednesday, 9 January)

陈智昌

• Re: INVALID_STREAM and STREAM_ALREADY_CLOSED (Tuesday, 26 March)
• Re: INVALID_STREAM and STREAM_ALREADY_CLOSED (Tuesday, 26 March)
• Re: REFUSED_STREAM and CANCEL (Tuesday, 26 March)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Wednesday, 6 March)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Thursday, 28 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Giving the Framing Layer a real name (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: Upgrade status for impl draft 1 (Wednesday, 27 February)
• Can't see error codes in HTML version of http://http2.github.com/http2-spec/#RST_STREAM (Wednesday, 27 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Wednesday, 27 February)
• Re: SYN_REPLY (Wednesday, 27 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Wednesday, 27 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Tuesday, 26 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: #43: SYN_REPLY (Tuesday, 26 February)
• Re: SYN_REPLY (Tuesday, 26 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Sunday, 24 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Saturday, 23 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: #38 - HTTP2 min value for server supported max_concurrent_streams (Friday, 22 February)
• Re: #40 - HTTP2 default value for client supported max_concurrent_streams (Friday, 22 February)
• Re: Using Github for HTTP2 (Friday, 22 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Wednesday, 20 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Tuesday, 19 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 19 February)
• HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items] (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Monday, 18 February)
• Re: Multi-GET, extreme compression? (Saturday, 16 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Saturday, 16 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Friday, 15 February)
• Re: http/2 prioritization/fairness bug with proxies (Wednesday, 13 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 11 February)
• Re: http/2 prioritization/fairness bug with proxies (Sunday, 10 February)
• Re: proposed WINDOW_UPDATE text for session flow control windows (Sunday, 10 February)
• Re: Using Github for HTTP2 (Sunday, 10 February)
• proposed WINDOW_UPDATE text for session flow control windows (Sunday, 10 February)
• Re: Using Github for HTTP2 (Sunday, 10 February)
• Re: Framing and control-frame continuations (Thursday, 7 February)
• Re: Outstanding Action Items (Wednesday, 6 February)
• Re: moving forward on draft-lear-httpbis-svcinfo-rr (Tuesday, 5 February)
• Re: http/2 prioritization/fairness bug with proxies (Tuesday, 5 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• http/2 prioritization/fairness bug with proxies (Monday, 4 February)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• Re: Should Web Services be served by a different HTTP n+1? (Friday, 25 January)
• http/2 flow control (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: Should Web Services be served by a different HTTP n+1? (Thursday, 24 January)
• Re: delta encoding and state management (Wednesday, 23 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: delta encoding and state management (Tuesday, 22 January)
• Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) (Tuesday, 22 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Monday, 21 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)
• Re: The use of binary data in any part of HTTP 2.0 is not good (Sunday, 20 January)

Last message date: Sunday, 31 March 2013 16:38:57 UTC