ietf-http-wg@w3.org from July to September 2014 by date

Tuesday, 30 September 2014

Re: null ciphers in 9.2.2 Martin Thomson
Re: null ciphers in 9.2.2 Stephen Farrell
Re: null ciphers in 9.2.2 Greg Wilkins
Re: #578: Header Table and Static Table Indices Switched Greg Wilkins
Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
Re: null ciphers in 9.2.2 Martin Thomson
Re: User-Agent header field and quoted-string Julian Reschke
Re: User-Agent header field and quoted-string Martin Thomson
Re: User-Agent header field and quoted-string Julian Reschke
User-Agent header field and quoted-string Martin Thomson
Re: #591: Permissible states for extension frames Mark Nottingham
Re: #601: HTTP2-Settings header field name Mark Nottingham
Re: #578: Header Table and Static Table Indices Switched Greg Wilkins
Re: null ciphers in 9.2.2 Martin Thomson
Re: #578: Header Table and Static Table Indices Switched Jason Greene
Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
Re: #578: Header Table and Static Table Indices Switched Greg Wilkins
Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
Re: I-D Action: draft-ietf-httpbis-alt-svc-03.txt Julian Reschke
I-D Action: draft-ietf-httpbis-alt-svc-03.txt internet-drafts@ietf.org
RE: SETTINGS frame - not documented as peer-to-peer only RUELLAN Herve
RE: #578: Header Table and Static Table Indices Switched RUELLAN Herve
Re: HTTP/2 and Websockets Yutaka Hirano
Re: SETTINGS frame - not documented as peer-to-peer only Matthew Kerwin
Re: upgrade prose bug Roy T. Fielding
Re: SETTINGS frame - not documented as peer-to-peer only Robert Collins
Re: SETTINGS frame - not documented as peer-to-peer only Matthew Kerwin
Re: SETTINGS frame - not documented as peer-to-peer only Stuart Douglas
Re: SETTINGS frame - not documented as peer-to-peer only Martin Thomson
Re: #603: Frame layout Simpson, Robby (GE Energy Management)
Re: #578: Header Table and Static Table Indices Switched Simpson, Robby (GE Energy Management)
Re: #603: Frame layout Nicholas Hurley

Monday, 29 September 2014

RE: #603: Frame layout Rob Trace
Re: HTTP/2 and Websockets Ilari Liusvaara
Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
Re: Getting it out the door. Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
Re: SETTINGS frame - not documented as peer-to-peer only Stuart Douglas
Re: #603: Frame layout Jason Greene
Re: HTTP/2 and Websockets Robert Collins
SETTINGS frame - not documented as peer-to-peer only Robert Collins
Re: #603: Frame layout Michaela LaVan
Re: HTTP/2 and Websockets Ilari Liusvaara
Re: HTTP/2 and Websockets Greg Wilkins
Re: #603: Frame layout Daniel Stenberg
Re: Frame size errors and GOAWAY prose still ambiguous Martin Thomson
Re: upgrade prose bug Martin Thomson
Re: #603: Frame layout Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Websockets Yutaka Hirano
Frame size errors and GOAWAY prose still ambiguous Jonathan Thackray
Re: Headers vs Response Code for 2NN Contents Of Related Roy T. Fielding
Re: HTTP/2 and Websockets Ilari Liusvaara
Re: #603: Frame layout Robert Collins
Re: #603: Frame layout Poul-Henning Kamp
Re: #603: Frame layout Daniel Stenberg
RE: #603: Frame layout K.Morgan@iaea.org
Re: Headers vs Response Code for 2NN Contents Of Related Amos Jeffries
Re: Getting it out the door. Re: #578: Header Table and Static Table Indices Switched Amos Jeffries
Re: Headers vs Response Code for 2NN Contents Of Related Julian Reschke
Re: HTTP/2 and Websockets Yutaka Hirano
Re: Headers vs Response Code for 2NN Contents Of Related Matthew Kerwin
Re: Headers vs Response Code for 2NN Contents Of Related Sandro Hawke
HTTP/2 and Websockets Robert Collins
upgrade prose bug Robert Collins
HTTP/2 REFUSED_STREAM and applications Robert Collins

Sunday, 28 September 2014

Re: Headers vs Response Code for 2NN Contents Of Related Matthew Kerwin
Re: Getting it out the door. Re: #578: Header Table and Static Table Indices Switched Adrian Cole
Re: Headers vs Response Code for 2NN Contents Of Related Sandro Hawke
Re: Headers vs Response Code for 2NN Contents Of Related Julian Reschke
Re: Headers vs Response Code for 2NN Contents Of Related Sandro Hawke
Re: Discussion of 9.2.2 Martin Nilsson
Re: Headers vs Response Code for 2NN Contents Of Related Julian Reschke
Re: RST_STREAM(OK) after an HTTP response Greg Wilkins
Getting it out the door. Re: #578: Header Table and Static Table Indices Switched Greg Wilkins
Re: Discussion of 9.2.2 Greg Wilkins

Saturday, 27 September 2014

Re: Headers vs Response Code for 2NN Contents Of Related Sandro Hawke
Re: Headers vs Response Code for 2NN Contents Of Related Julian Reschke
Re: Discussion of 9.2.2 Michael Sweet
Re: #578: Header Table and Static Table Indices Switched Mark Nottingham
Re: Discussion of 9.2.2 Jason Greene
Re: RST_STREAM(OK) after an HTTP response Jim Manico
Re: Discussion of 9.2.2 Martin Nilsson
Headers vs Response Code for 2NN Contents Of Related Sandro Hawke
Re: RST_STREAM(OK) after an HTTP response Martin Thomson
Re: Discussion of 9.2.2 Willy Tarreau
Re: #578: Header Table and Static Table Indices Switched Willy Tarreau
Re: #578: Header Table and Static Table Indices Switched Roberto Peon
Re: #601: HTTP2-Settings header field name Amos Jeffries
Re: #603: Frame layout Poul-Henning Kamp
Re: #578: Header Table and Static Table Indices Switched Amos Jeffries
Re: #603: Frame layout Amos Jeffries
Re: #603: Frame layout Greg Wilkins

Friday, 26 September 2014

Re: #603: Frame layout Matthew Kerwin
RE: RST_STREAM(OK) after an HTTP response Osama Mazahir
Re: #603: Frame layout Roy T. Fielding
Re: #578: Header Table and Static Table Indices Switched Matthew Kerwin
Re: #591: Permissible states for extension frames Matthew Kerwin
Re: #601: HTTP2-Settings header field name Matthew Kerwin
Re: PUSH_PROMISE and load balancers Glen Knowles
Re: #578: Header Table and Static Table Indices Switched Glen Knowles
Re: null ciphers in 9.2.2 Greg Wilkins
Re: #578: Header Table and Static Table Indices Switched Greg Wilkins
Re: Discussion of 9.2.2 Greg Wilkins
Re: RST_STREAM(OK) after an HTTP response Jeff Pinner
RE: RST_STREAM(OK) after an HTTP response Matthew Cox
Re: PUSH_PROMISE and load balancers Daniel Sommermann
Re: Discussion of 9.2.2 Michael Sweet
Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
editorial changes committed Martin Thomson
#603: Frame layout Nottingham, Mark
#578: Header Table and Static Table Indices Switched Mark Nottingham
#591: Permissible states for extension frames Mark Nottingham
null ciphers in 9.2.2 Martin Thomson
#601: HTTP2-Settings header field name Mark Nottingham
Re: Zero padding Mark Nottingham
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Eric Rescorla
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Michael Sweet
Re: Discussion of 9.2.2 Martin Thomson
Re: PUSH_PROMISE and load balancers Martin Thomson
Re: PUSH_PROMISE and load balancers Stuart Douglas
Re: Discussion of 9.2.2 Julian Reschke
Re: PUSH_PROMISE and load balancers Martin Thomson
Re: RST_STREAM(OK) after an HTTP response Martin Thomson
PUSH_PROMISE and load balancers Stuart Douglas

Thursday, 25 September 2014

RE: RST_STREAM(OK) after an HTTP response Matthew Cox
Re: RST_STREAM(OK) after an HTTP response Greg Wilkins
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Rob Trace
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Greg Wilkins
Re: Discussion of 9.2.2 Greg Wilkins
Re: Discussion of 9.2.2 Mark Nottingham
Re: Discussion of 9.2.2 Patrick McManus
Re: Discussion of 9.2.2 Ilari Liusvaara
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Michael Sweet
Re: Discussion of 9.2.2 Eric Rescorla
Re: Discussion of 9.2.2 Greg Wilkins
Re: Discussion of 9.2.2 Roland Zink
Re: Discussion of 9.2.2 Eric Rescorla
Re: Discussion of 9.2.2 Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: Discussion of 9.2.2 Martin Thomson
Re: RST_STREAM(OK) after an HTTP response Martin Thomson
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Andrei Popov

Wednesday, 24 September 2014

Re: RST_STREAM(OK) after an HTTP response Jeff Pinner
Re: RST_STREAM(OK) after an HTTP response Jeff Pinner
RE: RST_STREAM(OK) after an HTTP response Osama Mazahir
Re: RST_STREAM(OK) after an HTTP response Michaela LaVan
Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
Re: Discussion of 9.2.2 Jason Greene
Re: Discussion of 9.2.2 Greg Wilkins
Re: RST_STREAM(OK) after an HTTP response Jeff Pinner
RE: RST_STREAM(OK) after an HTTP response Mike Bishop
RST_STREAM(OK) after an HTTP response Jeff Pinner
Re: I-D Action: draft-ietf-httpbis-rfc7238bis-01.txt Barry Leiba
Re: Discussion of 9.2.2 Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Discussion of 9.2.2 Mark Nottingham
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: Zero padding Mark Nottingham
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Stuart Douglas
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Amos Jeffries
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Amos Jeffries
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: Frame size errors Martin Thomson

Tuesday, 23 September 2014

Re: Frame size errors Matthew Kerwin
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Andrei Popov
RE: Frame size errors Mike Bishop
Zero padding Martin Thomson
Frame size errors Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Julian Reschke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Willy Tarreau
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: Fwd: [http-auth] WGLC for draft-ietf-httpauth-hoba-04 Amos Jeffries
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Willy Tarreau
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Patrick McManus
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene

Monday, 22 September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Mark Nottingham
RE: Feedback on Fallback Mike Bishop
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Fwd: [http-auth] WGLC for draft-ietf-httpauth-hoba-04 Mark Nottingham
Re: Feedback on Fallback Ilari Liusvaara
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
RE: Feedback on Fallback Mike Bishop
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jim Manico
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla

Saturday, 20 September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roy T. Fielding
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Andrei Popov
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Ilari Liusvaara
registration requirement for range units, was: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Julian Reschke
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Andrei Popov

Friday, 19 September 2014

Re: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Sandro Hawke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Cory Benfield
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Amos Jeffries
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Stuart Douglas
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Cory Benfield
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Willy Tarreau
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Willy Tarreau
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Willy Tarreau
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Stuart Douglas

Thursday, 18 September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Ilari Liusvaara
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Jason Greene
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roy T. Fielding
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roy T. Fielding
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Patrick McManus
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Cory Benfield
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Stuart Douglas
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins

Wednesday, 17 September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Brian Smith
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Roland Zink
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Cory Benfield
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Brian Smith
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Ilari Liusvaara
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Amos Jeffries
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Amos Jeffries

Tuesday, 16 September 2014

Re: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Sandro Hawke
Re: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Martin J. Dürst
Re: Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Micaela Gallerini
Re: I-D Action: draft-ietf-httpbis-rfc7238bis-01.txt Julian Reschke
I-D Action: draft-ietf-httpbis-rfc7238bis-01.txt internet-drafts@ietf.org
Why Range doesn't work for LDP "paging" (cf 2NN Contents-of-Related) Sandro Hawke

Monday, 15 September 2014

Re: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Mark Nottingham

Friday, 12 September 2014

Re: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Poul-Henning Kamp
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> James M Snell
Re: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Martin Thomson
Re: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Buzonas, Steve
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Martin Nilsson

Thursday, 11 September 2014

Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Martin Thomson
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Julian Reschke
Re: h2 Connection Preface Simpson, Robby (GE Energy Management)
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Martin Thomson
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Julian Reschke
Re: Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Poul-Henning Kamp
Fwd: Expiration impending: <draft-nottingham-http-patch-status-00.txt> Mark Nottingham

Wednesday, 10 September 2014

Re: h2 Connection Preface Simpson, Robby (GE Energy Management)
Re: h2 Connection Preface Martin Thomson
RE: h2 Connection Preface Lucas Pardue
Re: h2 Connection Preface Simpson, Robby (GE Energy Management)

Tuesday, 9 September 2014

Re: h2 Connection Preface Martin Thomson
Re: h2 Connection Preface Martin Thomson
Re: h2 Connection Preface Simpson, Robby (GE Energy Management)
RE: h2 Connection Preface Lucas Pardue
RE: h2 Connection Preface RUELLAN Herve
RE: h2 Connection Preface RUELLAN Herve
RE: h2 Connection Preface RUELLAN Herve
RE: h2 Connection Preface Lucas Pardue
h2 Connection Preface Simpson, Robby (GE Energy Management)
Re: Connection: header in HTTP/2 Willy Tarreau
Re: Connection: header in HTTP/2 Poul-Henning Kamp
Re: Connection: header in HTTP/2 Willy Tarreau
Re: Connection: header in HTTP/2 Poul-Henning Kamp
Re: Connection: header in HTTP/2 Willy Tarreau
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Julian Reschke

Monday, 8 September 2014

Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Matthew Kerwin
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Julian Reschke
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Connection: header in HTTP/2 Poul-Henning Kamp
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Amos Jeffries

Sunday, 7 September 2014

Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: 303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Roy T. Fielding
303 for paging; was Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke

Saturday, 6 September 2014

