ietf-http-wg@w3.org from January to March 2014 by date

Monday, 31 March 2014

Alt-Svc related Chromium bug report (proxy related) 陈智昌
State of the Protocol (2014-03-31) Martin Thomson
Re: #421: Mixed Schemes Martin Thomson
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate K.Morgan@iaea.org
Re: h2#404 requiring gzip and/or deflate K.Morgan@iaea.org
Re: h2#404 requiring gzip and/or deflate K.Morgan@iaea.org
Re: h2#404 requiring gzip and/or deflate David Morris
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: h2#404 requiring gzip and/or deflate Patrick McManus
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate K.Morgan@iaea.org
Indicating Chosen Service #443 Martin Thomson
Re: h2#404 requiring gzip and/or deflate Martin Thomson
RE: h2#404 requiring gzip and/or deflate K.Morgan@iaea.org
Re: #426: Unsupported Scheme Julian Reschke
Re: current HTTP/2 spec prevents gzip of response to "Range" request Mark Nottingham
Re: Client requesting authentication on server & thomson-httpbis-catch Amos Jeffries
Re: Client requesting authentication on server & thomson-httpbis-catch Mark Nottingham

Sunday, 30 March 2014

#362: Blocked frame Mark Nottingham
#421: Mixed Schemes Mark Nottingham
#426: Unsupported Scheme Mark Nottingham
Re: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin

Saturday, 29 March 2014

Re: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: Dependency based properties Tatsuhiro Tsujikawa

Friday, 28 March 2014

Re: Adopting Alternative Services as a WG product Julian Reschke
Re: Adopting Alternative Services as a WG product Paul Hoffman
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: Adopting Alternative Services as a WG product Julian Reschke
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
I-D Action: draft-ietf-httpbis-alt-svc-00.txt internet-drafts@ietf.org

Thursday, 27 March 2014

Re: HTTPbis WG Interim Meeting, 5-6 June 2014 Mark Nottingham
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: Dependency based properties Martin Thomson
Re: Dependency based properties Roberto Peon
Re: Dependency based properties Martin Thomson
HTTPbis WG Interim Meeting, 5-6 June 2014 IESG Secretary
Re: WebSocket over HTTP/2.0 Yutaka Hirano
Re: Dependency based properties Tatsuhiro Tsujikawa
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: Adopting Alternative Services as a WG product Mark Nottingham
Re: Adopting Alternative Services as a WG product Mark Nottingham
Re: Dependency based properties Roberto Peon
Dependency based properties Tatsuhiro Tsujikawa

Wednesday, 26 March 2014

Re: current HTTP/2 spec prevents gzip of response to "Range" request Zhong Yu
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Zhong Yu
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Re: Client requesting authentication on server & thomson-httpbis-catch henry.story@bblfish.net
Re: current HTTP/2 spec prevents gzip of response to "Range" request Poul-Henning Kamp
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Patrick McManus

Tuesday, 25 March 2014

Re: Adopting Alternative Services as a WG product Martin Thomson
Re: Adopting Alternative Services as a WG product Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: Getting to consensus on HTTP:// over TLS 陈智昌
RE: Adopting Alternative Services as a WG product Rob Trace
Re: Adopting Alternative Services as a WG product Roberto Peon
Re: Adopting Alternative Services as a WG product Mark Nottingham
Re: Adopting Alternative Services as a WG product Roberto Peon
Re: Adopting Alternative Services as a WG product 陈智昌
Re: current HTTP/2 spec prevents gzip of response to "Range" request Patrick McManus
RE: current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roy T. Fielding
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: FYI: proposal for client authentication in TLS Michael Köller
Re: draft-montenegro-httpbis-uri-encoding Bjoern Hoehrmann
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Improving detection of unsupported Content-Codings, was: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: current HTTP/2 spec prevents gzip of response to "Range" request Mark Nottingham

Monday, 24 March 2014

Re: Support for gzip at the server #424 (Consensus Call) Roy T. Fielding
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: June Interim dates / location Mark Nottingham
Re: June Interim dates / location 陈智昌
Re: June Interim dates / location Mark Nottingham
Re: current HTTP/2 spec prevents gzip of response to "Range" request Matthew Kerwin
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roy T. Fielding
Re: current HTTP/2 spec prevents gzip of response to "Range" request Roland Zink
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Bjoern Hoehrmann
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Bjoern Hoehrmann
Re: current HTTP/2 spec prevents gzip of response to "Range" request Martin Thomson
Re: current HTTP/2 spec prevents gzip of response to "Range" request Zhong Yu
Re: current HTTP/2 spec prevents gzip of response to "Range" request Zhong Yu
Re: draft-montenegro-httpbis-uri-encoding Zhong Yu
current HTTP/2 spec prevents gzip of response to "Range" request K.Morgan@iaea.org
Re: Server push limited to cache priming? Martin J. Dürst
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: WebSocket over HTTP/2.0 Yutaka Hirano
Re: draft-montenegro-httpbis-uri-encoding Martin J. Dürst
Re: draft-montenegro-httpbis-uri-encoding Martin J. Dürst
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Martin J. Dürst
Re: draft-montenegro-httpbis-uri-encoding Martin J. Dürst
Re: WPAD ideas and considerations Eliezer Croitoru
Re: Flow control protocol redundancy David Krauss

Sunday, 23 March 2014

Flow control protocol redundancy David Krauss
Flow control protocol redundancy David Krauss

Saturday, 22 March 2014

Re: h2#404 requiring gzip and/or deflate Cory Benfield
Re: draft-montenegro-httpbis-uri-encoding Zhong Yu
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
RE: draft-montenegro-httpbis-uri-encoding Julian Reschke
RE: draft-montenegro-httpbis-uri-encoding Gabriel Montenegro

Friday, 21 March 2014

Re: draft-montenegro-httpbis-uri-encoding Mark Nottingham
Re: h2#404 requiring gzip and/or deflate Zhong Yu
Re: Support for gzip at the server #424 (Consensus Call) Roland Zink
Re: Support for gzip at the server #424 (Consensus Call) Zhong Yu
Re: Support for gzip at the server #424 (Consensus Call) Roland Zink
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
RE: Support for gzip at the server #424 Richard Wheeldon (rwheeldo)
Re: draft-montenegro-httpbis-uri-encoding Bjoern Hoehrmann
Re: draft-montenegro-httpbis-uri-encoding Zhong Yu
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Zhong Yu
Re: draft-montenegro-httpbis-uri-encoding Bjoern Hoehrmann
Re: draft-montenegro-httpbis-uri-encoding Zhong Yu
Re: draft-montenegro-httpbis-uri-encoding Poul-Henning Kamp
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Bjoern Hoehrmann
Re: draft-montenegro-httpbis-uri-encoding Poul-Henning Kamp
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Willy Tarreau
Re: draft-montenegro-httpbis-uri-encoding Martin Nilsson
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Poul-Henning Kamp
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Poul-Henning Kamp
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Mike Belshe
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Bjoern Hoehrmann
Re: draft-montenegro-httpbis-uri-encoding Michael Sweet
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: Support for gzip at the server #424 (Consensus Call) Roland Zink
Re: draft-montenegro-httpbis-uri-encoding Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: Adopting Alternative Services as a WG product Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: Time out error code for HTTP/2 stream? Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Nicolas Mailhot
Re: draft-montenegro-httpbis-uri-encoding Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Adopting Alternative Services as a WG product Mark Nottingham
Time out error code for HTTP/2 stream? Tatsuhiro Tsujikawa
Re: draft-montenegro-httpbis-uri-encoding Mark Nottingham
Re: Server push limited to cache priming? Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Amos Jeffries
Re: draft-montenegro-httpbis-uri-encoding Matthew Kerwin
draft-montenegro-httpbis-uri-encoding Mark Nottingham
Re: Client requesting authentication on server & thomson-httpbis-catch Mark Nottingham

Thursday, 20 March 2014

Re: Server push limited to cache priming? Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: Server push limited to cache priming? David Krauss
Adopting Alternative Services as a WG product Mark Nottingham
RE: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
RE: *** GMX Spamverdacht *** RE: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Gabriel Montenegro
Re: *** GMX Spamverdacht *** RE: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
RE: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Mike Bishop
Re: *** GMX Spamverdacht *** RE: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
RE: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Gabriel Montenegro
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Nicholas Hurley
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Stephen Farrell
RE: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Rob Trace
Re: Getting to consensus on HTTP:// over TLS Mark Nottingham
Re: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
ALTSVC and mixed scheme Yutaka Hirano
Getting to consensus on HTTP:// over TLS Mark Nottingham
Re: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Mark Nottingham
Re: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
Re: Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Daniel Stenberg
Finding consensus on alt-svc, was: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
RE: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Rob Trace
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Mark Nottingham
Re: Server push limited to cache priming? Mark Nottingham
Re: Server push limited to cache priming? Roberto Peon
Re: Server push limited to cache priming? Adrien de Croy
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: Server push limited to cache priming? Mark Nottingham
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Mark Nottingham
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Mark Nottingham

