ietf-http-wg@w3.org from July to September 2012 by author

Adam Barth

• Re: Re[2]: Straw-man for our next charter (Monday, 30 July)
• Re: Re[2]: Straw-man for our next charter (Monday, 30 July)
• Re: Re[2]: Straw-man for our next charter (Monday, 30 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: HTTP without being HTTPS all the time (Friday, 20 July)

Adrian Custer

• Comments on the HTTPbis draft, v20 (Wednesday, 5 September)
• ABNF for field-value (Sunday, 2 September)

Adrien de Croy

• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re[2]: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re[2]: Moving forward with HTTP/2.0: proposed charter (Sunday, 5 August)
• Re[2]: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re[2]: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re[2]: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Fw: Re: Our old friends, weak ETags (Friday, 20 July)
• Re[2]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re[2]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re[8]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re[4]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re[2]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re[2]: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)

Adrien W. de Croy

• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Semantics of HTTPS (Friday, 14 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Comments on the HTTPbis draft, v20 (Thursday, 6 September)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: Some general SPDY feedback / questions (Friday, 10 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Thursday, 9 August)
• Re: Some general SPDY feedback / questions (Wednesday, 8 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re[2]: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re[2]: Straw-man for our next charter (Sunday, 29 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re[2]: [ietf-http-wg] <none> (Wednesday, 18 July)
• Re[2]: Mandatory encryption (Wednesday, 18 July)
• Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re[4]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re[2]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re[2]: HTTP2 Expression of Interest (Wednesday, 18 July)

Albert Lunde

• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Content security model (Wednesday, 25 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Response to HTTP2 expresions of interest (Sunday, 15 July)

Alexey Melnikov

• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Friday, 13 July)
• Number of round trips in draft-melnikov-httpbis-scram-auth-00 (Friday, 13 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Tuesday, 10 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Monday, 9 July)
• draft-montenegro-httpbis-multilegged-auth-01 (Sunday, 8 July)

Amos Jeffries

• Re: Content-Length and 304 (Sunday, 23 September)
• Re: Comments on the HTTPbis draft, v20 (Thursday, 6 September)
• Re: Optimizations vs Functionality vs Architecture (Thursday, 23 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Thursday, 9 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Thursday, 9 August)
• Re: Some general SPDY feedback / questions (Wednesday, 8 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: Vancouver minutes (uploaded) (Sunday, 5 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Sunday, 29 July)
• Re: Straw-man for our next charter (Saturday, 28 July)
• Re: Straw-man for our next charter (Friday, 27 July)
• Re: RFC6585+HTTP/2.0 := 101 (Friday, 27 July)
• Re: Content security model (Wednesday, 25 July)
• Re: Straw-man for our next charter (Wednesday, 25 July)
• Re: Our old friends, weak ETags (Tuesday, 24 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Tuesday, 24 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• Re: Introducing a Session header... (Saturday, 21 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: HTTP2 Expression of Interest (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: #375: Most Conservative (caching and date parsing) (Wednesday, 18 July)
• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• Re: SPDY Header Frames (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: SPDY Header Frames (Sunday, 15 July)
• Re: SPDY Header Frames (Sunday, 15 July)
• Re: SPDY Header Frames (Sunday, 15 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Thursday, 12 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Thursday, 12 July)
• RE: Associated resource for PUT (Tuesday, 10 July)
• RE: draft-montenegro-httpbis-multilegged-auth-01 (Tuesday, 10 July)
• Re: Content-Integrity header (Monday, 9 July)
• Re: #364 Capturing more information in the method registry (Friday, 6 July)
• Re: #359 clarify connection header field values are case-insensitive (Wednesday, 4 July)
• Re: Revision of p2 2.2.1 / who can generate a status code? (Wednesday, 4 July)
• Re: Revision of p2 2.2.1 / who can generate a status code? (Wednesday, 4 July)
• Re: Revision of p2 2.2.1 / who can generate a status code? (Wednesday, 4 July)
• Re: #364 Capturing more information in the method registry (Tuesday, 3 July)
• Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)

Andy Wenk

• Re: [ietf-http-wg] <none> (Friday, 20 July)

Anil Sharma

• RE: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• RE: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• RE: Mandatory encryption (Thursday, 19 July)
• RE: Mandatory encryption (Thursday, 19 July)
• RE: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Wednesday, 18 July)

Barry Leiba

• Status of draft-ietf-appsawg-http-forwarded (Friday, 31 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list (Thursday, 5 July)
• draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list (Tuesday, 3 July)

Benjamin Carlyle

• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Wednesday, 1 August)
• Re: Content security model (Thursday, 26 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Wednesday, 25 July)
• RE: Benjamin Carlyle http 2.0 expression of interest (Wednesday, 25 July)
• Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)

Bjoern Hoehrmann

• Re: Status Line Syntax production/parsing (Tuesday, 28 August)

Brian Pane

• HTTP/2.0 negotiation latency Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)

Bruce Perens

• Re: Our old friends, weak ETags (Friday, 20 July)

Carl Wallace

• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)

Carsten Bormann

• Policy vs. URI (Re: Semantics of HTTPS) (Thursday, 13 September)
• Re: Connection limits, was: Straw-man for our next charter (Tuesday, 31 July)
• Mibiseconds (Re: Our old friends, weak ETags) (Friday, 20 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re: Protocol Design 101 (Re: Mandatory encryption) (Wednesday, 18 July)
• Protocol Design 101 (Re: Mandatory encryption) (Wednesday, 18 July)

Chad Goss

• Re: Explicit Proxy (draft-rpeon-httpbis-exproxy) (Thursday, 19 July)
• Explicit Proxy (draft-rpeon-httpbis-exproxy) (Friday, 13 July)

Dan Wing

• RE: frequent DNS queries RE: comments on draft-mbelshe-httpbis-spdy-00 (Friday, 17 August)
• frequent DNS queries RE: comments on draft-mbelshe-httpbis-spdy-00 (Friday, 17 August)

Daniel Stenberg

• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• HTTP2 Expression of Interest: curl (Thursday, 12 July)

David Morris

• Re: In Defense of Header Compresson (Thursday, 16 August)
• RE: In Defense of Header Compresson (Thursday, 16 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Wednesday, 8 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: Introducing a Session header... (Thursday, 19 July)

Dereq Dereq

• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 24 July)
• RE: Status code for censorship? (Tuesday, 10 July)
• Re: Status code for censorship? (Tuesday, 10 July)
• Re: Status code for censorship? (Tuesday, 10 July)
• Re: Status code for censorship? (Tuesday, 10 July)

Dirk Pranke

• Re: Introducing a Session header... (Tuesday, 17 July)

Doug Beaver

• RE: HTTP2 Expression of Interest (Tuesday, 17 July)
• HTTP2 Expression of Interest (Sunday, 15 July)

Eliot Lear

• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• comments on draft-mbelshe-httpbis-spdy-00 (Tuesday, 14 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Saturday, 4 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Saturday, 4 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Privacy and its costs (Tuesday, 31 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption prerequisites (Wednesday, 18 July)

Eric J. Bowman

• Re: Straw-man for our next charter (Wednesday, 25 July)
• Re: REST and HTTP, was: [ietf-http-wg] <none> (Wednesday, 25 July)
• Re: [ietf-http-wg] <none> (Tuesday, 24 July)
• Re: Our old friends, weak ETags (Tuesday, 24 July)
• Re: Our old friends, weak ETags (Tuesday, 24 July)
• Re: #241: clarify eval order/interaction of conditional headers (Thursday, 12 July)

Eric Rescorla

• Re: Semantics of HTTPS (Sunday, 26 August)

Erlend Hamnaberg

• Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt (Tuesday, 3 July)

Evan Prodromou

• "OAuth" not listed in initial authentication scheme registry (Thursday, 6 September)

Fall, Kevin

• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Thursday, 27 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Tuesday, 18 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Saturday, 15 September)
• question/comment on draft-ietf-httpbis-p5-range-20.txt (Thursday, 13 September)

Figroc Chen

• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)

Gabriel Montenegro

• RE: Re[4]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• RE: Re[2]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• RE: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)

Grahame Grieve

• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Tuesday, 17 July)
• Fwd: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)

Greg Wilkins

• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 7 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 26 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Friday, 20 July)
• Expression of Interest from Jetty. (Tuesday, 3 July)