Re: Huffman [was: Re: h2 header field names] Martin Nilsson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: Huffman [was: Re: h2 header field names] Poul-Henning Kamp
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins

Friday, 5 September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: Huffman [was: Re: h2 header field names] Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Brian Smith
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: Huffman [was: Re: h2 header field names] Simpson, Robby (GE Energy Management)
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Brian Smith
RE: 9.2.2 Cipher fallback and FF<->Jetty interop problem Andrei Popov
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: h2 header field names Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 2NN Contents Of Related (303 Shortcut) Eric Prud'hommeaux
Re: h2 header field names Poul-Henning Kamp
Re: Huffman [was: Re: h2 header field names] Martin Thomson
Re: h2 header field names Ilari Liusvaara
Re: Editorial notes on http://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-02 Julian Reschke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: Huffman [was: Re: h2 header field names] Poul-Henning Kamp
Re: 2NN Contents Of Related (303 Shortcut) Roy T. Fielding
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: Huffman [was: Re: h2 header field names] Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Huffman [was: Re: h2 header field names] Poul-Henning Kamp
Re: h2 header field names Martin Thomson
Re: h2 header field names Poul-Henning Kamp
Re: h2 header field names Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Editorial notes on http://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-02 Patrick McManus
Re: h2 header field names Poul-Henning Kamp
Re: h2 header field names Martin Thomson
Re: http2-14 Martin Thomson
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Michael Sweet
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Patrick McManus
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Patrick McManus
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Eric Prud'hommeaux
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Patrick McManus
Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Mark Nottingham
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Simone Bordet
Re: 2NN Contents Of Related (303 Shortcut) Julian Reschke
Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Julian Reschke
Re: 2NN Contents Of Related (303 Shortcut) Yves Lafon
Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Yves Lafon
Re: h2 header field names Poul-Henning Kamp
See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut) Julian Reschke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Martin Thomson
Re: h2 header field names Poul-Henning Kamp
Re: h2 use of Upgrade Poul-Henning Kamp
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: 2NN Contents Of Related (303 Shortcut) Julian Reschke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Eric Rescorla
Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: h2 padding Greg Wilkins
Re: h2 padding Martin Thomson
Re: 2NN Contents Of Related (303 Shortcut) Roy T. Fielding
9.2.2 Cipher fallback and FF<->Jetty interop problem Greg Wilkins
Re: h2 use of Upgrade Michael Sweet
http2-14 山本和彦
Re: h2 padding Greg Wilkins

Thursday, 4 September 2014

Re: Rejecting messages with illegal characters in header fields (was Re: h2 header field names) Matthew Kerwin
Re: h2 padding Martin Thomson
Re: h2 header field names Greg Wilkins
Re: h2 padding Greg Wilkins
Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: h2 use of Upgrade Martin Thomson
Re: h2 priority Patrick McManus
Re: h2 header field names Martin Nilsson
Re: h2 header field names Martin Nilsson
Re: h2 use of Upgrade Roy T. Fielding
Re: h2 header field names Poul-Henning Kamp
Re: Rejecting messages with illegal characters in header fields (was Re: h2 header field names) Martin Thomson
Re: Rejecting messages with illegal characters in header fields (was Re: h2 header field names) Julian Reschke
Rejecting messages with illegal characters in header fields (was Re: h2 header field names) Martin Thomson
Re: h2 use of Upgrade Michael Sweet
Re: h2 use of Upgrade Martin Thomson
Re: h2 padding Guille -bisho-
Re: 2NN Contents Of Related (303 Shortcut) Martin Thomson
Re: h2 priority Roy T. Fielding
Re: h2 padding Brian Smith
Re: h2 header field names Kinkie
Re: h2 header field names Poul-Henning Kamp
Re: h2 priority Patrick McManus
Re: h2 padding Jason Greene
Re: h2 header field names Julian Reschke
Re: h2 header field names Michael Sweet
Re: h2 header field names Poul-Henning Kamp
Re: h2 header field names Jason Greene
Re: h2 header field names James M Snell
Re: h2 header field names Julian Reschke
Re: h2 header field names Poul-Henning Kamp
Re: Reporting interop issues Paul Hoffman
Re: h2 header field names Poul-Henning Kamp
Re: h2 header field names Julian Reschke
Re: h2 header field names Amos Jeffries
Re: h2 header field names Amos Jeffries
Re: h2 requirements on authoritative responses Amos Jeffries
Re: h2 header field names Michael Sweet
Re: h2 header field names Martin Nilsson
Re: h2 header field names Willy Tarreau
Re: h2 header field names Julian Reschke
Re: h2 header field names Greg Wilkins
Re: 2NN Contents Of Related (303 Shortcut) Sandro Hawke
Re: h2 header field names Mark Nottingham
Re: h2 header field names Poul-Henning Kamp
Re: 2NN Contents Of Related (303 Shortcut) Mark Nottingham
Re: h2 header field names Mark Nottingham
RE: h2 padding K.Morgan@iaea.org
Re: h2 header field names Poul-Henning Kamp
Re: h2 header field names Mark Nottingham
Re: h2 requirements on authoritative responses Roland Zink
Re: h2 header field names Poul-Henning Kamp
Re: h2 padding Poul-Henning Kamp
Re: h2 padding Guille -bisho-
Re: h2 header field names Mark Nottingham
Re: h2 header field names Julian Reschke
Re: h2 header field names Willy Tarreau
Re: h2 padding Willy Tarreau
Re: h2 use of Upgrade Willy Tarreau
Re: h2 header field names Mark Nottingham
Re: h2 padding Amos Jeffries
Re: h2 padding Roberto Peon
Re: h2 padding Greg Wilkins
Re: h2 padding Martin Thomson
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 use of Upgrade Roy T. Fielding

Wednesday, 3 September 2014

Re: h2 padding Roy T. Fielding
Re: h2 use of Upgrade Roberto Peon
Re: h2 padding Roberto Peon
Re: h2 use of Upgrade Roy T. Fielding
Re: h2 padding K.Morgan@iaea.org
Re: h2 padding Brian Smith
Re: h2 requirements on authoritative responses Roy T. Fielding
Re: h2 padding Brian Smith
Re: h2 padding Martin Thomson
Re: h2 padding Brian Smith
Re: h2 use of Upgrade Roberto Peon
Re: h2 padding Brian Smith
Re: h2 padding Roberto Peon
Re: h2 padding Martin Thomson
Re: h2 use of Upgrade Roy T. Fielding
Re: h2 padding Greg Wilkins
Re: h2 priority Roy T. Fielding
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 requirements on authoritative responses Matthew Kerwin
Re: h2 use of Upgrade Roberto Peon
Re: h2 definition of HTTP2-Settings Roy T. Fielding
Re: h2 use of Upgrade Roy T. Fielding
Re: h2 requirements on authoritative responses Daniel Sommermann
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 requirements on authoritative responses Roy T. Fielding
Re: h2 requirements on authoritative responses Roy T. Fielding
Re: h2 padding Poul-Henning Kamp
Re: h2 padding Roy T. Fielding
Re: h2 header field names Poul-Henning Kamp
Re: h2 padding Poul-Henning Kamp
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 header field names Martin Thomson
Re: h2 padding Brian Smith
Re: h2 padding Jason Greene
Re: h2 requirements on authoritative responses Guille -bisho-
Re: h2 padding Brian Smith
Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 padding Guille -bisho-
JSON encoding, was: Quick feedback on draft-nottingham-web-proxy-desc-00 Julian Reschke
Re:Quick feedback on draft-nottingham-web-proxy-desc-00 Nicolas Mailhot
Quick feedback on draft-nottingham-web-proxy-desc-00 Julian Reschke
Re: Ending streams/connections Greg Wilkins
Re: h2 priority Amos Jeffries
Re: h2 padding Poul-Henning Kamp
Re: h2 padding Amos Jeffries
Re: h2 padding Amos Jeffries
Re: Ending streams/connections Cory Benfield
Re: h2 priority Poul-Henning Kamp
Re: h2 priority Greg Wilkins
Re: h2 frame layout Poul-Henning Kamp
Re: h2 header field names Mark Nottingham
Re: h2 priority Mark Nottingham
Re: h2 padding Poul-Henning Kamp
Re: HPACK WGLC feedback Mark Nottingham
Re: h2 requirements on authoritative responses Mark Nottingham
Re: h2 padding Poul-Henning Kamp
Re: h2 frame layout Mark Nottingham
Re: h2 padding Brian Smith
Re: h2 padding Brian Smith
Re: h2 use of Upgrade Mark Nottingham
Re: h2 padding Mark Nottingham
Re: h2 definition of HTTP2-Settings Mark Nottingham
Ending streams/connections Greg Wilkins
Re: h2 requirements on authoritative responses Amos Jeffries
Re: h2 frame layout Greg Wilkins
Re: h2 priority James M Snell
Re: h2 priority Greg Wilkins
Re: h2 use of Upgrade Martin Thomson
Re: h2 requirements on authoritative responses Martin Thomson

Tuesday, 2 September 2014

Re: h2 requirements on authoritative responses Martin Thomson
Re: h2 priority Roy T. Fielding
Re: h2 padding Roy T. Fielding
Re: h2 priority Greg Wilkins
Re: h2 use of Upgrade Roy T. Fielding
Re: h2 padding Roy T. Fielding
Re: h2 definition of HTTP2-Settings Martin Thomson
Re: h2 use of Upgrade Martin Thomson
Re: h2 frame layout Martin Thomson
Re: h2 padding Martin Thomson
Re: h2 frame layout Poul-Henning Kamp
Re: h2 frame layout Patrick McManus
Re: h2 padding Guille -bisho-
Re: h2 padding Patrick McManus
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Roy T. Fielding
LC process, was: h2 priority Julian Reschke
Re: h2 frame layout Roy T. Fielding
Re: h2 priority Roberto Peon
Re: h2 priority Poul-Henning Kamp
Re: h2 frame layout Martin Thomson
Re: h2 priority James M Snell
Re: h2 priority Patrick McManus
Re: h2 priority Willy Tarreau
Re: h2 priority Cory Benfield
Re: h2 priority James M Snell
Re: h2 priority Poul-Henning Kamp
Re: h2 priority Patrick McManus
Re: h2 priority Patrick McManus
Re: 2NN Contents Of Related (303 Shortcut) Eric Prud'hommeaux
Re: h2 priority Ilari Liusvaara
Re: h2 priority Simone Bordet
Re: 2NN Contents Of Related (303 Shortcut) Eric Prud'hommeaux
Re: Reporting interop issues Patrick McManus
Reporting interop issues Cory Benfield
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Eric J. Bowman

Monday, 1 September 2014

Re: HPACK WGLC feedback Pavel Rappo
Re: h2 frame layout Stefan Eissing
Re: h2 priority Poul-Henning Kamp
RE: HPACK WGLC feedback RUELLAN Herve
Re: h2 priority Cory Benfield
Re: h2 use of Upgrade Poul-Henning Kamp
h2 definition of HTTP2-Settings Roy T. Fielding
h2 use of Upgrade Roy T. Fielding
Re: h2 frame layout Greg Wilkins
h2 header field names Roy T. Fielding
h2 requirements on authoritative responses Roy T. Fielding
Re: h2 frame layout Matthew Kerwin
Re: h2 priority Greg Wilkins
Re: h2 frame layout Greg Wilkins

Sunday, 31 August 2014

Re: h2 frame layout Matthew Kerwin
h2 priority Roy T. Fielding
Re: h2 frame layout Greg Wilkins
Re: h2 padding Greg Wilkins
HPACK WGLC feedback: appendices Julian Reschke
Re: HPACK WGLC feedback Willy Tarreau
HPACK->HTTP/2 dependency Julian Reschke
HPACK WGLC feedback Julian Reschke
Re: h2 frame layout Poul-Henning Kamp
Re: h2 frame layout Matthew Kerwin

Saturday, 30 August 2014

h2 padding Roy T. Fielding
Re: h2 frame layout Roy T. Fielding
Re: h2 frame layout Greg Wilkins
Re: h2 frame layout Poul-Henning Kamp

Friday, 29 August 2014

Re: h2 frame layout Matthew Kerwin
Re: h2 frame layout Poul-Henning Kamp
h2 frame layout Roy T. Fielding
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Roy T. Fielding
Re: HPACK, Draft 09, Integer Representation Ilari Liusvaara
RE: HPACK, Draft 09, Integer Representation RUELLAN Herve
RE: draft-ietf-httpbis-header-compression-09, 4.2. Header Field Representation Processing | Re: draft-ietf-httpbis-header-compression-09, 5.3. Entry Eviction when Adding New Entries RUELLAN Herve
RE: draft-ietf-httpbis-header-compression-09, 3.3.2. Header Table RUELLAN Herve
RE: HPACK opcode bit patterns RUELLAN Herve
Re: HPACK, Draft 09, Integer Representation Pavel Rappo
Re: Working Group Last Call: RFC7238bis Julian Reschke
RE: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Lucas Pardue
Re: HPACK, Draft 09, Integer Representation Mark Nottingham

Thursday, 28 August 2014

Re: Miscellaneous Comments on -14 Simpson, Robby (GE Energy Management)
RE: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Mike Bishop
Re: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Martin Thomson
Re: HPACK, Draft 09, Integer Representation Tatsuhiro Tsujikawa
Re: HPACK, Draft 09, Integer Representation Pavel Rappo
RE: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Lucas Pardue
Re: HPACK, Draft 09, Integer Representation Tatsuhiro Tsujikawa
HPACK, Draft 09, Integer Representation Pavel Rappo
RE: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Mike Bishop
Re: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Lucas Pardue
Re: Working Group Last Call: RFC7238bis Mark Nottingham
Re: Working Group Last Call: RFC7238bis Matthew Kerwin
Re: Working Group Last Call: RFC7238bis Brian Smith
Working Group Last Call: RFC7238bis Mark Nottingham