Wednesday, 19 March 2014

Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Patrick McManus
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Martin Thomson
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Patrick McManus
Re: http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 Julian Reschke
http://tools.ietf.org/html/draft-nottingham-httpbis-alt-svc as a normative reference in http/2 陈智昌
Re: Server push limited to cache priming? Daniel Sommermann
Re: Server push limited to cache priming? Martin Thomson
Re: Server push limited to cache priming? Martin Thomson
Re: Server push limited to cache priming? 陈智昌
Server push limited to cache priming? Daniel Sommermann
Re: Client requesting authentication on server & thomson-httpbis-catch henry.story@bblfish.net
Re: Support for gzip at the server #424 (Consensus Call) Willy Tarreau
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Roberto Peon
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham

Tuesday, 18 March 2014

Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Roy T. Fielding
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
Re: Support for gzip at the server #424 (Consensus Call) Bjoern Hoehrmann
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Bjoern Hoehrmann
Client requesting authentication on server & thomson-httpbis-catch henry.story@bblfish.net
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Roberto Peon
Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
Re: Support for gzip at the server #424 (Consensus Call) Daniel Sommermann
Re: Support for gzip at the server #424 (Consensus Call) Michael Sweet
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Amos Jeffries
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 David Morris

Monday, 17 March 2014

Re: PAD_HIGH and PAD_LOW bits David Krauss
Re: Support for gzip at the server #424 Mark Nottingham
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 Mark Nottingham
Re: Support for gzip at the server #424 Nicolas Mailhot
Re: Support for gzip at the server #424 Willy Tarreau
Re: Support for gzip at the server #424 Amos Jeffries
Re: WPAD ideas and considerations Amos Jeffries
Re: Support for gzip at the server #424 Nicolas Mailhot
Re: Support for gzip at the server #424 Nicolas Mailhot
Re: Support for gzip at the server #424 Nicolas Mailhot
Re: WPAD ideas and considerations Nicolas Mailhot
Improving on Huffman David Krauss
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Nicolas Mailhot
PAD_HIGH and PAD_LOW bits David Krauss
Re: Support for gzip at the server #424 Nicolas Mailhot
Re: HTTP/2, "h2t" and protocol identifiers in general Yutaka Hirano
Re: HTTP/2, "h2t" and protocol identifiers in general Yutaka Hirano
June Interim dates / location Mark Nottingham

Sunday, 16 March 2014

Re: Support for gzip at the server #424 James Cloos
Re: WPAD ideas and considerations Eliot Lear
Small editorial clarification to p2-semantics 3.1.4.2 David Booth
Re: Preliminary minutes for London IETF Willy Tarreau
RE: WPAD ideas and considerations Christian Huitema
Re: Support for gzip at the server #424 Ilari Liusvaara
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 James Cloos
Re: WPAD ideas and considerations Amos Jeffries

Saturday, 15 March 2014

Preliminary minutes for London IETF Mark Nottingham
Re: Support for gzip at the server #424 Roland Zink
Re: WPAD ideas and considerations Peter Lepeska

Friday, 14 March 2014

Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Willy Tarreau
Re: Support for gzip at the server #424 Julian Reschke
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 Amos Jeffries
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 Amos Jeffries
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Amos Jeffries
Re: Support for gzip at the server #424 陈智昌
Re: Support for gzip at the server #424 Amos Jeffries
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Michael Sweet
Re: Support for gzip at the server #424 Poul-Henning Kamp
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Michael Sweet
Re: Support for gzip at the server #424 Julian Reschke
Re: Support for gzip at the server #424 Julian Reschke
Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Zhong Yu
Re: Support for gzip at the server #424 Zhong Yu
Re: Support for gzip at the server #424 Michael Sweet
Re: Security implications of gzip #423 Martin Thomson
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Roland Zink
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Patrick McManus
Re: Support for gzip at the server #424 Bjoern Hoehrmann
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Roland Zink
Re: Security implications of gzip #423 Ted Johnson
WPAD ideas and considerations Amos Jeffries
Re: HTTP/2 schedule - implementation draft, interim meeting, WGLC Adrian Cole
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Martin Thomson
Re: Support for gzip at the server #424 Bjoern Hoehrmann
Re: Support for gzip at the server #424 Bjoern Hoehrmann
Re: HTTP/2 schedule - implementation draft, interim meeting, WGLC Martin Thomson
Re: Support for gzip at the server #424 Roberto Peon
Re: Support for gzip at the server #424 Roberto Peon
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Adrien de Croy
Re: Support for gzip at the server #424 Bjoern Hoehrmann
Re: Security implications of gzip #423 Bjoern Hoehrmann
Re: HTTP/2 schedule - implementation draft, interim meeting, WGLC Adrian Cole
Re: Security implications of gzip #423 Adrian Cole

Thursday, 13 March 2014

Security implications of gzip #423 Martin Thomson
RE: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Appanasamy, Palanivelan
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Salvatore Loreto
RE: HTTP/1.1 proxy behavior when Host differs from absoluteURI Richard Wheeldon (rwheeldo)
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Peter L
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Eliot Lear

Wednesday, 12 March 2014

HTTP/2 schedule - implementation draft, interim meeting, WGLC Mark Nottingham

Thursday, 13 March 2014

Re: HTTP/1.1 proxy behavior when Host differs from absoluteURI Roy T. Fielding
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Mark Nottingham
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Peter Lepeska
Re: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac Mark Nottingham

Wednesday, 12 March 2014

RE: Publically accessible website running HTTP2 compatible servers Brian Raymor (MS OPEN TECH)
Re: Publically accessible website running HTTP2 compatible servers Daniel Stenberg
Publically accessible website running HTTP2 compatible servers Richard Wheeldon (rwheeldo)

Tuesday, 11 March 2014

RE: HTTP/1.1 proxy behavior when Host differs from absoluteURI Amos Jeffries
RE: HTTP/1.1 proxy behavior when Host differs from absoluteURI Richard Wheeldon (rwheeldo)
HTTP/1.1 proxy behavior when Host differs from absoluteURI Daniel Sommermann
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: FYI: proposal for client authentication in TLS Yoav Nir
Re: FYI: proposal for client authentication in TLS Yoav Nir
Re: Feedback on draft-thomson-httpbis-catch Julian Reschke
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: Feedback on draft-thomson-httpbis-catch Martin Thomson
Re: FYI: proposal for client authentication in TLS Julian Reschke
Re: FYI: proposal for client authentication in TLS Yoav Nir
Feedback on draft-thomson-httpbis-catch Julian Reschke
Re: FYI: proposal for client authentication in TLS Julian Reschke
Re: FYI: proposal for client authentication in TLS Yoav Nir

Monday, 10 March 2014

Re: PUSH_PROMISE associated stream Roberto Peon
Re: PUSH_PROMISE associated stream Daniel Sommermann
Re: PUSH_PROMISE associated stream Jeff Pinner
Re: PUSH_PROMISE associated stream Johnny Graettinger
PUSH_PROMISE associated stream Daniel Sommermann
RE: Preliminary minutes from the Design Team Meeting: WPAD and Proxy.pac emile.stephan@orange.com
Web Proxy Traffic Profile (HTTPS, Inspection, etc.) Richard Wheeldon (rwheeldo)
Re: FYI: proposal for client authentication in TLS Julian Reschke
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: Support for gzip at the server #424 Martin Thomson
Re: FYI: proposal for client authentication in TLS henry.story@bblfish.net
Re: Support for gzip at the server #424 Julian Reschke
Support for gzip at the server #424 Martin Thomson
Re: HTTP/2, "h2t" and protocol identifiers in general Takeshi Yoshino
Re: FYI: proposal for client authentication in TLS Julian Reschke
Re: FYI: proposal for client authentication in TLS Martin Thomson
RE: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue Appanasamy, Palanivelan

Sunday, 9 March 2014

Re: FYI: proposal for client authentication in TLS Julian Reschke
Re: FYI: proposal for client authentication in TLS Martin Thomson

Saturday, 8 March 2014