HAYASHI, Tatsuya

• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: SPDY Header Frames (Monday, 16 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Content-Integrity header (Monday, 9 July)

Henrik Frystyk Nielsen

• RE: In Defense of Header Compresson (Thursday, 16 August)
• RE: In Defense of Header Compresson (Thursday, 16 August)
• RE: In Defense of Header Compresson (Thursday, 16 August)
• RE: In Defense of Header Compresson (Wednesday, 15 August)
• RE: Some general SPDY feedback / questions (Tuesday, 7 August)
• RE: Some general SPDY feedback / questions (Tuesday, 7 August)
• RE: Moving forward with HTTP/2.0: proposed charter (Saturday, 4 August)
• RE: Would a header/schema compiler help? (Thursday, 2 August)
• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• HTTP 2.0 and a Faster, more Mobile-friendly web (Sunday, 29 July)
• RE: HTTP2 Expression of Interest (Wednesday, 18 July)

Henry Story

• Re: HTTP without being HTTPS all the time (Friday, 20 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)

Ilya Grigorik

• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)

internet-drafts@ietf.org

• I-D Action: draft-ietf-httpbis-authscheme-registrations-04.txt (Thursday, 16 August)
• I-D Action: draft-ietf-httpbis-method-registrations-09.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p7-auth-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p6-cache-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p5-range-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p4-conditional-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p3-payload-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p2-semantics-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-p1-messaging-20.txt (Monday, 16 July)
• I-D Action: draft-ietf-httpbis-method-registrations-08.txt (Monday, 2 July)

