ietf-http-wg@w3.org from April to June 2014 by date

Monday, 30 June 2014

RE: CONTINUATION proposal w/ minimum change Mike Bishop
Re: CONTINUATION proposal w/ minimum change Jason Greene
RE: CONTINUATION proposal w/ minimum change Mike Bishop
Re: CONTINUATION proposal w/ minimum change Jason Greene
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
RE: CONTINUATION proposal w/ minimum change Mike Bishop
Re: [Technical Errata Reported] RFC7231 (4031) Julian Reschke
Re: END_SEGMENT? (#397) David Krauss
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: END_SEGMENT? (#397) Martin Thomson
Re: CRLF requirement Martin Thomson
Re: [Technical Errata Reported] RFC7231 (4031) Barry Leiba
Re: END_SEGMENT? (#397) David Krauss
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: CONTINUATION proposal w/ minimum change Martin Thomson
CONTINUATION proposal w/ minimum change K.Morgan@iaea.org
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Fwd: I-D Action: draft-prudhommeaux-http-status-2nn-00.txt Julian Reschke
Re: END_SEGMENT? (#397) Martin Thomson
Re: END_SEGMENT? (#537) Daniel Sommermann
Re: END_SEGMENT? (#397) David Krauss
Re: END_SEGMENT? (#397) Martin Thomson
Re: why not multiple, short-lived HTTP/2 connections? Mike Belshe
Re: why not multiple, short-lived HTTP/2 connections? Patrick McManus
Re: END_SEGMENT? (#397) David Krauss
Re: END_SEGMENT? (#397) Martin Thomson
Re: END_SEGMENT? (#397) Daniel Sommermann
Re: hpack table size 0 Martin Thomson
Re: draft-hutton-httpbis-connect-protocol-00.txt Martin Thomson
Re: Re: draft-hutton-httpbis-connect-protocol-00.txt Martin Thomson
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
RE: hpack table size 0 K.Morgan@iaea.org
Re: CRLF requirement David Krauss
RE: hpack table size 0 Mike Bishop
RE: REFUSED_STREAM and HPACK RUELLAN Herve
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Julian Reschke
Re: CRLF requirement Carsten Bormann
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Julian Reschke
hpack table size 0 K.Morgan@iaea.org
Re: CRLF requirement Michael Sweet
Re: CRLF requirement Julian Reschke
REFUSED_STREAM and HPACK K.Morgan@iaea.org
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Willy Tarreau
Re: CRLF requirement Julian Reschke
Re: [Technical Errata Reported] RFC7231 (4031) Julian Reschke
CRLF requirement Anne van Kesteren
Re: [Technical Errata Reported] RFC7231 (4031) Mark Nottingham
Re: draft-hutton-httpbis-connect-protocol-00.txt Sergio Garcia Murillo
Re: CONTINUATION was: #540: "jumbo" frames Nicolas Mailhot

Saturday, 28 June 2014

Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Roberto Peon
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Roberto Peon
Re: Confusing numbering of flags & bits Mike Bishop
Confusing numbering of flags & bits Willy Tarreau
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re:Re: draft-hutton-httpbis-connect-protocol-00.txt squid3@treenet.co.nz

Friday, 27 June 2014

RE: #540: "jumbo" frames Mike Bishop
Re: draft-hutton-httpbis-connect-protocol-00.txt Martin Thomson
Re: draft-hutton-httpbis-connect-protocol-00.txt Sergio Garcia Murillo
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Willy Tarreau
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Willy Tarreau
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Jason Greene
RE: proposed clarifications regarding the state machine (editorial) K.Morgan@iaea.org
Re: #540: "jumbo" frames Michael Sweet
Re: #540: "jumbo" frames Michael Sweet
Re: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Jason Greene
Re: #541: Stateless Multiplexable Continuations Jason Greene
Re: #535: No 1xx Status Codes Michael Sweet
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Michael Sweet
Re: #535: No 1xx Status Codes Julian Reschke
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: CONTINUATION was: #540: "jumbo" frames Michael Sweet
Re: #535: No 1xx Status Codes Michael Sweet
Re: #540: "jumbo" frames Adrian Cole
RE: #540: "jumbo" frames Mike Bishop
Re: #540: "jumbo" frames Martin Thomson
Re: CONTINUATION was: #540: "jumbo" frames Martin Thomson
Re: #535: No 1xx Status Codes Michael Sweet
Re: #541: Stateless Multiplexable Continuations Martin Thomson
CONTINUATION was: #540: "jumbo" frames K.Morgan@iaea.org
Re: proposed clarifications regarding the state machine (editorial) Martin Thomson
Re: #540: "jumbo" frames Michael Sweet
Re: #540: "jumbo" frames Martin Thomson
Re: CONTINUATION was: #540: "jumbo" frames Michael Sweet
Re: draft-hutton-httpbis-connect-protocol-00.txt Martin Thomson
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: #541: Stateless Multiplexable Continuations Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Patrick McManus
Re: CONTINUATION was: #540: "jumbo" frames Shigeki Ohtsu
Re: CONTINUATION was: #540: "jumbo" frames Johnny Graettinger
proposed clarifications regarding the state machine (editorial) K.Morgan@iaea.org
Re: CONTINUATION was: #540: "jumbo" frames Tatsuhiro Tsujikawa
Re: CONTINUATION was: #540: "jumbo" frames Simone Bordet
Re: CONTINUATION was: #540: "jumbo" frames Mark Nottingham
Re: #540: "jumbo" frames David Krauss
Re: CONTINUATION was: #540: "jumbo" frames Poul-Henning Kamp
RE: draft-hutton-httpbis-connect-protocol-00.txt Sergio Garcia Murillo
RE: #535: No 1xx Status Codes K.Morgan@iaea.org
Re: CONTINUATION was: #540: "jumbo" frames Simone Bordet
Re: #535: No 1xx Status Codes Julian Reschke
FW: I-D Action: draft-hutton-httpbis-connect-protocol-00.txt Hutton, Andrew
Initial agenda for Toronto Mark Nottingham
Re: CONTINUATION was: #540: "jumbo" frames Cory Benfield
HTTP/2 Implementation Draft 5 (and getting to Working Group Last Call) Mark Nottingham
#535: No 1xx Status Codes Mark Nottingham
Re: #540: "jumbo" frames Mark Nottingham
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Mark Nottingham
Re: #540: "jumbo" frames Greg Wilkins
#541: Stateless Multiplexable Continuations Mark Nottingham
Re: CONTINUATION was: #540: "jumbo" frames David Krauss
#540: "jumbo" frames Mark Nottingham
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re: CONTINUATION was: #540: "jumbo" frames Amos Jeffries
Re: CONTINUATION was: #540: "jumbo" frames Poul-Henning Kamp
Re: CONTINUATION was: #540: "jumbo" frames Poul-Henning Kamp
Re: CONTINUATION was: #540: "jumbo" frames Willy Tarreau
Re: Stateless Multiplexable Continuations #541 Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Martin Thomson
RE: CONTINUATION was: #540: "jumbo" frames Roberto Peon

Thursday, 26 June 2014

RE: CONTINUATION was: #540: "jumbo" frames K.Morgan@iaea.org
Re: CONTINUATION was: #540: "jumbo" frames Jesse McConnell
Re: CONTINUATION was: #540: "jumbo" frames Martin Thomson
RE: CONTINUATION was: #540: "jumbo" frames K.Morgan@iaea.org
RE: Stateless Multiplexable Continuations #541 K.Morgan@iaea.org
Re: CONTINUATION was: #540: "jumbo" frames Roberto Peon
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re: CONTINUATION was: #540: "jumbo" frames Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Martin Thomson
Re: CONTINUATION was: #540: "jumbo" frames Greg Wilkins
Re: Stateless Multiplexable Continuations #541 Jason Greene
Re: CONTINUATION was: #540: "jumbo" frames Mike Bishop
Stateless Multiplexable Continuations #541 Jason Greene
Re: Stuck in a train -- reading HTTP/2 draft. Johnny Graettinger
Re: #540: "jumbo" frames Martin Thomson
CONTINUATION was: #540: "jumbo" frames K.Morgan@iaea.org
Re: agenda/charter brainstorming Stephen Farrell
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Amos Jeffries
Re: #540: "jumbo" frames Amos Jeffries
Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Willy Tarreau
Re: agenda/charter brainstorming Yoav Nir
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
Re: #540: "jumbo" frames 陈智昌
Re: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Jason Greene
RE: #540: "jumbo" frames Daniel Stenberg
Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Jason Greene
Re: agenda/charter brainstorming Mark Nottingham
Re: #540: "jumbo" frames Martin Thomson
RE: #540: "jumbo" frames Gabriel Montenegro

Wednesday, 25 June 2014

Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Jason Greene
Re: Stuck in a train -- reading HTTP/2 draft. Johnny Graettinger
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Greg Wilkins
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Roberto Peon
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Roberto Peon
RE: #540: "jumbo" frames K.Morgan@iaea.org
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: Stuck in a train -- reading HTTP/2 draft. Roberto Peon
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Greg Wilkins
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Roberto Peon
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Mike Belshe
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Greg Wilkins
Re: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Mike Belshe
Re: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Roberto Peon
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
Re: #540: "jumbo" frames Martin Thomson
Re: Stuck in a train -- reading HTTP/2 draft. Roberto Peon
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Nicholas Hurley
Re: #540: "jumbo" frames Greg Wilkins
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
Re: #540: "jumbo" frames Roberto Peon
Re: #540: "jumbo" frames Roberto Peon
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Nicholas Hurley
Re: #540: "jumbo" frames Patrick McManus
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Willy Tarreau
Re: agenda/charter brainstorming Poul-Henning Kamp
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Jason Greene
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Re: #540: "jumbo" frames Nicholas Hurley
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
Re: agenda/charter brainstorming Yoav Nir
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Martin Thomson
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: agenda/charter brainstorming Poul-Henning Kamp
Re: Back to the drawing board? was: #540: "jumbo" frames David Krauss
Re: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Johnny Graettinger
Re: why not multiple, short-lived HTTP/2 connections? Mike Belshe
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: #540: "jumbo" frames Patrick McManus
Re: #540: "jumbo" frames Ludin, Stephen
Re: #540: "jumbo" frames Adrian Cole
Re: agenda/charter brainstorming Yoav Nir
Re: agenda/charter brainstorming Amos Jeffries
Re: Back to the drawing board? was: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Matthew Kerwin
Re: #540: "jumbo" frames Greg Wilkins
Re: #540: "jumbo" frames Mark Nottingham
Re: Should we discuss "split UAs" in the context of proxies, was: Proxies (includes call for adopting new work item, call for input) John Mattsson
Back to the drawing board? was: #540: "jumbo" frames Greg Wilkins
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Willy Tarreau
Re: #540: "jumbo" frames Greg Wilkins
Re: #540: "jumbo" frames David Krauss
RE: #540: "jumbo" frames K.Morgan@iaea.org
Re: #540: "jumbo" frames Martin J. Dürst
Re: #540: "jumbo" frames Greg Wilkins
Re: Ops advice Mark Nottingham
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: #540: "jumbo" frames Willy Tarreau
#540: "jumbo" frames Mark Nottingham
Re: Trusted proxy UI redux Mark Nottingham

Tuesday, 24 June 2014

Re: #540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: why not multiple, short-lived HTTP/2 connections? Mike Belshe
Re: why not multiple, short-lived HTTP/2 connections? Greg Wilkins
Re: agenda/charter brainstorming Yoav Nir
Re: #540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
RE: #540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
Re: why not multiple, short-lived HTTP/2 connections? Willy Tarreau
Re: why not multiple, short-lived HTTP/2 connections? Guille -bisho-
why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: #540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
#540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
Re: Trusted proxy UI redux Patrick McManus
Trusted proxy UI redux bizzbyster@gmail.com
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Who to trust? Greg Wilkins
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
Re: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
Re: Framing the proxy discussion Martin J. Dürst
Re: Stuck in a train -- reading HTTP/2 draft. Amos Jeffries
Re: Stuck in a train -- reading HTTP/2 draft. David Krauss
Re: Stuck in a train -- reading HTTP/2 draft. David Krauss
Re: agenda/charter brainstorming Amos Jeffries
Re: Stuck in a train -- reading HTTP/2 draft. Willy Tarreau
Re: Stuck in a train -- reading HTTP/2 draft. Mark Nottingham
Re: agenda/charter brainstorming Julian Reschke
Re: agenda/charter brainstorming Mark Nottingham
Re: HTTP/2 vs. proxies ? Adrien de Croy
Re: HTTP/2 vs. proxies ? Amos Jeffries
Re: Framing the proxy discussion: does HTTP2 come with new proxy mechanism ? Mark Nottingham
Fwd: httpbis - Requested sessions have been scheduled for IETF 90 Mark Nottingham
Re: agenda/charter brainstorming Mark Nottingham
Re: Framing the proxy discussion Mark Nottingham
Re: HTTP/2 vs. proxies ? Matthew Kerwin

Monday, 23 June 2014

Re: Who to trust? Martin Thomson
Re: Proxies (includes call for adopting new work item, call for input) Martin Thomson
Re: agenda/charter brainstorming James M Snell
Re: HTTP/2 vs. proxies ? Peter L
Re: HTTP/2 vs. proxies ? Adrien de Croy
Re: Who to trust? Frode Kileng
Re: Who to trust? Poul-Henning Kamp
Re: Framing the proxy discussion Barry Leiba
Re: HTTP/2 vs. proxies ? Poul-Henning Kamp
Re: Trusted proxy UI strawman Nicolas Mailhot
Re: Who to trust? Adrien de Croy
Who to trust? Frode Kileng
Re: HTTP/2 vs. proxies ? bizzbyster@gmail.com
Re: Proxies (includes call for adopting new work item, call for input) bizzbyster@gmail.com
Re: Trusted proxy UI strawman 陈智昌
Re: agenda/charter brainstorming Julian Reschke
Re: HTTP/2 vs. proxies ? Jason Greene
Re: agenda/charter brainstorming Poul-Henning Kamp
RE: HTTP/2 vs. proxies ? Mike Bishop
Re: Framing the proxy discussion: does HTTP2 come with new proxy mechanism ? Martin Thomson
Re: Proxies (includes call for adopting new work item, call for input) Martin Thomson
Re: agenda/charter brainstorming Julian Reschke
Re: jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. James M Snell
Re: agenda/charter brainstorming James M Snell
Re: Should we discuss "split UAs" in the context of proxies, was: Proxies (includes call for adopting new work item, call for input) Nicolas Mailhot
Should we discuss "split UAs" in the context of proxies, was: Proxies (includes call for adopting new work item, call for input) Julian Reschke
jumbo frame, was: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Trusted proxy UI strawman Nicolas Mailhot
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Framing the proxy discussion Michael Sweet
Re: Trusted proxy UI strawman 陈智昌
RE: Framing the proxy discussion: does HTTP2 come with new proxy mechanism ? emile.stephan@orange.com
RE: Framing the proxy discussion K.Morgan@iaea.org
Re: Proxies (includes call for adopting new work item, call for input) Smith, Kevin, (R&D) Vodafone Group
Re: Proxies (includes call for adopting new work item, call for input) Nicolas Mailhot
Re: Proxies (includes call for adopting new work item, call for input) Nicolas Mailhot
Re: Range Requests vs Content Codings Roland Zink
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
RE: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
RE: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
Re: agenda/charter brainstorming Poul-Henning Kamp
agenda/charter brainstorming Julian Reschke
Re: Trusted proxy UI strawman Nicolas Mailhot
Framing the proxy discussion Mark Nottingham
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: HTTP/2 vs. proxies ? Mark Nottingham
Re: Proxies (includes call for adopting new work item, call for input) Albert Lunde

Sunday, 22 June 2014

Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Proxies (includes call for adopting new work item, call for input) Eric Rescorla
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: Proxies (includes call for adopting new work item, call for input) Eric Rescorla
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Proxies (includes call for adopting new work item, call for input) Eric Rescorla
Re: Proxies (includes call for adopting new work item, call for input) Julian Reschke
Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: Stuck in a train -- reading HTTP/2 draft. Mark Nottingham
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Proxies (includes call for adopting new work item, call for input) Julian Reschke
Re: HTTP/2 vs. proxies ? Amos Jeffries
Re: HTTP/2 vs. proxies ? Cory Benfield
Re: intermediaries, implicit gzip, etags, no-transform Eric J. Bowman
Re: HTTP/2 vs. proxies ? Matthew Kerwin
Re: HTTP/2 vs. proxies ? Eric J. Bowman
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: Ops advice Adrian Cole

Saturday, 21 June 2014

Re: intermediaries, implicit gzip, etags, no-transform Eric J. Bowman
Re: intermediaries, implicit gzip, etags, no-transform Eric J. Bowman
Re: intermediaries, implicit gzip, etags, no-transform Greg Wilkins
Re: Stuck in a train -- reading HTTP/2 draft. Martin Nilsson
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Stuck in a train -- reading HTTP/2 draft. Martin Nilsson
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
RE: Proxies (includes call for adopting new work item, call for input) Richard Wheeldon (rwheeldo)
RE: Stuck in a train -- reading HTTP/2 draft. Richard Wheeldon (rwheeldo)
Re: Range Requests vs Content Codings Zhong Yu
Re: Range Requests vs Content Codings Zhong Yu
RE: Range Requests vs Content Codings K.Morgan@iaea.org
HTTP/2 vs. proxies ? Poul-Henning Kamp
Re: intermediaries, implicit gzip, etags, no-transform Poul-Henning Kamp
RE: Range Requests vs Content Codings K.Morgan@iaea.org
RE: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
RE: Stuck in a train -- reading HTTP/2 draft. K.Morgan@iaea.org
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: intermediaries, implicit gzip, etags, no-transform Amos Jeffries
Re: Stuck in a train -- reading HTTP/2 draft. Amos Jeffries
Re: intermediaries, implicit gzip, etags, no-transform Matthew Kerwin

Friday, 20 June 2014

Re: intermediaries, implicit gzip, etags, no-transform Michael Piatek
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Martin Thomson
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Johnny Graettinger
Re: intermediaries, implicit gzip, etags, no-transform Michael Piatek
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Michael Piatek
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: intermediaries, implicit gzip, etags, no-transform Martin Nilsson
Re: Stuck in a train -- reading HTTP/2 draft. Martin Nilsson
RE: Trusted proxy UI strawman Richard Wheeldon (rwheeldo)
Re: Proxies (includes call for adopting new work item, call for input) Eric Rescorla
Re: intermediaries, implicit gzip, etags, no-transform James M Snell
Re: Proxies (includes call for adopting new work item, call for input) Roland Zink
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: Trusted proxy UI strawman Diego R. Lopez
Re: intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Proxies (includes call for adopting new work item, call for input) Eric Rescorla
Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
heads in the _security_ sand was: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
Re: intermediaries, implicit gzip, etags, no-transform Martin Thomson
Re: Proxies (includes call for adopting new work item, call for input) Martin Thomson
intermediaries, implicit gzip, etags, no-transform Julian Reschke
Re: Proxies (includes call for adopting new work item, call for input) Julian Reschke
Re: Trusted proxy UI strawman Stephen Farrell
Re: Trusted proxy UI strawman Roland Zink
Re: Trusted proxy UI strawman Roland Zink
Re: Trusted proxy UI strawman Eliot Lear
Re: Trusted proxy UI strawman Roland Zink
Fwd: New Version Notification for draft-nottingham-http-over-version-00.txt Mark Nottingham
Ops advice Mark Nottingham
Re: END_SEGMENT? (#397) Yutaka Hirano
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
RE: Trusted proxy UI strawman Richard Wheeldon (rwheeldo)
RE: Trusted proxy UI strawman Richard Wheeldon (rwheeldo)

Thursday, 19 June 2014

Re: Trusted proxy UI strawman Adrien de Croy
Re: Trusted proxy UI strawman 陈智昌
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Re: END_SEGMENT? (#397) Jeff Pinner
Re: END_SEGMENT? (#397) Daniel Sommermann
RE: Negotiating extensions Mike Bishop
RE: Stuck in a train -- reading HTTP/2 draft. Richard Wheeldon (rwheeldo)
Re: HPACK Poul-Henning Kamp
Re: HPACK Martin Nilsson
RE: Stuck in a train -- reading HTTP/2 draft. Richard Wheeldon (rwheeldo)
Re: END_SEGMENT? (#397) Jeff Pinner
Re: END_SEGMENT? (#397) Jeff Pinner
Negotiating extensions Martin Thomson
Re: END_SEGMENT? (#397) Daniel Sommermann
Re: strong server authentication Martin Thomson
Re: END_SEGMENT? (#397) Martin Thomson
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Client Behavior for SETTINGS_TIMEOUT Patrick McManus
Re: Stuck in a train -- reading HTTP/2 draft. Kinkie
Re: HPACK Greg Wilkins
Re: explicitly authenticated proxy: new draft Chris Bentzel
strong server authentication emile.stephan@orange.com
Re: END_SEGMENT? (#397) Yutaka Hirano
Re: Stuck in a train -- reading HTTP/2 draft. Amos Jeffries
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Amos Jeffries
Re: explicitly authenticated proxy: new draft Mark Nottingham
Re: ALPN RFC Amos Jeffries
Re: Stuck in a train -- reading HTTP/2 draft. Mark Nottingham
Re: Trusted proxy UI strawman Adrien de Croy
Re: END_SEGMENT? (#397) Martin Thomson
Re: Trusted proxy UI strawman Martin Nilsson
Re: END_SEGMENT? (#397) Yutaka Hirano
Re: Stuck in a train -- reading HTTP/2 draft. Mark Nottingham

Wednesday, 18 June 2014

Re: HPACK Roberto Peon
Re: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: HPACK Greg Wilkins
Re: Stuck in a train -- reading HTTP/2 draft. James M Snell
Re: Trusted proxy UI strawman Barry Leiba
Re: Trusted proxy UI strawman Roland Zink
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Trusted proxy UI strawman Jason Greene
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Re: HPACK Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Client Behavior for SETTINGS_TIMEOUT Jason Greene
Re: Trusted proxy UI strawman Martin Thomson
Re: END_SEGMENT? (#397) Martin Thomson
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
Re: Stuck in a train -- reading HTTP/2 draft. Jason Greene
Re: Connection fatal HTTP/2 stream errors Martin Thomson
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
RE: HPACK Mike Bishop
Re: Trusted proxy UI strawman Barry Leiba
Re: END_SEGMENT? (#397) Daniel Sommermann
Re: Range Requests vs Content Codings Zhong Yu
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
Re: HPACK Michael Sweet
Re: HPACK Greg Wilkins
Re: Trusted proxy UI strawman Nicolas Mailhot
Re: HPACK Martin J. Dürst
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: HPACK Cory Benfield
Re: Range Requests vs Content Codings Julian Reschke
Re: Range Requests vs Content Codings Roland Zink
Re: ALPN RFC Julian Reschke
Re: Range Requests vs Content Codings Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: HPACK Poul-Henning Kamp
Re: Connection fatal HTTP/2 stream errors Tatsuhiro Tsujikawa
ALPN RFC Simone Bordet
Re: Toronto 陈智昌
Connection fatal HTTP/2 stream errors Greg Wilkins
Re: Trusted proxy UI strawman Martin Nilsson
Re: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
Re: Stuck in a train -- reading HTTP/2 draft. Amos Jeffries
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: Proxies (includes call for adopting new work item, call for input), ## HTTP Proxy Problems Amos Jeffries
Re: Range Requests vs Content Codings Julian Reschke
Re: Range Requests vs Content Codings Mark Nottingham
Re: Range Requests vs Content Codings Julian Reschke
Re: explicitly authenticated proxy: new draft Mark Nottingham
Re: Range Requests vs Content Codings Mark Nottingham
Re: Range Requests vs Content Codings Mark Nottingham
Toronto Mark Nottingham

Tuesday, 17 June 2014

Re: Done Mark Nottingham
Re: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: Range Requests vs Content Codings Zhong Yu
Re: Range Requests vs Content Codings Zhong Yu
Re: Range Requests vs Content Codings Matthew Kerwin
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
RE: END_SEGMENT? (#397) Mike Bishop
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Stuck in a train -- reading HTTP/2 draft. Poul-Henning Kamp
Re: Range Requests vs Content Codings Peter L
Re: Range Requests vs Content Codings Julian Reschke
Done Martin Thomson
I-D Action: draft-ietf-httpbis-http2-13.txt internet-drafts@ietf.org
Re: Range Requests vs Content Codings bizzbyster@gmail.com
I-D Action: draft-ietf-httpbis-header-compression-08.txt internet-drafts@ietf.org
Re: Range Requests vs Content Codings Julian Reschke
Re: Range Requests vs Content Codings Julian Reschke
Re: END_SEGMENT? (#397) Daniel Sommermann
Re: explicitly authenticated proxy: new draft Smith, Kevin, (R&D) Vodafone Group
Re: Range Requests vs Content Codings Matthew Kerwin
Re: Range Requests vs Content Codings Roland Zink
Re: Trusted proxy UI strawman Smith, Kevin, (R&D) Vodafone Group
Re: Stuck in a train -- reading HTTP/2 draft. Greg Wilkins
RE: HPACK RUELLAN Herve
Range Requests vs Content Codings Julian Reschke
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: explicitly authenticated proxy: new draft Julian Reschke
Re: explicitly authenticated proxy: new draft lingli deng
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Re: Stuck in a train -- reading HTTP/2 draft. Matthew Kerwin
Re: explicitly authenticated proxy: new draft Mark Nottingham
Re: explicitly authenticated proxy: new draft Stephen Farrell
Fwd: HPACK Mark Nottingham
Re: explicitly authenticated proxy: new draft Diego R. Lopez

Monday, 16 June 2014

Re: Stuck in a train -- reading HTTP/2 draft. Martin Thomson
Fwd: Stuck in a train -- reading HTTP/2 draft. Mark Nottingham
Moving 421 Martin Thomson
Re: Trusted proxy UI strawman 陈智昌
Re: explicitly authenticated proxy: new draft Mark Nottingham
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Trusted proxy UI strawman Salvatore Loreto
Re: Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt Martin Thomson
Re: Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt Stephen Farrell
Re: Trusted proxy UI strawman Martin Thomson
Re: Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt Martin Thomson
Re: Trusted proxy UI strawman Stephen Farrell
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Trusted proxy UI strawman 陈智昌
Re: Trusted proxy UI strawman Stephen Farrell
RE: Proxies (includes call for adopting new work item, call for input), ## HTTP Proxy Problems emile.stephan@orange.com
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt Martin J. Dürst
Re: Trusted proxy UI strawman Adrien de Croy
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: explicitly authenticated proxy: new draft Eric Rescorla

Sunday, 15 June 2014

Re: Proxies (includes call for adopting new work item, call for input) Diego R. Lopez
Re: Trusted proxy UI strawman Martin Nilsson
Re: Trusted proxy UI strawman Stephen Farrell
Re: Trusted proxy UI strawman Martin Nilsson
Re: Proxies (includes call for adopting new work item, call for input) Martin Nilsson
Re: Trusted proxy UI strawman Stephen Farrell
Re: explicitly authenticated proxy: new draft Martin Nilsson
Re: Trusted proxy UI strawman bizzbyster@gmail.com
Re: Trusted proxy UI strawman Martin Thomson
Re: what about Proxies in Toronto? Dan Wing
Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt Mark Nottingham
I-D Action: draft-ietf-httpbis-http2-encryption-00.txt internet-drafts@ietf.org
Trusted proxy UI strawman bizzbyster@gmail.com

Saturday, 14 June 2014

Re: Other work items Julian Reschke
Re: Other work items Matthew Kerwin
Re: Other work items Julian Reschke
Re: Other work items Mark Nottingham
Re: Priority inside PUSH_PROMISE frames David Krauss
Re: http2 Working Code David Krauss

Friday, 13 June 2014

Re: Other work items Matthew Kerwin
Re: Other work items James M Snell
Re: http2 Working Code Matthew Kerwin
Re: Other work items Martin Thomson
Re: Proxies (includes call for adopting new work item, call for input) Julian Reschke
Re: Other work items Julian Reschke
Other work items Mark Nottingham
Proxies (includes call for adopting new work item, call for input) Mark Nottingham
Re: explicitly authenticated proxy: new draft Mark Nottingham
Re: what about Proxies in Toronto? Tony Hansen
Re: http2 Working Code Martin Thomson
Re: what about Proxies in Toronto? Martin Thomson
Re: Reserved extension ids Daniel Sommermann
Re: Priority inside PUSH_PROMISE frames Martin Thomson
Re: Reserved extension ids Martin Thomson
Re: what about Proxies in Toronto? Diego R. Lopez
Reserved extension ids Daniel Sommermann
RE: what about Proxies in Toronto? DRUTA, DAN
Re: http2 Working Code Mark Nottingham
Re: http2 Working Code Willy Tarreau
Re: what about Proxies in Toronto? 陈智昌
http2 Working Code Greg Wilkins
RE: what about Proxies in Toronto? Smith, Kevin, (R&D) Vodafone Group
Re: explicitly authenticated proxy: new draft Smith, Kevin, (R&D) Vodafone Group
Re: explicitly authenticated proxy: new draft Thomas Fossati
Re: Priority inside PUSH_PROMISE frames David Krauss
Re: Priority inside PUSH_PROMISE frames Roberto Peon
Re: Priority inside PUSH_PROMISE frames Martin Thomson
Re: Priority inside PUSH_PROMISE frames Roberto Peon

Thursday, 12 June 2014

Re: Priority inside PUSH_PROMISE frames Tatsuhiro Tsujikawa
RE: Priority inside PUSH_PROMISE frames Mike Bishop
RE: what about Proxies in Toronto? Jeroen de Borst
Re: what about Proxies in Toronto? Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
what about Proxies in Toronto? Salvatore Loreto
Re: HTTP/2 vs 1.1 semantics: intermediate codes Jason Greene
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: Priority inside PUSH_PROMISE frames Jeff Pinner
Priority inside PUSH_PROMISE frames RUELLAN Herve
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
Re: #492: Alt-Svc header host restriction Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Jason Greene
Re: #492: Alt-Svc header host restriction Martin Thomson
Re: Clarifications on flow control and padding Martin Thomson
Clarifications on flow control and padding Simone Bordet
Re: #492: Alt-Svc header host restriction Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Martin Thomson
Re: #492: Alt-Svc header host restriction Martin Thomson
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Martin Thomson
Re: Including screen size to header messages (extending UserAgent) Mark Nottingham
Re: explicitly authenticated proxy: new draft Martin Nilsson
Re: #492: Alt-Svc header host restriction Julian Reschke
#492: Alt-Svc header host restriction Julian Reschke
Re: Including screen size to header messages (extending UserAgent) Roland Zink
Re: Including screen size to header messages (extending UserAgent) Basem Emara
Re: *** GMX Spamverdacht *** Re: Including screen size to header messages (extending UserAgent) Julian Reschke
Re: Including screen size to header messages (extending UserAgent) Michael Sweet
Re: Including screen size to header messages (extending UserAgent) Francesco
Re: Including screen size to header messages (extending UserAgent) Basem Emara
Re: Including screen size to header messages (extending UserAgent) Martin Nilsson
Re: Including screen size to header messages (extending UserAgent) Walter H.
Including screen size to header messages (extending UserAgent) Basem Emara
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Willy Tarreau
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Willy Tarreau
Re: HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke
Re: HTTP/2 vs 1.1 semantics: intermediate codes Willy Tarreau
HTTP/2 vs 1.1 semantics: intermediate codes Julian Reschke

Wednesday, 11 June 2014

Hard fail on self-dependency Martin Thomson
HPACK security considerations Martin Thomson

Tuesday, 10 June 2014

Re: hpack huffman codes David Krauss
Re: hpack huffman codes Roberto Peon
Re: hpack huffman codes Martin Thomson
Re: hpack huffman codes Roberto Peon
RE: hpack huffman codes Mike Bishop
Re: hpack huffman codes Martin Thomson
Re: hpack huffman codes Johnny Graettinger
Re: hpack huffman codes Martin Thomson
hpack huffman codes Martin Nilsson
Re: Major decisions at the NYC Interim Mark Nottingham
Re: Major decisions at the NYC Interim Greg Wilkins
Re: OAuth 2.0 - Proxy-Authenticate Bearer Chris Bentzel
Internet draft making SSL/TLS more transparent to the user Walter H.

Monday, 9 June 2014

RE: Values for Accept-Encoding Richard Wheeldon (rwheeldo)
Re: Values for Accept-Encoding Jeff Pinner
Re: Values for Accept-Encoding Roberto Peon
RE: Values for Accept-Encoding Mike Bishop
Re: Values for Accept-Encoding Mark Nottingham
Values for Accept-Encoding Martin Thomson
Major decisions at the NYC Interim Mark Nottingham
Minutes from the New York Interim Mark Nottingham

Sunday, 8 June 2014

Re: HTTP/1.1: They're done. Julian Reschke
Re: HTTP/1.1: They're done. Thomas Fossati
Re: HTTP/1.1: They're done. Julian Reschke
Re: HTTP/1.1: They're done. Salvatore Loreto
Re: HTTP/1.1: They're done. Eliot Lear
OAuth 2.0 - Proxy-Authenticate Bearer Amos Jeffries

Saturday, 7 June 2014

Re: HTTP/1.1: They're done. Willy Tarreau
Re: HTTP/1.1: They're done. Greg Wilkins
Re: HTTP/1.1: They're done. Amos Jeffries
Re: HTTP/1.1: They're done. Willy Tarreau
Re: HTTP/1.1: They're done. Roberto Peon
Re: HTTP/1.1: They're done. Mark Nottingham
HTTP/1.1: They're done. Mark Nottingham

Friday, 6 June 2014

Re: Limiting allowable pre-SETTINGS requests Jason Greene
Re: Limiting allowable pre-SETTINGS requests Jason Greene
Re: Limiting allowable pre-SETTINGS requests Jason Greene
Re: Limiting allowable pre-SETTINGS requests Amos Jeffries
Re: Stricter TLS Usage in HTTP/2 Simone Bordet
Re: Limiting allowable pre-SETTINGS requests Mike Bishop

Thursday, 5 June 2014

Re: Limiting allowable pre-SETTINGS requests David Krauss
Re: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression Matthew Kerwin
Limiting allowable pre-SETTINGS requests Jason Greene
Re: Question on HTTP 408 Zhong Yu
Re: Stricter TLS Usage in HTTP/2 Jason Greene
Re: Minutes Etherpad Patrick McManus
Minutes Etherpad Martin Thomson
Re: Stricter TLS Usage in HTTP/2 Yoav Nir
Re: Issues for discussion in NYC Greg Wilkins
Re: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression Greg Wilkins
Re: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression Greg Wilkins
Re: Stricter TLS Usage in HTTP/2 Cory Benfield
Re: Stricter TLS Usage in HTTP/2 Daniel Stenberg
Re: Stricter TLS Usage in HTTP/2 Yoav Nir
Re: Stricter TLS Usage in HTTP/2 Cory Benfield
Re: Question on HTTP 408 Willy Tarreau
Re: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression Matthew Kerwin
Re: Question on HTTP 408 Amos Jeffries
Re: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
Re: Issues for discussion in NYC K.Morgan@iaea.org

Wednesday, 4 June 2014

Re: Question on HTTP 408 Zhong Yu
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Michael Sweet
Re: Question on HTTP 408 Daniel Stenberg
Re: Question on HTTP 408 Daniel Stenberg
Re: Question on HTTP 408 Zhong Yu
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 陈智昌
Re: #492: Alt-Svc header host restriction Ryan Hamilton
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Sébastien Barnoud
Re: Making extensibility cheap Greg Wilkins
Re: Question on HTTP 408 Daniel Stenberg
Re: Stricter TLS Usage in HTTP/2 Adam Langley
Re: Stricter TLS Usage in HTTP/2 Martin Thomson
Re: Stricter TLS Usage in HTTP/2 Cory Benfield
Re: Stricter TLS Usage in HTTP/2 Roland Zink
Re: Making extensibility cheap Martin Thomson
RE: Stricter TLS Usage in HTTP/2 Richard Wheeldon (rwheeldo)
Re: #492: Alt-Svc header host restriction Martin Thomson
Re: Stricter TLS Usage in HTTP/2 Cory Benfield
Re: Question on HTTP 408 Zhong Yu
Issues for discussion in NYC Mark Nottingham
#492: Alt-Svc header host restriction Mark Nottingham
Re: Stricter TLS Usage in HTTP/2 Patrick McManus
Re: Stricter TLS Usage in HTTP/2 Martin Thomson
RE: Stricter TLS Usage in HTTP/2 Richard Wheeldon (rwheeldo)
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Zhong Yu
Re: Making extensibility cheap Tatsuhiro Tsujikawa
Re: Making extensibility cheap Daniel Sommermann
Re: Question on HTTP 408 Roland Zink
Re: Question on HTTP 408 Amos Jeffries
Re: Question on HTTP 408 Sébastien Barnoud
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
Re: Question on HTTP 408 Willy Tarreau
Re: Stricter TLS Usage in HTTP/2 Patrick McManus
Re: Question on HTTP 408 Michael Sweet
Re: Making extensibility cheap Amos Jeffries
Re: Making extensibility cheap Amos Jeffries
Re: ezflate: proposal to reinstitute deflate header compression Greg Wilkins
Re: Making extensibility cheap Greg Wilkins
Re: 401 ("unauthenticated" v.s. "unauthorized") Wenbo Zhu
Re: Making extensibility cheap Mike Bishop
Re: Making extensibility cheap Mike Bishop
Re: 401 ("unauthenticated" v.s. "unauthorized") Julian Reschke
Re: Question on HTTP 408 Willy Tarreau
Re: Making extensibility cheap Matthew Kerwin
Re: Stricter TLS Usage in HTTP/2 Yoav Nir
Re: Making extensibility cheap Daniel Sommermann
Re: Making extensibility cheap Tatsuhiro Tsujikawa
Re: Making extensibility cheap James M Snell
Making extensibility cheap Martin Thomson

Tuesday, 3 June 2014

Re: Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: Interleaving #481 (was Re: Limiting header block size) Roberto Peon
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
Re: Stricter TLS Usage in HTTP/2 Martin Thomson
Re: Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: 401 ("unauthenticated" v.s. "unauthorized") Grahame Grieve
401 ("unauthenticated" v.s. "unauthorized") Wenbo Zhu
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
RE: Interleaving #481 (was Re: Limiting header block size) Mike Bishop
Re: Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
Re: Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: Interleaving #481 (was Re: Limiting header block size) Simone Bordet
Re: Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: hpack static table question? Greg Wilkins
Re: ezflate: proposal to reinstitute deflate header compression Willy Tarreau
Re: hpack static table question? Greg Wilkins
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
Re: Question on HTTP 408 Patrick McManus
Re: Question on HTTP 408 Michael Sweet
Re: Interleaving #481 (was Re: Limiting header block size) Roland Zink
Re: Interleaving #481 (was Re: Limiting header block size) Roberto Peon
Re: Interleaving #481 (was Re: Limiting header block size) Roland Zink
Re: Interleaving #481 (was Re: Limiting header block size) Roberto Peon
Re: Interleaving #481 (was Re: Limiting header block size) Greg Wilkins
Re: Interleaving #481 (was Re: Limiting header block size) Roland Zink
RE: ezflate: proposal to reinstitute deflate header compression RUELLAN Herve
Re: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
Re: ezflate: proposal to reinstitute deflate header compression Roberto Peon
Re: ezflate: proposal to reinstitute deflate header compression Willy Tarreau
RE: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
RE: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
Re: Question on HTTP 408 Willy Tarreau
Re: Question on HTTP 408 Roy T. Fielding
Re: Coalescing #490 Patrick McManus
Question on HTTP 408 陈智昌
Coalescing #490 Martin Thomson

Monday, 2 June 2014

Interleaving #481 (was Re: Limiting header block size) Martin Thomson
Re: Limiting header block size Martin Thomson
Re: hpack static table question? Greg Wilkins
Re: ezflate: proposal to reinstitute deflate header compression Martin Thomson
Re: ezflate: proposal to reinstitute deflate header compression Roberto Peon
Re: hpack static table question? Roberto Peon
Re: ezflate: proposal to reinstitute deflate header compression Willy Tarreau
RE: ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
ezflate: proposal to reinstitute deflate header compression K.Morgan@iaea.org
Re: hpack static table question? Greg Wilkins
Re: improved caching in HTTP: new draft Guille -bisho-
Re: hpack static table question? Roberto Peon
Re: hpack static table question? Greg Wilkins
Re: hpack static table question? Roberto Peon
Re: hpack static table question? Roberto Peon
RE: hpack static table question? RUELLAN Herve
RE: hpack static table question? RUELLAN Herve
Re: hpack static table question? Nicholas Hurley
Re: hpack static table question? Michael Sweet
Re: hpack static table question? Cory Benfield
Re: hpack static table question? Tatsuhiro Tsujikawa
Re: hpack static table question? Jason Greene
Re: hpack static table question? Greg Wilkins
Re: hpack static table question? Tatsuhiro Tsujikawa
Re: hpack static table question? Greg Wilkins
Re: Header Size? Was: Our Schedule Jason Greene
Re: hpack static table question? Ilari Liusvaara
Re: Header Size? Was: Our Schedule Michael Sweet
hpack static table question? Greg Wilkins
Re: Header Size? Was: Our Schedule Greg Wilkins
RE: Header Size? Was: Our Schedule Richard Wheeldon (rwheeldo)
Re: Will HTTP/2.0 be green ? Roland Zink
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: Negotiating compression Eliot Lear

Sunday, 1 June 2014

Re: Will HTTP/2.0 be green ? Mike Belshe
Re: Will HTTP/2.0 be green ? Martin Nilsson
Re: Will HTTP/2.0 be green ? Greg Wilkins
Re: Will HTTP/2.0 be green ? Poul-Henning Kamp
Re: Will HTTP/2.0 be green ? Poul-Henning Kamp
Re: Will HTTP/2.0 be green ? Mike Belshe
Re: Will HTTP/2.0 be green ? Roberto Peon
Re: Will HTTP/2.0 be green ? Jason Greene
Re: Will HTTP/2.0 be green ? Roberto Peon
Re: Will HTTP/2.0 be green ? Poul-Henning Kamp
Re: Will HTTP/2.0 be green ? Roberto Peon
Re: Will HTTP/2.0 be green ? Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Jason Greene
Re: Will HTTP/2.0 be green ? Roberto Peon
Will HTTP/2.0 be green ? Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Jason Greene
Re: Header Size? Was: Our Schedule Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Poul-Henning Kamp
Re: Negotiating compression David Krauss
Re: Negotiating compression Matthew Kerwin
Re: Negotiating compression Amos Jeffries
Re: Header Size? Was: Our Schedule Roberto Peon
RE: Header Size? Was: Our Schedule K.Morgan@iaea.org

Saturday, 31 May 2014

Re: Header Size? Was: Our Schedule Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Amos Jeffries
Re: improved caching in HTTP: new draft Amos Jeffries
Re: improved caching in HTTP: new draft Amos Jeffries
Re: Header Size? Was: Our Schedule Poul-Henning Kamp
Re: Header Size? Was: Our Schedule Roberto Peon
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt Mark Nottingham
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt K.Morgan@iaea.org

Friday, 30 May 2014

Re: Header Size? Was: Our Schedule Roberto Peon
RE: Header Size? Was: Our Schedule Richard Wheeldon (rwheeldo)
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: New Version Notification for draft-nottingham-http2-ops-00.txt 陈智昌
Re: Header Size? Was: Our Schedule Roberto Peon
Re: Header Size? Was: Our Schedule Roberto Peon
Re: Negotiating compression Roberto Peon
Re: Header Size? Was: Our Schedule Michael Sweet
Re: Header Size? Was: Our Schedule Martin Thomson
Re: Negotiating compression Martin Thomson
RE: Header Size? Was: Our Schedule Richard Wheeldon (rwheeldo)
Re: Negotiating compression Jason Greene
Re: Header Size? Was: Our Schedule Michael Sweet
Re: Negotiating compression Michael Sweet
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: Header Size? Was: Our Schedule Matthew Kerwin
Fwd: New Version Notification for draft-nottingham-http2-ops-00.txt Mark Nottingham
Re: Header Size? Was: Our Schedule Martin J. Dürst

Thursday, 29 May 2014

Re: Negotiating compression Michael Sweet
Re: Header Size? Was: Our Schedule Wenbo Zhu
Re: Negotiating compression Roberto Peon
Re: HEADERS and flow control Johnny Graettinger
Re: HEADERS and flow control Johnny Graettinger
Re: Negotiating compression Jason Greene
Re: Negotiating compression Eliot Lear
Re: Negotiating compression Willy Tarreau
Re: Negotiating compression David Krauss
Re: Negotiating compression Martin Thomson
Re: Negotiating compression Martin Thomson
Re: Negotiating compression Willy Tarreau
Re: Negotiating compression Kennedy, Smith (Wireless Architect)
Re: Negotiating compression David Krauss
Re: Negotiating compression Michael Sweet
Re: Negotiating compression David Krauss
Re: Negotiating compression Jason Greene
RE: Header Size? Was: Our Schedule Richard Wheeldon (rwheeldo)
Re: Negotiating compression Willy Tarreau
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: HEADERS and flow control Greg Wilkins
Re: Header Size? Was: Our Schedule Simone Bordet
Re: Negotiating compression Matthew Kerwin
Re: Negotiating compression Simone Bordet
Re: Negotiating compression Willy Tarreau
Re: Negotiating compression Willy Tarreau
Re: Negotiating compression Willy Tarreau
Re: Header Size? Was: Our Schedule Willy Tarreau
Re: Header Size? Was: Our Schedule Amos Jeffries
Re: Negotiating compression David Krauss
Re: Header Size? Was: Our Schedule Roberto Peon
Re: Header Size? Was: Our Schedule Roberto Peon
Re: Header Size? Was: Our Schedule Matthew Kerwin

Wednesday, 28 May 2014

Re: Header Size? Was: Our Schedule David Krauss
RE: Negotiating compression Richard Wheeldon (rwheeldo)
Re: HEADERS and flow control Johnny Graettinger
Re: Header Size? Was: Our Schedule Greg Wilkins
Re: Negotiating compression Jason Greene
Re: Negotiating compression Roberto Peon
Re: Negotiating compression Michael Sweet
Re: Negotiating compression Yoav Nir
Re: Our Schedule Jason Greene
RE: Negotiating compression Richard Wheeldon (rwheeldo)
Re: Our Schedule Roberto Peon
Re: Our Schedule Jason Greene
Re: Negotiating compression Roberto Peon
Re: Negotiating compression Martin Thomson
Re: Negotiating compression Michael Sweet
Re: Header Size? Was: Our Schedule Martin Thomson
Re: Negotiating compression Michael Sweet
Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Greg Wilkins
Re: HEADERS and flow control Greg Wilkins
RE: Our Schedule James M Snell
Re: Negotiating compression Johnny Graettinger
Re: Negotiating compression Eliot Lear
Re: Negotiating compression James M Snell
Re: Our Schedule Tatsuhiro Tsujikawa
RE: Header Size? Was: Our Schedule Richard Wheeldon (rwheeldo)
Re: Negotiating compression Eliot Lear
Re: Negotiating compression Kennedy, Smith (Wireless Architect)
Re: Our Schedule David Krauss
Re: HEADERS and flow control Tatsuhiro Tsujikawa
Re: Negotiating compression Michael Sweet
Re: HEADERS and flow control Greg Wilkins
Re: Negotiating compression Eliot Lear
Re: HEADERS and flow control Tatsuhiro Tsujikawa
Re: Our Schedule Tatsuhiro Tsujikawa
Re: Negotiating compression Michael Sweet
Re: improved caching in HTTP: new draft Chris Drechsler
Re: Negotiating compression Roland Zink
Re: improved caching in HTTP: new draft Chris Drechsler
Re: Negotiating compression Greg Wilkins
Re: Header Size? Was: Our Schedule Cory Benfield
Re: HEADERS and flow control Greg Wilkins
Header Size? Was: Our Schedule Greg Wilkins
Re: Negotiating compression Simone Bordet
Re: Our Schedule David Krauss
Re: Negotiating compression David Krauss

Tuesday, 27 May 2014

RE: Negotiating compression Richard Wheeldon (rwheeldo)
Re: Negotiating compression Martin Thomson
Re: Negotiating compression Michael Sweet
Re: Negotiating compression Nicholas Hurley
Re: Negotiating compression Martin Thomson
Re: Negotiating compression Michael Sweet
Negotiating compression Martin Thomson
Re: Fwd: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
Re: Our Schedule Tatsuhiro Tsujikawa
RE: Our Schedule Mike Bishop
Re: Our Schedule Willy Tarreau
Re: improved caching in HTTP: new draft Poul-Henning Kamp
Re: Our Schedule Yoav Nir
Re: improved caching in HTTP: new draft Chris Drechsler
Re: Our Schedule Adrien de Croy
Re: Design FAQs, Was: Our Schedule Greg Wilkins
Re: Our Schedule Willy Tarreau
Re: Our Schedule Eliot Lear
Re: Our Schedule Willy Tarreau
Re: Design FAQs, Was: Our Schedule Mark Nottingham
Re: Our Schedule David Krauss
Re: Fwd: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Nilsson

Monday, 26 May 2014

Re: explicitly authenticated proxy: new draft Martin Nilsson
Re: Design FAQs, Was: Our Schedule Roland Zink
Re: Our Schedule Martin Nilsson
Re: Our Schedule Daniel Stenberg
Fwd: New Version Notification for draft-snell-link-method-09.txt James M Snell
Design FAQs, Was: Our Schedule Greg Wilkins
Re: Our Schedule Simone Bordet
Re: Our Schedule James M Snell
Re: Our Schedule Johnny Graettinger
Re: Please admit defeat (was: Our Schedule) Werner Baumann
Re: Our Schedule Mark Nottingham
Re: Our Schedule Simone Bordet
Re: Our Schedule Michael Sweet
Re: Our Schedule Michael Sweet
Re: Our Schedule James M Snell
Re: Our Schedule Patrick McManus
Re: Our Schedule Greg Wilkins
Header fair share, Was: Our Schedule Greg Wilkins
Re: large file transfers, was: Please admit defeat Poul-Henning Kamp
Re: Our Schedule Tatsuhiro Tsujikawa
Re: Our Schedule James M Snell
Re: Our Schedule Cory Benfield
RE: Our Schedule Richard Wheeldon (rwheeldo)
Re: Our Schedule Michael Sweet
Re: Our Schedule Mark Nottingham
Re: Our Schedule Greg Wilkins
Re: Please admit defeat (was: Our Schedule) Poul-Henning Kamp
Re: large file transfers, was: Please admit defeat Julian Reschke
Re: Please admit defeat (was: Our Schedule) Mark Nottingham
Re: Please admit defeat (was: Our Schedule) Poul-Henning Kamp
Re: explicitly authenticated proxy: new draft Salvatore Loreto
Re: Please admit defeat Amos Jeffries
Re: large file transfers, was: Please admit defeat Yoav Nir
Re: Please admit defeat (was: Our Schedule) Mark Nottingham
Re: large file transfers, was: Please admit defeat Julian Reschke
Re: large file transfers, was: Please admit defeat Poul-Henning Kamp
Re: large file transfers, was: Please admit defeat Yoav Nir
Re: large file transfers, was: Please admit defeat Poul-Henning Kamp
Re: large file transfers, was: Please admit defeat Yoav Nir
Re: Please admit defeat (was: Our Schedule) Poul-Henning Kamp
Re: Our Schedule Salvatore Loreto
large file transfers, was: Please admit defeat Julian Reschke
Re: Please admit defeat (was: Our Schedule) Mark Nottingham
Re: Please admit defeat (was: Our Schedule) Mike Belshe
Re: Please admit defeat (was: Our Schedule) David Krauss
Re: Please admit defeat (was: Our Schedule) Poul-Henning Kamp
Re: Please admit defeat (was: Our Schedule) Yoav Nir
Please admit defeat (was: Our Schedule) Poul-Henning Kamp
Re: Our Schedule Mark Nottingham
Re: HEADERS and flow control Matthew Kerwin
RE: explicitly authenticated proxy: new draft Richard Wheeldon (rwheeldo)

Sunday, 25 May 2014

Re: HEADERS and flow control Yoav Nir

Saturday, 24 May 2014

Re: Our Schedule Roland Zink
Re: Our Schedule Mike Sweet
Re: Our Schedule James M Snell
Re: Our Schedule Greg Wilkins

Friday, 23 May 2014

RE: Stricter TLS Usage in HTTP/2 Andrei Popov
Our Schedule Mark Nottingham
Re: HEADERS and flow control Michael Sweet
Re: HEADERS and flow control Cory Benfield
Re: improved caching in HTTP: new draft Guille -bisho-
Re: improved caching in HTTP: new draft Poul-Henning Kamp
Re: improved caching in HTTP: new draft Chris Drechsler
Re: Limiting header block size Martin Thomson
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt James M Snell
Re: improved caching in HTTP: new draft Poul-Henning Kamp
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt Matthew Kerwin
Re: improved caching in HTTP: new draft Chris Drechsler
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt Mike Bishop
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt James M Snell
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt James M Snell
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt Matthew Kerwin
Re: Limiting header block size Mark Nottingham
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt Mark Nottingham
Re: HEADERS and flow control Matthew Kerwin
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt Roberto Peon
Re: Stricter TLS Usage in HTTP/2 Eric Rescorla

Thursday, 22 May 2014

Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt Matthew Kerwin
Re: Stricter TLS Usage in HTTP/2 陈智昌
Re: Stricter TLS Usage in HTTP/2 Eric Rescorla
Re: Stricter TLS Usage in HTTP/2 Martin Thomson
Stricter TLS Usage in HTTP/2 陈智昌
Re: HEADERS and flow control K.Morgan@iaea.org
Re: HEADERS and flow control Greg Wilkins
Re: New Version Notification for draft-bishop-http2-extension-frames-01.txt Michael Sweet
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt Roberto Peon
Re: Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt James M Snell
Fw: New Version Notification for draft-bishop-http2-extension-frames-01.txt Mike Bishop
Re: Limiting header block size Martin Thomson
Re: Limiting header block size Roland Zink
Re: Limiting header block size Martin Thomson
Re: Limiting header block size Roland Zink
Re: Limiting header block size Michael Sweet
Re: HEADERS and flow control Roland Zink
Re: Limiting header block size Michael Sweet
Limiting header block size Martin Thomson
Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Ilari Liusvaara
Re: HEADERS and flow control David Krauss
Re: HEADERS and flow control Martin Thomson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
Re: #429: HPACKing security/privacy related header fields Mark Nottingham
Re: HEADERS and flow control David Krauss
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Mark Nottingham
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt 陈智昌

Wednesday, 21 May 2014

Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Michael Sweet
Re: HEADERS and flow control Michael Sweet
Re: improved caching in HTTP: new draft Guille -bisho-
Re: HEADERS and flow control David Krauss
Re: HEADERS and flow control David Krauss
Re: HEADERS and flow control Ilari Liusvaara
Re: HEADERS and flow control Michael Sweet
Re: HEADERS and flow control Greg Wilkins
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
RE: Minor points in draft 12 Richard Wheeldon (rwheeldo)
Re: HEADERS and flow control David Krauss
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt 陈智昌
Re: HEADERS and flow control David Krauss
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Nilsson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Salvatore Loreto

Tuesday, 20 May 2014

Re: New Version Notification for draft-nottingham-http2-encryption-03.txt 陈智昌
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Stephen Farrell
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Stephen Farrell
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Nilsson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Nilsson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Paul Hoffman
Re: Minor points in draft 12 Martin Thomson
RE: Minor points in draft 12 Mike Bishop
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
RE: Minor points in draft 12 Richard Wheeldon (rwheeldo)
Re: improved caching in HTTP: new draft Chris Drechsler
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Stephen Farrell
HTTP/1.1 and HTTP/2 investigation document Cory Benfield
Re: New Version Notification for draft-nottingham-http2-encryption-03.txt Martin Thomson
Fwd: New Version Notification for draft-nottingham-http2-encryption-03.txt Mark Nottingham
Re: unclaimed push streams using up the connection window David Krauss

Monday, 19 May 2014

unclaimed push streams using up the connection window 陈智昌
Re: Minor points in draft 12 Martin Thomson
Re: END_STREAM flag and trailing headers Greg Wilkins
Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control Tatsuhiro Tsujikawa
Re: HEADERS and flow control Greg Wilkins
Re: improved caching in HTTP: new draft Amos Jeffries
Re: END_STREAM flag and trailing headers Greg Wilkins
Re: HEADERS and flow control Mark Nottingham
improved caching in HTTP: new draft Chris Drechsler
Re: Making Implicit C-E work. Mark Nottingham

Sunday, 18 May 2014

RE: Making Implicit C-E work. Martin Thomson
RE: Making Implicit C-E work. Matthew Kerwin

Saturday, 17 May 2014

RE: Making Implicit C-E work. K.Morgan@iaea.org

Friday, 16 May 2014

RE: Making Implicit C-E work. Matthew Kerwin
Re: HTTP status code for transaction incomplete??? Alek Storm
HTTP status code for transaction incomplete??? Phillip Hallam-Baker

Thursday, 15 May 2014

RE: Making Implicit C-E work. K.Morgan@iaea.org
Re: Making Implicit C-E work. Mark Nottingham
Re: Making Implicit C-E work. Amos Jeffries
Re: Making Implicit C-E work. Roberto Peon
Re: Addressing gzip focus Martin Thomson
Re: Making Implicit C-E work. Martin Thomson
Re: Addressing gzip focus Matthew Kerwin

Wednesday, 14 May 2014

Re: Making Implicit C-E work. Matthew Kerwin
Re: Addressing gzip focus Matthew Kerwin
Addressing gzip focus Daniel Sommermann
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Martin Thomson
Re: Making Implicit C-E work. Johnny Graettinger
RE: Making Implicit C-E work. Martin Thomson
RE: Making Implicit C-E work. K.Morgan@iaea.org
Re: Making Implicit C-E work. Roland Zink
Re: #304, was: If-Range and cache validation using Last-Modified Julian Reschke
Re: Making Implicit C-E work. Johnny Graettinger
RE: Making Implicit C-E work. K.Morgan@iaea.org
RE: Making Implicit C-E work. K.Morgan@iaea.org
RE: Making Implicit C-E work. K.Morgan@iaea.org

Tuesday, 13 May 2014

Re: C-E for clients, was: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin

Monday, 12 May 2014

Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control Hasan Khalil
Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control Roberto Peon
Re: HTTP/2 in examples Martin Thomson
Re: END_STREAM flag and trailing headers Martin Thomson
Re: HEADERS and flow control Martin Thomson
Re: C-E for clients, was: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: C-E for clients, was: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
C-E for clients, was: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: HTTP/2 in examples James M Snell
HTTP/2 in examples Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: Coalescing and Connection Management Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham

Sunday, 11 May 2014

Re: Support for gzip at the server #424 (Consensus Call) Amos Jeffries

Saturday, 10 May 2014

Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
push vs safe methods with payload, Re: END_STREAM flag and trailing headers Julian Reschke
Re: END_STREAM flag and trailing headers David Krauss
Re: END_STREAM flag and trailing headers Julian Reschke
Re: END_STREAM flag and trailing headers David Krauss
Re: HEADERS and flow control Roberto Peon
Re: HEADERS and flow control Tatsuhiro Tsujikawa
Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control Roberto Peon

Friday, 9 May 2014

Re: HEADERS and flow control Johnny Graettinger
Re: HEADERS and flow control Roberto Peon
Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Hasan Khalil
Re: HEADERS and flow control James M Snell
Re: HEADERS and flow control Roberto Peon
Re: HEADERS and flow control Martin Thomson
Re: HEADERS and flow control Roberto Peon
Re: HEADERS and flow control Martin Thomson
HEADERS and flow control Roberto Peon
Re: END_STREAM flag and trailing headers Julian Reschke

Thursday, 8 May 2014

Re: Graceful shutdown #458 Jeff Pinner
Re: Graceful shutdown #458 Martin Thomson
Re: Graceful shutdown #458 Jeff Pinner
Re: Graceful shutdown #458 Daniel Sommermann
Re: Graceful shutdown #458 Roberto Peon
Re: END_STREAM flag and trailing headers Martin Thomson
Re: END_STREAM flag and trailing headers Greg Wilkins
Re: Graceful shutdown #458 Martin Thomson
Re: Graceful shutdown #458 Roberto Peon
Graceful shutdown #458 Martin Thomson
Re: HPACK problems (was http/2 & hpack protocol review) Cory Benfield

Wednesday, 7 May 2014

Re: PONG (was Re: Why do DATA frames have padding?) Roberto Peon
PONG (was Re: Why do DATA frames have padding?) Martin Thomson
RE: Why do DATA frames have padding? Mike Bishop
Re: Why do DATA frames have padding? Martin Thomson
Re: Why do DATA frames have padding? Martin Thomson
Re: HPACK problems (was http/2 & hpack protocol review) Martin Thomson
Re: END_STREAM flag and trailing headers Martin Thomson
RE: Why do DATA frames have padding? Mike Bishop
Why do DATA frames have padding? Greg Wilkins
END_STREAM flag and trailing headers Greg Wilkins
Re: HPACK problems (was http/2 & hpack protocol review) Greg Wilkins
RE: HPACK problems (was http/2 & hpack protocol review) RUELLAN Herve

Tuesday, 6 May 2014

Re: Making Implicit C-E work. Johnny Graettinger
RE: http/2 & hpack protocol review K.Morgan@iaea.org
Re: http/2 & hpack protocol review Cory Benfield
Re: http/2 & hpack protocol review Poul-Henning Kamp
Re: HPACK problems (was http/2 & hpack protocol review) Cory Benfield
Re: HPACK problems (was http/2 & hpack protocol review) Tatsuhiro Tsujikawa
Re: http/2 & hpack protocol review Peter Gutmann
Re: HPACK problems (was http/2 & hpack protocol review) Cory Benfield
Re: HPACK problems (was http/2 & hpack protocol review) Cory Benfield
Re: HPACK problems (was http/2 & hpack protocol review) Tatsuhiro Tsujikawa
Re: HPACK problems (was http/2 & hpack protocol review) Daniel Stenberg
Re: HPACK problems (was http/2 & hpack protocol review) Cory Benfield
Re: http/2 & hpack protocol review Cory Benfield

Monday, 5 May 2014

Re: http/2 & hpack protocol review Martin Thomson
Re: http/2 & hpack protocol review Yoav Nir
Re: http/2 & hpack protocol review Erik Nygren
RE: http/2 & hpack protocol review Julian Reschke
RE: http/2 & hpack protocol review Larry Masinter
Re: http/2 & hpack protocol review James M Snell
Re: http/2 & hpack protocol review Yoav Nir
http/2 & hpack protocol review K.Morgan@iaea.org
explicitly authenticated proxy: new draft Salvatore Loreto

Saturday, 3 May 2014

Minor points in draft 12 Richard Wheeldon (rwheeldo)
Re: Making Implicit C-E work. Matthew Kerwin
Re: GOAWAY and proxies (#458) Martin Thomson
Re: GOAWAY and proxies (#458) Roberto Peon
Re: GOAWAY and proxies (#458) Martin Thomson

Friday, 2 May 2014

Re: GOAWAY and proxies (#458) 陈智昌
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Making Implicit C-E work. Roberto Peon
Re: GOAWAY and proxies (#458) 陈智昌
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: GOAWAY and proxies (#458) Roberto Peon
Re: #466 segment compression Roberto Peon
Re: GOAWAY and proxies (#458) Martin Thomson
Re: #466 segment compression K.Morgan@iaea.org
Re: GOAWAY and proxies (#458) Roberto Peon
Re: #466 segment compression Roberto Peon
Re: #466 segment compression K.Morgan@iaea.org
Re: Alternative Service Indication 陈智昌
Re: Alternative Service Indication Martin Thomson
Re: #466 segment compression Roland Zink
Re: Alternative Service Indication 陈智昌
Re: Alternative Service Indication Martin Thomson
Re: #466 segment compression Roberto Peon
Re: Alternative Service Indication 陈智昌
Re: GOAWAY and proxies (#458) Martin Thomson
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: #466 segment compression K.Morgan@iaea.org
Re: GOAWAY and proxies (#458) Martin Thomson
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: #466 segment compression Johnny Graettinger
RE: #466 segment compression K.Morgan@iaea.org
Re: Alternative Service Indication Martin Thomson
Re: #466 segment compression Johnny Graettinger
Re: Alternative Service Indication 陈智昌
Re: Alternative Service Indication Erik Nygren

Thursday, 1 May 2014

RE: #466 segment compression K.Morgan@iaea.org
Re: #466 segment compression Martin Thomson
RE: Making Implicit C-E work. Matthew Kerwin
RE: #466 segment compression K.Morgan@iaea.org
RE: Making Implicit C-E work. K.Morgan@iaea.org
RE: Making Implicit C-E work. K.Morgan@iaea.org
RE: Making Implicit C-E work. K.Morgan@iaea.org
Alternative Service Indication Martin Thomson
Re: Header Field definition is too broad Dmitry Filimonov
Re: Header Field definition is too broad Martin Thomson
Re: Header Field definition is too broad Tatsuhiro Tsujikawa
Header Field definition is too broad Dmitry Filimonov

Wednesday, 30 April 2014

Re: Making Implicit C-E work. Adrien de Croy
Re: Making Implicit C-E work. Amos Jeffries
Re: Making Implicit C-E work. Roland Zink
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Matthew Kerwin
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Roland Zink
Re: Making Implicit C-E work. Roland Zink
Re: Making Implicit C-E work. Roland Zink
RE: Making Implicit C-E work. Richard Wheeldon (rwheeldo)
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Matthew Kerwin
Re: Making Implicit C-E work. Eric J. Bowman
Re: Making Implicit C-E work. Roberto Peon

Tuesday, 29 April 2014

Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Amos Jeffries
Re: Making Implicit C-E work. Matthew Kerwin
Re: Making Implicit C-E work. Zhong Yu
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Matthew Kerwin
Re: Making Implicit C-E work. Roberto Peon
Re: Making Implicit C-E work. Matthew Kerwin
Re: Making Implicit C-E work. Roberto Peon
Making Implicit C-E work. Roberto Peon
Re: #466 segment compression Roberto Peon
RE: #466 segment compression K.Morgan@iaea.org
Re: #466 segment compression Matthew Kerwin
Re: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
Re: Support for gzip at the server #424 (Consensus Call) Willy Tarreau
#466 segment compression Matthew Kerwin
Re: Alt-Svc header + ALTSVC frame Roberto Peon
Alt-Svc header + ALTSVC frame Mark Nottingham

Monday, 28 April 2014

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) Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Matthew Kerwin
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) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham

Saturday, 26 April 2014

Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Re: Support for gzip at the server #424 (Consensus Call) Amos Jeffries
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) Mark Nottingham
Re: Remove reserved bits from ALTSVC #467 Mark Nottingham
Re: #444: Flushing Alt-Svc Cache Erik Nygren
Re: #444: Flushing Alt-Svc Cache Mark Nottingham

Friday, 25 April 2014

Remove reserved bits from ALTSVC #467 Martin Thomson
Re: Indicating Chosen Service #443 Erik Nygren
Re: Indicating Chosen Service #443 Martin Thomson
Re: Indicating Chosen Service #443 Erik Nygren
Re: Indicating Chosen Service #443 Martin Thomson
Re: Indicating Chosen Service #443 Erik Nygren
Re: #444: Flushing Alt-Svc Cache Martin Thomson
Re: #444: Flushing Alt-Svc Cache Ryan Hamilton
Re: #444: Flushing Alt-Svc Cache Martin Thomson
Re: Indicating Chosen Service #443 Martin Thomson
Re: Support for gzip at the server #424 (Consensus Call) Martin Thomson
Re: #445: Transfer-Codings Martin Thomson
Re: #444: Flushing Alt-Svc Cache Ryan Hamilton
Re: Indicating Chosen Service #443 Erik Nygren
RE: #445: Transfer-Codings K.Morgan@iaea.org
RE: #445: Transfer-Codings K.Morgan@iaea.org
Re: Support for gzip at the server #424 (Consensus Call) Julian Reschke
Reservation and validity of colon-prefixed header keys David Krauss
Re: Indicating Chosen Service #443 Martin Thomson
Re: #444: Flushing Alt-Svc Cache Mark Nottingham
Re: #444: Flushing Alt-Svc Cache Martin Thomson
Re: Indicating Chosen Service #443 Mark Nottingham
#423: Security Implications of GZIP Mark Nottingham
#429: HPACKing security/privacy related header fields Mark Nottingham
#444: Flushing Alt-Svc Cache Mark Nottingham
Re: Support for gzip at the server #424 (Consensus Call) Mark Nottingham

Thursday, 24 April 2014

Fourth Implementation Draft [was: I-D Action: draft-ietf-httpbis-http2-12.txt] Mark Nottingham
Re: #445: Transfer-Codings Martin Thomson
Re: #445: Transfer-Codings K.Morgan@iaea.org
Re: #445: Transfer-Codings Martin Thomson
Re: #445: Transfer-Codings K.Morgan@iaea.org
Re: #445: Transfer-Codings Martin Thomson
Re: #445: Transfer-Codings Johnny Graettinger
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal bizzbyster@gmail.com
Re: #445: Transfer-Codings Martin Thomson
RE: #445: Transfer-Codings K.Morgan@iaea.org
Re: I-D Action: draft-ietf-httpbis-http2-12.txt Martin Thomson
I-D Action: draft-ietf-httpbis-http2-12.txt internet-drafts@ietf.org

Wednesday, 23 April 2014

Re: #445: Transfer-Codings Martin Thomson
Re: #445: Transfer-Codings Martin Thomson
RE: #445: Transfer-Codings K.Morgan@iaea.org
Re: #445: Transfer-Codings Martin Thomson
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal Roberto Peon
Re: Alt-Svc related Chromium bug report (proxy related) Ryan Hamilton
Re: Transfer-codings, mandatory content-coding support and intermediaries James Cloos
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: Transfer-codings, mandatory content-coding support and intermediaries 陈智昌
Re: Transfer-codings, mandatory content-coding support and intermediaries James Cloos
Re: Alt-Svc related Chromium bug report (proxy related) Mark Nottingham
Re: Alt-Svc related Chromium bug report (proxy related) Ryan Hamilton
#445: Transfer-Codings Mark Nottingham
Re: HTTP/2 Priorities Proposal Mark Nottingham
Re: Alt-Svc related Chromium bug report (proxy related) Mark Nottingham
Re: Alt-Svc related Chromium bug report (proxy related) Ryan Hamilton
Re: Alt-Svc related Chromium bug report (proxy related) Mark Nottingham

Tuesday, 22 April 2014

Re: BLOCKED frame specification Martin Thomson
Re: GOAWAY and proxies (#458) Martin Thomson
Re: HTTP/2 Priorities Proposal Jeff Pinner
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: HTTP/2 Priorities Proposal bizzbyster@gmail.com
Re: GOAWAY and proxies (#458) Martin Thomson
Re: Frame Length Restrictions Martin Thomson
Re: Frame Length Restrictions Martin Thomson
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
RE: HTTP/2 Priorities Proposal RUELLAN Herve
Re: Frame Length Restrictions Amos Jeffries
Re: Transfer-codings, mandatory content-coding support and intermediaries Roy T. Fielding
Re: Frame Length Restrictions Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries Daniel Stenberg
Re: Frame Length Restrictions Mark Nottingham
Re: Frame Length Restrictions Mark Nottingham
Re: Dealing with BLOCKED [#362] Mark Nottingham
#460 [was: Transfer-codings, mandatory content-coding support and intermediaries] Mark Nottingham
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: Frame Length Restrictions Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries Roy T. Fielding
Re: Maintenance frame contention vs CONTINUATION David Krauss
Re: Maintenance frame contention vs CONTINUATION Roberto Peon
Re: Maintenance frame contention vs CONTINUATION Martin Thomson
Re: GOAWAY and proxies (#458) Martin Thomson
Re: Frame Length Restrictions Martin Thomson
Re: Maintenance frame contention vs CONTINUATION David Krauss
Re: GOAWAY and proxies (#458) Jeff Pinner
Re: Frame Length Restrictions David Krauss
RE: GOAWAY and proxies (#458) Daniel Sommermann
Re: Frame Length Restrictions Roberto Peon
Re: GOAWAY and proxies (#458) Jeff Pinner
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: GOAWAY and proxies (#458) 陈智昌
Re: GOAWAY and proxies (#458) Jeff Pinner
Re: END_SEGMENT and END_STREAM redundant David Krauss
Re: Frame Length Restrictions Jeff Pinner
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Frame Length Restrictions Martin Thomson
Re: Frame Length Restrictions Jeff Pinner

Monday, 21 April 2014

Re: GOAWAY and proxies (#458) Martin Thomson
Re: Maintenance frame contention vs CONTINUATION Roberto Peon
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Maintenance frame contention vs CONTINUATION Martin Thomson
Maintenance frame contention vs CONTINUATION David Krauss
Re: Frame Length Restrictions Martin Thomson
Re: GOAWAY and proxies (#458) 陈智昌
Re: Frame Length Restrictions Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries 陈智昌
Re: Frame Length Restrictions Martin Thomson
Re: Frame Length Restrictions 陈智昌
Re: Frame Length Restrictions Jeff Pinner
Re: Frame Length Restrictions Jeff Pinner
Re: Frame Length Restrictions Martin Thomson
Re: Frame Length Restrictions Patrick McManus
Re: Frame Length Restrictions Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: Frame Length Restrictions Johnny Graettinger
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
Re: Frame Length Restrictions Martin Thomson
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: Alt-Svc related Chromium bug report (proxy related) Martin Thomson
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: PING frame behavior Martin Thomson
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
RE: Dealing with BLOCKED Jeroen de Borst
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
Re: END_SEGMENT? Jeff Pinner
Re: END_SEGMENT and headers Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries Albert Lunde
Re: Transfer-codings, mandatory content-coding support and intermediaries Patrick McManus
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
Re: END_SEGMENT and headers Matthew Kerwin
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: END_SEGMENT and END_STREAM redundant David Krauss
Re: #462: Intermediaries and Alt-Svc [was: Alt-Svc related Chromium bug report (proxy related)] Willy Tarreau
Re: #462: Intermediaries and Alt-Svc [was: Alt-Svc related Chromium bug report (proxy related)] Amos Jeffries
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: END_SEGMENT and END_STREAM redundant David Krauss
#462: Intermediaries and Alt-Svc [was: Alt-Svc related Chromium bug report (proxy related)] Mark Nottingham
Re: Ambiguous case in WWW-Authenticate grammar? Jesse Wilson
Re: Ambiguous case in WWW-Authenticate grammar? Ilari Liusvaara
Ambiguous case in WWW-Authenticate grammar? Jesse Wilson

Sunday, 20 April 2014

Re: Transfer-codings, mandatory content-coding support and intermediaries Mark Nottingham
Re: Dealing with BLOCKED Jeff Pinner
Re: Transfer-codings, mandatory content-coding support and intermediaries Daniel Stenberg
Re: Frame Length Restrictions Adrian Cole
Re: Transfer-codings, mandatory content-coding support and intermediaries Roland Zink
Re: END_SEGMENT and END_STREAM redundant Adrian Cole
Re: Dealing with BLOCKED Shigeki Ohtsu
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: END_SEGMENT and END_STREAM redundant David Krauss
Re: Transfer-codings, mandatory content-coding support and intermediaries Julian Reschke
Re: Transfer-codings, mandatory content-coding support and intermediaries Tatsuhiro Tsujikawa
Re: Alt-Svc related Chromium bug report (proxy related) Amos Jeffries
Re: Frame Length Restrictions Amos Jeffries
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: Transfer-codings, mandatory content-coding support and intermediaries Mark Nottingham
Re: PING frame behavior Alek Storm
Re: PING frame behavior David Krauss
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
Re: END_SEGMENT and END_STREAM redundant David Krauss
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: END_SEGMENT and END_STREAM redundant David Krauss
Re: Alt-Svc related Chromium bug report (proxy related) Mark Nottingham
Re: Transfer-codings, mandatory content-coding support and intermediaries Mark Nottingham

Saturday, 19 April 2014

Re: Transfer-codings, mandatory content-coding support and intermediaries Nicholas Hurley
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
Re: END_SEGMENT and END_STREAM redundant Roberto Peon
Re: Transfer-codings, mandatory content-coding support and intermediaries Patrick McManus
Re: Frame Length Restrictions Patrick McManus
PING frame behavior Alek Storm
Re: Transfer-codings, mandatory content-coding support and intermediaries Roland Zink
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
RE: Frame Length Restrictions K.Morgan@iaea.org
END_SEGMENT and END_STREAM redundant Adrian Cole
Re: Dealing with BLOCKED Daniel Stenberg
Re: Dealing with BLOCKED Tatsuhiro Tsujikawa
Re: Dealing with BLOCKED Cory Benfield
Re: Frame Length Restrictions Amos Jeffries
Re: Transfer-codings, mandatory content-coding support and intermediaries Amos Jeffries
Re: Frame Length Restrictions Roberto Peon
Re: Dealing with BLOCKED MIAN.HASAN.KHALIL@GMAIL.COM
Re: Dealing with BLOCKED 陈智昌
Re: Frame Length Restrictions Mark Nottingham
Re: Dealing with BLOCKED Mark Nottingham
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
Re: Call for Consensus: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa

Friday, 18 April 2014

Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: Transfer-codings, mandatory content-coding support and intermediaries Michael Sweet
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
Re: Transfer-codings, mandatory content-coding support and intermediaries David Morris
Re: END_SEGMENT and headers, #2 Roberto Peon
Re: END_SEGMENT and headers, #2 Erik Nygren
Re: Transfer-codings, mandatory content-coding support and intermediaries Matthew Kerwin
RE: Dealing with BLOCKED Brian Raymor (MS OPEN TECH)
Re: END_SEGMENT and headers, #2 Martin Thomson
Re: END_SEGMENT and headers, #2 David Krauss
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: END_SEGMENT and headers, #2 Martin Thomson
Re: END_SEGMENT and headers, #2 David Krauss
Re: END_SEGMENT and headers, #2 Martin Thomson
Re: END_SEGMENT and headers, #2 David Krauss
Re: END_SEGMENT and headers, #2 Martin Thomson
Re: END_SEGMENT? David Krauss
END_SEGMENT and headers, #2 David Krauss
Re: HTTP/2 Priorities Proposal David Krauss
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: Transfer-codings, mandatory content-coding support and intermediaries Martin Thomson
Re: HTTP/2 Priorities Proposal Mike Bishop
RE: HTTP/2 Priorities Proposal RUELLAN Herve
RE: Transfer-codings, mandatory content-coding support and intermediaries K.Morgan@iaea.org
Re: END_SEGMENT? Roberto Peon
Re: Frame Length Restrictions David Krauss
Transfer-codings, mandatory content-coding support and intermediaries Mark Nottingham
Call for Consensus: HTTP/2 Priorities Proposal Mark Nottingham
Dealing with BLOCKED Mark Nottingham
Re: END_SEGMENT? Roy T. Fielding
Re: END_SEGMENT? Mark Nottingham
Re: HTTP/2 Priorities Proposal Martin Thomson

Thursday, 17 April 2014

Re: Indicating Chosen Service #443 Erik Nygren
Re: Alt-Svc related Chromium bug report (proxy related) Martin Thomson
Re: Alt-Svc related Chromium bug report (proxy related) Erik Nygren
Encoding Context Update Kulkarni, Saurabh
Re: END_SEGMENT? Matthew Kerwin
Re: END_SEGMENT? Amos Jeffries
Re: END_SEGMENT? K.Morgan@iaea.org
Re: Frame Length Restrictions Jeff Pinner
Re: Frame Length Restrictions Martin Thomson
Re: GOAWAY and proxies (#458) Martin Thomson
Re: END_SEGMENT? Jeff Pinner
Re: GOAWAY and proxies (#458) Daniel Sommermann
Re: BLOCKED frame specification Yoav Nir
RE: GZip Content-Encoding / Reopen #404 K.Morgan@iaea.org
END_SEGMENT? K.Morgan@iaea.org
Re: Frame Length Restrictions Jeff Pinner
Re: Diminishing priorities in proposal Martin Thomson
Re: Frame Length Restrictions David Krauss
Re: BLOCKED frame specification 陈智昌
Re: BLOCKED frame specification David Krauss
Re: BLOCKED frame specification 陈智昌
Re: BLOCKED frame specification David Krauss
Re: Frame Length Restrictions Roberto Peon
Re: Diminishing priorities in proposal David Krauss
Re: END_SEGMENT and headers David Krauss
Frame Length Restrictions Jeff Pinner
Re: END_SEGMENT and headers David Krauss

Wednesday, 16 April 2014

Re: END_SEGMENT and headers Kulkarni, Saurabh
Re: END_SEGMENT and headers Jeff Pinner
Re: END_SEGMENT and headers Roberto Peon
Re: END_SEGMENT and headers David Krauss
Re: END_SEGMENT and headers David Krauss
Re: END_SEGMENT and headers Roberto Peon
Re: END_SEGMENT and headers David Krauss
Re: END_SEGMENT and headers Roberto Peon
Re: Diminishing priorities in proposal Martin Thomson
Re: END_SEGMENT and headers David Krauss
Re: BLOCKED frame specification Hasan Khalil
Re: BLOCKED frame specification 陈智昌
Re: END_SEGMENT and headers Roberto Peon
Re: BLOCKED frame specification Nicholas Hurley
Re: BLOCKED frame specification Roberto Peon
Re: BLOCKED frame specification Roberto Peon
Re: BLOCKED frame specification David Krauss
Re: BLOCKED frame specification Johnny Graettinger
Re: GOAWAY and proxies Daniel Sommermann
Re: BLOCKED frame specification David Krauss
Re: BLOCKED frame specification Johnny Graettinger
Re: BLOCKED frame specification Amos Jeffries
Re: BLOCKED frame specification Roberto Peon
Re: BLOCKED frame specification David Krauss
Diminishing priorities in proposal David Krauss
Re: END_SEGMENT and headers Roberto Peon
END_SEGMENT and headers David Krauss
Re: BLOCKED frame specification 陈智昌

Tuesday, 15 April 2014

Re: HTTP/2 Priorities Proposal Roberto Peon
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: HTTP/2 Priorities Proposal 陈智昌
Re: HTTP/2 Priorities Proposal Jeff Pinner
Re: #445: Transfer-codings Eric J. Bowman
Re: #445: Transfer-codings Eric J. Bowman
Re: #445: Transfer-codings Eric J. Bowman
Re: #445: Transfer-codings Eric J. Bowman
Re: Porting T-E to HTTP/2: Reasons Against Eric J. Bowman

Monday, 14 April 2014

Re: HTTP/2 Priorities Proposal Mark Nottingham
RE: GZip Content-Encoding / Reopen #404 K.Morgan@iaea.org
Re: GZip Content-Encoding / Reopen #404 Roland Zink
Re: SETTINGS frames as header blocks? Alek Storm
GZip Content-Encoding / Reopen #404 Matthew Kerwin
Re: SETTINGS frames as header blocks? Amos Jeffries

Sunday, 13 April 2014

SETTINGS frames as header blocks? Alek Storm
Re: Optimizing Huffman inputs Martin Thomson
Re: Optimizing Huffman inputs Ilari Liusvaara
Re: Optimizing Huffman inputs Martin Thomson
Re: Optimizing Huffman inputs Martin Thomson
Re: Optimizing Huffman inputs Amos Jeffries
Re: Optimizing Huffman inputs Ilari Liusvaara
Re: Optimizing Huffman inputs David Krauss

Saturday, 12 April 2014

Optimizing Huffman inputs Martin Thomson
Re: #445: Transfer-codings Roland Zink

Friday, 11 April 2014

Coalescing and Connection Management Rob Trace
Re: #445: Transfer-codings Matthew Kerwin
Re: Porting T-E to HTTP/2: Reasons Against Martin Thomson
Re: Porting T-E to HTTP/2: Reasons Against Roland Zink
Re: Porting T-E to HTTP/2: Reasons Against Martin Thomson
RE: Shipping, was: BLOCKED frame specification Rob Trace
Re: Porting T-E to HTTP/2: Reasons Against Roland Zink
Re: Porting T-E to HTTP/2: Reasons Against Julian Reschke
Re: Porting T-E to HTTP/2: Reasons Against Martin Thomson
Re: Porting T-E to HTTP/2: Reasons Against Roland Zink
Re: #445: Transfer-codings Roland Zink
decompression at 2 -> 1.1 gateway breaks ranges K.Morgan@iaea.org
RE: Porting T-E to HTTP/2: Reasons Against C.Brunhuber@iaea.org
Re: #445: Transfer-codings Amos Jeffries
Re: Porting T-E to HTTP/2: Reasons Against Matthew Kerwin
Re: BLOCKED frame specification Nicholas Hurley
Re: Porting T-E to HTTP/2: Reasons Against Nicholas Hurley
Re: GOAWAY and proxies Roberto Peon
Re: Porting T-E to HTTP/2: Reasons Against Roberto Peon
Re: GOAWAY and proxies Martin Thomson

Thursday, 10 April 2014

Porting T-E to HTTP/2: Reasons Against Martin Thomson
Re: GOAWAY and proxies Roberto Peon
Re: #445: Transfer-codings Roberto Peon
Re: GOAWAY and proxies Daniel Sommermann
Re: GOAWAY and proxies Martin Thomson
Re: GOAWAY and proxies Daniel Sommermann
Re: GOAWAY and proxies Roberto Peon
Re: GOAWAY and proxies Martin Thomson
GOAWAY and proxies Daniel Sommermann
Re: HTTP/2 Priorities Proposal Mike Bishop
RE: #445: Transfer-codings C.Brunhuber@iaea.org
RE: #445: Transfer-codings K.Morgan@iaea.org
RE: #445: Transfer-codings K.Morgan@iaea.org
Re: HTTP/2 Priorities Proposal MIAN.HASAN.KHALIL@GMAIL.COM
Re: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa
RE: #445: Transfer-codings - Alternate proposal K.Morgan@iaea.org
Shipping, was: BLOCKED frame specification Julian Reschke
Re: #445: Transfer-codings Matthew Kerwin
Re: HTTP/2 Priorities Proposal Mark Nottingham
Re: HTTP/2 Priorities Proposal Amos Jeffries
Re: #445: Transfer-codings Amos Jeffries
Re: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa

Wednesday, 9 April 2014

RE: BLOCKED frame specification Rob Trace
RE: #445: Transfer-codings K.Morgan@iaea.org
Re: HTTP/2 Priorities Proposal Jeff Pinner
Re: HTTP/2 Priorities Proposal Jeff Pinner
RE: GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari C.Brunhuber@iaea.org
Re: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa
Re: #445: Transfer-codings Bjoern Hoehrmann
Re: BLOCKED frame specification Roberto Peon
Re: BLOCKED frame specification Mark Nottingham
Re: BLOCKED frame specification Yoav Nir
Re: BLOCKED frame specification David Krauss
Re: BLOCKED frame specification Yoav Nir
Re: BLOCKED frame specification David Krauss
Re: BLOCKED frame specification Yoav Nir
Re: HTTP/2 Priorities Proposal Martin Thomson
Re: #445: Transfer-codings Matthew Kerwin
Re: HTTP/2 Priorities Proposal Jeff Pinner
Re: HTTP/2 Priorities Proposal Roberto Peon
Re: HTTP/2 Priorities Proposal Tatsuhiro Tsujikawa
Re: #445: Transfer-codings Mark Nottingham

Tuesday, 8 April 2014

HTTP/2 Priorities Proposal Jeff Pinner
Re: GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari Zhong Yu
Re: BLOCKED frame specification Daniel Sommermann
Re: GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari Zhong Yu
Re: BLOCKED frame specification Daniel Stenberg
Re: BLOCKED frame specification Martin Thomson
Re: I-D Action: draft-lnageleisen-http-chunked-progress-00.txt Martin Thomson
Re: GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari Martin Thomson
Re: BLOCKED frame specification Yoav Nir
Re: #445: Transfer-codings - Alternate proposal Amos Jeffries
Re: I-D Action: draft-lnageleisen-http-chunked-progress-00.txt Bjoern Hoehrmann
#445: Transfer-codings - Alternate proposal K.Morgan@iaea.org
GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari C.Brunhuber@iaea.org
Re: #445: Transfer-codings Matthew Kerwin

Monday, 7 April 2014

Re: BLOCKED frame specification Mark Nottingham
BLOCKED frame specification Hasan Khalil
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Helge Hess
Re: #445: Transfer-codings David Krauss
Re: #445: Transfer-codings Roberto Peon
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Roberto Peon
Re: #445: Transfer-codings Matthew Kerwin

Saturday, 5 April 2014

Re: #445: Transfer-codings Roland Zink
Re: #445: Transfer-codings Roland Zink
Re: #445: Transfer-codings Albert Lunde
Re: #445: Transfer-codings Amos Jeffries
Re: #445: Transfer-codings Amos Jeffries
Re: #445: Transfer-codings Amos Jeffries

Friday, 4 April 2014

Re: #445: Transfer-codings Roland Zink
RE: #445: Transfer-codings K.Morgan@iaea.org
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Frédéric Kayser
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings K.Morgan@iaea.org
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Michael Sweet
Re: #445: Transfer-codings Matthew Kerwin
RE: #445: Transfer-codings K.Morgan@iaea.org
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Ilari Liusvaara
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Martin Nilsson
Re: #445: Transfer-codings Ilari Liusvaara
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Matthew Kerwin
Re: #445: Transfer-codings Mark Nottingham
Re: #445: Transfer-codings Martin Thomson
Re: #445: Transfer-codings Matthew Kerwin
Re: review: http2-10 Michael Köller
Re: #445: Transfer-codings Amos Jeffries
Re: Alt-Svc with UPGRADE Yutaka Hirano
#445: Transfer-codings Matthew Kerwin
Re: New HTTP/2 draft Mark Nottingham

Thursday, 3 April 2014

New HTTP/2 draft Martin Thomson
I-D Action: draft-ietf-httpbis-http2-11.txt internet-drafts@ietf.org
Re: review: http2-10 Martin Thomson
review: http2-10 Michael Köller
Re: TLS Renegotiation and HTTP/2 (#363) Martin Thomson
Re: Zero weight for 100 CONTINUE, instead of flow control Martin Thomson
RE: I-D Action: draft-ietf-httpbis-header-compression-07.txt RUELLAN Herve
I-D Action: draft-ietf-httpbis-header-compression-07.txt internet-drafts@ietf.org
Re: TLS Renegotiation and HTTP/2 (#363) Yoav Nir
Re: Zero weight for 100 CONTINUE, instead of flow control David Krauss
Re: Zero weight for 100 CONTINUE, instead of flow control Tatsuhiro Tsujikawa
Re: Zero weight for 100 CONTINUE, instead of flow control David Krauss
Re: Zero weight for 100 CONTINUE, instead of flow control David Krauss

Wednesday, 2 April 2014

Re: Zero weight for 100 CONTINUE, instead of flow control Martin Thomson
RE: Zero weight for 100 CONTINUE, instead of flow control David Morris
RE: Zero weight for 100 CONTINUE, instead of flow control Mike Bishop
Re: #421: Mixed Schemes Martin Thomson
Re: #421: Mixed Schemes Roy T. Fielding
Re: #421: Mixed Schemes Martin Thomson
Re: Padding should be specified for PUSH_PROMISE frames too? Johnny Graettinger
Padding should be specified for PUSH_PROMISE frames too? Jonathan Thackray
Re: #421: Mixed Schemes Roy T. Fielding
Re: TLS Renegotiation and HTTP/2 (#363) Nicolas Mailhot
RE: Enable weight of 0 RUELLAN Herve
RE: #436: Enable weight of 0 RUELLAN Herve
Re: #446: alt-svc header field syntax Mark Nottingham
#436: Enable weight of 0 Mark Nottingham
Re: #421: Mixed Schemes Mark Nottingham
Re: Alt-Svc related Chromium bug report (proxy related) Mark Nottingham
Re: #446: alt-svc header field syntax Mark Nottingham

Tuesday, 1 April 2014

Re: Enable weight of 0 David Krauss
Zero weight for 100 CONTINUE, instead of flow control David Krauss
Re: #446: alt-svc header field syntax Julian Reschke
Re: #446: alt-svc header field syntax Paul Hoffman
Re: TLS Renegotiation and HTTP/2 (#363) Martin Thomson
Re: TLS Renegotiation and HTTP/2 (#363) Yoav Nir
Re: TLS Renegotiation and HTTP/2 (#363) Martin Thomson
Re: Alt-Svc with UPGRADE Martin Thomson
I-D Action: draft-ietf-httpbis-alt-svc-01.txt internet-drafts@ietf.org
Enable weight of 0 RUELLAN Herve
Re: #446: alt-svc header field syntax Martin Thomson
Re: TLS Renegotiation and HTTP/2 (#363) Yoav Nir
Re: TLS Renegotiation and HTTP/2 (#363) Ilari Liusvaara
Re: TLS Renegotiation and HTTP/2 (#363) Yoav Nir
Re: TLS Renegotiation and HTTP/2 (#363) Ilari Liusvaara
Re: TLS Renegotiation and HTTP/2 (#363) Yoav Nir
Re: h2#404 requiring gzip and/or deflate Roland Zink
Alt-Svc with UPGRADE Yutaka Hirano
#446: alt-svc header field syntax Julian Reschke
Re: State of the Protocol (2014-03-31) Mark Nottingham
Re: Alt-Svc related Chromium bug report (proxy related) 陈智昌
Re: TLS Renegotiation and HTTP/2 (#363) Patrick McManus
Re: Alt-Svc related Chromium bug report (proxy related) Martin Thomson
Re: Alt-Svc related Chromium bug report (proxy related) Amos Jeffries
Re: #421: Mixed Schemes Roy T. Fielding
Re: Alt-Svc related Chromium bug report (proxy related) 陈智昌
Re: Alt-Svc related Chromium bug report (proxy related) Martin Thomson
TLS Renegotiation and HTTP/2 (#363) Martin Thomson

Last message date: Monday, 30 June 2014 23:48:15 UTC