Preliminary minutes from the Design Team Meeting Mark Nottingham
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: FYI: proposal for client authentication in TLS Ilari Liusvaara
Re: HPACK edge cases Tatsuhiro Tsujikawa
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: FYI: proposal for client authentication in TLS Ilari Liusvaara
Re: FYI: proposal for client authentication in TLS Martin Thomson
Re: FYI: proposal for client authentication in TLS Ilari Liusvaara
FYI: proposal for client authentication in TLS Martin Thomson

Friday, 7 March 2014

Re: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue James Cloos
Re: Proxies and packet loss Peter Lepeska
Re: HPACK edge cases Ilari Liusvaara
Re: HPACK edge cases Tatsuhiro Tsujikawa
Fwd: HPACK edge cases Johnny Graettinger
RE: feedback on draft-nottingham-httpbis-alt-svc Rob Trace
HPACK edge cases Ilari Liusvaara
Re: [HPACK]Looking for huffman frequency tables Ilari Liusvaara
Re: [HPACK]Looking for huffman frequency tables Ashok Kumar
Re: [HPACK]Looking for huffman frequency tables Ilari Liusvaara
[HPACK]Looking for huffman frequency tables Ashok Kumar
Re: Proxies and packet loss Peter Lepeska

Thursday, 6 March 2014

RE: Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Julian Reschke
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Martin Thomson
RE: Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
Re: feedback on draft-nottingham-httpbis-alt-svc Patrick McManus
Re: feedback on draft-nottingham-httpbis-alt-svc Patrick McManus
Re: feedback on draft-nottingham-httpbis-alt-svc Martin Thomson
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Martin Thomson
Re: feedback on draft-nottingham-httpbis-alt-svc Julian Reschke
Re: feedback on draft-nottingham-httpbis-alt-svc Martin Thomson
RE: Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
Re: feedback on draft-nottingham-httpbis-alt-svc 陈智昌
Re: feedback on draft-nottingham-httpbis-alt-svc Julian Reschke
Re: feedback on draft-nottingham-httpbis-alt-svc Martin Thomson
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Julian Reschke
RE: Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
RE: Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
Re: feedback on draft-nottingham-httpbis-alt-svc Roberto Peon
Re: feedback on draft-nottingham-httpbis-alt-svc Mark Nottingham
Re: feedback on draft-nottingham-httpbis-alt-svc Julian Reschke
Re: feedback on draft-nottingham-httpbis-alt-svc Mark Nottingham
feedback on draft-nottingham-httpbis-alt-svc Julian Reschke

Wednesday, 5 March 2014

alt-svc header field syntax Julian Reschke
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Yutaka OIWA
Re: Alternate service framework: question about Alt-Svc HTTP Header Field Martin Thomson
Alternate service framework: question about Alt-Svc HTTP Header Field emile.stephan@orange.com
Re: Proxies and packet loss 陈智昌
Re: TLS renegotiation Craig Taylor
Re: h2#373 HPACK attack mitigation options Martin Thomson
Re: h2#373 HPACK attack mitigation options Michael Sweet
Re: h2#373 HPACK attack mitigation options Roberto Peon
Re: h2#373 HPACK attack mitigation options Michael Sweet
Re: h2#373 HPACK attack mitigation options Roberto Peon
Proxies and packet loss Peter Lepeska
Re: h2#373 HPACK attack mitigation options Eric Rescorla
Re: h2#373 HPACK attack mitigation options Roberto Peon
Re: h2#373 HPACK attack mitigation options Roland Zink
Re: h2#373 HPACK attack mitigation options Roberto Peon
Re: h2#373 HPACK attack mitigation options Martin Thomson
Re: h2#373 HPACK attack mitigation options Roberto Peon
h2#373 HPACK attack mitigation options Martin Thomson
Re: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue Martin Thomson
Re: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue Nicolas Mailhot
Re: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue Julian Reschke
Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue Brian Smith

Tuesday, 4 March 2014

Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: HTTP/2, "h2t" and protocol identifiers in general 陈智昌
Re: HTTP/2, "h2t" and protocol identifiers in general Mark Nottingham
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: HTTP/2, "h2t" and protocol identifiers in general Mark Nottingham
Status codes in the HPACK static table Ludin, Stephen

Monday, 3 March 2014

Re: HTTP/2, "h2t" and protocol identifiers in general Matthew Kerwin
Fwd: I-D Action: draft-zhu-httpbis-http2-protocol-layering-00.txt Wenbo Zhu
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Nicolas Mailhot
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Roland Zink
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Peter Lepeska
RE: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Nicolas Mailhot
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
RE: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Rob Trace
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon

Sunday, 2 March 2014

Dynamic discovery of the support for HTTP/2 during domain name resolution emile.stephan@orange.com

Saturday, 1 March 2014

Re: HTTP/2, "h2t" and protocol identifiers in general Matthew Kerwin
RE: Secure Proxy definition [was: "Secure" proxies for HTTP URIs] Nicolas Mailhot
Re: HTTP/2, "h2t" and protocol identifiers in general Amos Jeffries
Re: HTTP/2, "h2t" and protocol identifiers in general Amos Jeffries

Friday, 28 February 2014

Re: The first settings Martin Thomson
Re: WebSocket over HTTP/2.0 Takeshi Yoshino
Re: HTTP/2, "h2t" and protocol identifiers in general Mark Nottingham
RE: Preliminary agenda for London: explicit proxy discussion in HTTPbis DRUTA, DAN
RE: Secure Proxy definition [was: "Secure" proxies for HTTP URIs] DRUTA, DAN
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Cory Benfield
Re: The first settings Cory Benfield
RE: Preliminary agenda for London: explicit proxy discussion in HTTPbis emile.stephan@orange.com
RE: Secure Proxy definition [was: "Secure" proxies for HTTP URIs] emile.stephan@orange.com
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Amos Jeffries
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Amos Jeffries
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Amos Jeffries
Re: padding and compression 山本和彦
Re: The first settings 山本和彦
TLS-HTTP channel binding John Mattsson

Thursday, 27 February 2014

Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Josh Goodall
Re: The first settings Martin Thomson
Re: The first settings Takeshi Yoshino
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Patrick McManus
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade 陈智昌
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Josh Goodall
Re: h2#416: Limit stream count Martin Thomson
Re: Alt-Svc NOT_AUTHORITATIVE proposal 陈智昌
Re: Alt-Svc NOT_AUTHORITATIVE proposal Martin Thomson
Re: Preliminary agenda for London Martin Thomson
Re: The first settings Martin Thomson
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: Alt-Svc NOT_AUTHORITATIVE proposal Mark Baker
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: Alt-Svc NOT_AUTHORITATIVE proposal Martin Thomson
Re: Alt-Svc NOT_AUTHORITATIVE proposal Mark Baker
Re: Alt-Svc NOT_AUTHORITATIVE proposal Martin Thomson
Re: Secure Proxy definition [was: "Secure" proxies for HTTP URIs] Peter Lepeska
Re: Alt-Svc NOT_AUTHORITATIVE proposal Patrick McManus
Re: Alt-Svc NOT_AUTHORITATIVE proposal Patrick McManus
Re: Preliminary agenda for London Smith, Kevin, (R&D) Vodafone Group
Secure Proxy definition [was: "Secure" proxies for HTTP URIs] Salvatore Loreto
Re: WebSocket over HTTP2 RFC6455 conformance Salvatore Loreto
Re: The first settings 山本和彦
Re: Alt-Svc NOT_AUTHORITATIVE proposal Ryan Hamilton
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: Alt-Svc NOT_AUTHORITATIVE proposal 陈智昌
Re: HTTP/2, "h2t" and protocol identifiers in general 陈智昌
Re: Alt-Svc NOT_AUTHORITATIVE proposal Mark Nottingham
Re: Preliminary agenda for London Mark Nottingham
Re: HTTP/2, "h2t" and protocol identifiers in general Mark Nottingham

Wednesday, 26 February 2014

Re: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? Mark Nottingham
Re: new version trusted-proxy20 draft Amos Jeffries
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Peter Lepeska
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Amos Jeffries
Re: WebSocket over HTTP2 RFC6455 conformance Roberto Peon
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Peter Lepeska
Secure Proxy Clarifications John Mattsson
Re: HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: WebSocket over HTTP2 RFC6455 conformance Martin Thomson
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft Peter Lepeska
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft 陈智昌
Re: HTTP/2, "h2t" and protocol identifiers in general Roberto Peon
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] 陈智昌
Re: WebSocket over HTTP2 RFC6455 conformance Yutaka Hirano
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Peter Lepeska
RE: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? emile.stephan@orange.com
Re: Alt-Svc NOT_AUTHORITATIVE proposal Patrick McManus
Re: new version trusted-proxy20 draft Peter Lepeska
Re: Preliminary agenda for London Smith, Kevin, (R&D) Vodafone Group
Re: HTTP/2, "h2t" and protocol identifiers in general Salvatore Loreto
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Amos Jeffries
Re: new version trusted-proxy20 draft Jeff Pinner
Re: h2#404 requiring gzip and/or deflate Amos Jeffries
Re: new version trusted-proxy20 draft Peter Lepeska
Re: h2#416: Limit stream count Roberto Peon
h2#416: Limit stream count Martin Thomson