Wednesday, 27 August 2014

Re: Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Martin Thomson
Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface Lucas Pardue
Re: Push and Caching Greg Wilkins

Tuesday, 26 August 2014

Re: Push and Caching Martin Thomson
Re: Push and Caching Greg Wilkins
Re: Push and Caching Greg Wilkins
RE: Push and Caching William Chow
Re: Push and Caching Roy T. Fielding
Re: Push and Caching Martin Thomson
Re: Push and Caching Martin Thomson
RE: Push and Caching William Chow
Re: Push and Caching Michael Sweet
Re: Push and Caching Roy T. Fielding
Re: Push and Caching Martin Thomson
Re: Push and Caching Roy T. Fielding
Re: Push and Caching Roy T. Fielding
Re: Push and Caching Chris Drechsler
Re: Push and Caching Mark Nottingham
Re: Push and Caching Matthew Kerwin
RE: Push and Caching William Chow
Re: Push and Caching Mark Nottingham
RE: Push and Caching William Chow
Re: Push and Caching Greg Wilkins
Re: 2NN Contents Of Related (303 Shortcut) Mark Nottingham
Re: 2NN Contents Of Related (303 Shortcut) Martin Thomson
2NN Contents Of Related (303 Shortcut) Eric Prud'hommeaux

Monday, 25 August 2014