J Ross Nicoll

• Re: Mandatory encryption (Wednesday, 18 July)

James French

• Re: Content security model (Wednesday, 25 July)
• Re: #271: use of "may" and "should" (Friday, 29 June)

James M Snell

• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: Some general SPDY feedback / questions (Friday, 10 August)
• Re: Some general SPDY feedback / questions (Thursday, 9 August)
• Re: Some general SPDY feedback / questions (Wednesday, 8 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Sunday, 5 August)
• FYI... In-Stream Key Negotiation Initial Draft (Friday, 3 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: HTTP/2: Another reason to find a safer encoding (Tuesday, 31 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• Re: Straw-man for our next charter (Monday, 30 July)
• Re: Content security model (Wednesday, 25 July)
• Re: Straw-man for our next charter (Wednesday, 25 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• More SPDY Related Questions.. (Saturday, 21 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Some general SPDY feedback / questions (Thursday, 19 July)
• RE: Some general SPDY feedback / questions (Thursday, 19 July)
• Re: Some general SPDY feedback / questions (Wednesday, 18 July)
• Some general SPDY feedback / questions (Wednesday, 18 July)
• Re: [ietf-http-wg] <none> (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Wednesday, 18 July)
• Re: Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest : Squid (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Fwd: Introducing a Session header... (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest (Tuesday, 17 July)
• Introducing a Session header... (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: SPDY Header Frames (Monday, 16 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• SPDY Header Frames (Friday, 13 July)
• Re: KEY_NEGO within SPDY (was: Re: Response to HTTP2 expresions of interest) (Friday, 13 July)
• KEY_NEGO within SPDY (was: Re: Response to HTTP2 expresions of interest) (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Wednesday, 11 July)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Content-Integrity header (Friday, 6 July)

James Tucker

• HTTP2 Expression of Interest (Monday, 16 July)

Jan Algermissen

• Re: Content security model (Thursday, 26 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)

Jan Engelhardt

• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)

Jeroen de Borst

• HTTP/2 expression of interest: F5 (Monday, 16 July)

Jitu Padhye

• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• RE: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)

Joe Mason

• RE: Managing Obsolete Information (Wednesday, 5 September)

John Sullivan

• Re: Revision of p2 2.2.1 / who can generate a status code? (Tuesday, 3 July)

Jonathan Ballard

• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Sunday, 5 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Straw-man for our next charter (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Straw-man for our next charter (Monday, 30 July)
• Re: RFC6585+HTTP/2.0 := 101 (Friday, 27 July)
• RFC6585+HTTP/2.0 := 101 (Friday, 27 July)
• Re: Content security model (Thursday, 26 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• Re: Introducing a Session header... (Saturday, 21 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Cookies, sessions, browser software (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Friday, 13 July)

Jonathan Silvera

• HTTP2 Expression of Interest (Saturday, 14 July)
• RE: draft-montenegro-httpbis-multilegged-auth-01 (Wednesday, 11 July)
• RE: draft-montenegro-httpbis-multilegged-auth-01 (Wednesday, 11 July)
• RE: draft-montenegro-httpbis-multilegged-auth-01 (Monday, 9 July)

Joshua Zhu

• HTTP2 Expression of Interest: Alibaba (Sunday, 15 July)

Julian Reschke

• Re: Content-Length and 304 (Thursday, 20 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Tuesday, 18 September)
• Re: ABNF for field-value (Thursday, 6 September)
• #382, was: "OAuth" not listed in initial authentication scheme registry (Thursday, 6 September)
• Re: Comments on the HTTPbis draft, v20 (Wednesday, 5 September)
• Re: Status Line Syntax production/parsing (Tuesday, 28 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Saturday, 4 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Saturday, 4 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Connection limits, was: Straw-man for our next charter (Tuesday, 31 July)
• Connection limits, was: Straw-man for our next charter (Tuesday, 31 July)
• Re: #160: Redirects and non-GET methods (Thursday, 26 July)
• Re: #295: Applying original fragment to "plain" redirected URI (also #43) (Thursday, 26 July)
• Re: Straw-man for our next charter (Wednesday, 25 July)
• REST and HTTP, was: [ietf-http-wg] <none> (Wednesday, 25 July)
• Re: Our old friends, weak ETags (Tuesday, 24 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• #376 rename b64token for clarity, was: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: #375: Most Conservative (caching and date parsing) (Wednesday, 18 July)
• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: #375: Most Conservative (caching and date parsing) (Tuesday, 17 July)
• httpbis -20 drafts (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: Response to HTTP2 expresions of interest (Sunday, 15 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Friday, 13 July)
• Re: #241: clarify eval order/interaction of conditional headers (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: #372: refactor conditional header field descriptions (Thursday, 12 July)
• Re: #364 Capturing more information in the method registry (Thursday, 12 July)
• Re: #241: clarify eval order/interaction of conditional headers (Thursday, 12 July)
• Re: #371: If-Modified-Since lacks definition for method != GET (Thursday, 12 July)
• Re: #372: refactor conditional header field descriptions (Thursday, 12 July)
• #371: If-Modified-Since lacks definition for method != GET (Wednesday, 11 July)
• Re: #370: If-None-Match vs 412 vs ignoring the header field (Wednesday, 11 July)
• Re: Associated resource for PUT (Wednesday, 11 July)
• #372: refactor conditional header field descriptions (Tuesday, 10 July)
• #370: If-None-Match vs 412 vs ignoring the header field (Tuesday, 10 July)
• Re: Associated resource for PUT (Tuesday, 10 July)
• Re: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Friday, 6 July)
• If-* vs Range (part of #366) (Friday, 6 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 6 July)
• Re: #364 Capturing more information in the method registry (Friday, 6 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Thursday, 5 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Thursday, 5 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Wednesday, 4 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)
• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)
• Re: #359 clarify connection header field values are case-insensitive (Tuesday, 3 July)
• #359 clarify connection header field values are case-insensitive (Tuesday, 3 July)
• #364 Capturing more information in the method registry (Tuesday, 3 July)
• Re: cache invalidation and "denial of service" [was: WGLC #363: rare cases] (Tuesday, 3 July)
• Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt (Monday, 2 July)

Karl Dubost

• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Managing Obsolete Information (Wednesday, 5 September)
• Managing Obsolete Information (Wednesday, 5 September)
• Re: Status Line Syntax production/parsing (Tuesday, 28 August)
• Status Line Syntax production/parsing (Tuesday, 28 August)
• Re: Some general SPDY feedback / questions (Thursday, 9 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: [ietf-http-wg] <none> (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Reminder about Opera and SPDY, HTTP/2.0 (Sunday, 15 July)
• Re: 451 Unavailable For Legal Reasons (Wednesday, 11 July)

Larry Masinter

• Re: Re[2]: Straw-man for our next charter (Monday, 30 July)
• RE: Re[2]: Straw-man for our next charter (Monday, 30 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• RE: Straw-man for our next charter (Saturday, 28 July)
• Re: Straw-man for our next charter (Saturday, 28 July)
• RE: Straw-man for our next charter (Saturday, 28 July)

Ludin, Stephen

• Re: Straw-man for our next charter (Thursday, 26 July)
• HTTP/2.0 Expression of Interest: Akamai (Monday, 16 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Content-Integrity header (Tuesday, 10 July)

Manger, James H

• RE: Content security model (Thursday, 26 July)
• hoba: mixing origin-bound certs and user login (Monday, 23 July)
• RE: Some general SPDY feedback / questions (Thursday, 19 July)
• p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)

Marcelo Fernandez

• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)

Mark Nottingham

• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Thursday, 27 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Fwd: [new-work] WG Review: Hypertext Transfer Protocol Bis (httpbis) (Wednesday, 19 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Tuesday, 18 September)
• Re: Secdir review of draft-ietf-httpbis-p6-cache-20 (Tuesday, 18 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Saturday, 15 September)
• Re: question/comment on draft-ietf-httpbis-p5-range-20.txt (Saturday, 15 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Secdir review of draft-ietf-httpbis-p6-cache-20 (Wednesday, 5 September)
• Re: Secdir review of draft-ietf-httpbis-p6-cache-20 (Wednesday, 5 September)
• Fwd: Secdir review of draft-ietf-httpbis-p6-cache-20 (Wednesday, 5 September)
• Re: Status Line Syntax production/parsing (Wednesday, 29 August)
• Re: [Editorial Errata Reported] RFC6266 (3325) (Saturday, 18 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Semantics of HTTPS (Monday, 6 August)
• Discussion of mandatory encryption / privacy impact / etc. (Monday, 6 August)
• Re: Vancouver minutes (uploaded) (Monday, 6 August)
• Re: Vancouver minutes (uploaded) (Sunday, 5 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: Vancouver minutes (Friday, 3 August)
• Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: Vancouver minutes (Friday, 3 August)
• Vancouver minutes (Friday, 3 August)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Straw-man for our next charter (Friday, 27 July)
• Re: RFC6585+HTTP/2.0 := 101 (Friday, 27 July)
• Re: Straw-man for our next charter (Friday, 27 July)
• Re: Straw-man for our next charter (Friday, 27 July)
• Re: Straw-man for our next charter (Friday, 27 July)
• Straw-man for our next charter (Wednesday, 25 July)
• Issues addressed in the -20 drafts (Tuesday, 24 July)
• Re: Discussing Client Sessions (Monday, 23 July)
• Discussing Client Sessions (Saturday, 21 July)
• Fwd: Our old friends, weak ETags (Friday, 20 July)
• Our old friends, weak ETags (Friday, 20 July)
• Re: HTTP Semantics in HTTP 2.0 (Friday, 20 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: #375: Most Conservative (caching and date parsing) (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Fwd: SPDY Feedback (Tuesday, 17 July)
• Re: #375: Most Conservative (caching and date parsing) (Tuesday, 17 July)
• Re: Implementing SPDY, is a day a meaningful criteria? (Monday, 16 July)
• Re: #365: Conditional Request Security Considerations (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• #365: Conditional Request Security Considerations (Monday, 16 July)
• Re: #350: WGLC Issue for p4: Optionality of Conditional Request Support (Monday, 16 July)
• Fwd: HTTP/2.0 proposal feedback (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Fwd: HTTP2 Expression of Interest [twitter] (Sunday, 15 July)
• Re: #372: refactor conditional header field descriptions (Thursday, 12 July)
• Re: #371: If-Modified-Since lacks definition for method != GET (Thursday, 12 July)
• Using HTTP Trailers [was: Content-Integrity header] (Tuesday, 10 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Tuesday, 10 July)
• Caching unsafe methods - p6 overview clarification (Tuesday, 10 July)
• FYI: p6 re-org (Monday, 9 July)
• Re: Revision of p2 2.2.1 / who can generate a status code? (Thursday, 5 July)
• Re: #350: WGLC Issue for p4: Optionality of Conditional Request Support (Thursday, 5 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: #364 Capturing more information in the method registry (Thursday, 5 July)
• Re: #241: clarify eval order/interaction of conditional headers (Wednesday, 4 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Wednesday, 4 July)
• Straw-man agenda for Vancouver sessions (Wednesday, 4 July)
• Re: #364 Capturing more information in the method registry (Tuesday, 3 July)
• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: Revision of p2 2.2.1 / who can generate a status code? (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)
• Re: #359 clarify connection header field values are case-insensitive (Tuesday, 3 July)
• #241: clarify eval order/interaction of conditional headers (Tuesday, 3 July)
• Fwd: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• #360: Considerations for new cache directives (Tuesday, 3 July)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Tuesday, 3 July)
• Re: WGLC #363: rare cases (Tuesday, 3 July)
• cache invalidation and "denial of service" [was: WGLC #363: rare cases] (Tuesday, 3 July)
• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)
• Revision of p2 2.2.1 / who can generate a status code? (Tuesday, 3 July)
• Re: #271: use of "may" and "should" (Tuesday, 3 July)
• Fwd: New Version Notification for draft-nottingham-link-template-00.txt (Tuesday, 3 July)
• Vancouver Scheduling (Monday, 2 July)

Mark Watson

• Re: Protocol Design 101 (Re: Mandatory encryption) (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)

Martin J. Dürst

• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Managing Obsolete Information (Thursday, 6 September)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: Straw-man for our next charter (Monday, 30 July)
• Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: Response to HTTP2 expresions of interest (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)

Martin Nilsson

• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Tuesday, 31 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Sunday, 29 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Sunday, 29 July)

Martin Thomson

• Re: Policy vs. URI (Re: Semantics of HTTPS) (Thursday, 13 September)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Introducing a Session header... (Tuesday, 17 July)
• Re: Introducing a Session header... (Tuesday, 17 July)
• Re: Content-Integrity header (Saturday, 7 July)

mike amundsen

• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)
• Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt (Tuesday, 3 July)

Mike Belshe

• SPDY compression and CRIME attack (Friday, 14 September)
• Re: Some general SPDY feedback / questions (Thursday, 9 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Sunday, 5 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Connection limits, was: Straw-man for our next charter (Tuesday, 31 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 31 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Tuesday, 31 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• Re: Straw-man for our next charter (Tuesday, 31 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[4]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: SPDY Header Frames (Friday, 13 July)

Musatov, Martin - CW

• RE: [httpbis] #364: Capturing more information in the method registry (Tuesday, 3 July)

N A Bhaskar

• Referrer - unable to identify the originating page with nested iframes (Monday, 17 September)

Nico Williams

• New I-D: RESTauth (forget GSS) (Saturday, 11 August)
• Re: Privacy and its costs (Thursday, 19 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Misconceptions about the GSS-API (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Wednesday, 11 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• MACing HTTP requests/responses (Re: Content-Integrity header) (Wednesday, 11 July)
• Feedback on REST-GSS (Wednesday, 11 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Tuesday, 10 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Sunday, 8 July)

Nicolas Mailhot

• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• RE: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: [ietf-http-wg] <none> (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: [ietf-http-wg] <none> (Wednesday, 18 July)
• [ietf-http-wg] <none> (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)

Osama Mazahir

• RE: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• RE: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• RE: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)

Patrick McManus

• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• RE: In Defense of Header Compresson (Thursday, 16 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• In Defense of Header Compresson (Wednesday, 8 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Firefox Expression of Interest in HTTP/2.0 (Thursday, 12 July)

Paul Frazee

• Re: Cookies, sessions, browser software (Friday, 20 July)
• Cookies, sessions, browser software (Friday, 20 July)

Paul Hoffman

• Re: Content security model (Wednesday, 25 July)
• Re: Protocol Design 101 (Re: Mandatory encryption) (Wednesday, 18 July)
• Mandatory encryption (Wednesday, 18 July)
• New version of draft-farrell-httpbis-hoba (Monday, 16 July)
• HTTP2 Expression of Interest (Friday, 13 July)

Paul Leach

• RE: HTTP2 Expression of Interest : Squid (Thursday, 16 August)
• RE: HTTP2 Expression of Interest : Squid (Wednesday, 18 July)
• RE: HTTP2 Expression of Interest (Friday, 13 July)

Peter Saint-Andre

• Fwd: web+: enabling websites to expose services with custom URI schemes to registerProtocolHandler. (Wednesday, 1 August)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Privacy and its costs (Thursday, 19 July)
• Re: Privacy and its costs (Thursday, 19 July)

Philippe Mougin

• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Thursday, 19 July)

Phillip Hallam-Baker

• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Optimizations vs Functionality vs Architecture (Thursday, 23 August)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Tuesday, 14 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• Re: HTTP/2: Another reason to find a safer encoding (Tuesday, 31 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Wednesday, 25 July)
• Re: Content security model (Wednesday, 25 July)
• Content security model (Wednesday, 25 July)
• Re: REST and HTTP, was: [ietf-http-wg] <none> (Wednesday, 25 July)
• Re: Discussing Client Sessions (Monday, 23 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• What HTTP/2.0 should mandate instead (Wednesday, 18 July)
• Re: Protocol Design 101 (Re: Mandatory encryption) (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Would a header/schema compiler help? (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: Implementing SPDY, is a day a meaningful criteria? (Monday, 16 July)
• Implementing SPDY, is a day a meaningful criteria? (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: HTTP2 Expression of Interest (Friday, 13 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Thursday, 12 July)
• Re: MACing HTTP requests/responses (Re: Content-Integrity header) (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• Re: Content-Integrity header (Tuesday, 10 July)
• Re: Content-Integrity header (Saturday, 7 July)
• Re: Content-Integrity header (Friday, 6 July)
• Re: Content-Integrity header (Friday, 6 July)
• Re: Content-Integrity header (Friday, 6 July)
• Content-Integrity header (Friday, 6 July)

Poul-Henning Kamp

• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Comments on the HTTPbis draft, v20 (Thursday, 6 September)
• Re: Managing Obsolete Information (Wednesday, 5 September)
• Re: Optimizations vs Functionality vs Architecture (Wednesday, 22 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Sunday, 5 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: Would a header/schema compiler help? (Friday, 3 August)
• Re: Re[2]: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: HTTP/2: Another reason to find a safer encoding (Wednesday, 1 August)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Re[2]: Straw-man for our next charter (Monday, 30 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Content security model (Thursday, 26 July)
• Re: Straw-man for our next charter (Wednesday, 25 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re: HTTP Semantics in HTTP 2.0 (Friday, 20 July)
• Re: Our old friends, weak ETags (Friday, 20 July)
• Re: Fwd: Our old friends, weak ETags (Friday, 20 July)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Re[2]: Mandatory encryption (Wednesday, 18 July)
• Re: Some general SPDY feedback / questions (Wednesday, 18 July)
• Re: Some general SPDY feedback / questions (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Introducing a Session header... (Wednesday, 18 July)
• Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: Re[4]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: #375: Most Conservative (caching and date parsing) (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• Re: Implementing SPDY, is a day a meaningful criteria? (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• Re: SPDY Header Frames (Sunday, 15 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Friday, 13 July)
• Re: SPDY Header Frames (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: Misconceptions about the GSS-API (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• HTTP/2 Expression of luke-warm interest: Varnish (Thursday, 12 July)
• Re: Content-Integrity header (Friday, 6 July)

Rajeev Bector

• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Wednesday, 1 August)
• Re: Thoughts on server push and http/2.0 (Friday, 27 July)
• Re: Re[2]: HTTP2 Expression of Interest (Wednesday, 18 July)

Reto Bachmann-Gmür

• Re: Privacy and its costs (was: Re: Mandatory encryption) (Friday, 20 July)

Rob Trace

• RE: Straw-man for our next charter (Friday, 27 July)
• HTTP2 Expression of Interest (Thursday, 12 July)

Robert Brewer

• RE: In Defense of Header Compresson (Thursday, 16 August)
• RE: character encoding in header fields, was: SPDY Header Frames (Tuesday, 17 July)
• RE: Associated resource for PUT (Tuesday, 10 July)
• RE: Associated resource for PUT (Tuesday, 10 July)
• Associated resource for PUT (Tuesday, 10 July)

Robert Collins

• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)

Roberto Peon

• Re: Semantics of HTTPS (Friday, 14 September)
• Re: Optimizations vs Functionality vs Architecture (Thursday, 23 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: In Defense of Header Compresson (Thursday, 16 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 10 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Wednesday, 8 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: FYI... In-Stream Key Negotiation Initial Draft (Sunday, 5 August)
• Re: Would a header/schema compiler help? (Friday, 3 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Tuesday, 31 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Sunday, 29 July)
• Re: Thoughts on server push and http/2.0 (Saturday, 28 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• Re: More SPDY Related Questions.. (Saturday, 21 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Some general SPDY feedback / questions (Wednesday, 18 July)
• Re: Some general SPDY feedback / questions (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[4]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: Re[2]: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Expression of Interest in HTTP/2.0 (Friday, 13 July)
• Re: Explicit Proxy (draft-rpeon-httpbis-exproxy) (Friday, 13 July)
• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)

Roland Zink

• Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames (Tuesday, 17 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Friday, 13 July)

Ross Nicoll

• Re: Cookies, sessions, browser software (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Introducing a Session header... (Tuesday, 17 July)

Roy T. Fielding

• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Managing Obsolete Information (Wednesday, 5 September)
• Re: Comments on the HTTPbis draft, v20 (Wednesday, 5 September)
• Re: Managing Obsolete Information (Wednesday, 5 September)
• Re: #241: clarify eval order/interaction of conditional headers (Friday, 13 July)
• Re: #241: clarify eval order/interaction of conditional headers (Thursday, 12 July)
• Re: Content-Integrity header (Friday, 6 July)
• Re: draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list (Thursday, 5 July)

Safruti, Ido

• Re: Thoughts on server push and http/2.0 (Friday, 27 July)
• Thoughts on server push and http/2.0 (Friday, 27 July)

Salvatore Loreto

• Re: Moving forward with HTTP/2.0: proposed charter (Thursday, 9 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Wednesday, 8 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Wednesday, 8 August)
• Re: Moving forward with HTTP/2.0: proposed charter (Wednesday, 8 August)
• Explicit Proxies for HTTP/2.0: comments (Tuesday, 24 July)

Sam Johnston

• HTTP2 Expression of Interest (Sunday, 15 July)

Samuel Erdtman

• [ietf-http-wg] <none> (Friday, 20 July)

Stephen Farrell

• Re: Semantics of HTTPS (Friday, 14 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: hoba: mixing origin-bound certs and user login (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Sunday, 22 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Discussion of Mandatory TLS in HTTP/2.0 (Thursday, 19 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: HTTP2 Expression of Interest: curl (Friday, 13 July)
• Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Tuesday, 3 July)

Subbu Allamaraju

• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)

Ted Hardie

• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• HTTP Semantics in HTTP 2.0 (Thursday, 19 July)
• Opportunity to review and give feedback on IAB privacy document (Thursday, 19 July)

Tim Bray

• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Monday, 6 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 31 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: [ietf-http-wg] <none> (Wednesday, 18 July)
• Re: HTTP2 Expression of Interest (Tuesday, 17 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Thursday, 12 July)
• Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Tuesday, 10 July)

Timothy Knox

• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)

tom

• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)

Wenbo Zhu

• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)

Wendy Seltzer

• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Friday, 13 July)
• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt (Thursday, 12 July)

Werner Baumann

• Re: HTTP without being HTTPS all the time (Friday, 20 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)

Willy Tarreau

• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: Some general SPDY feedback / questions (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: Re[2]: Moving forward with HTTP/2.0: proposed charter (Monday, 6 August)
• Re: Vancouver minutes (Friday, 3 August)
• Re: Would a header/schema compiler help? (Thursday, 2 August)
• Re: HTTP/2: Another reason to find a safer encoding (Wednesday, 1 August)
• HTTP/2: Another reason to find a safer encoding (Tuesday, 31 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Saturday, 21 July)
• Re: Discussing Client Sessions (Saturday, 21 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: Introducing a Session header... (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: Mandatory encryption (Thursday, 19 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: Re[6]: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP2 Expression of Interest : Squid (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Monday, 16 July)
• Re: HTTP2 Expression of Interest : Squid (Sunday, 15 July)
• Re: HTTP2 Expression of Interest (Sunday, 15 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: Response to HTTP2 expresions of interest (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Saturday, 14 July)
• Re: SPDY Header Frames (Friday, 13 July)
• Re: Response to HTTP2 expresions of interest (Friday, 13 July)
• HTTP2 Expression of Interest : haproxy (Friday, 13 July)
• Re: #372: refactor conditional header field descriptions (Thursday, 12 July)
• Re: #359 clarify connection header field values are case-insensitive (Tuesday, 3 July)

Yoav Nir

• Re: Semantics of HTTPS (Thursday, 13 September)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: Optimizations vs Functionality vs Architecture (Tuesday, 21 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• HTTP 1.1 --> 2.0 Upgrade (Monday, 20 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: Semantics of HTTPS (Tuesday, 7 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Thursday, 2 August)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 31 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Tuesday, 31 July)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Introducing a Session header... (Friday, 20 July)
• Re: HTTP2 Expression of Interest (Wednesday, 18 July)
• Re: Mandatory encryption (Wednesday, 18 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Tuesday, 17 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)
• Re: HTTP/2 Expression of luke-warm interest: Varnish (Monday, 16 July)

Yutaka OIWA

• Re: Vancouver minutes (Friday, 3 August)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: p7: rename b64token (to token68) to avoid misunderstandings (Wednesday, 18 July)
• Re: #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• Re: #375: Most Conservative (caching and date parsing) (Monday, 16 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Saturday, 14 July)
• Re: HTTP2 Expression of Interest: curl (Friday, 13 July)
• Re: Content-Integrity header (Wednesday, 11 July)
• Re: draft-montenegro-httpbis-multilegged-auth-01 (Monday, 9 July)

Yves Lafon

• Re: If-* vs Range (part of #366) (Wednesday, 11 July)
• Re: #370: If-None-Match vs 412 vs ignoring the header field (Wednesday, 11 July)

Zhen Cao

• Re: Vancouver minutes (Saturday, 4 August)

Zhong Yu

• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Saturday, 22 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Re: Content-Length and 304 (Thursday, 20 September)
• Content-Length and 304 (Thursday, 20 September)
• Re: Managing Obsolete Information (Wednesday, 5 September)
• Re: Status Line Syntax production/parsing (Tuesday, 28 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Monday, 6 August)
• Re: FYI... Binary Optimized Header Encoding for SPDY (Friday, 3 August)
• Re: HTTP/2: Another reason to find a safer encoding (Wednesday, 1 August)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Saturday, 21 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Friday, 20 July)
• Re: Privacy and its costs (was: Re: Mandatory encryption) (Thursday, 19 July)
• Re: Re[2]: Mandatory encryption (Thursday, 19 July)
• Re: Re[2]: Mandatory encryption (Thursday, 19 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea (Wednesday, 18 July)
• Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid (Wednesday, 18 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Thursday, 12 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Thursday, 12 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: Using HTTP Trailers [was: Content-Integrity header] (Wednesday, 11 July)
• Re: #241: clarify eval order/interaction of conditional headers (Wednesday, 4 July)

イアンフェッティ

• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: Straw-man for our next charter (Sunday, 29 July)
• Re: Introducing a Session header... (Tuesday, 17 July)

陈智昌

• Re: Content-Length and 304 (Saturday, 22 September)
• frequent DNS queries RE: comments on draft-mbelshe-httpbis-spdy-00 (Friday, 17 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Thursday, 16 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: comments on draft-mbelshe-httpbis-spdy-00 (Wednesday, 15 August)
• Re: Semantics of HTTPS (Monday, 6 August)
• Re: HTTP 2.0 and a Faster, more Mobile-friendly web (Monday, 30 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: Benjamin Carlyle http 2.0 expression of interest (Monday, 23 July)
• Re: HTTP without being HTTPS all the time (Thursday, 19 July)
• Re: Firefox Expression of Interest in HTTP/2.0 (Thursday, 19 July)

Last message date: Thursday, 27 September 2012 17:06:37 UTC