Tuesday, 25 February 2014

Re: h2#404 requiring gzip and/or deflate Roberto Peon
Alt-Svc NOT_AUTHORITATIVE proposal Martin Thomson
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? Mark Nottingham
Re: h2#404 requiring gzip and/or deflate Amos Jeffries
Re: h2#404 requiring gzip and/or deflate Zhong Yu
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Mark Nottingham
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Mark Nottingham
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Jesse Wilson
HTTP/2, "h2t" and protocol identifiers in general Martin Thomson
Re: h2#404 requiring gzip and/or deflate Michael Sweet
Re: h2#404 requiring gzip and/or deflate Michael Sweet
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Michael Sweet
Re: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? Salvatore Loreto
Re: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? Martin Thomson
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Michael Sweet
Re: h2#404 requiring gzip and/or deflate Jeff Pinner
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Daniel Sommermann
Re: h2#404 requiring gzip and/or deflate Bjoern Hoehrmann
Re: h2#404 requiring gzip and/or deflate Patrick McManus
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: h2#404 requiring gzip and/or deflate Cory Benfield
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: h2#404 requiring gzip and/or deflate Cory Benfield
RE: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? emile.stephan@orange.com
Re: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? Barry Leiba
Re: new version trusted-proxy20 draft Ryan Hamilton
RE: The "trusted" / "explicit" proxy discussion: ML for HTTP2 proxy discussion ? emile.stephan@orange.com
Re: h2#404 requiring gzip and/or deflate Jesse Wilson
Re: The first settings Moto Ishizawa
Re: new version trusted-proxy20 draft Roland Zink
Re: The "trusted" / "explicit" proxy discussion Mark Nottingham
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Nicolas Mailhot
Re: The "trusted" / "explicit" proxy discussion Eliot Lear
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] James Cloos
The "trusted" / "explicit" proxy discussion Mark Nottingham

Monday, 24 February 2014

Re: new version trusted-proxy20 draft Paul Ferguson
Re: padding and compression Roberto Peon
Re: padding and compression Martin Nilsson
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: padding and compression Roberto Peon
Re: padding and compression Martin Thomson
Re: new version trusted-proxy20 draft Bjoern Hoehrmann
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Salvatore Loreto
Re: new version trusted-proxy20 draft Nicolas Mailhot
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Patrick McManus
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Ilari Liusvaara
Re: new version trusted-proxy20 draft Mikael Abrahamsson
Re: new version trusted-proxy20 draft Ilari Liusvaara
Re: The first settings 山本和彦
Re: new version trusted-proxy20 draft Mikael Abrahamsson
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Nicolas Mailhot
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Nicolas Mailhot
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Salvatore Loreto
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Amos Jeffries
Re: new version trusted-proxy20 draft Ilari Liusvaara
Re: The first settings Cory Benfield
Re: padding and compression Cory Benfield
Re: The first settings 山本和彦
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] 陈智昌
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Mark Nottingham
Re: "Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] 陈智昌
"Secure" proxies for HTTP URIs [was: new version trusted-proxy20 draft] Mark Nottingham
Re: The first settings Martin Thomson
padding and compression 山本和彦
The first settings 山本和彦

Saturday, 22 February 2014

Re: debug field in GOAWAY Cory Benfield
Re: debug field in GOAWAY Adrian Cole

Friday, 21 February 2014

Re: h2#404 requiring gzip and/or deflate Jeff Pinner
Re: h2#404 requiring gzip and/or deflate Zhong Yu
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Zhong Yu
Re: h2#404 requiring gzip and/or deflate Michael Sweet
Re: h2#404 requiring gzip and/or deflate Bjoern Hoehrmann
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: h2#404 requiring gzip and/or deflate Albert Lunde
Re: h2#404 requiring gzip and/or deflate Bjoern Hoehrmann
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: debug field in GOAWAY Martin Thomson
Re: h2#404 requiring gzip and/or deflate Roberto Peon
Re: debug field in GOAWAY Cory Benfield
Re: h2#404 requiring gzip and/or deflate Martin Thomson
Re: debug field in GOAWAY Ilari Liusvaara
Re: debug field in GOAWAY Tatsuhiro Tsujikawa
Re: debug field in GOAWAY Hasan Khalil
Re: debug field in GOAWAY Cory Benfield
debug field in GOAWAY Tatsuhiro Tsujikawa
Re: new version trusted-proxy20 draft Patrick McManus
Re: h2#404 requiring gzip and/or deflate Patrick McManus
Re: WebSocket over HTTP2 RFC6455 conformance Yutaka Hirano
Re: h2#404 requiring gzip and/or deflate Matthew Kerwin
Re: h2#404 requiring gzip and/or deflate Amos Jeffries
Re: h2#404 requiring gzip and/or deflate Mark Nottingham
Re: WebSocket over HTTP2 RFC6455 conformance Takeshi Yoshino

Thursday, 20 February 2014

Re: h2#404 requiring gzip and/or deflate Willy Tarreau
Re: h2#404 requiring gzip and/or deflate Poul-Henning Kamp
Re: h2#404 requiring gzip and/or deflate Bjoern Hoehrmann
h2#404 requiring gzip and/or deflate Martin Thomson
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Eliot Lear
Re: new version trusted-proxy20 draft Roland Zink
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Martin Thomson
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Martin Thomson
Re: WebSocket over HTTP2 RFC6455 conformance Martin Thomson
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Eliot Lear
RE: new version trusted-proxy20 draft Liliana Dinale
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Mark Nottingham
Re: WebSocket over HTTP2 RFC6455 conformance Yutaka Hirano
Re: WebSocket over HTTP2 RFC6455 conformance Takeshi Yoshino
Re: WebSocket over HTTP2 RFC6455 conformance Takeshi Yoshino
Re: WebSocket over HTTP2 RFC6455 conformance Martin Thomson
Re: WebSocket over HTTP2 RFC6455 conformance Takeshi Yoshino
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft 陈智昌

Wednesday, 19 February 2014

Re: WebSocket over HTTP/2.0 Martin Thomson
Re: new version trusted-proxy20 draft Thomas Fossati
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: WebSocket over HTTP2 RFC6455 conformance Martin Thomson
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft Patrick McManus
Re: new version trusted-proxy20 draft Patrick McManus
Re: new version trusted-proxy20 draft Thomas Fossati
Re: new version trusted-proxy20 draft Paul Hoffman
Re: new version trusted-proxy20 draft Peter Lepeska
Re: WebSocket over HTTP/2.0 Yutaka Hirano
WebSocket over HTTP2 RFC6455 conformance Yutaka Hirano
Re: new version trusted-proxy20 draft Amos Jeffries
Re: new version trusted-proxy20 draft Fabian Keil
Re: new version trusted-proxy20 draft Nicolas Mailhot
Re: new version trusted-proxy20 draft Nicolas Mailhot
Re: new version trusted-proxy20 draft 陈智昌
Re: GOAWAY -> GTFO SM
Re: new version trusted-proxy20 draft Thomas Fossati
Re: new version trusted-proxy20 draft Thomas Fossati
draft-loreto-httpbis-trusted-proxy Eliot Lear
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Dan Wing
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft 陈智昌
Re: new version trusted-proxy20 draft Paul Hoffman
Re: new version trusted-proxy20 draft Paul Hoffman
Re: new version trusted-proxy20 draft 陈智昌
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade 陈智昌

Tuesday, 18 February 2014

Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Paul Hoffman
Re: License for test suite Ludin, Stephen
Re: new version trusted-proxy20 draft Patrick McManus
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Fabian Keil
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Eliot Lear
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Eliot Lear

Monday, 17 February 2014

Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Josh Goodall
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Eliot Lear
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Martin Thomson
Re: new version trusted-proxy20 draft Nicolas Mailhot
Re: new version trusted-proxy20 draft Patrick McManus
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: new version trusted-proxy20 draft Salvatore Loreto
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Josh Goodall
Re: new version trusted-proxy20 draft Paul Hoffman

Sunday, 16 February 2014

Re: new version trusted-proxy20 draft Thomas Fossati
Re: new version trusted-proxy20 draft Thomas Fossati