Re: Push and Caching Mark Nottingham
Re: Push and Caching Martin Thomson
Re: Push and Caching Mark Nottingham
Re: Push and Caching Martin Thomson
Re: Alt-Svc alternative cache invalidation (ext#16) Mark Nottingham
Re: Permissible states for extension frames #591 Mark Nottingham
Re: Push and Caching Mark Nottingham

Sunday, 24 August 2014

Re: Push and Caching Mark Nottingham
Re: Push and Caching Greg Wilkins
Re: Push and Caching Mark Nottingham
Re: Alt-Svc alternative cache invalidation (ext#16) Erik Nygren
Re: Alt-Svc-Used indicator granularity (ext#34) Erik Nygren

Saturday, 23 August 2014

Re: Permissible states for extension frames #591 Greg Wilkins
Re: handling bad priority parameters Matthew Kerwin
Re: Permissible states for extension frames #591 Martin Thomson
Re: Alt-Svc-Used indicator granularity (ext#34) Martin Thomson

Friday, 22 August 2014

Re: Permissible states for extension frames #591 Greg Wilkins
Re: Alt-Svc alternative cache invalidation (ext#16) Martin Thomson
Alt-Svc-Used indicator granularity (ext#34) Erik Nygren
Re: Alt-Svc alternative cache invalidation (ext#16) Erik Nygren
RE: Push and Caching Mike Bishop
Re: h2 proxy and connection flow control Martin Thomson
Re: Push and Caching Martin Thomson
Re: handling bad priority parameters Martin Thomson
RE: Push and Caching Mike Bishop
Re: Push and Caching Martin Thomson
Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
Re: h2 proxy and connection flow control Ilari Liusvaara
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Julian Reschke
Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
handling bad priority parameters Matthew Kerwin
Re: Push and Caching Mark Nottingham
Re: Push and Caching Patrick McManus

Thursday, 21 August 2014

RE: Push and Caching Mike Bishop
RE: Push and Caching William Chow
Re: h2 proxy and connection flow control Martin Thomson
RE: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Makaraju, Maridi Raju (Raju)
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Martin Thomson
Re: h2 proxy and connection flow control Amos Jeffries
Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Amos Jeffries
Re: h2 proxy and connection flow control Patrick McManus
Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
Re: h2 proxy and connection flow control Patrick McManus
h2 proxy and connection flow control Tatsuhiro Tsujikawa
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Adam Rice
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Amos Jeffries
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Adam Rice
I-D Action: draft-ietf-httpbis-rfc7238bis-00.txt internet-drafts@ietf.org

Wednesday, 20 August 2014

RE: Permissible states for extension frames #591 Mike Bishop
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Martin Thomson
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Martin Thomson
Re: updated http 1.1 rfcs and hop-by-hop Roy T. Fielding
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: Push and Caching Mark Nottingham
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Greg Wilkins
Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Greg Wilkins
Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
Re: Ciphersuite requirements ext#26 Martin Thomson

Tuesday, 19 August 2014

Re: Ciphersuite requirements ext#26 Mark Nottingham
Re: Alt-Svc: alternatives assigned by alternatives Mark Nottingham
Re: Push and Caching Martin Thomson
Re: Push and Caching Greg Wilkins
Re: Alt-Svc alternative cache invalidation (ext#16) Martin Thomson
Re: Alt-Svc alternative cache invalidation (ext#16) Erik Nygren
Ciphersuite requirements ext#26 Martin Thomson
Re: Alt-Svc: alternatives assigned by alternatives Martin Thomson
Re: Push and Caching Martin Thomson
Re: Alt-Svc alternative cache invalidation (ext#16) Martin Thomson
Push and Caching Mike Bishop
Re: Alt-Svc: alternatives assigned by alternatives Patrick McManus
Re: HTTP/2 Push deployed on webtide.com Martin Nilsson
Re: Alt-Svc alternative cache invalidation (ext#16) Julian Reschke
Re: Alt-Svc alternative cache invalidation (ext#16) Erik Nygren
Re: updated http 1.1 rfcs and hop-by-hop Martijn Faassen
Re: updated http 1.1 rfcs and hop-by-hop Amos Jeffries
Re: updated http 1.1 rfcs and hop-by-hop Martijn Faassen
Alt-Svc: alternatives assigned by alternatives Mark Nottingham
Re: Alt-Svc alternative cache invalidation (ext#16) Mark Nottingham
Re: updated http 1.1 rfcs and hop-by-hop Amos Jeffries
Re: HTTP/2 Push deployed on webtide.com Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt Mark Nottingham

Monday, 18 August 2014

Re: HTTP/2 Push deployed on webtide.com Greg Wilkins
I-D Action: draft-ietf-httpbis-tunnel-protocol-00.txt internet-drafts@ietf.org
Re: Alt-Svc alternative cache invalidation (ext#16) Martin Thomson
Re: Alt-Svc alternative cache invalidation (ext#16) Erik Nygren
Alt-Svc alternative cache invalidation (ext#16) Martin Thomson
HTTP/2 Push deployed on webtide.com Simone Bordet
Re: updated http 1.1 rfcs and hop-by-hop Martijn Faassen

Sunday, 17 August 2014

Re: HTTP/2 and Pervasive Monitoring Ilari Liusvaara
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Eliot Lear
Re: HTTP/2 and Pervasive Monitoring Amos Jeffries

Saturday, 16 August 2014

Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
Re: HTTP/2 and Pervasive Monitoring Roland Zink
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp

Friday, 15 August 2014

Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
Re: HTTP/2 and Pervasive Monitoring Eliot Lear
Re: TLS over http2 frames Ben Burkert
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Brian Smith
Re: HTTP/2 and Pervasive Monitoring Martin Thomson
Re: HTTP/2 and Pervasive Monitoring Roland Zink
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Erik Nygren
Re: HTTP/2 and Pervasive Monitoring Cory Benfield
RE: HTTP/2 and Pervasive Monitoring Albert Lunde
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Martin Nilsson
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Eliot Lear
Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
RE: HTTP/2 and Pervasive Monitoring K.Morgan@iaea.org
Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
Re: HTTP/2 and Pervasive Monitoring Amos Jeffries
Re: ext#9: OppSec and Proxies Mark Nottingham
Re: TLS over http2 frames Mark Nottingham
HTTP/2 and Pervasive Monitoring Mark Nottingham
TLS over http2 frames Ben Burkert
Re: Feedback on Fallback Mark Nottingham

Thursday, 14 August 2014

Feedback on Fallback Mike Bishop
Re: [http2-spec] Hpack optimization (#587) Mark Nottingham

Wednesday, 13 August 2014

Re: Miscellaneous Comments on -14 Martin Thomson
RE: [http2-spec] Hpack optimization (#587) Mike Bishop
Re: [http2-spec] Hpack optimization (#587) Greg Wilkins

Tuesday, 12 August 2014

Re: Permissible states for extension frames #591 Greg Wilkins
Re: Permissible states for extension frames #591 Ilari Liusvaara
Re: Hawaii meeting Patrick McManus
Re: Permissible states for extension frames #591 Amos Jeffries
Hawaii meeting Mark Nottingham
Re: Permissible states for extension frames #591 Greg Wilkins
Re: Permissible states for extension frames #591 Martin Thomson
Re: Permissible states for extension frames #591 Greg Wilkins

Monday, 11 August 2014

Permissible states for extension frames #591 Martin Thomson
updated http 1.1 rfcs and hop-by-hop Martijn Faassen
Re: HTTP2 Stream timeouts? Greg Wilkins

Sunday, 10 August 2014

Re: Moving RFC7238 (308 Status Code) to Proposed Standard Barry Leiba
Re: HTTP2 Stream timeouts? Michael Sweet

Friday, 8 August 2014

Re: Static Table Entries Martin Thomson
Re: Static Table Entries Simpson, Robby (GE Energy Management)
Re: Static Table Entries Martin Thomson
Re: Static Table Entries Simpson, Robby (GE Energy Management)
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
Re: Static Table Entries Poul-Henning Kamp
Re: Static Table Entries Martin Nilsson
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Amos Jeffries
Re: Static Table Entries Poul-Henning Kamp
Re: Static Table Entries Greg Wilkins
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Mark Nottingham
Re: Static Table Entries Poul-Henning Kamp
Re: Static Table Entries Martin Thomson
Re: Static Table Entries Greg Wilkins

Thursday, 7 August 2014

Re: Static Table Entries Martin Thomson
Re: Static Table Entries K.Morgan@iaea.org
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Mike Bishop
Re: Static Table Entries Kulkarni, Saurabh
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
Re: Static Table Entries Martin Thomson
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Osama Mazahir
Re: Static Table Entries Kulkarni, Saurabh
Re: Static Table Entries Martin Thomson
Static Table Entries Simpson, Robby (GE Energy Management)
Re: HTTP2 Stream timeouts? Martin Thomson
HTTP2 Stream timeouts? Greg Wilkins
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
Re: HPACK opcode bit patterns Martin Thomson
Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Martin Thomson
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Mike Bishop
Fwd: Second Last Call: <draft-ietf-paws-protocol-14.txt> (Protocol to Access White-Space (PAWS) Databases) to Proposed Standard Mark Nottingham
Re: HPACK opcode bit patterns Michael Sweet
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Osama Mazahir

Wednesday, 6 August 2014

Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Mark Nottingham
Re: HPACK opcode bit patterns Greg Wilkins
Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Hutton, Andrew
Re: HPACK: pseudo-headers ordering Martin Thomson
Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Martin Thomson
Re: Header Table and Static Table Indicies Switched Amos Jeffries
Re: HPACK opcode bit patterns Michael Sweet
Re: Header Table and Static Table Indicies Switched Jeff Pinner
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 K.Morgan@iaea.org
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Jason Greene
Re: HPACK opcode bit patterns Jason Greene
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Greg Wilkins
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Mike Bishop
Re: HPACK opcode bit patterns Michael Sweet
Re: HPACK opcode bit patterns David Krauss
Re: stream state management was: 1xx (informational) responses affect on stream management Greg Wilkins
Re: HPACK opcode bit patterns Alvaro Lopez Ortega
HPACK: pseudo-headers ordering Kaoru Maeda
stream state management was: 1xx (informational) responses affect on stream management K.Morgan@iaea.org
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Mark Nottingham
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Mark Nottingham
Compression ratio of 09 (was: Reference set in HPACK) 山本和彦
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Michael Sweet
HPACK opcode bit patterns Osama Mazahir

Tuesday, 5 August 2014

Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Greg Wilkins
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Zhong Yu
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Greg Wilkins
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Ryan Hamilton
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Ryan Hamilton
Re: 1xx (informational) responses affect on stream management Greg Wilkins
Re: 1xx (informational) responses affect on stream management Martin Thomson
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
Re: 1xx (informational) responses affect on stream management Simone Bordet
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
RE: legality of Transfer-Encoding: chunked bodies in HTTP/2 Osama Mazahir
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Zhong Yu
Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 Martin Thomson
Re: 1xx (informational) responses affect on stream management Martin Thomson
legality of Transfer-Encoding: chunked bodies in HTTP/2 Johnny Graettinger
1xx (informational) responses affect on stream management Matthew Cox
Re: Section 6.9 (WINDOW_UPDATE), shouldn't it always be a connection error if window increment is 0? Martin Thomson
Section 6.9 (WINDOW_UPDATE), shouldn't it always be a connection error if window increment is 0? Matthew Cox
Re: HTTP/2 and Constrained Devices David Krauss
Re: 100 Continue editorial comment Martin Thomson
Re: HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Constrained Devices David Krauss
Re: HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Constrained Devices Ilari Liusvaara
100 Continue editorial comment Greg Wilkins
Re: Moving RFC7238 (308 Status Code) to Proposed Standard Mark Nottingham

Monday, 4 August 2014

Re: HTTP/2 and Constrained Devices Martin Thomson
Re: HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Constrained Devices Jason Greene
Re: HTTP/2 and Constrained Devices Martin Thomson
Re: HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Re: HTTP/2 and Constrained Devices Martin Thomson
Editorial comments (was: WGLC) Martin Thomson
HTTP/2 and Constrained Devices Simpson, Robby (GE Energy Management)
Miscellaneous Comments on -14 Simpson, Robby (GE Energy Management)
RE: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Mike Bishop
RE: Header Table and Static Table Indicies Switched Mike Bishop
Re: Header Table and Static Table Indicies Switched Johnny Graettinger

Sunday, 3 August 2014

Fwd: [apps-discuss] Call For Adoption: draft-nottingham-http-problem Alexey Melnikov
Re: Header Table and Static Table Indicies Switched Martin Thomson
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Ilari Liusvaara
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Ilari Liusvaara
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Process? Was: Header Table and Static Table Indicies Switched Greg Wilkins

Saturday, 2 August 2014

Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Martin Thomson
Re: draft-ietf-httpbis-http2-14, 10.5.1. Limits on Header Block Size Martin Thomson
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Header Table and Static Table Indicies Switched Amos Jeffries
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Martin Thomson
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: New Version Notification for draft-snell-link-method-10.txt James M Snell
Re: New Version Notification for draft-snell-link-method-10.txt Mark Nottingham
Re: Header Table and Static Table Indicies Switched Roberto Peon
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Header Table and Static Table Indicies Switched Roberto Peon

Friday, 1 August 2014

Re: Header Table and Static Table Indicies Switched Greg Wilkins
Re: Header Table and Static Table Indicies Switched Jeff Pinner
h2-14 live on webtide.com Simone Bordet
Re: Header Table and Static Table Indicies Switched Greg Wilkins
Fwd: New Version Notification for draft-snell-link-method-10.txt James M Snell
Re: draft-ietf-httpbis-http2-14, 8.1.3. Examples Martin Thomson
RE: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 Mike Bishop
Re: Header Table and Static Table Indicies Switched Jeff Pinner
Re: Header Table and Static Table Indicies Switched Jason Greene
Re: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 Jeff Pinner
Re: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 K.Morgan@iaea.org
Header Table and Static Table Indicies Switched Jeff Pinner
Re: draft-ietf-httpbis-http2-14, 8.1.3. Examples Martin Thomson
Re: draft-ietf-httpbis-header-compression-09, 3.3.2. Header Table Martin Thomson
Re: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 Martin Thomson
s/RST_STREAM/TERMINATE_STREAM (editorial) was: Naming Consistency (editorial) K.Morgan@iaea.org
RE: Naming Consistency (editorial) K.Morgan@iaea.org
RE: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 K.Morgan@iaea.org
Repository for HTTP/1.1 Issues Mark Nottingham
Re: Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Greg Wilkins
Working Group Last Call: draft-ietf-httpbis-http2-14 and draft-ietf-httpbis-header-compression-09 Mark Nottingham
RE: ext#9: OppSec and Proxies William Chow

Thursday, 31 July 2014

Re: Why "MUST" encoder emit Context Update Martin Thomson
Re: draft-ietf-httpbis-http2-14. 5.1. Stream States Martin Thomson
RE: Why "MUST" encoder emit Context Update RUELLAN Herve
RE: Why "MUST" encoder emit Context Update K.Morgan@iaea.org
I-D Action: draft-ietf-httpbis-header-compression-09.txt internet-drafts@ietf.org
Re: Why "MUST" encoder emit Context Update Ilari Liusvaara

Wednesday, 30 July 2014

Why "MUST" encoder emit Context Update Osama Mazahir
I-D Action: draft-ietf-httpbis-http2-14.txt internet-drafts@ietf.org

Tuesday, 29 July 2014

Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Martin Thomson
Re: ext#9: OppSec and Proxies Martin Thomson
RE: ext#9: OppSec and Proxies emile.stephan@orange.com
Re: ext#9: OppSec and Proxies Roland Zink
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Michael Sweet
Re: Header Parsing Profile Amos Jeffries
Re: ext#9: OppSec and Proxies Amos Jeffries
Re: Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Amos Jeffries
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Amos Jeffries
RE: Preliminary minutes from Toronto emile.stephan@orange.com
Re: Header Parsing Profile Willy Tarreau
Header Parsing Profile Mark Nottingham
ext#9: OppSec and Proxies Mark Nottingham
Call for Adoption: draft-hutton-httpbis-connect-protocol-00 Mark Nottingham
Preliminary minutes from Toronto Mark Nottingham

Monday, 28 July 2014

Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Michael Sweet
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Amos Jeffries
Re: Moving RFC7238 (308 Status Code) to Proposed Standard Tony Hansen
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Michael Sweet
RE: draft-hutton-httpbis-connect-protocol-00.txt Hutton, Andrew
RE: consensus on :query ? Richard Wheeldon (rwheeldo)
RE: Pseudo end-to-end connections considered harmful Richard Wheeldon (rwheeldo)
Re: Moving RFC7238 (308 Status Code) to Proposed Standard Amos Jeffries
Re: Moving RFC7238 (308 Status Code) to Proposed Standard Willy Tarreau
Moving RFC7238 (308 Status Code) to Proposed Standard Mark Nottingham

Friday, 25 July 2014

Thursday, 24 July 2014

Re: TLS 1.2 MTI Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Amos Jeffries
Re: #549: END_STREAM flag on CONTINUATION Mark Nottingham
Re: Consequences of removing the reference set Greg Wilkins
Re: Consequences of removing the reference set Greg Wilkins
Re: Consequences of removing the reference set Greg Wilkins
Re: consensus on :query ? Roland Zink
Re: :scheme, was: consensus on :query ? Erik Nygren
Re: :scheme, was: consensus on :query ? Martin Thomson
Re: Consequences of removing the reference set Roberto Peon
Re: Consequences of removing the reference set Martin Thomson
Re: :scheme, was: consensus on :query ? Erik Nygren
Re: Consequences of removing the reference set Roberto Peon
Re: Consequences of removing the reference set Martin Thomson
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Roberto Peon
RE: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Mike Bishop
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Julian Reschke
Re: Consequences of removing the reference set Roberto Peon
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Poul-Henning Kamp
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Roy T. Fielding
Re: Consequences of removing the reference set Mark Nottingham
Re: consensus on :query ? Mark Nottingham
RE: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Mike Bishop
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Julian Reschke
Re: Pseudo end-to-end connections considered harmful Roland Zink
Re: :scheme, was: consensus on :query ? Roy T. Fielding
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Tatsuhiro Tsujikawa
Re: Consequences of removing the reference set Poul-Henning Kamp
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Michael Sweet
Re: Consequences of removing the reference set Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Consequences of removing the reference set Poul-Henning Kamp
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Amos Jeffries
Consequences of removing the reference set Martin Thomson
Re: Pseudo end-to-end connections considered harmful Amos Jeffries
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Poul-Henning Kamp
Re: Pseudo end-to-end connections considered harmful Roland Zink
Re: Pseudo end-to-end connections considered harmful Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Amos Jeffries
Re: :scheme, was: consensus on :query ? Martin Thomson
Re: :scheme, was: consensus on :query ? Patrick McManus
Pseudo end-to-end connections considered harmful Roland Zink
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Martin Thomson
Re: :scheme, was: consensus on :query ? Erik Nygren
Re: :scheme, was: consensus on :query ? Martin Nilsson
Re: :scheme, was: consensus on :query ? Amos Jeffries
Re: :scheme, was: consensus on :query ? Amos Jeffries
Re: consensus on :query ? Poul-Henning Kamp
Re: :scheme, was: consensus on :query ? Willy Tarreau
Re: :scheme, was: consensus on :query ? Yutaka Hirano
Re: :scheme, was: consensus on :query ? Zhong Yu
Re: :scheme, was: consensus on :query ? Greg Wilkins
Re: :scheme, was: consensus on :query ? Adrien de Croy
:scheme, was: consensus on :query ? Greg Wilkins
Re: consensus on :query ? Matthew Kerwin
Re: consensus on :query ? Adrien de Croy
Re: consensus on :query ? Zhong Yu
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Tatsuhiro Tsujikawa
Re: consensus on :query ? Matthew Kerwin
Re: consensus on :query ? Zhong Yu

Wednesday, 23 July 2014

Re: consensus on :query ? Adrien de Croy
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Martin Thomson
Re: consensus on :query ? Martin Thomson
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Matthew Kerwin
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Roberto Peon
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Roberto Peon
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Matthew Kerwin
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Amos Jeffries
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Roberto Peon
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Amos Jeffries
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Tatsuhiro Tsujikawa
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Matthew Kerwin
Re: #557: Intra-message HEADERS frames Roberto Peon
Re: #557: Intra-message HEADERS frames Amos Jeffries
Re: consensus on :query ? Adrien de Croy

Tuesday, 22 July 2014

Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Greg Wilkins
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: Fwd: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Matthew Kerwin
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: referring to the HTTP spec Ruben Verborgh
Re: referring to the HTTP spec Roy T. Fielding
referring to the HTTP spec Ruben Verborgh
TLS 1.2 MTI Martin Thomson
Fwd: [apps-discuss] Last Call conduct redux (Was: Last Call: <draft-ietf-appsawg-nullmx-05.txt> (A NULL MX Resource Record for Domains that Accept No Mail) to Proposed Standard) Mark Nottingham
Re: #557: Intra-message HEADERS frames Mark Nottingham
Re: draft-ietf-httpbis-http2-encryption Mark Nottingham
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Martin Thomson
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Tatsuhiro Tsujikawa
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Martin Thomson
Re: #557: Intra-message HEADERS frames Martin Thomson
Re: Getting to Consensus on 1xx Status Codes (#535) Cyrus Daboo
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: #557: Intra-message HEADERS frames James M Snell
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: #557: Intra-message HEADERS frames Poul-Henning Kamp
Re: #557: Intra-message HEADERS frames Alvaro Lopez Ortega
Re: Getting to Consensus on 1xx Status Codes (#535) Martin Thomson
Re: draft-ietf-httpbis-http2-encryption Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Cyrus Daboo
Re: draft-ietf-httpbis-http2-encryption Martin Thomson
draft-ietf-httpbis-http2-encryption emile.stephan@orange.com
Re: #557: Intra-message HEADERS frames Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Ilari Liusvaara
Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues)) Ilari Liusvaara
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Fwd: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Poul-Henning Kamp
Re: consensus on :query ? David Krauss
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Willy Tarreau
Re: #539: Priority from server to client David Krauss
Re: consensus on :query ? Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: Getting to Consensus on 1xx Status Codes (#535) Zhong Yu
Re: Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Roy T. Fielding
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Fwd: New Version Notification for draft-kerwin-http2-encoded-data-01.txt Matthew Kerwin

Monday, 21 July 2014

Re: consensus on :query ? Adrien de Croy
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Adrien de Croy
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Adrien de Croy
Re: consensus on :query ? Jason Greene
RE: Priority Tree Synchronization Draft RUELLAN Herve
Re: #555: frame synchronization Yoav Nir
Issues #555 and #556 (:query and frame sync) Mark Nottingham
Re: consensus on :query ? Alvaro Lopez Ortega
Re: proxies are dangerous slide Poul-Henning Kamp
Re: proxies are dangerous slide Adrien de Croy
Re: proxies are dangerous slide Willy Tarreau
proxies are dangerous slide Cullen Jennings (fluffy)
Re: #555: frame synchronization Patrick McManus
Re: #555: frame synchronization Cory Benfield
Re: #555: frame synchronization Poul-Henning Kamp
Re: consensus on :query ? Ted Hardie
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? James M Snell
Re: #539: Priority from server to client Johnny Graettinger
Re: consensus on :query ? Willy Tarreau
Re: #539: Priority from server to client Mark Nottingham
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Martin Thomson
Re: #555: frame synchronization Mark Nottingham
Re: consensus on :query ? Mark Nottingham
Re: consensus on :query ? Julian Reschke
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Julian Reschke
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Jeroen de Borst
Re: #555: frame synchronization Poul-Henning Kamp
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Eric Rescorla
Re: consensus on :query ? Willy Tarreau
Re: consensus on :query ? Mark Nottingham
Re: consensus on :query ? Patrick McManus
Re: #555: frame synchronization Kinkie
Re: consensus on :query ? Martin Thomson
Re: consensus on :query ? James M Snell
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: consensus on :query ? Julian Reschke
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Mark Nottingham
Re: #555: frame synchronization Michael Sweet
Re: consensus on :query ? Eric Rescorla
Re: consensus on :query ? Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Michael Sweet
Re: #557: Intra-message HEADERS frames Martin Thomson
Re: #555: frame synchronization Kinkie
Re: #549: END_STREAM flag on CONTINUATION David Krauss
Re: #549: END_STREAM flag on CONTINUATION Poul-Henning Kamp
Re: #555: frame synchronization Poul-Henning Kamp
Re: consensus on :query ? Willy Tarreau
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Willy Tarreau
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Willy Tarreau
Re: #549: END_STREAM flag on CONTINUATION Glen Knowles
Re: consensus on :query ? Phil Hunt
Re: Getting to Consensus: CONTINUATION-related issues Mark Nottingham
Re: #549: END_STREAM flag on CONTINUATION Greg Wilkins
Re: #549: END_STREAM flag on CONTINUATION Matthew Kerwin
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Greg Wilkins
Re: #557: Intra-message HEADERS frames Greg Wilkins
Re: consensus on :query ? Greg Wilkins
Re: consensus on :query ? Roberto Peon

Sunday, 20 July 2014

Re: #549: END_STREAM flag on CONTINUATION Jeff Pinner
Re: #555: frame synchronization Martin Thomson
Re: #557: Intra-message HEADERS frames James M Snell
Re: #549: END_STREAM flag on CONTINUATION Poul-Henning Kamp
Re: Getting to Consensus: CONTINUATION-related issues David Krauss
Re: #557: Intra-message HEADERS frames Poul-Henning Kamp
Re: Getting to Consensus: CONTINUATION-related issues Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Poul-Henning Kamp
Re: consensus on :query ? Roberto Peon
Re: consensus on :query ? Erik Nygren
Re: consensus on :query ? Phil Hunt
#555: frame synchronization Mark Nottingham
Re: consensus on :query ? Mark Nottingham
#549: END_STREAM flag on CONTINUATION Mark Nottingham
#557: Intra-message HEADERS frames Mark Nottingham
Re: Getting to Consensus: CONTINUATION-related issues Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.5 Malformed Requests and Responses, response of HEAD request Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Priority Tree Synchronization Draft RUELLAN Herve
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Roberto Peon
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Brian Smith
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Brian Smith
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Roberto Peon
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) David Krauss

Saturday, 19 July 2014

Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Greg Wilkins
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Eric Rescorla
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Roberto Peon
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Brian Smith
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) David Krauss
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Greg Wilkins
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Roberto Peon
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Amos Jeffries
Re: Getting to Consensus: CONTINUATION-related issues Glen Knowles
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Greg Wilkins

Friday, 18 July 2014

Re: Getting to Consensus on 1xx Status Codes (#535) Roy T. Fielding
Re: Getting to Consensus on 1xx Status Codes (#535) Roy T. Fielding
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Michael Sweet
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Michael Sweet
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Ilari Liusvaara
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Poul-Henning Kamp
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Michael Sweet
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Jason Greene
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Willy Tarreau
Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Michael Sweet
Re: Getting to Consensus: CONTINUATION-related issues Poul-Henning Kamp
Re: Getting to Consensus: CONTINUATION-related issues Martin Thomson
Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues) Martin Thomson
Re: Getting to Consensus: CONTINUATION-related issues Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Willy Tarreau
Re: Getting to Consensus: CONTINUATION-related issues Nicholas Hurley
Re: Getting to Consensus: CONTINUATION-related issues Jason Greene
Re: Getting to Consensus on 1xx Status Codes (#535) Roy T. Fielding
Re: Getting to Consensus: CONTINUATION-related issues Martin Thomson
Re: Getting to Consensus: CONTINUATION-related issues Michael Sweet
Re: Getting to Consensus: CONTINUATION-related issues Nicholas Hurley
Re: Getting to Consensus: CONTINUATION-related issues Patrick McManus
Re: Getting to Consensus: CONTINUATION-related issues Tatsuhiro Tsujikawa
Re: Getting to Consensus: CONTINUATION-related issues Michael Sweet
Re: Getting to Consensus: CONTINUATION-related issues Cory Benfield
RE: Getting to Consensus: CONTINUATION-related issues K.Morgan@iaea.org
Re: Getting to Consensus: CONTINUATION-related issues Mike Belshe
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Getting to Consensus: CONTINUATION-related issues David Krauss
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Getting to Consensus: CONTINUATION-related issues Shigeki Ohtsu
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Getting to Consensus: CONTINUATION-related issues Willy Tarreau
Re: Getting to Consensus: CONTINUATION-related issues Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Getting to Consensus on 1xx Status Codes (#535) Roberto Peon
Re: Getting to Consensus: CONTINUATION-related issues Roberto Peon
Re: Getting to Consensus: CONTINUATION-related issues Robert Collins
Re: Getting to Consensus: CONTINUATION-related issues K.Morgan@iaea.org
Re: Getting to Consensus: CONTINUATION-related issues Jason Greene
RE: Getting to Consensus: CONTINUATION-related issues Rob Trace
Re: Getting to Consensus: CONTINUATION-related issues Amos Jeffries
Re: Getting to Consensus: CONTINUATION-related issues Greg Wilkins
Re: Getting to Consensus: CONTINUATION-related issues Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Amos Jeffries
Re: Getting to Consensus: CONTINUATION-related issues Amos Jeffries
Re: Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Getting to Consensus: CONTINUATION-related issues Mark Nottingham
Re: Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Re: Options for CONTINUATION-related issues Greg Wilkins
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Getting to Consensus on 1xx Status Codes (#535) Martin Thomson

Thursday, 17 July 2014

Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Poul-Henning Kamp
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Ciphersuites (was Re: Mandatory to implement cipher suites) Martin Thomson
Ciphersuites (was Re: Mandatory to implement cipher suites) Yoav Nir
Re: Options for CONTINUATION-related issues Roberto Peon
Re: Options for CONTINUATION-related issues Jason Greene
Re: Mandatory to implement cipher suites Nicholas Hurley
Re: Getting to Consensus on 1xx Status Codes (#535) Nicholas Hurley
Re: Options for CONTINUATION-related issues Roberto Peon
Re: Getting to Consensus on 1xx Status Codes (#535) Martin Thomson
Re: Options for CONTINUATION-related issues Nicholas Hurley
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Yutaka Hirano
Re: Options for CONTINUATION-related issues Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Yutaka Hirano
Re: Options for CONTINUATION-related issues Jason Greene
Re: Getting to Consensus on 1xx Status Codes (#535) Martin Thomson
Re: #551: Limiting header sizes Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: #537: Remove segments (consensus call) Martin Thomson
Re: Getting to Consensus on 1xx Status Codes (#535) Amos Jeffries
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Getting to Consensus on 1xx Status Codes (#535) Amos Jeffries
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Willy Tarreau
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: #551: Limiting header sizes Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Poul-Henning Kamp
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Julian Reschke
Re: Getting to Consensus on 1xx Status Codes (#535) Michael Sweet
Re: Getting to Consensus on 1xx Status Codes (#535) Greg Wilkins
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Yutaka Hirano
Re: #551: Limiting header sizes Glen Knowles
Re: Options for CONTINUATION-related issues Mark Nottingham
Re: 5.5 Extending HTTP/2, WS_OVER_HTTP/2 | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Yutaka Hirano
Re: Options for CONTINUATION-related issues Greg Wilkins
Getting to Consensus on 1xx Status Codes (#535) Mark Nottingham
Re: #537: Remove segments (consensus call) Yutaka Hirano
Re: Options for CONTINUATION-related issues Mark Nottingham
Re: Options for CONTINUATION-related issues Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Re: #537: Remove segments (consensus call) Mark Nottingham
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Yutaka Hirano
RE: "Upgrade: h2c" Rob Trace
Re: #537: Remove segments (consensus call) Greg Wilkins
Mandatory to implement cipher suites Martin Thomson

Wednesday, 16 July 2014

Re: #537: Remove segments (consensus call) Martin Thomson
Re: #537: Remove segments (consensus call) Erik Nygren
Re: Possible to support only HTTP/2 for "http" URIs? "https" URIs? Martin Thomson
Re: Possible to support only HTTP/2 for "http" URIs? "https" URIs? K.Morgan@iaea.org
Re: #539: Priority from server to client K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: #539: Priority from server to client Martin Thomson
Re: #551: Limiting header sizes Martin Thomson
Re: Possible to support only HTTP/2 for "http" URIs? "https" URIs? Martin Thomson
Re: http/2 and "extensions" Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Options for CONTINUATION-related issues Jason Greene
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Nilsson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
Re: Options for CONTINUATION-related issues Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) James M Snell
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: draft-ietf-httpbis-alt-svc-02, 5. The Alt-Svc-Used HTTP Header Field Julian Reschke
REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Tatsuhiro Tsujikawa
RE: "Upgrade: h2c" K.Morgan@iaea.org
RE: #539: Priority from server to client RUELLAN Herve
Re: "Upgrade: h2c" Michael Sweet
RE: "Upgrade: h2c" K.Morgan@iaea.org
Re: "Upgrade: h2c" Mark Nottingham
Re: "Upgrade: h2c" Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
"Upgrade: h2c" K.Morgan@iaea.org
Re: #551: Limiting header sizes Poul-Henning Kamp
Re: http/2 and "extensions" Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
Possible to support only HTTP/2 for "http" URIs? "https" URIs? K.Morgan@iaea.org
Re: Options for CONTINUATION-related issues Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Options for CONTINUATION-related issues Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Cory Benfield
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: #551: Limiting header sizes Willy Tarreau
Re: #551: Limiting header sizes Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
#551: Limiting header sizes Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Matthew Kerwin
Re: #537: Remove segments (consensus call) Roberto Peon
RE: Call for Consensus: Remove "reference set" from HPACK (to address #552) Rob Trace
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: #537: Remove segments (consensus call) Yutaka Hirano
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) James M Snell

Tuesday, 15 July 2014

Re: #537: Remove segments (consensus call) Greg Wilkins
Re: #537: Remove segments (consensus call) Martin Thomson
Re: #537: Remove segments (consensus call) Martin Thomson
Re: #537: Remove segments (consensus call) Greg Wilkins
Re: #539: Priority from server to client Martin Thomson
Re: #537: Remove segments (consensus call) David Krauss
Re: #539: Priority from server to client David Krauss
Re: #539: Priority from server to client Martin Thomson
Re: #539: Priority from server to client David Krauss
Re: http/2 and "extensions" Matthew Kerwin
Re: http/2 and "extensions" Martin Thomson
Re: http/2 and "extensions" Matthew Kerwin
Re: #537: Remove segments (consensus call) Martin Thomson
Re: #537: Remove segments (consensus call) Nicholas Hurley
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Jason Greene
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
Re: http/2 and "extensions" Martin Thomson
Re: http/2 and "extensions" James M Snell
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
Re: http/2 and "extensions" Martin Thomson
http/2 and "extensions" James M Snell
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) James M Snell
Re: #539: Priority from server to client Martin Thomson
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Julian Reschke
Re: #535: No 1xx Status Codes Martin Thomson
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt James M Snell
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Eric Rescorla
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: #537: Remove segments (consensus call) Martin Thomson
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
RE: Sending priority from a server RUELLAN Herve
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
RE: #539: Priority from server to client RUELLAN Herve
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Eric Rescorla
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Julian Reschke
Re: Treating paths and queries differently, was: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
Re: Initial agenda for Toronto bizzbyster@gmail.com
Re: Treating paths and queries differently, was: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt James M Snell
Treating paths and queries differently, was: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Julian Reschke
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Eric Rescorla
Re: #535: No 1xx Status Codes Greg Wilkins
Re: #535: No 1xx Status Codes Amos Jeffries
Re: Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
RE: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Richard Wheeldon (rwheeldo)
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: #535: No 1xx Status Codes Willy Tarreau
RE: Call for Consensus: Remove "reference set" from HPACK (to address #552) K.Morgan@iaea.org
Re: #535: No 1xx Status Codes Willy Tarreau
Re: #535: No 1xx Status Codes Poul-Henning Kamp
Re: #535: No 1xx Status Codes Greg Wilkins
Re: #535: No 1xx Status Codes Julian Reschke
Re: #535: No 1xx Status Codes Poul-Henning Kamp
Re: #535: No 1xx Status Codes Mark Nottingham
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Roberto Peon
Re: #537: Remove segments (consensus call) Mark Nottingham
Re: #529: Working around concurrency limits Mark Nottingham
Re: #539: Priority from server to client Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: PRIORITY extension Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Roberto Peon
Re: Initial agenda for Toronto Mark Nottingham
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Martin Thomson
Editor-ready: Frame size (to address #553) Mark Nottingham
Re: PRIORITY extension Jason Greene
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins

Monday, 14 July 2014

Re: PRIORITY extension Greg Wilkins
Re: PRIORITY extension Jason Greene
Re: Striving for Compromise (Consensus?) Greg Wilkins
Re: PRIORITY extension Roberto Peon
Re: PRIORITY extension Jason Greene
Re: Wiki for CONTINUATION Proposals Roberto Peon
Re: PRIORITY extension Roberto Peon
Re: Call for Consensus: Frame size (to address #553) Martin Thomson
Re: Call for Consensus: Frame size (to address #553) Johnny Graettinger
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Jeff Pinner
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Johnny Graettinger
Re: Call for Consensus: Frame size (to address #553) Jason Greene
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Jason Greene
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Johnny Graettinger
Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: PRIORITY extension Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Johnny Graettinger
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Johnny Graettinger
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: PRIORITY extension Patrick McManus
Re: PRIORITY extension Patrick McManus
Re: PRIORITY extension K.Morgan@iaea.org
Re: PRIORITY extension Martin Thomson
Re: PRIORITY extension K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Tatsuhiro Tsujikawa
Re: PRIORITY extension Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Cory Benfield
Re: Striving for Compromise (Consensus?) Johnny Graettinger
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Johnny Graettinger
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Jeff Pinner
Re: PRIORITY extension Poul-Henning Kamp
Re: Fwd: I-D Action: draft-reschke-http-jfv-00.txt Poul-Henning Kamp
Re: Fwd: I-D Action: draft-reschke-http-jfv-00.txt James M Snell
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Tatsuhiro Tsujikawa
Re: PRIORITY extension Patrick McManus
Re: PRIORITY extension Tatsuhiro Tsujikawa
Re: PRIORITY extension Patrick McManus
RE: PRIORITY extension K.Morgan@iaea.org
RE: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: PRIORITY extension Patrick McManus
Re: Fwd: I-D Action: draft-reschke-http-jfv-00.txt Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Yoav Nir
Fwd: I-D Action: draft-reschke-http-jfv-00.txt Julian Reschke
Re: Initial agenda for Toronto Julian Reschke
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Large Frame Proposal Salvatore Loreto
RE: PRIORITY extension Richard Wheeldon (rwheeldo)
Re: Call for Consensus: Frame size (to address #553) Yoav Nir
RE: #557 Intra-Message HEADERS frames was: Striving for Compromise (Consensus?) K.Morgan@iaea.org
RE: Call for Consensus: Remove "reference set" from HPACK (to address #552) K.Morgan@iaea.org
RE: PRIORITY extension K.Morgan@iaea.org
RE: Fragmentation for headers: why jumbo != continuation. K.Morgan@iaea.org
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Yoav Nir
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Roberto Peon
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) 山本和彦
Re: reserved flags and extensions Willy Tarreau
Re: reserved flags and extensions Willy Tarreau
Re: reserved flags and extensions Willy Tarreau
Re: PRIORITY extension Tatsuhiro Tsujikawa
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Tatsuhiro Tsujikawa
Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Yutaka Hirano
Re: Wiki for CONTINUATION Proposals Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) 山本和彦
Re: PRIORITY extension David Krauss
Re: PRIORITY extension Greg Wilkins
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Greg Wilkins
Re: PRIORITY extension Patrick McManus
Re: PRIORITY extension Tatsuhiro Tsujikawa
Re: PRIORITY extension Poul-Henning Kamp
Re: reserved flags and extensions Greg Wilkins
Re: PRIORITY extension Patrick McManus
Re: Call for Consensus: Frame size (to address #553) Greg Wilkins
Re: reserved flags and extensions Matthew Kerwin

Sunday, 13 July 2014

Re: PRIORITY extension David Krauss
Re: PRIORITY extension David Krauss
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Jeff Pinner
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: PRIORITY extension Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Jeff Pinner
Re: reserved flags and extensions Poul-Henning Kamp
Re: #557 Intra-Message HEADERS frames was: Striving for Compromise (Consensus?) Martin Thomson
Re: reserved flags and extensions Martin Thomson
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: PRIORITY extension Martin Thomson
Re: Call for Consensus: Frame size (to address #553) Martin Thomson
Re: #557 Intra-Message HEADERS frames was: Striving for Compromise (Consensus?) Erik Nygren
Re: Call for Consensus: Frame size (to address #553) Erik Nygren
Re: Fragmentation for headers: why jumbo != continuation. Poul-Henning Kamp
Re: reserved flags and extensions Willy Tarreau
Re: Fragmentation for headers: why jumbo != continuation. Johnny Graettinger
Re: Fragmentation for headers: why jumbo != continuation. Johnny Graettinger
Re: reserved flags and extensions Yoav Nir
Re: Call for Consensus: Frame size (to address #553) Yoav Nir
Re: Fragmentation for headers: why jumbo != continuation. David Krauss
reserved flags and extensions Willy Tarreau
Re: Striving for Compromise (Consensus?) Willy Tarreau

Saturday, 12 July 2014

Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) 山本和彦
#557 Intra-Message HEADERS frames was: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) K.Morgan@iaea.org
PRIORITY extension K.Morgan@iaea.org
Re: Call for Consensus: Frame size (to address #553) Jeff Pinner
Re: Call for Consensus: Frame size (to address #553) Jason Greene
Issues 555 and 556 Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) James M Snell
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) James M Snell
Re: [Editorial Errata Reported] RFC7230 (4050) Barry Leiba
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Cory Benfield
Re: Call for Consensus: Frame size (to address #553) K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) K.Morgan@iaea.org
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Moto Ishizawa
Re: Fragmentation for headers: why jumbo != continuation. Amos Jeffries
Re: Sending priority from a server David Krauss
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Poul-Henning Kamp
Re: Sending priority from a server Amos Jeffries
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Tatsuhiro Tsujikawa
Re: Call for Consensus: Frame size (to address #553) Tatsuhiro Tsujikawa
Re: Fragmentation for headers: why jumbo != continuation. Willy Tarreau
RE: Call for Consensus: Frame size (to address #553) Osama Mazahir
Re: Call for Consensus: Frame size (to address #553) Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Poul-Henning Kamp
Re: Call for Consensus: Frame size (to address #553) Willy Tarreau
Re: Call for Consensus: Remove "reference set" from HPACK (to address #552) Willy Tarreau
Re: Wiki for CONTINUATION Proposals Willy Tarreau
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Wiki for CONTINUATION Proposals Mark Nottingham
Call for Consensus: Remove "reference set" from HPACK (to address #552) Mark Nottingham
Call for Consensus: Frame size (to address #553) Mark Nottingham
Re: Striving for Compromise (Consensus?) Mark Nottingham
Re: Striving for Compromise (Consensus?) Mark Nottingham
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Striving for Compromise (Consensus?) Greg Wilkins
Re: Striving for Compromise (Consensus?) Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Striving for Compromise (Consensus?) Roberto Peon
Re: A rough analysis of the impact of headers on DoS Amos Jeffries
Re: Fragmentation for headers: why jumbo != continuation. Amos Jeffries
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Sending priority from a server David Krauss
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Sending priority from a server Roberto Peon
Re: Striving for Compromise (Consensus?) Roberto Peon
Re: Sending priority from a server David Krauss
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Sending priority from a server Martin Thomson
Re: Striving for Compromise (Consensus?) Amos Jeffries
Re: Large Frame Proposal Amos Jeffries
Re: A rough analysis of the impact of headers on DoS Martin Thomson
Re: Sending priority from a server David Krauss
Re: A rough analysis of the impact of headers on DoS Amos Jeffries
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Sending priority from a server Martin Thomson
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Striving for Compromise (Consensus?) Roberto Peon
Re: Large Frame Proposal Roberto Peon
Re: Sending priority from a server David Krauss

Friday, 11 July 2014

Re: Striving for Compromise (Consensus?) Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Striving for Compromise (Consensus?) Martin Thomson
Sending priority from a server Martin Thomson
Re: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
RE: Striving for Compromise (Consensus?) Rob Trace
Re: Striving for Compromise (Consensus?) Nicholas Hurley
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Phil Hunt
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) Erik Nygren
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Johnny Graettinger
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Erik Nygren
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Jason Greene
Re: Striving for Compromise (Consensus?) Willy Tarreau
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Jason Greene
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Martin Thomson
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Phil Hunt
Re: Striving for Compromise (Consensus?) Johnny Graettinger
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Martin Thomson
Re: Striving for Compromise (Consensus?) Jason Greene
Re: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Phil Hunt
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Jason Greene
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: Striving for Compromise (Consensus?) Jason Greene
Re: Striving for Compromise (Consensus?) Nicholas Hurley
Re: Striving for Compromise (Consensus?) Willy Tarreau
Re: Striving for Compromise (Consensus?) Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2 Martin Thomson
Re: Striving for Compromise (Consensus?) Johnny Graettinger
Re: Striving for Compromise (Consensus?) Johnny Graettinger
RE: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Richard Wheeldon (rwheeldo)
A rough analysis of the impact of headers on DoS Roberto Peon
Re: Large Frame Proposal Albert Lunde
Re: Large Frame Proposal Jason Greene
Re: Large Frame Proposal Roberto Peon
RE: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads K.Morgan@iaea.org
Re: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Mike Belshe
Re: Large Frame Proposal Jason Greene
Re: Striving for Compromise (Consensus?) Jeff Pinner
RE: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Patrick McManus
Re: Striving for Compromise (Consensus?) Jeff Pinner
Re: Fragmentation for headers: why jumbo != continuation. Amos Jeffries
Re: Fragmentation for headers: why jumbo != continuation. Amos Jeffries
RE: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Fragmentation for headers: why jumbo != continuation. Mark Nottingham
Re: Striving for Compromise (Consensus?) Mark Nottingham
RE: draft-ietf-httpbis-header-compression-latest, 4.1 Header Field Representation Processing RUELLAN Herve
Re: Fragmentation for headers: why jumbo != continuation. Amos Jeffries
Re: #540: "jumbo" frames Poul-Henning Kamp
Re: Striving for Compromise (Consensus?) Poul-Henning Kamp
Re: #540: "jumbo" frames Amos Jeffries
RE: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) Mark Nottingham
Re: Striving for Compromise (Consensus?) Willy Tarreau
Re: Striving for Compromise (Consensus?) Mark Nottingham
Re: Striving for Compromise (Consensus?) K.Morgan@iaea.org
Re: Striving for Compromise (Consensus?) Willy Tarreau
Re: Striving for Compromise (Consensus?) Mark Nottingham
Re: Striving for Compromise (Consensus?) Greg Wilkins
Re: Striving for Compromise (Consensus?) Willy Tarreau
Striving for Compromise (Consensus?) Jeff Pinner
Re: Initial agenda for Toronto Peter L
RE: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Rob Trace
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Jeff Pinner
Re: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Mark Nottingham
Re: Fragmentation for headers: why jumbo != continuation. Mark Nottingham
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Willy Tarreau
Re: Fragmentation for headers: why jumbo != continuation. Mark Nottingham
Re: Fragmentation for headers: why jumbo != continuation. Willy Tarreau
Re: willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads Martin Thomson
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Greg Wilkins
Re: #540: "jumbo" frames Jason Greene
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Martin Thomson
Re: Bad Actors, was: Fragmentation for headers: why jumbo != continuation. Roberto Peon
willchan's thoughts on continuations, jumbo frames, etc after *only skimming* the threads 陈智昌
Re: Large Frame Proposal David Krauss
Bad Actors, was: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: #540: "jumbo" frames Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
RE: Large Frame Proposal Rob Trace
RE: Fragmentation for headers: why jumbo != continuation. Rob Trace
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: Fragmentation for headers: why jumbo != continuation. James M Snell

Thursday, 10 July 2014

Re: #540: "jumbo" frames Nicholas Hurley
Re: #540: "jumbo" frames Nicholas Hurley
Re: Fragmentation for headers: why jumbo != continuation. Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Poul-Henning Kamp
Re: #540: "jumbo" frames Greg Wilkins
Re: Fragmentation for headers: why jumbo != continuation. Roland Zink
Re: Fragmentation for headers: why jumbo != continuation. Willy Tarreau
Re: Fragmentation for headers: why jumbo != continuation. K.Morgan@iaea.org
Fragmentation for headers: why jumbo != continuation. Roberto Peon
Re: "Can we please append a byte to the HEADERS frame" Poul-Henning Kamp
Re: "Can we please append a byte to the HEADERS frame" Martin Thomson
Re: "Can we please append a byte to the HEADERS frame" Poul-Henning Kamp
Re: #540: "jumbo" frames Jason Greene
Re: #540: "jumbo" frames Jeff Pinner
Re: #540: "jumbo" frames Nicholas Hurley
"Can we please append a byte to the HEADERS frame" Martin Thomson
RE: Large Frame Proposal K.Morgan@iaea.org
Re: #540: "jumbo" frames Amos Jeffries
Re: Large Frame Proposal Amos Jeffries
Re: Large Frame Proposal Amos Jeffries
Re: Large Frame Proposal Amos Jeffries
Re: Large Frame Proposal Tatsuhiro Tsujikawa
RE: Compressing HTTP headers K.Morgan@iaea.org
RE: Large Frame Proposal K.Morgan@iaea.org
Re: Large Frame Proposal Yoav Nir
RE: Large Frame Proposal K.Morgan@iaea.org
Re: Large Frame Proposal Poul-Henning Kamp
RE: Large Frame Proposal K.Morgan@iaea.org
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: draft-ietf-httpbis-http2-latest, 4.3 Header Compression and Decompression, 10.6 Use of Compression Martin Thomson
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Jason Greene
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Mark Nottingham
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Mark Nottingham
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Greg Wilkins

Wednesday, 9 July 2014

Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Julian Reschke
Re: draft-ietf-httpbis-http2-latest, 4.3 Header Compression and Decompression, 10.6 Use of Compression Martin Thomson
Re: Large Frame Proposal 陈智昌
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal James M Snell
Re: Large Frame Proposal Patrick McManus
RE: Large Frames, Continuations, Flow Control, and changing HPACK K.Morgan@iaea.org
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Patrick McManus
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Patrick McManus
Re: #529: Working around concurrency limits Peter L
Re: #529: Working around concurrency limits Peter L
RE: Large Frame Proposal K.Morgan@iaea.org
Re: Large Frames, Continuations, Flow Control, and changing HPACK Cory Benfield
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal David Krauss
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) Eliot Lear
Re: Ambiguity parsing WWW-Authenticate value Julian Reschke
Re: Compressing HTTP headers Poul-Henning Kamp
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) 陈智昌
Re: Large Frame Proposal Matthew Kerwin
Re: Large Frame Proposal Amos Jeffries
Ambiguity parsing WWW-Authenticate value cowwoc
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Amos Jeffries
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Jason Greene
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Amos Jeffries
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Jason Greene
Re: Large Frames, Continuations, Flow Control, and changing HPACK Amos Jeffries
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Greg Wilkins
Re: Large Frames, Continuations, Flow Control, and changing HPACK James M Snell
Re: Large Frame Proposal David Krauss
Re: Large Frame Proposal Greg Wilkins
Re: Large Frames, Continuations, Flow Control, and changing HPACK Greg Wilkins
Re: Large Frames, Continuations, Flow Control, and changing HPACK James M Snell
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) Erik Nygren
Re: Large Frame Proposal Jeff Pinner
Re: Large Frame Proposal Jeff Pinner
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) 陈智昌
Re: Large Frames, Continuations, Flow Control, and changing HPACK Mark Nottingham
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) Erik Nygren
Re: Large Frames, Continuations, Flow Control, and changing HPACK 陈智昌
Re: Large Frames, Continuations, Flow Control, and changing HPACK Tatsuhiro Tsujikawa
Re: Large Frames, Continuations, Flow Control, and changing HPACK Erik Nygren
Re: Service Bindings DNS Records (draft-nygren-service-bindings-00) 陈智昌
Re: Large Frames, Continuations, Flow Control, and changing HPACK Mike Belshe
Re: Compressing HTTP headers 陈智昌
Re: Large Frame Proposal 陈智昌
Re: Large Frame Proposal 陈智昌
Re: Large Frames, Continuations, Flow Control, and changing HPACK 陈智昌
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner

Tuesday, 8 July 2014

Re: Large Frames, Continuations, Flow Control, and changing HPACK Roberto Peon
Re: Large Frames, Continuations, Flow Control, and changing HPACK Greg Wilkins
Re: Large Frames, Continuations, Flow Control, and changing HPACK Roberto Peon
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Nicholas Hurley
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Nicholas Hurley
Re: Large Frame Proposal - WINDOW UPDATE Greg Wilkins
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jason Greene
Re: #541: CONTINUATION Jason Greene
Re: Large Frame Proposal Mike Belshe
Re: Large Frames, Continuations, Flow Control, and changing HPACK Mike Belshe
Re: Another CONTINUATION Proposal Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Another CONTINUATION Proposal K.Morgan@iaea.org
Re: Large Frames, Continuations, Flow Control, and changing HPACK K.Morgan@iaea.org
Re: Large Frames, Continuations, Flow Control, and changing HPACK K.Morgan@iaea.org
Re: #541: CONTINUATION Martin Thomson
Re: #541: CONTINUATION K.Morgan@iaea.org
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Martin Thomson
Re: #541: CONTINUATION Martin Thomson
RE: #541: CONTINUATION K.Morgan@iaea.org
RE: Large Frames, Continuations, Flow Control, and changing HPACK RUELLAN Herve
Re: Large Frames, Continuations, Flow Control, and changing HPACK Poul-Henning Kamp
Re: Large Frames, Continuations, Flow Control, and changing HPACK Johnny Graettinger
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: #541: CONTINUATION Martin Thomson
Re: Large Frames, Continuations, Flow Control, and changing HPACK Martin Thomson
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Shigeki Ohtsu
Re: #541: CONTINUATION Jeff Pinner
Re: #541: CONTINUATION Michael Sweet
Re: #541: CONTINUATION Jeff Pinner
RE: Large Frames, Continuations, Flow Control, and changing HPACK K.Morgan@iaea.org
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: Large Frames, Continuations, Flow Control, and changing HPACK Cory Benfield
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: #541: CONTINUATION Poul-Henning Kamp
Re: #541: CONTINUATION Poul-Henning Kamp
Re: Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: #541: CONTINUATION Tatsuhiro Tsujikawa
Re: #541: CONTINUATION Michael Sweet
Re: Large Frames, Continuations, Flow Control, and changing HPACK Tatsuhiro Tsujikawa
Re: Large Frames, Continuations, Flow Control, and changing HPACK Poul-Henning Kamp
Re: #541: CONTINUATION Poul-Henning Kamp
Re: Large Frames, Continuations, Flow Control, and changing HPACK Cory Benfield
Large Frames, Continuations, Flow Control, and changing HPACK Jeff Pinner
Re: #541: CONTINUATION Tatsuhiro Tsujikawa
Re: #541: CONTINUATION Poul-Henning Kamp
Re: #541: CONTINUATION Poul-Henning Kamp
Service Bindings DNS Records (draft-nygren-service-bindings-00) Erik Nygren
Re: #541: CONTINUATION Michael Sweet
Re: Large Frame Proposal Michael Sweet
Re: Large Frame Proposal Tatsuhiro Tsujikawa
Re: #541: CONTINUATION Tatsuhiro Tsujikawa
Re: Large Frame Proposal Michael Sweet
Re: #541: CONTINUATION Greg Wilkins
Re: Large Frame Proposal - WINDOW UPDATE Greg Wilkins
Re: Large Frame Proposal - WINDOW UPDATE Martin Thomson
Re: #541: CONTINUATION Martin Thomson
Re: Large Frame Proposal - WINDOW UPDATE Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Mark Nottingham
Re: #541: CONTINUATION Mark Nottingham
Re: Large Frame Proposal Mark Nottingham
Re: Large Frame Proposal Mark Nottingham
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Michael Sweet
Re: Large Frame Proposal Michael Sweet
Re: Large Frame Proposal Michael Sweet
Re: Large Frame Proposal Mark Nottingham
Re: #541: CONTINUATION Roberto Peon
Re: Large Frame Proposal Martin Thomson
Re: #541: CONTINUATION Jason Greene
Re: Large Frame Proposal Mike Belshe
Re: Large Frame Proposal Jason Greene
Re: Large Frame Proposal Greg Wilkins

Monday, 7 July 2014

Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal K.Morgan@iaea.org
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Martin Thomson
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Martin Thomson
Re: Large Frame Proposal Johnny Graettinger
Re: #541: CONTINUATION Roberto Peon
Re: #541: CONTINUATION K.Morgan@iaea.org
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Greg Wilkins
Re: #541: CONTINUATION Poul-Henning Kamp
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Willy Tarreau
Re: #541: CONTINUATION Johnny Graettinger
Re: Large Frame Proposal Jason Greene
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Willy Tarreau
Re: #541: CONTINUATION Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: #541: CONTINUATION Johnny Graettinger
Re: Large Frame Proposal Roberto Peon
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Roberto Peon
Re: #541: CONTINUATION Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Compressing HTTP headers Poul-Henning Kamp
Re: Large Frame Proposal Willy Tarreau
Re: Large Frame Proposal Willy Tarreau
Re: Large Frame Proposal Nicholas Hurley
Re: Large Frame Proposal Michael Sweet
Re: Large Frame Proposal Johnny Graettinger
Re: Large Frame Proposal Willy Tarreau
Re: Large Frame Proposal Nicholas Hurley
Re: draft-ietf-httpbis-http2-latest, 8.1 HTTP Request/Response Exchange Martin Thomson
Re: Large Frame Proposal Martin Thomson
Re: Compressing HTTP headers Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 8.1 HTTP Request/Response Exchange Martin Thomson
Re: draft-ietf-httpbis-http2-latest, 6.2 HEADERS again Martin Thomson
Re: #541: CONTINUATION Johnny Graettinger
Re: Large Frame Proposal Michael Sweet
Compressing HTTP headers Poul-Henning Kamp
Re: Large Frame Proposal Poul-Henning Kamp
Re: Large Frame Proposal Greg Wilkins
Re: #541: CONTINUATION - option #4 Poul-Henning Kamp
Re: Large Frame Proposal Mark Nottingham
Re: #541: CONTINUATION - option #4 Willy Tarreau

Saturday, 5 July 2014

draft-ietf-httpbis-http2-latest, 6.8 GOAWAY Kari Hurtta

Friday, 4 July 2014

Re: draft-ietf-httpbis-http2-latest, 6.2 HEADERS, 6.10 CONTINUATION, END_SEGMENT (0x2) Kari Hurtta

Sunday, 6 July 2014

draft-ietf-httpbis-http2-latest, 8.1 HTTP Request/Response Exchange Kari Hurtta
draft-ietf-httpbis-http2-latest, 6.2 HEADERS again Kari Hurtta

Monday, 7 July 2014

RE: #541: CONTINUATION - option #4 K.Morgan@iaea.org
RE: YAC Proposal K.Morgan@iaea.org
RE: CONTINUATION proposal w/ minimum change K.Morgan@iaea.org
Re: #541: CONTINUATION - option #4 Mark Nottingham
Re: #541: CONTINUATION - option #4 Willy Tarreau
Re: Large Frame Proposal Greg Wilkins
Re: Large Frame Proposal Mark Nottingham
Re: #541: CONTINUATION - option #4 Mark Nottingham
Large Frame Proposal Greg Wilkins

Sunday, 6 July 2014

Re: #541: CONTINUATION Adrian Cole
Re: #541: CONTINUATION Mark Nottingham

Saturday, 5 July 2014

Re: draft-ietf-httpbis-http2-latest, 6.8 GOAWAY Martin Thomson
Re: CRLF requirement Poul-Henning Kamp
Re: CRLF requirement Peter Gutmann
Re: #541: CONTINUATION K.Morgan@iaea.org
Re: #541: CONTINUATION Martin J. Dürst

Friday, 4 July 2014

Re: #541: CONTINUATION Jason Greene
Re: #541: CONTINUATION Mike Bishop
Re: draft-ietf-httpbis-http2-latest, 6.2 HEADERS, 6.10 CONTINUATION, END_SEGMENT (0x2) Martin Thomson
Re: ext#7 / ext#8: multiple alt-svc Kinkie
I-D Action: draft-ietf-httpbis-alt-svc-02.txt internet-drafts@ietf.org
Re: H2 HEADERS and flow control Poul-Henning Kamp
Re: H2 HEADERS and flow control David Krauss
Re: #541: CONTINUATION Poul-Henning Kamp
Re: H2 HEADERS and flow control Greg Wilkins
Re: H2 HEADERS and flow control David Krauss
Fwd: New Version Notification for draft-nottingham-http-proxy-problem-01.txt Mark Nottingham
Re: H2 HEADERS and flow control Greg Wilkins
Re: H2 HEADERS and flow control David Krauss
Re: #541: CONTINUATION David Krauss
Re: #541: CONTINUATION Mark Nottingham
Re: #541: CONTINUATION Michael Sweet
Re: #541: CONTINUATION Mark Nottingham
Re: #541: CONTINUATION Greg Wilkins
Re: H2 HEADERS and flow control Greg Wilkins

Thursday, 3 July 2014

Re: #541: CONTINUATION Martin Thomson
Re: #541: CONTINUATION Matthew Kerwin
Re: Reference set in HPACK Eric J. Bowman
Re: #541: CONTINUATION Mark Nottingham
Re: #541: CONTINUATION Martin Thomson
Re: #541: CONTINUATION Nicholas Hurley
RE: draft-ietf-httpbis-http2-latest, 6.2 HEADERS, 6.10 CONTINUATION, END_SEGMENT (0x2) K.Morgan@iaea.org
RE: #541: CONTINUATION K.Morgan@iaea.org
Re: #541: CONTINUATION Jason Greene
Re: #541: CONTINUATION Martin Thomson
Re: #541: CONTINUATION Martin Thomson
Re: #541: CONTINUATION Adrian Cole
Re: draft-ietf-httpbis-http2-latest, 6.2 HEADERS, 6.10 CONTINUATION, END_SEGMENT (0x2) Martin Thomson
Re: Size of window variables Willy Tarreau
Re: Size of window variables Poul-Henning Kamp
RE: Questions about SETTINGS and SETTINGS ACK Mike Bishop
Re: Size of window variables Willy Tarreau
Questions about SETTINGS and SETTINGS ACK Michael Sweet
Re: WINDOW_UPDATE(0) ? Martin Thomson
Re: ext#7 / ext#8: multiple alt-svc Martin Thomson
Re: #541: CONTINUATION Jason Greene
Re: Size of window variables Poul-Henning Kamp
Re: Size of window variables Daniel Sommermann
Size of window variables Poul-Henning Kamp
Re: H2 HEADERS and flow control 陈智昌
Re: H2 HEADERS and flow control 陈智昌
Re: H2 HEADERS and flow control Nicholas Hurley
Re: H2 HEADERS and flow control Martin Thomson
RE: Reference set in HPACK RUELLAN Herve
RE: Encouraging a healthy HTTP/2 ecosystem (and not arguing about CONTINUATION frames) Mike Bishop
Re: #541: CONTINUATION Michael Sweet
Re: #541: CONTINUATION Matthew Kerwin
Re: #541: CONTINUATION Michael Sweet
RE: YAC Proposal Amos Jeffries
Re: #541: CONTINUATION Amos Jeffries
advanced uses of TLS-renegotiation & draft-thomson specs henry.story@bblfish.net
H2 HEADERS and flow control Greg Wilkins
Re: #541: CONTINUATION Cory Benfield
Re: #541: CONTINUATION Walter H.
Re: WINDOW_UPDATE(0) ? Poul-Henning Kamp
Re: #541: CONTINUATION Poul-Henning Kamp
Re: WINDOW_UPDATE(0) ? Cory Benfield
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: #541: CONTINUATION Poul-Henning Kamp
WINDOW_UPDATE(0) ? Poul-Henning Kamp
Re: #541: CONTINUATION Greg Wilkins
Re: #541: CONTINUATION Yoav Nir
Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
Re: YAC Proposal Greg Wilkins
Re: #541: CONTINUATION Walter H.
Re: #541: CONTINUATION Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: #541: CONTINUATION Amos Jeffries
Re: ext#7 / ext#8: multiple alt-svc Kinkie
Re: ext#7 / ext#8: multiple alt-svc Matthew Kerwin
Re: Encouraging a healthy HTTP/2 ecosystem Yoav Nir
Re: YAC Proposal Poul-Henning Kamp
RE: YAC Proposal Mike Bishop
Re: ext#7 / ext#8: multiple alt-svc Kinkie
Re: ext#7 / ext#8: multiple alt-svc Kinkie
Re: YAC Proposal Willy Tarreau
Re: YAC Proposal Michael Sweet
RE: #529: Working around concurrency limits Amos Jeffries
Re: Reference set in HPACK Eric J. Bowman
Re: Reference set in HPACK Roberto Peon
RE: YAC Proposal Amos Jeffries
Re: YAC Proposal Amos Jeffries
Re: Reference set in HPACK Eric J. Bowman
RE: #529: Working around concurrency limits Mike Bishop
RE: #541: CONTINUATION Mike Bishop
RE: YAC Proposal Mike Bishop
Re: Reference set in HPACK Roberto Peon
Re: #541: CONTINUATION Mark Nottingham
Re: #541: CONTINUATION Mark Nottingham
Re: YAC Proposal Jason Greene
Re: #541: CONTINUATION Tatsuhiro Tsujikawa
Re: Reference set in HPACK Eric J. Bowman
Re: YAC Proposal Roberto Peon
Re: YAC Proposal Jason Greene
Re: YAC Proposal Roberto Peon
Re: YAC Proposal Jason Greene
Re: #529: Working around concurrency limits Roberto Peon
Re: ext#7 / ext#8: multiple alt-svc Mark Nottingham
Re: YAC Proposal Roberto Peon
Re: #529: Working around concurrency limits Mark Nottingham
Re: ext#7 / ext#8: multiple alt-svc Mark Nottingham

Wednesday, 2 July 2014

Changing the Internet was: Encouraging a healthy HTTP/2 ecosystem Roland Zink
Re: YAC Proposal Nicholas Hurley
Re: #541: CONTINUATION Adrian Cole
Re: YAC Proposal Adrian Cole
Re: #541: CONTINUATION Daniel Stenberg
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: YAC Proposal Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem (and not arguing about CONTINUATION frames) Poul-Henning Kamp
Re: YAC Proposal Jason Greene
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: HTTP/2 response completed before its request Martin Thomson
YAC Proposal K.Morgan@iaea.org
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: HTTP/2 response completed before its request Zhong Yu
Re: Encouraging a healthy HTTP/2 ecosystem (and not arguing about CONTINUATION frames) Cory Benfield
Re: #529: Working around concurrency limits 陈智昌
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: #541: CONTINUATION Jason Greene
Re: Reference set in HPACK Martin Thomson
Re: #541: CONTINUATION Nicholas Hurley
Re: trailers and pseudo-headers Martin Thomson
RE: HTTP/2 response completed before its request Mike Bishop
Re: HTTP/2 response completed before its request Jason Greene
Re: HTTP/2 response completed before its request 陈智昌
RE: #541: CONTINUATION Mike Bishop
Re: HTTP/2 response completed before its request Willy Tarreau
Re: ext#7 / ext#8: multiple alt-svc Martin Thomson
Re: #536: clarify extensibility for :pseudo header fields Martin Thomson
Re: #536: clarify extensibility for :pseudo header fields Martin Thomson
RE: HTTP/2 response completed before its request Mike Bishop
Re: HTTP/2 response completed before its request Patrick McManus
Re: HTTP/2 response completed before its request Jason Greene
RE: Encouraging a healthy HTTP/2 ecosystem Mike Bishop
Re: HTTP/2 response completed before its request Patrick McManus
Re: HTTP/2 response completed before its request Martin Thomson
Re: Reference set in HPACK Johnny Graettinger
Re: HTTP/2 response completed before its request Willy Tarreau
Re: HTTP/2 response completed before its request Patrick McManus
Re: HTTP/2 response completed before its request Mike Bishop
Re: #537: Remove segments (consensus call) Mike Bishop
HEADERS/CONTINUATION data point for CUPS and HTTP/2 (in case anyone is interested) Michael Sweet
Re: ext#9: OppSec and Proxies Patrick McManus
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: #541: CONTINUATION Jason Greene
Typos in draft-ietf-httpbis-header-compression-08 examples... Michael Sweet
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: #541: CONTINUATION Yoav Nir
Re: Reference set in HPACK Kaoru Maeda
Re: #541: CONTINUATION Cory Benfield
RE: trailers and pseudo-headers K.Morgan@iaea.org
Re: #541: CONTINUATION Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Peter Ghosh
Re: #541: CONTINUATION Poul-Henning Kamp
Re: trailers and pseudo-headers Julian Reschke
Re: trailers and pseudo-headers Willy Tarreau
HTTP/3, was: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Julian Reschke
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: trailers and pseudo-headers Julian Reschke
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
Re: #541: CONTINUATION Mark Nottingham
Re: #541: CONTINUATION Mark Nottingham
RE: #541: CONTINUATION K.Morgan@iaea.org
Re: #541: CONTINUATION Shigeki Ohtsu
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Mike Belshe
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: #541: CONTINUATION Greg Wilkins
Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: trailers and pseudo-headers Michael Sweet
#541: CONTINUATION Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: Reference set in HPACK Michael Sweet
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Blackmail??? Was: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: Blackmail??? Was: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: trailers and pseudo-headers Julian Reschke
Re: trailers and pseudo-headers Alvaro Lopez Ortega
Blackmail??? Was: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
Re: trailers and pseudo-headers Mark Nottingham
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
Re: trailers and pseudo-headers Eric J. Bowman
Re: Encouraging a healthy HTTP/2 ecosystem Eric J. Bowman
RE: ext#9: OppSec and Proxies Richard Wheeldon (rwheeldo)
Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
Re: #529: Working around concurrency limits Amos Jeffries
RE: #529: Working around concurrency limits Richard Wheeldon (rwheeldo)
RE: Reference set in HPACK K.Morgan@iaea.org
Re: #535: No 1xx Status Codes Greg Wilkins
Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
Re: agenda/charter brainstorming Mark Nottingham
Re: CRLF requirement Martin Nilsson
Re: agenda/charter brainstorming Julian Reschke
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: trailers and pseudo-headers Julian Reschke
Re: Reference set in HPACK Poul-Henning Kamp
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: Reference set in HPACK Poul-Henning Kamp
RE: Reference set in HPACK K.Morgan@iaea.org
RE: Reference set in HPACK K.Morgan@iaea.org
Re: Reference set in HPACK Roberto Peon
RE: Reference set in HPACK K.Morgan@iaea.org
Re: #537: Remove segments (consensus call) Greg Wilkins
Re: Reference set in HPACK Roberto Peon
Re: trailers and pseudo-headers Julian Reschke
Re: Reference set in HPACK Roberto Peon
Re: Reference set in HPACK Greg Wilkins
Re: trailers and pseudo-headers Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Reference set in HPACK Poul-Henning Kamp
Re: HTTP/2 response completed before its request Greg Wilkins
Re: HTTP/2 response completed before its request Greg Wilkins
Re: HTTP/2 response completed before its request Willy Tarreau
Re: trailers and pseudo-headers Julian Reschke
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: ext#7 / ext#8: multiple alt-svc Matthew Kerwin
Re: #537: Remove segments (consensus call) Roberto Peon
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Eric J. Bowman
Re: trailers and pseudo-headers Mark Nottingham
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
Re: #537: Remove segments (consensus call) Roberto Peon
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Roberto Peon
Re: #535: No 1xx Status Codes Julian Reschke
Re: Reference set in HPACK Roberto Peon
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Eric J. Bowman
Re: Reference set in HPACK Roberto Peon
Re: #537: Remove segments (consensus call) Poul-Henning Kamp
Re: Reference set in HPACK Poul-Henning Kamp
trailers and pseudo-headers Julian Reschke
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: #535: No 1xx Status Codes Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields Poul-Henning Kamp
Re: Reference set in HPACK 山本和彦
ext#9: OppSec and Proxies Mark Nottingham
Re: #535: No 1xx Status Codes Julian Reschke
ext#7 / ext#8: multiple alt-svc Mark Nottingham
Re: #537: Remove segments (consensus call) David Krauss
Re: #537: Remove segments (consensus call) Roberto Peon
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: Reference set in HPACK Roberto Peon
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: HTTP/2 response completed before its request Roberto Peon
Re: #535: No 1xx Status Codes Mark Nottingham
Re: #535: No 1xx Status Codes Julian Reschke
Re: Reference set in HPACK 山本和彦
Re: #537: Remove segments (consensus call) David Krauss
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Poul-Henning Kamp
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: Reference set in HPACK 山本和彦
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: Reference set in HPACK Mark Nottingham
Re: HTTP/2 response completed before its request Jesse Wilson
Re: Reference set in HPACK Roberto Peon
Re: #535: No 1xx Status Codes Mark Nottingham
Reference set in HPACK 山本和彦
Re: #537: Remove segments (consensus call) Yutaka Hirano
#529: Working around concurrency limits Mark Nottingham
#537: Remove segments (consensus call) Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: HTTP/2 response completed before its request Roberto Peon
Re: HTTP/2 response completed before its request Roberto Peon
Re: HTTP/2 response completed before its request Jesse Wilson
Re: Encouraging a healthy HTTP/2 ecosystem James M Snell
Re: HTTP/2 response completed before its request Roberto Peon
Re: HTTP/2 response completed before its request Zhong Yu
Re: #536: clarify extensibility for :pseudo header fields Roberto Peon
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: CRLF requirement David Krauss
Re: CRLF requirement Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: CRLF requirement Glen Knowles
Re: #536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Adrian Cole
Re: CRLF requirement David Krauss
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Roberto Peon
Re: CRLF requirement Martin Nilsson

Tuesday, 1 July 2014

Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Poul-Henning Kamp
Re: CRLF requirement Carsten Bormann
Re: HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Roberto Peon
Re: CRLF requirement Martin Nilsson
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
HTTP/2 DoS Vulnerability (Was: HTTP/2 response completed before its request) Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: HTTP/2 response completed before its request Roberto Peon
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Encouraging a healthy HTTP/2 ecosystem (and not arguing about CONTINUATION frames) 陈智昌
Re: HTTP/2 response completed before its request Roberto Peon
Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: Encouraging a healthy HTTP/2 ecosystem Jeff Pinner
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Participating to the WG (Was: Re: Encouraging a healthy HTTP/2 ecosystem) Willy Tarreau
Re: HTTP/2 response completed before its request Martin Thomson
Re: why not multiple, short-lived HTTP/2 connections? bizzbyster@gmail.com
Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
Re: Encouraging a healthy HTTP/2 ecosystem James Adjamli
Re: HTTP/2 response completed before its request Roberto Peon
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Johnny Graettinger
Re: Encouraging a healthy HTTP/2 ecosystem Jason Greene
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
Re: HTTP/2 response completed before its request Jeff Pinner
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Jeff Pinner
Re: HTTP/2 response completed before its request Johnny Graettinger
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
Re: HTTP/2 response completed before its request 陈智昌
Re: Another CONTINUATION Proposal Jeff Pinner
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Re: CONTINUATION proposal w/ minimum change Poul-Henning Kamp
Re: Another CONTINUATION Proposal Jason Greene
Re: HTTP/2 response completed before its request 陈智昌
Re: HTTP/2 response completed before its request Johnny Graettinger
Re: HTTP/2 response completed before its request Willy Tarreau
Re: CONTINUATION proposal w/ minimum change Jason Greene
Re: HTTP/2 response completed before its request Michael Sweet
Re: HTTP/2 response completed before its request Poul-Henning Kamp
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Re: HTTP/2 response completed before its request Zhong Yu
Re: HTTP/2 response completed before its request Jeff Pinner
Re: HTTP/2 response completed before its request 陈智昌
Re: HTTP/2 response completed before its request Jesse Wilson
Re: HTTP/2 response completed before its request Martin Thomson
Re: HTTP/2 response completed before its request Patrick McManus
Re: HTTP/2 response completed before its request Martin Thomson
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: HTTP/2 response completed before its request 陈智昌
Re: HTTP/2 response completed before its request Mike Bishop
Re: HTTP/2 response completed before its request Jeff Pinner
Re: HTTP/2 response completed before its request Martin Thomson
Re: END_SEGMENT? (#397) Martin Thomson
Re: I-D Action: draft-hutton-httpbis-connect-protocol-00.txt Martin Thomson
Re: #539: Priority from server to client Johnny Graettinger
Re: HTTP/2 response completed before its request 陈智昌
Re: #536: clarify extensibility for :pseudo header fields Martin Thomson
Re: HTTP/2 response completed before its request Jesse Wilson
Re: CONTINUATION proposal w/ minimum change Tatsuhiro Tsujikawa
Re: HTTP/2 response completed before its request 陈智昌
Re: HTTP/2 response completed before its request Roberto Peon
RE: #539: Priority from server to client RUELLAN Herve
Re: HTTP/2 response completed before its request Willy Tarreau
HTTP/2 response completed before its request Jesse Wilson
Re: #539: Priority from server to client Johnny Graettinger
Re: CRLF requirement Julian Reschke
Re: CONTINUATION proposal w/ minimum change Jason Greene
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Julian Reschke
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Carsten Bormann
Another CONTINUATION Proposal Jeff Pinner
Re: CONTINUATION proposal w/ minimum change Tatsuhiro Tsujikawa
Re: Encouraging a healthy HTTP/2 ecosystem Jason Greene
Re: CRLF requirement Anne van Kesteren
Re: CRLF requirement Zhong Yu
Re: CRLF requirement Willy Tarreau
Re: CONTINUATION proposal w/ minimum change Jason Greene
Re: CRLF requirement Zhong Yu
RE: draft-hutton-httpbis-connect-protocol-00.txt Hutton, Andrew
RE: hpack table size 0 Mike Bishop
RE: #539: Priority from server to client Mike Bishop
Re: CONTINUATION proposal w/ minimum change Poul-Henning Kamp
Re: [Technical Errata Reported] RFC7231 (4031) Anne van Kesteren
Re: [Technical Errata Reported] RFC7231 (4031) Barry Leiba
Re: END_SEGMENT? (#397) Yutaka Hirano
Re: CONTINUATION proposal w/ minimum change Tatsuhiro Tsujikawa
RE: CONTINUATION proposal w/ minimum change RUELLAN Herve
Re: Encouraging a healthy HTTP/2 ecosystem Patrick McManus
RE: CONTINUATION proposal w/ minimum change K.Morgan@iaea.org
RE: I-D Action: draft-hutton-httpbis-connect-protocol-00.txt Rauschenbach, Uwe (NSN - DE/Munich)
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem Cory Benfield
Re: #536: clarify extensibility for :pseudo header fields Martin Nilsson
Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
Re: hpack table size 0 Mark Nottingham
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: [Technical Errata Reported] RFC7231 (4031) Julian Reschke
#539: Priority from server to client Mark Nottingham
Re: [Technical Errata Reported] RFC7231 (4031) Anne van Kesteren
Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
Re: #536: clarify extensibility for :pseudo header fields Julian Reschke
Re: [Technical Errata Reported] RFC7231 (4031) Julian Reschke
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: Encouraging a healthy HTTP/2 ecosystem 陈智昌
Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
Re: [Technical Errata Reported] RFC7231 (4031) Anne van Kesteren
Re: CONTINUATION proposal w/ minimum change Matthew Kerwin
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Re: #536: clarify extensibility for :pseudo header fields Matthew Kerwin
Re: why not multiple, short-lived HTTP/2 connections? 陈智昌
Re: #536: clarify extensibility for :pseudo header fields David Krauss
Re: CONTINUATION proposal w/ minimum change Mark Nottingham
Re: CONTINUATION proposal w/ minimum change Jason Greene
Encouraging a healthy HTTP/2 ecosystem 陈智昌
#536: clarify extensibility for :pseudo header fields Mark Nottingham
Re: [Technical Errata Reported] RFC7231 (4031) Mark Nottingham

Last message date: Tuesday, 30 September 2014 23:54:29 UTC