Saturday, 15 February 2014

Re: WebSocket over HTTP/2.0 Mark Nottingham
Handshake optimization (was: Re: WebSocket over HTTP/2.0) Takeshi Yoshino

Friday, 14 February 2014

Re: new version trusted-proxy20 draft Patrick McManus
Re: Padding for PUSH_PROMISE frames Ryan Hamilton
Re: Padding for PUSH_PROMISE frames Martin Thomson
Re: Padding for PUSH_PROMISE frames Martin Thomson
Re: Padding for PUSH_PROMISE frames Roberto Peon
Re: Padding for PUSH_PROMISE frames Ryan Hamilton
Re: Padding for PUSH_PROMISE frames Roberto Peon
Re: Padding for PUSH_PROMISE frames Nicholas Hurley
Re: WebSocket over HTTP/2.0 Martin Thomson
Re: License for test suite Tony Hansen
Re: WebSocket over HTTP/2.0 Roberto Peon
Re: License for test suite Tim Wicinski
new version trusted-proxy20 draft Salvatore Loreto
Re: License for test suite Ludin, Stephen
WebSocket over HTTP/2.0 Yutaka Hirano
I-D Action: draft-ietf-httpbis-header-compression-06.txt internet-drafts@ietf.org
Re: Padding for PUSH_PROMISE frames Roberto Peon
Re: Padding for PUSH_PROMISE frames Jeff Pinner
Padding for PUSH_PROMISE frames Nicholas Hurley
Re: License for test suite Michael Ray
Re: License for test suite James M Snell
Re: License for test suite Michael Ray
Re: HTTP Status 308 (Permanent Redirect) Mark Nottingham
License for test suite Mark Nottingham
Re: HTTP Status 308 (Permanent Redirect) Barry Leiba

Thursday, 13 February 2014

I-D Action: draft-ietf-httpbis-http2-10.txt internet-drafts@ietf.org
RE: Priorities, draft -10 and our next implementation draft Osama Mazahir
Re: Priorities, draft -10 and our next implementation draft MIAN.HASAN.KHALIL@GMAIL.COM
Re: Priorities, draft -10 and our next implementation draft Patrick McManus
Re: HTTP Status 308 (Permanent Redirect) Julian Reschke
Re: Priorities, draft -10 and our next implementation draft 陈智昌
Priorities, draft -10 and our next implementation draft Mark Nottingham
Re: HTTP Status 308 (Permanent Redirect) Mark Nottingham

Wednesday, 12 February 2014

Re: Trusted Proxy Alternatives Analysis Mark Nottingham
RE: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade emile.stephan@orange.com
Re: Reg spydy implementations 陈智昌
Re: Re-work of op-code patterns Jeff Pinner
Re: Re-work of op-code patterns Tatsuhiro Tsujikawa
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Patrick McManus
Document Action: 'Initial Hypertext Transfer Protocol (HTTP) Method Registrations' to Informational RFC (draft-ietf-httpbis-method-registrations-15.txt) The IESG
Document Action: 'Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations' to Informational RFC (draft-ietf-httpbis-authscheme-registrations-10.txt) The IESG
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Authentication' to Proposed Standard (draft-ietf-httpbis-p7-auth-26.txt) The IESG
Reg spydy implementations Appanasamy, Palanivelan
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Caching' to Proposed Standard (draft-ietf-httpbis-p6-cache-26.txt) The IESG
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Range Requests' to Proposed Standard (draft-ietf-httpbis-p5-range-26.txt) The IESG
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests' to Proposed Standard (draft-ietf-httpbis-p4-conditional-26.txt) The IESG
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content' to Proposed Standard (draft-ietf-httpbis-p2-semantics-26.txt) The IESG
Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing' to Proposed Standard (draft-ietf-httpbis-p1-messaging-26.txt) The IESG
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Amos Jeffries
RE: Re-work of op-code patterns RUELLAN Herve
Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade Salvatore Loreto
issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade emile.stephan@orange.com
Re: Trusted Proxy Alternatives Analysis Nicolas Mailhot
Re: Trusted Proxy Alternatives Analysis Mark Nottingham
Preliminary agenda for London Mark Nottingham

Tuesday, 11 February 2014

Re: WINDOW_UPDATE with streamid = 0 redundant? Amos Jeffries
Re: WINDOW_UPDATE with streamid = 0 redundant? 陈智昌
RE: WINDOW_UPDATE with streamid = 0 redundant? Mike Bishop
Re: WINDOW_UPDATE with streamid = 0 redundant? Roberto Peon
Re: WINDOW_UPDATE with streamid = 0 redundant? Johnny Graettinger
Re: WINDOW_UPDATE with streamid = 0 redundant? Daniel Sommermann
Re: WINDOW_UPDATE with streamid = 0 redundant? Roberto Peon
Re: WINDOW_UPDATE with streamid = 0 redundant? Roberto Peon
Re: WINDOW_UPDATE with streamid = 0 redundant? Daniel Sommermann
Re: WINDOW_UPDATE with streamid = 0 redundant? Martin Thomson
WINDOW_UPDATE with streamid = 0 redundant? Daniel Sommermann
Re: Trusted Proxy Alternatives Analysis Nicolas Mailhot
Re: new draft trusted-proxy20-00 Salvatore Loreto
Re: new draft trusted-proxy20-00 Salvatore Loreto
Re: new draft trusted-proxy20-00 Salvatore Loreto
Re: Announcement: HTTP/2 Design Team Meeting Mark Nottingham
Re: Trusted Proxy Alternatives Analysis Mark Nottingham
Fwd: New Version Notification for draft-nottingham-httpbis-alt-svc-03.txt Mark Nottingham

Monday, 10 February 2014

Re: HTTP/1.1 revision status [was: HTTP/1.1bis draft -26] Mark Nottingham
501 Not Implemented - generic or only method specific? Best
clarify PUT failure response status (400, 404 or 405) when resource handler doesn't exists Best
Re: Priority straw man Jeff Pinner
Re: Priority straw man Jeff Pinner
RE: Priority straw man Mike Bishop
Re: Priority straw man Martin Thomson
Fwd: Expiration impending: <draft-snell-httpbis-bohe-13.txt> James M Snell
Re: Priority straw man Michael Sweet
Re: Trusted Proxy Alternatives Analysis Peter Lepeska
Re: HTTP/1.1 revision status [was: HTTP/1.1bis draft -26] Michael Sweet
Re: Trusted Proxy Alternatives Analysis Nicolas Mailhot
HTTP/1.1 revision status [was: HTTP/1.1bis draft -26] Mark Nottingham

Sunday, 9 February 2014

Re: Trusted Proxy Alternatives Analysis Frode Kileng
Re: Trusted Proxy Alternatives Analysis Salvatore Loreto
Re: Trusted Proxy Alternatives Analysis Salvatore Loreto

Saturday, 8 February 2014

Re: Priority straw man Jeff Pinner
Re: Priority straw man Michael Sweet
Re: Priority straw man Michael Sweet
Re: HPACK padding Tatsuhiro Tsujikawa
Re: Priority straw man 陈智昌
Re: HPACK padding Tatsuhiro Tsujikawa
Re: Priority straw man Jeff Pinner

Friday, 7 February 2014

Re: HPACK padding Jeff Pinner
Re: HPACK padding Roberto Peon
Re: HPACK padding Jeff Pinner
Re: Priority straw man Roberto Peon
Re: Priority straw man Martin Thomson
RE: User defined SETTINGS frame extensions Mike Bishop
Re: User defined SETTINGS frame extensions Martin Thomson
Re: Priority straw man 陈智昌
Re: User defined SETTINGS frame extensions 陈智昌
RE: User defined SETTINGS frame extensions Mike Bishop
Re: User defined SETTINGS frame extensions Ilari Liusvaara
Re: Trusted Proxy Alternatives Analysis 陈智昌
RE: HPACK padding Hasan Khalil
Re: User defined SETTINGS frame extensions 陈智昌
Re: HPACK padding Kennedy, Smith (Wireless Architect)
User defined SETTINGS frame extensions Daniel Sommermann
RE: HPACK padding Osama Mazahir
Re: HPACK padding Jeff Pinner
Re: HPACK padding Michael Sweet
Re: Trusted Proxy Alternatives Analysis Peter Lepeska
Re: HPACK padding Martin Thomson
HPACK padding RUELLAN Herve
Re: Trusted Proxy Alternatives Analysis Peter Lepeska
Re: Trusted Proxy Alternatives Analysis Frode Kileng
RE: Trusted Proxy Alternatives Analysis emile.stephan@orange.com
Re: HTTP/1.1bis draft -26 Willy Tarreau
Re: HPACK analysis 山本和彦
Re: How to handle HTTP/2 negotiation failure WRT TLS Martin Thomson
Re: How to handle HTTP/2 negotiation failure WRT TLS Mark Nottingham

Thursday, 6 February 2014

Re: Trusted Proxy Alternatives Analysis Frode Kileng
Trusted Proxy Alternatives Analysis Peter Lepeska
Re: Priority straw man Peter Lepeska
Re: HTTP Status 308 (Permanent Redirect) Julian Reschke
Re: HTTP Status 308 (Permanent Redirect) Bjoern Hoehrmann
Re: Priority straw man Tatsuhiro Tsujikawa
HTTP Status 308 (Permanent Redirect) Julian Reschke
Re: How to handle HTTP/2 negotiation failure WRT TLS Amos Jeffries
Re: HTTP/1.1bis draft -26 Amos Jeffries
Re: HTTP/1.1bis draft -26 Willy Tarreau
RE: Priority straw man RUELLAN Herve
HTTP/1.1bis draft -26 Mark Nottingham
I-D Action: draft-ietf-httpbis-authscheme-registrations-10.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-method-registrations-15.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p7-auth-26.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p6-cache-26.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p5-range-26.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p4-conditional-26.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p2-semantics-26.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p1-messaging-26.txt internet-drafts@ietf.org

Wednesday, 5 February 2014

Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: http/2 presentation at a large Java conference 陈智昌
Re: How to handle HTTP/2 negotiation failure WRT TLS Michael Sweet
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Roy T. Fielding
Re: How to handle HTTP/2 negotiation failure WRT TLS Mark Nottingham
RE: How to handle HTTP/2 negotiation failure WRT TLS Rob Trace
HPack changes Roberto Peon

Tuesday, 4 February 2014

Re: Priority straw man Michael Sweet
RE: Priority straw man Osama Mazahir
Re: Priority straw man Martin Thomson
RE: Priority straw man RUELLAN Herve
http/2 presentation at a large Java conference Adrian Cole
Re: TLS renegotiation Yoav Nir
Announcement: HTTP/2 Design Team Meeting Mark Nottingham
Re: IETF 89 Preliminary Agenda Mark Nottingham

Monday, 3 February 2014

Re: Priority straw man Martin Thomson
RE: Priority straw man Mike Bishop
Re: Priority straw man Martin Thomson
Re: TLS renegotiation Martin Thomson
Re: IETF 89 Preliminary Agenda Martin Thomson
Re: How to handle HTTP/2 negotiation failure WRT TLS Patrick McManus
Re: How to handle HTTP/2 negotiation failure WRT TLS Michael Sweet
Re: TLS renegotiation Ilari Liusvaara
Re: IETF 89 Preliminary Agenda Yoav Nir
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Simon Yarde
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Julian Reschke
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Simon Yarde
Re: Reasons to not use huffman encoding? Michael Sweet
Re: IETF 89 Preliminary Agenda Peter Lepeska
Re: TLS renegotiation Yoav Nir
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Julian Reschke
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Simon Yarde
Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Julian Reschke
TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0 Simon Yarde
Re: HPACK analysis Adam Barth

Sunday, 2 February 2014

getting the HTTP/1.1 specs published Julian Reschke
Re: #549: augmented security considerations in p1 Julian Reschke
Re: Server Push -> Cache Push? Salvatore Loreto
Re: HPACK analysis Mike Bishop
Re: How to handle HTTP/2 negotiation failure WRT TLS Paul Hoffman
Re: Mark's coalescing proposal Mark Nottingham

Saturday, 1 February 2014

Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: How to handle HTTP/2 negotiation failure WRT TLS Martin Thomson
Re: FW: HPACK analysis Martin Thomson
Re: Mark's coalescing proposal Martin Thomson
Re: Mark's coalescing proposal Alexey Melnikov
Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: #549: augmented security considerations in p1 Roy T. Fielding
Re: #552: allow privacy proxies to be conformant Roy T. Fielding
Re: Mark's coalescing proposal Carsten Bormann
Re: #551: recipient handling of trailer fields Roy T. Fielding
Re: #549: augmented security considerations in p1 Roy T. Fielding
Re: FW: HPACK analysis Adam Barth
Re: Reasons to not use huffman encoding? Mark Nottingham
Re: #549: augmented security considerations in p1 Mark Nottingham
Re: Mark's coalescing proposal Mark Nottingham
Fwd: IETF 89 Preliminary Agenda Mark Nottingham

Friday, 31 January 2014

Re: Reasons to not use huffman encoding? Martin Thomson
Re: Reasons to not use huffman encoding? 山本和彦
Re: Reasons to not use huffman encoding? Fred Akalin
Re: Reasons to not use huffman encoding? Michael Sweet
Re: Compression ratio of HPACK. 山本和彦
Re: Reasons to not use huffman encoding? Adrian Cole
Re: Mark's coalescing proposal Martin Thomson
Re: Reasons to not use huffman encoding? Gábor Molnár
Re: Mark's coalescing proposal Ted Hardie
Mark's coalescing proposal Martin Thomson
Re: Reasons to not use huffman encoding? Jeff Pinner
Re: Compression ratio of HPACK. Jeff Pinner
Re: Reasons to not use huffman encoding? Amos Jeffries
Re: Compression ratio of HPACK. Amos Jeffries
Reasons to not use huffman encoding? Adrian Cole
Re: Compression ratio of HPACK. Jeff Pinner
Re: #549: augmented security considerations in p1 Michael Sweet
#549: augmented security considerations in p1 Roy T. Fielding
Re: Compression ratio of HPACK. 山本和彦
Re: #551: recipient handling of trailer fields Bjoern Hoehrmann
Re: #551: recipient handling of trailer fields Richard Barnes
Re: #551: recipient handling of trailer fields Mark Nottingham

Thursday, 30 January 2014

Re: How to handle HTTP/2 negotiation failure WRT TLS Martin Thomson
Re: Server Push request header fields Martin Thomson
Re: How to handle HTTP/2 negotiation failure WRT TLS Brian Smith
Re: Compression ratio of HPACK. Roberto Peon
Re: How to handle HTTP/2 negotiation failure WRT TLS Michael Sweet
Re: How to handle HTTP/2 negotiation failure WRT TLS Paul Hoffman
Re: How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Server Push request header fields RUELLAN Herve
RE: Server Push -> Cache Push? RUELLAN Herve
Re: How to handle HTTP/2 negotiation failure WRT TLS Michael Sweet
Re: Priority straw man Tatsuhiro Tsujikawa
Re: Compression ratio of HPACK. Adrian Cole
Re: Server Push -> Cache Push? Adrian Cole
Re: Server Push -> Cache Push? Daniel Stenberg
Re: Server Push -> Cache Push? Stefan Eissing
Re: Server Push -> Cache Push? Stefan Eissing
Re: Clarification requested on use of HTTP Redirect 307 Julian Reschke
Compression ratio of HPACK. 山本和彦
Re: Server Push -> Cache Push? Mark Nottingham
Re: Server Push -> Cache Push? Jeff Pinner
How to handle HTTP/2 negotiation failure WRT TLS 陈智昌
Re: Server Push -> Cache Push? Matthew Kerwin
Re: Server Push -> Cache Push? Mike Belshe
Re: Server Push -> Cache Push? Amos Jeffries
Re: Server Push -> Cache Push? Mark Nottingham
Re: Server Push -> Cache Push? Roberto Peon
Re: Server Push -> Cache Push? Roberto Peon
Server Push -> Cache Push? Hasan Khalil

Wednesday, 29 January 2014

Server Push -> Cache Push? Mark Nottingham
Re: TLS renegotiation Ilari Liusvaara
Re: TLS renegotiation Yoav Nir
Re: GOAWAY -> GTFO Matthew Kerwin
Clarification requested on use of HTTP Redirect 307 Phil Hunt
Re: #552: allow privacy proxies to be conformant Bjoern Hoehrmann
Re: TLS renegotiation Ilari Liusvaara
Re: #552: allow privacy proxies to be conformant Roy T. Fielding
Re: GOAWAY -> GTFO Zhong Yu
Re: TLS renegotiation Martin Thomson
Re: Priority straw man Martin Thomson
Re: GOAWAY -> GTFO Yoav Nir
Re: GOAWAY -> GTFO Simon Yarde
Re: GOAWAY -> GTFO CIURANA EUGENE (pr3d4t0r)
Re: TLS renegotiation Michael Sweet
Re: Priority straw man Tatsuhiro Tsujikawa
RE: TLS renegotiation Yoav Nir
Re: #552: allow privacy proxies to be conformant Amos Jeffries
Re: TLS renegotiation Ludin, Stephen
#552: allow privacy proxies to be conformant Roy T. Fielding

Tuesday, 28 January 2014

Re: GOAWAY -> GTFO Phil Hunt
Re: GOAWAY -> GTFO Zhong Yu
Re: GOAWAY -> GTFO Adrian Cole
Re: TLS renegotiation Brian Smith
Re: GOAWAY -> GTFO Adrian Cole
Re: Priorities Michael Sweet
Re: Priorities Martin Thomson
Re: GOAWAY -> GTFO Daniel Sommermann
RE: Re-work of op-code patterns RUELLAN Herve
Re: #545 requirement on implementing methods according to their semantics Julian Reschke
Priorities Julian Reschke
Re: GOAWAY -> GTFO Yoav Nir
Re: GOAWAY -> GTFO Simon Yarde
Initial minutes for Zurich Mark Nottingham
Re: GOAWAY -> GTFO Martin J. Dürst
Re: GOAWAY -> GTFO Glen Knowles
Re: GOAWAY -> GTFO Mark Nottingham
Re: GOAWAY -> GTFO Roberto Peon

Monday, 27 January 2014

Re: GOAWAY -> GTFO Martin Thomson
Re: GOAWAY -> GTFO Amos Jeffries
Re: GOAWAY -> GTFO David Morris
Re: GOAWAY -> GTFO David Morris
RE: GOAWAY -> GTFO David Morris
Re: GOAWAY -> GTFO Martin Thomson
Re: GOAWAY -> GTFO Martin Thomson
Re: GOAWAY -> GTFO Amos Jeffries
Re: GOAWAY -> GTFO Bruce Perens
Re: GOAWAY -> GTFO Mike Belshe
RE: GOAWAY -> GTFO Amos Jeffries
Re: GOAWAY -> GTFO Jesse Wilson
Re: Priority straw man Jeff Pinner
Re: Priority straw man Martin Thomson
RE: GOAWAY -> GTFO Mike Bishop
Re: GOAWAY -> GTFO Bruce Perens
Re: GOAWAY -> GTFO Mike Belshe
Re: Priority straw man Jeff Pinner
Re: Priority straw man Martin Thomson
Re: Priority straw man Jeff Pinner
Re: Re-work of op-code patterns Jeff Pinner
Re: Re-work of op-code patterns Martin Thomson
GOAWAY -> GTFO Daniel Sommermann
Re: Re-work of op-code patterns Jeff Pinner
FW: HPACK analysis Rob Trace
Re-work of op-code patterns RUELLAN Herve
Re: BLOCKED frame. Patrick McManus
Re: #545 requirement on implementing methods according to their semantics Julian Reschke

Sunday, 26 January 2014

Re: BLOCKED frame. Roberto Peon
Priority straw man Martin Thomson
Re: BLOCKED frame. Martin Thomson

Saturday, 25 January 2014

Re: BLOCKED frame. Mike Belshe
Re: TLS renegotiation Mike Belshe
TLS renegotiation Martin Thomson
BLOCKED frame. Roberto Peon

Friday, 24 January 2014

#551: recipient handling of trailer fields Roy T. Fielding

Thursday, 23 January 2014

#347 extra opcodes vs. flags Martin Thomson
Re: #539: mention TLS vs plain text passwords or dict attacks? Julian Reschke
Re: Minutes from the interim? Martin Thomson
Minutes from the interim? James M Snell

Wednesday, 22 January 2014

RE: UTF-8 in URIs Larry Masinter
Re: #539: mention TLS vs plain text passwords or dict attacks? Julian Reschke

Tuesday, 21 January 2014

Re: comparing eproxy proposals -- with some corrections Peter Lepeska

Monday, 20 January 2014

Re: Comments on draft-chan-http2-stream-dependencies-00 Jeff Pinner

Sunday, 19 January 2014

Re: Comments on draft-chan-http2-stream-dependencies-00 Amos Jeffries
Re: UTF-8 in URIs Martin Thomson
Re: #532 draft-ietf-httpbis-p1-messaging-25, "5.7.2 Transformations" Roy T. Fielding
Re: viewport size header Patrick McManus
Re: Comments on draft-chan-http2-stream-dependencies-00 Tatsuhiro Tsujikawa
comparing eproxy proposals -- with some corrections Peter Lepeska
Re: comparing eproxy proposals Peter Lepeska

Saturday, 18 January 2014

Re: viewport size header Guustaaf Damave
Re: viewport size header Julian Reschke
Re: comparing eproxy proposals Roberto Peon
Re: comparing eproxy proposals Peter Lepeska
viewport size header Guustaaf Damave
Re: comparing eproxy proposals Stephen Farrell
Re: comparing eproxy proposals Poul-Henning Kamp
Re: UTF-8 in URIs Tim Bray
comparing eproxy proposals Peter Lepeska
Re: UTF-8 in URIs Zhong Yu

Friday, 17 January 2014

Re: Proposal: Explicit HTTP2S proxy with any node refusal Peter Lepeska
RE: Comments on draft-chan-http2-stream-dependencies-00 RUELLAN Herve
Re: UTF-8 in URIs Michael Sweet
Re: UTF-8 in URIs Poul-Henning Kamp
Re: UTF-8 in URIs Zhong Yu
Re: *** GMX Spamverdacht *** Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Julian Reschke
Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Nicolas Mailhot
Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Nicolas Mailhot
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Poul-Henning Kamp
Re: UTF-8 in URIs Martin J. Dürst
Re: UTF-8 in URIs Martin J. Dürst
RE: UTF-8 in URIs Larry Masinter

Thursday, 16 January 2014

Re: *** GMX Spamverdacht *** Re: #550 handling mismatches between socket connection and host header field Amos Jeffries
#532 draft-ietf-httpbis-p1-messaging-25, "5.7.2 Transformations" Julian Reschke
Re: *** GMX Spamverdacht *** Re: #550 handling mismatches between socket connection and host header field Julian Reschke
Re: #550 handling mismatches between socket connection and host header field Bjoern Hoehrmann
#550 handling mismatches between socket connection and host header field Julian Reschke
Re: UTF-8 in URIs Julian Reschke
Re: Clarification on HTTP redirects 301,302, and 307 Julian Reschke
Re: Clarification on HTTP redirects 301,302, and 307 Phil Hunt
Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Amos Jeffries
Re: Clarification on HTTP redirects 301,302, and 307 Julian Reschke
Re: Clarification on HTTP redirects 301,302, and 307 Phil Hunt
Re: Clarification on HTTP redirects 301,302, and 307 Julian Reschke
Re: Clarification on HTTP redirects 301,302, and 307 Phil Hunt
Re: Clarification on HTTP redirects 301,302, and 307 Julian Reschke
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Mark Baker
Clarification on HTTP redirects 301,302, and 307 Phil Hunt
Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Martin Thomson
RE: *** GMX Spamverdacht *** Re: UTF-8 in URIs Gabriel Montenegro
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Phil Hunt
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Julian Reschke
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Phil Hunt
Re: Comments on draft-chan-http2-stream-dependencies-00 Peter Lepeska
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Julian Reschke
Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt Phil Hunt
Re: Fwd: New Version Notification for draft-hunt-http-rest-redirect-00.txt Mark Baker
Re: why not WPAD? Peter Lepeska
Re: *** GMX Spamverdacht *** Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Nicolas Mailhot
Re: UTF-8 in URIs Nicolas Mailhot
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Nicolas Mailhot
Re: UTF-8 in URIs Michael Sweet
Re: why not WPAD? Adrien de Croy
Re: UTF-8 in URIs Zhong Yu
Re: UTF-8 in URIs Zhong Yu
Re: UTF-8 in URIs Bjoern Hoehrmann
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Nicolas Mailhot
Re: UTF-8 in URIs Poul-Henning Kamp
Re: why not WPAD? Nicolas Mailhot
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Julian Reschke
Re: why not WPAD? Nicolas Mailhot
Re: UTF-8 in URIs Nicolas Mailhot
Re: why not WPAD? Nicolas Mailhot
Re: UTF-8 in URIs Poul-Henning Kamp
Re: UTF-8 in URIs Julian Reschke
Re: UTF-8 in URIs Poul-Henning Kamp
Re: Fwd: New Version Notification for draft-hunt-http-rest-redirect-00.txt Julian Reschke
Re: UTF-8 in URIs Julian Reschke
Re: Comments on draft-chan-http2-stream-dependencies-00 Amos Jeffries
Re: why not WPAD? Adrien de Croy
Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Shigeki Ohtsu
Re: why not WPAD? Amos Jeffries
Fwd: New Version Notification for draft-hunt-http-rest-redirect-00.txt Phil Hunt

Wednesday, 15 January 2014

Re: why not WPAD? Adrien de Croy
Re: Comments on draft-chan-http2-stream-dependencies-00 Roberto Peon
Re: why not WPAD? Peter Lepeska
Re: new draft trusted-proxy20-00 Adrien de Croy
Re: Comments on draft-chan-http2-stream-dependencies-00 Amos Jeffries
Re: new draft trusted-proxy20-00 Peter Lepeska
Re: why not WPAD? Peter Lepeska
Re: Comments on draft-chan-http2-stream-dependencies-00 陈智昌
Re: why not WPAD? Adrien de Croy
Re: new draft trusted-proxy20-00 Adrien de Croy
Re: why not WPAD? Eliot Lear
Re: UTF-8 in URIs Poul-Henning Kamp
Re: UTF-8 in URIs Zhong Yu
RE: UTF-8 in URIs Dave Thaler
Re: UTF-8 in URIs Michael Sweet
UTF-8 in URIs Gabriel Montenegro
Re: why not WPAD? Martin Thomson
why not WPAD? Peter Lepeska
Re: new draft trusted-proxy20-00 Peter Lepeska
Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Roberto Peon
Re: new draft trusted-proxy20-00 Peter Lepeska
Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Martin Thomson
Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Roberto Peon
Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Martin Thomson
Re: Comments on draft-chan-http2-stream-dependencies-00 Martin Thomson
Re: #549 augment security considerations Julian Reschke
Re: #549 augment security considerations Julian Reschke
Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS Shigeki Ohtsu
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt 陈智昌
Re: Comments on draft-chan-http2-stream-dependencies-00 陈智昌

Tuesday, 14 January 2014

Re: new draft trusted-proxy20-00 Nicolas Mailhot
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt Jeff Pinner
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt 陈智昌
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt Jeff Pinner
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt Roberto Peon
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt Jeff Pinner

Monday, 13 January 2014

Comments on draft-chan-http2-stream-dependencies-00 Martin Thomson
Re: #549 augment security considerations Michael Sweet
Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt 陈智昌
Re: new draft trusted-proxy20-00 Adrien de Croy
Re: new draft trusted-proxy20-00 Nicolas Mailhot
#549 augment security considerations Julian Reschke
Re: new draft trusted-proxy20-00 Yoav Nir
Re: #547 clarify PUT on content negotiated resource Julian Reschke

Sunday, 12 January 2014

Invitation to connect on LinkedIn SUNGHAN WIPO
Poll: Design Team Meeting after London Mark Nottingham

Saturday, 11 January 2014

Re: #547 clarify PUT on content negotiated resource Amos Jeffries

Friday, 10 January 2014

Re: #547 clarify PUT on content negotiated resource Bjoern Hoehrmann
Re: #547 clarify PUT on content negotiated resource Martin Thomson
#547 clarify PUT on content negotiated resource Julian Reschke
Re: Error behevior of receiving PUSH_PROMISE when SETTINGS_ENABLE_PUSH is 0 Martin Thomson
Re: Does anyone know if F5 are working on http/2 陈智昌
Does anyone know if F5 are working on http/2 Adrian Cole
new draft trusted-proxy20-00 Salvatore Loreto
Re: Interim meeting around London? Salvatore Loreto
FYI: ALPN implementation status tracking Mark Nottingham
RE: Interim meeting around London? Rob Trace
Re: working on HPACK test case Jeff Pinner
Re: HTTP/2.0 draft, NPN/ALPN, and TLS Adrian Cole
Things I like about HPACK Adrian Cole
Re: working on HPACK test case Adrian Cole

Thursday, 9 January 2014

Re: Interim meeting around London? Martin Thomson
Re: Interim meeting around London? Roberto Peon
Re: HTTP/2 stream state Reserved can only go to Half-Closed 陈智昌
Re: Interim meeting around London? 陈智昌
Re: HTTP/2 stream state Reserved can only go to Half-Closed Jeff Pinner
HTTP/2 stream state Reserved can only go to Half-Closed 陈智昌
Re: Interim meeting around London? Patrick McManus
Interim meeting around London? Mark Nottingham
Re: Error behevior of receiving PUSH_PROMISE when SETTINGS_ENABLE_PUSH is 0 Shigeki Ohtsu
Re: Error behevior of receiving PUSH_PROMISE when SETTINGS_ENABLE_PUSH is 0 Roberto Peon
Error behevior of receiving PUSH_PROMISE when SETTINGS_ENABLE_PUSH is 0 Shigeki Ohtsu

Wednesday, 8 January 2014

Re: Questions in draft-09 Martin Thomson
Re: Questions in draft-09 Tatsuhiro Tsujikawa
Re: HTTP/2 and NCSA Poul-Henning Kamp
Re: Questions in draft-09 Shigeki Ohtsu
Re: Questions in draft-09 Tatsuhiro Tsujikawa
Re: HTTP/2 and NCSA Mark Nottingham
Re: Questions in draft-09 Shigeki Ohtsu

Tuesday, 7 January 2014

working on HPACK test case block.rxckin.beats@gmail.com
Re: userinfo in :authority Martin Thomson
Re: Questions in draft-09 Martin Thomson
Re: userinfo in :authority Patrick McManus
Re: userinfo in :authority Martin Thomson
Re: Questions in draft-09 Tatsuhiro Tsujikawa
Re: HTTP/2 and NCSA Nicolas Mailhot
Questions in draft-09 Shigeki Ohtsu
Re: HTTP/2 and NCSA Poul-Henning Kamp
Re: HTTP/2 and NCSA Stephen Farrell
Re: userinfo in :authority Bjoern Hoehrmann
Re: HTTP/2 and NCSA Mark Nottingham

Monday, 6 January 2014

Re: Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt Amos Jeffries
Re: HPACK: replace Huffman by possibly faster and more efficient FSE (Finite State Entropy) Amos Jeffries
Re: userinfo in :authority Amos Jeffries
userinfo in :authority Martin Thomson
Fwd: New Version Notification for draft-chan-http2-stream-dependencies-00.txt 陈智昌
Re: HPACK: replace Huffman by possibly faster and more efficient FSE (Finite State Entropy) Peter Lepeska
Re: HPACK: replace Huffman by possibly faster and more efficient FSE (Finite State Entropy) James M Snell
Re: HTTP/2 and NCSA Poul-Henning Kamp
Re: HPACK: replace Huffman by possibly faster and more efficient FSE (Finite State Entropy) Michael Sweet
Re: HTTP/2 and NCSA Yves Lafon
HTTP/2 and NCSA Poul-Henning Kamp
Re: #545 requirement on implementing methods according to their semantics Mark Nottingham

Sunday, 5 January 2014

Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS 陈智昌
Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS Roberto Peon
Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS Martin Thomson
Re: New Version Notification for draft-nottingham-http2-encryption-02.txt Eliot Lear

Saturday, 4 January 2014

HPACK: replace Huffman by possibly faster and more efficient FSE (Finite State Entropy) Frédéric Kayser
#546 considerations for new headers: privacy Julian Reschke
Re: #532 IESG ballot on draft-ietf-httpbis-p2-semantics-25, reason phrase optional? Amos Jeffries
#532 IESG ballot on draft-ietf-httpbis-p2-semantics-25, reason phrase optional? Julian Reschke
Re: #545 requirement on implementing methods according to their semantics Julian Reschke

Friday, 3 January 2014

Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS 陈智昌
Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS Martin Thomson
Re: minimum value for SETTINGS_MAX_CONCURRENT_STREAMS Daniel Sommermann
Re: #545 requirement on implementing methods according to their semantics Julian Reschke
Re: #545 requirement on implementing methods according to their semantics Amos Jeffries
#545 requirement on implementing methods according to their semantics Julian Reschke
minimum value for SETTINGS_MAX_CONCURRENT_STREAMS Daniel Sommermann

Thursday, 2 January 2014

Re: Risks with NULL Mime type Martin Nilsson
Re: #539: mention TLS vs plain text passwords or dict attacks? Amos Jeffries
#539: mention TLS vs plain text passwords or dict attacks? Julian Reschke
Re: #540 clarify ABNF layering Mark Nottingham
Risks with NULL Mime type Amit Aggarwal

Wednesday, 1 January 2014

Re: #540 clarify ABNF layering Julian Reschke
Zurich Agenda Mark Nottingham
Re: #540 clarify ABNF layering Mark Nottingham

Last message date: Monday, 31 March 2014 23:53:06 UTC