ietf-http-wg@w3.org from October to December 2014 by date

Wednesday, 31 December 2014

• Re: comments about draft-ietf-httpbis-header-compression Mark Nottingham
• comments about draft-ietf-httpbis-header-compression Jyrki Alakuijala
• Re: Reviving discussion on error code 451 Mark Nottingham
• Re: Reviving discussion on error code 451 David Morris
• Last Call: <draft-ietf-httpbis-http2-16.txt> (Hypertext Transfer Protocol version 2) to Proposed Standard The IESG
• Last Call: <draft-ietf-httpbis-header-compression-10.txt> (HPACK - Header Compression for HTTP/2) to Proposed Standard The IESG
• Re: Reviving discussion on error code 451 James M Snell
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Greg Wilkins

Tuesday, 30 December 2014

• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke
• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke
• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke
• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke
• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke
• Re: Adrian Farrel's Discuss on status-change-http-status-code-308-ps-01: (with DISCUSS) Julian Reschke

Monday, 29 December 2014

• Barry Leiba's Yes on status-change-http-status-code-308-ps-01: (with COMMENT) Barry Leiba

Saturday, 27 December 2014

• Re: Use of TLS Features in HTTP2 Walter H.

Friday, 26 December 2014

• Fwd: IETF areas re-organisation steps Mark Nottingham
• Re: Use of TLS Features in HTTP2 FERNANDO PASCUAL BLANCO

Thursday, 25 December 2014

• [Errata Verified] RFC7230 (4205) RFC Errata System

Wednesday, 24 December 2014

• Re: [Editorial Errata Reported] RFC7230 (4205) Barry Leiba
• Re: [Editorial Errata Reported] RFC7230 (4205) Roy T. Fielding
• Use of TLS Features in HTTP2 WeiXinpeng

Tuesday, 23 December 2014

• Re: [Editorial Errata Reported] RFC7230 (4205) Barry Leiba
• Re: [Editorial Errata Reported] RFC7230 (4205) Barry Leiba
• [Editorial Errata Reported] RFC7230 (4205) RFC Errata System

Monday, 22 December 2014

• Re: FYI: HTTP/2 temporarily disabled for Google websites Bence Béky

Friday, 19 December 2014

• Re: Reviving discussion on error code 451 nicolas.mailhot@laposte.net
• Re: Reviving discussion on error code 451 Michael Sweet
• Re: Reviving discussion on error code 451 Tim Bray

Thursday, 18 December 2014

• Re: HTTP/2 status, IPR Mark Nottingham
• Re: draft-murchison-webdav-prefer Ken Murchison
• Re: draft-murchison-webdav-prefer Ken Murchison
• Re: draft-murchison-webdav-prefer Julian Reschke
• Re: draft-murchison-webdav-prefer James M Snell
• draft-murchison-webdav-prefer Ken Murchison
• FYI: HTTP/2 temporarily disabled for Google websites Biren Roy
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Stefan Eissing
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Stefan Eissing
• Re: Reviving discussion on error code 451 Amos Jeffries
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Stefan Eissing
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Yoav Nir
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Julian Reschke
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Martin J. Dürst
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Virgil Griffith

Wednesday, 17 December 2014

• Re: Reviving discussion on error code 451 Eliot Lear
• Re: Reviving discussion on error code 451 Mark Nottingham
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Stefan Eissing
• Re: Reviving discussion on error code 451 Amos Jeffries
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Virgil Griffith
• Re: Reviving discussion on error code 451 Virgil Griffith
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-05.txt Virgil Griffith
• Re: Reviving discussion on error code 451 Julian Reschke
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-05.txt Roy T. Fielding
• Re: Reviving discussion on error code 451 Matthew Kerwin
• Re: Reviving discussion on error code 451 Cory Benfield
• Re: Reviving discussion on error code 451 Stephane Bortzmeyer
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Stephane Bortzmeyer
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Yoav Nir
• Re: support for draft-thomson-httpbis-cant Julian Reschke
• Re: Reviving discussion on error code 451 Yoav Nir
• Re: Reviving discussion on error code 451 Willy Tarreau
• Re: Reviving discussion on error code 451 Tim Bray
• Re: Reviving discussion on error code 451 Yoav Nir
• FYI: Publication requested Mark Nottingham
• Re: Reviving discussion on error code 451 Mark Nottingham
• Re: Reviving discussion on error code 451 Yoav Nir
• Re: Reviving discussion on error code 451 Tim Bray
• Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-05.txt Tim Bray
• Re: Reviving discussion on error code 451 Mark Nottingham

Tuesday, 16 December 2014

• support for draft-thomson-httpbis-cant Kent Watsen
• Re: draft-thomson-httpbis-catch-00 Martin Thomson
• Re: -encryption draft -01 Julian Reschke
• Re: -encryption draft -01 Roy T. Fielding
• Re: -encryption draft -01 Julian Reschke
• Re: -encryption draft -01 Roy T. Fielding
• Re: -encryption draft -01 Daniel Stenberg
• Re: -encryption draft -01 Martin Thomson
• Re: -encryption draft -01 Julian Reschke
• Re: -encryption draft -01 Martin Thomson
• Reviving discussion on error code 451 Niels ten Oever
• Re: -encryption draft -01 Julian Reschke
• -encryption draft -01 Martin Thomson
• I-D Action: draft-ietf-httpbis-http2-encryption-01.txt internet-drafts@ietf.org

Monday, 15 December 2014

• Re: HTTP/2 status, IPR Mark Nottingham
• HTTP/2 status, IPR Mark Nottingham
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Bence Béky
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Biren Roy

Saturday, 13 December 2014

• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Salvatore Loreto
• RE: I-D Action: draft-ietf-httpbis-http2-16.txt DRUTA, DAN

Friday, 12 December 2014

• Re: Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) Frédéric Kayser

Thursday, 11 December 2014

• Re: Gen-Art LC review: status-change-http-status-code-308-ps-01 Julian Reschke
• Re: ALPN ID for HTTP/2 interop Bence Béky
• Gen-Art LC review: status-change-http-status-code-308-ps-01 Robert Sparks
• RE: I-D Action: draft-ietf-httpbis-http2-16.txt Gabriel Montenegro
• Re: Last Calls Julian Reschke
• Re: Last Calls Mark Nottingham

Wednesday, 10 December 2014

• Re: HTTP/2 has mandatory security with optional compliance; violates RFC 2119 Martin Thomson
• Last Calls Julian Reschke
• Re: PUSH_PROMISE and load balancers Stuart Douglas
• Re: Pushing 304's Greg Wilkins

Tuesday, 9 December 2014

• Re: wordsmithing priority Patrick McManus
• Re: wordsmithing priority Martin Thomson
• wordsmithing priority Patrick McManus
• New PR Martin Thomson

Friday, 5 December 2014

• Re: PSA: Chromium ramping up h2-14 support. Bence Béky
• unbearable - new mailing list to discuss better than bearer tokens... Stephen Farrell
• RE: Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) RUELLAN Herve

Thursday, 4 December 2014

• Re: PRIORITY flag on HEADERS Frame? Mark Nottingham
• Re: HTTP/2 and Websockets Roberto Peon
• Re: HTTP/2 and Websockets Glen Knowles
• Re: HTTP/2 and Websockets Roberto Peon

Wednesday, 3 December 2014

• Re: PRIORITY flag on HEADERS Frame? Kulkarni, Saurabh
• Re: PRIORITY flag on HEADERS Frame? Ryan Hamilton
• Re: PRIORITY flag on HEADERS Frame? Patrick McManus
• Re: HTTP/2 and Websockets Brad Fitzpatrick
• Re: HTTP/2 and Websockets Roberto Peon
• Re: PRIORITY flag on HEADERS Frame? Brad Fitzpatrick
• Re: PRIORITY flag on HEADERS Frame? Greg Wilkins
• Re: HTTP/2 and Websockets Martin Thomson
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: Origin cookies, and First-party cookies. Yoav Nir
• Re: Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) Roberto Peon
• Re: Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) Frédéric Kayser

Tuesday, 2 December 2014

• Re: Frames and State Machine Martin Thomson
• Frames and State Machine Mike Bishop
• Fwd: [http-auth] Working Group Last Call for draft-ietf-httpauth-basicauth-update-03.txt Julian Reschke
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Willy Tarreau
• Re: PRIORITY flag on HEADERS Frame? Martin Thomson
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Martin Thomson
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Willy Tarreau
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Willy Tarreau
• Re: PRIORITY flag on HEADERS Frame? Jeff Pinner
• Re: PRIORITY flag on HEADERS Frame? Mark Nottingham
• Re: PRIORITY flag on HEADERS Frame? Jeff Pinner
• Re: Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) Roberto Peon
• Speed concern related to bit order in Huffman (was: I-D Action: draft-ietf-httpbis-header-compression-10.txt) Frédéric Kayser
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Mark Nottingham
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Martin Thomson
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Mark Nottingham
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Martin Thomson
• Re: PRIORITY flag on HEADERS Frame? Martin Thomson
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Mark Nottingham
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Martin Thomson
• PRIORITY flag on HEADERS Frame? Jeff Pinner
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Mark Nottingham

Monday, 1 December 2014

• Do any implementations issue AltSvc frames? Adrian Cole
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Willy Tarreau
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Brad Fitzpatrick
• Re: I-D Action: draft-ietf-httpbis-http2-16.txt Mark Nottingham
• Fwd: Last Call: <status-change-http-status-code-308-ps-01.txt> (HTTP Status Code 308 (Permanent Redirect) to Proposed Standard (from Experimental)) Barry Leiba
• Fwd: Last Call: <status-change-http-status-code-308-ps-01.txt> (HTTP Status Code 308 (Permanent Redirect) to Proposed Standard (from Experimental)) Julian Reschke
• Fwd: Last Call: <status-change-http-status-code-308-ps-01.txt> (HTTP Status Code 308 (Permanent Redirect) to Proposed Standard (from Experimental)) Julian Reschke
• I-D Action: draft-ietf-httpbis-header-compression-10.txt internet-drafts@ietf.org
• Re: I-D Action: draft-ietf-httpbis-alt-svc-05.txt Julian Reschke
• I-D Action: draft-ietf-httpbis-alt-svc-05.txt internet-drafts@ietf.org
• Re: Pushing 304's Martin Thomson

Sunday, 30 November 2014

• Re: Pushing 304's Greg Wilkins
• Re: Pushing 304's Martin Thomson
• I-D Action: draft-ietf-httpbis-http2-16.txt internet-drafts@ietf.org

Saturday, 29 November 2014

• Re: What error code when concurrent stream limit is exceeded Mark Nottingham
• Re: HTTP/2 and Websockets Roberto Peon
• Re: HTTP/2 and Websockets Amos Jeffries

Friday, 28 November 2014

• Re: Pushing 304's Greg Wilkins
• Re: Pushing 304's Julian Reschke
• Re: [Technical Errata Reported] RFC7230 (4189) Zhong Yu

Thursday, 27 November 2014

• Pushing 304's Greg Wilkins
• Re: Improving the state machine Greg Wilkins
• Re: Improving the state machine Jonathan Thackray
• Re: Improving the state machine Matthew Kerwin
• RE: Improving the state machine RUELLAN Herve
• Re: [Technical Errata Reported] RFC7230 (4189) Julian Reschke
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Andy Green

Wednesday, 26 November 2014

• Re: HTTP/2 and Websockets Greg Wilkins
• Re: Improving the state machine Matthew Kerwin
• Re: Improving the state machine Greg Wilkins
• Improving the state machine Martin Thomson
• [Technical Errata Reported] RFC7230 (4189) RFC Errata System
• Re: What error code when concurrent stream limit is exceeded Brad Fitzpatrick
• RE: What error code when concurrent stream limit is exceeded Mike Bishop
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: What error code when concurrent stream limit is exceeded Mark Nottingham
• Re: HTTP/2 and Websockets Willy Tarreau
• Re: HTTP/2 and Websockets Martin Thomson
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Andy Green

Tuesday, 25 November 2014

• Re: HTTP/2 and Websockets Jason Greene
• Re: HTTP/2 and Websockets Jason Greene
• Re: HTTP/2 and Websockets Willy Tarreau
• Re: HTTP/2 and Websockets Roberto Peon
• Re: HTTP/2 and Websockets Martin Thomson
• Re: HTTP/2 and Websockets Jason Greene
• Re: #645: Privacy impact of connection coalescing Martin Thomson
• Re: HTTP/2 and Websockets Martin Thomson
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: #645: Privacy impact of connection coalescing Mark Nottingham
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Robert Collins
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Jason Greene

Monday, 24 November 2014

• Re: What error code when concurrent stream limit is exceeded Matthew Kerwin
• Re: HTTP/2 and Websockets Andy Green
• Re: Origin cookies, and First-party cookies. Mark Nottingham
• Re: #612: Adopting pull #644 Mark Nottingham
• RE: What error code when concurrent stream limit is exceeded Mike Bishop
• Re: Origin cookies, and First-party cookies. Yoav Nir
• Re: What error code when concurrent stream limit is exceeded Matthew Kerwin
• Re: What is the rough plan from here? Martin Thomson
• Re: What error code when concurrent stream limit is exceeded Martin Thomson
• Re: What error code when concurrent stream limit is exceeded Willy Tarreau
• Re: What error code when concurrent stream limit is exceeded Brad Fitzpatrick
• Re: What is the rough plan from here? Julian Reschke
• Re: What error code when concurrent stream limit is exceeded Michael Sweet
• Re: What error code when concurrent stream limit is exceeded Willy Tarreau
• Re: What error code when concurrent stream limit is exceeded Brad Fitzpatrick
• Re: What error code when concurrent stream limit is exceeded Willy Tarreau
• Re: What error code when concurrent stream limit is exceeded Roberto Peon
• Re: What error code when concurrent stream limit is exceeded Brad Fitzpatrick
• Re: What error code when concurrent stream limit is exceeded Roberto Peon

Sunday, 23 November 2014

• Re: What error code when concurrent stream limit is exceeded Matthew Kerwin
• What error code when concurrent stream limit is exceeded Martin Thomson

Saturday, 22 November 2014

• Re: Origin cookies, and First-party cookies. Mike West
• Re: encoding and other h2 extensions Poul-Henning Kamp
• RE: #612: Adopting pull #644 Mike Bishop
• Re: encoding and other h2 extensions Martin Thomson
• Re: #612: Adopting pull #644 Martin Thomson
• Re: Origin cookies, and First-party cookies. Martin Thomson

Friday, 21 November 2014

• Re: encoding and other h2 extensions Matthew Kerwin
• Re: #612: Adopting pull #644 Mike Sweet
• Re: Origin cookies, and First-party cookies. Yoav Nir
• Re: #612: Adopting pull #644 Patrick McManus
• Re: encoding and other h2 extensions Poul-Henning Kamp
• Re: HTTP/2 and Websockets Jason Greene
• Origin cookies, and First-party cookies. Mike West
• Re: HTTP/2 and Websockets Jason Greene
• Re: HTTP/2 and Websockets Andy Green
• Re: #645: Privacy impact of connection coalescing Patrick McManus
• Re: encoding and other h2 extensions Amos Jeffries
• Re: HTTP/2 and Websockets Jason Greene
• Re: #645: Privacy impact of connection coalescing Amos Jeffries
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: #645: Privacy impact of connection coalescing Patrick McManus
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Robert Collins
• Re: HTTP/2 and Websockets Robert Collins
• Re: HTTP/2 and Websockets Andy Green
• encoding and other h2 extensions Matthew Kerwin
• Re: #645: Privacy impact of connection coalescing Martin Thomson
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: #612: Adopting pull #644 Jason Greene
• Re: #612: Adopting pull #644 Jason Greene
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: #612: Adopting pull #644 Martin Thomson
• Re: #612: Adopting pull #644 Martin Thomson
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Andy Green
• Re: #645: Privacy impact of connection coalescing Mark Nottingham
• Re: #645: Privacy impact of connection coalescing Greg Wilkins
• Re: HTTP/2 and Websockets Andy Green
• Re: #612: Adopting pull #644 Yoav Nir
• Re: #645: Privacy impact of connection coalescing Mark Nottingham
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Andy Green
• Re: #645: Privacy impact of connection coalescing Greg Wilkins
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• #645: Privacy impact of connection coalescing Mark Nottingham
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: #612: Adopting pull #644 Greg Wilkins
• Re: HTTP/2 and Websockets Andy Green
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: HTTP/2 and Websockets Andy Green
• Re: #612: Adopting pull #644 Mark Nottingham
• Re: What is the rough plan from here? Mark Nottingham

Thursday, 20 November 2014

• What is the rough plan from here? Greg Wilkins
• Re: HTTP/2 and Websockets Robert Collins
• Re: IAB Statement on Internet Confidentiality Mark Nottingham
• Re: IAB Statement on Internet Confidentiality Amos Jeffries
• Re: IAB Statement on Internet Confidentiality Greg Wilkins
• Re: IAB Statement on Internet Confidentiality Willy Tarreau
• Re: IAB Statement on Internet Confidentiality Tim Bray
• Re: IAB Statement on Internet Confidentiality Greg Wilkins
• Go's HTTP/2 interop test server Brad Fitzpatrick

Wednesday, 19 November 2014

• Re: ALPN ID for HTTP/2 interop Greg Wilkins
• Re: #612: Adopting pull #644 Greg Wilkins

Tuesday, 18 November 2014

• Re: #612: Adopting pull #644 Yoav Nir
• Re: #612: Adopting pull #644 Jason Greene
• Re: #612: Adopting pull #644 Jason Greene
• Re: IAB Statement on Internet Confidentiality Eliot Lear
• Re: IAB Statement on Internet Confidentiality Jason Greene
• Re: Fwd: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: Fwd: IAB Statement on Internet Confidentiality Mike Belshe
• Re: IAB Statement on Internet Confidentiality Willy Tarreau
• Re: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: IAB Statement on Internet Confidentiality FOSSATI, Thomas (Thomas)
• Re: #612: Adopting pull #644 Michael Sweet
• Re: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: IAB Statement on Internet Confidentiality Stefan Eissing
• Re: #612: Adopting pull #644 Yoav Nir
• Re: #612: Adopting pull #644 Poul-Henning Kamp
• Re: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• RE: #612: Adopting pull #644 Mike Bishop
• Re: IAB Statement on Internet Confidentiality Martin Thomson
• #612: Adopting pull #644 Mark Nottingham

Monday, 17 November 2014

• Re: Fwd: IAB Statement on Internet Confidentiality Willy Tarreau
• Re: Fwd: IAB Statement on Internet Confidentiality Willy Tarreau
• Re: Fwd: IAB Statement on Internet Confidentiality Phillip Hallam-Baker
• Re: Fwd: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: IAB Statement on Internet Confidentiality Jason Greene
• Re: Fwd: IAB Statement on Internet Confidentiality Mike Belshe
• Re: Fwd: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: Fwd: IAB Statement on Internet Confidentiality Willy Tarreau
• Re: Fwd: IAB Statement on Internet Confidentiality Phillip Hallam-Baker
• Re: Fwd: IAB Statement on Internet Confidentiality Roland Zink
• Re: Fwd: IAB Statement on Internet Confidentiality Phillip Hallam-Baker
• Re: Fwd: IAB Statement on Internet Confidentiality Poul-Henning Kamp
• Re: Fwd: IAB Statement on Internet Confidentiality Roland Zink
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Mark Nottingham
• Re: Rough minutes from HNL Mark Nottingham
• Rough minutes from HNL Mark Nottingham

Sunday, 16 November 2014

• Re: IAB Statement on Internet Confidentiality Mike Belshe
• Re: IAB Statement on Internet Confidentiality Mark Nottingham

Saturday, 15 November 2014

• Re: Unified User-Agent String (draft-karcz-uuas) Walter H.
• Re: Unified User-Agent String (draft-karcz-uuas) Amos Jeffries
• Re: Unified User-Agent String (draft-karcz-uuas) Martin Nilsson

Friday, 14 November 2014

• Re: Unified User-Agent String (draft-karcz-uuas) Daniel Stenberg
• Re: Unified User-Agent String (draft-karcz-uuas) Walter H.
• Unified User-Agent String (draft-karcz-uuas) Mateusz Karcz
• Re: IAB Statement on Internet Confidentiality Jim Manico
• Re: ALPN ID for HTTP/2 interop Tatsuhiro Tsujikawa
• Re: IAB Statement on Internet Confidentiality Matthew Kerwin
• Fwd: IAB Statement on Internet Confidentiality Mark Nottingham
• [Errata Rejected] RFC7231 (4180) RFC Errata System
• Re: [Technical Errata Reported] RFC7231 (4180) Barry Leiba
• [Technical Errata Reported] RFC7231 (4180) RFC Errata System
• Re: #612: 9.2.2 and ALPN Martin Thomson
• RE: #612: 9.2.2 and ALPN Mike Bishop
• Re: ALPN ID for HTTP/2 interop Mark Nottingham
• Re: #612: 9.2.2 and ALPN Yoav Nir
• Re: #612: 9.2.2 and ALPN Martin Thomson
• Re: #612: 9.2.2 and ALPN Eric J. Bowman
• Re: #612: 9.2.2 and ALPN Yoav Nir
• Re: #612: 9.2.2 and ALPN Eric J. Bowman
• Re: #612: 9.2.2 and ALPN Eric J. Bowman
• Re: ALPN ID for HTTP/2 interop Ryan Hamilton
• Re: #612: 9.2.2 and ALPN Martin Thomson

Thursday, 13 November 2014

• Re: #612: 9.2.2 and ALPN Greg Wilkins
• Re: #612: 9.2.2 and ALPN Eric Rescorla
• Re: #612: 9.2.2 and ALPN Jason Greene
• Re: #612: 9.2.2 and ALPN Eric Rescorla
• RE: #612: 9.2.2 and ALPN Albert Lunde
• Re: ALPN ID for HTTP/2 interop Moto Ishizawa
• RE: ALPN ID for HTTP/2 interop Lucas Pardue
• Re: ALPN ID for HTTP/2 interop Amos Jeffries
• ALPN ID for HTTP/2 interop Tatsuhiro Tsujikawa
• Re: #612: 9.2.2 and ALPN Poul-Henning Kamp
• Re: #612: 9.2.2 and ALPN Roy T. Fielding
• Re: #612: 9.2.2 and ALPN Yoav Nir
• Re: #612: 9.2.2 and ALPN Roy T. Fielding
• Re: #612: 9.2.2 and ALPN Yoav Nir
• Re: #612: 9.2.2 and ALPN Jason Greene
• Re: #612: 9.2.2 and ALPN Jason Greene
• Re: #612: 9.2.2 and ALPN Jason Greene
• Re: #612: 9.2.2 and ALPN Jason Greene
• Re: #612: 9.2.2 and ALPN Eric Rescorla
• Re: #612: 9.2.2 and ALPN Roy T. Fielding
• Re: #612: 9.2.2 and ALPN Eric Rescorla
• Re: #612: 9.2.2 and ALPN Roy T. Fielding

Wednesday, 12 November 2014

• Re: #612: 9.2.2 and ALPN Eric Rescorla
• Re: #612: 9.2.2 and ALPN Greg Wilkins
• Re: #612: 9.2.2 and ALPN Simpson, Robby (GE Energy Management)
• RE: #612: 9.2.2 and ALPN Mike Bishop
• RE: #612: 9.2.2 and ALPN Mike Bishop
• Re: #612: 9.2.2 and ALPN Ryan Hamilton
• RE: #612: 9.2.2 and ALPN Albert Lunde
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Tatsuhiro Tsujikawa
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Shigeki Ohtsu
• Re: #612: 9.2.2 and ALPN Greg Wilkins
• Re: #612: 9.2.2 and ALPN Brian Smith
• Re: #612: 9.2.2 and ALPN Yoav Nir
• #612: 9.2.2 and ALPN Mark Nottingham
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Mark Nottingham
• FW: subscribe sungkuen.lee@sk.com Lee Sungkuen

Tuesday, 11 November 2014

• Re: [Technical Errata Reported] RFC7230 (4169) Roy T. Fielding
• Re: [Technical Errata Reported] RFC7230 (4169) Barry Leiba
• Re: [Technical Errata Reported] RFC7230 (4169) Martin Thomson

Monday, 10 November 2014

• [Errata Verified] RFC7230 (4169) RFC Errata System
• Re: [Technical Errata Reported] RFC7230 (4169) Barry Leiba
• Re: [Technical Errata Reported] RFC7230 (4169) Roy T. Fielding
• Re: [Technical Errata Reported] RFC7230 (4169) Barry Leiba
• Re: [Technical Errata Reported] RFC7230 (4169) Amos Jeffries
• Re: [Technical Errata Reported] RFC7230 (4169) Julian Reschke
• Re: [Technical Errata Reported] RFC7230 (4169) Barry Leiba
• [Technical Errata Reported] RFC7230 (4169) RFC Errata System

Friday, 7 November 2014

• Re: HNL agenda Mark Nottingham

Thursday, 6 November 2014

• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• RE: 9.2.2, Rough Consensus, and Working Code Mike Bishop
• RE: 9.2.2, Rough Consensus, and Working Code Mike Bishop
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: Concerns about HTTP/2 Priority Ilya Grigorik
• Re: 9.2.2, Rough Consensus, and Working Code Roy T. Fielding
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Roy T. Fielding
• Re: Concerns about HTTP/2 Priority Francesco Chemolli
• Re: 9.2.2, Rough Consensus, and Working Code Yoav Nir
• Re: 9.2.2, Rough Consensus, and Working Code Yoav Nir
• Re: 9.2.2, Rough Consensus, and Working Code Patrick McManus
• Re: 9.2.2, Rough Consensus, and Working Code Ilari Liusvaara
• Re: 9.2.2, Rough Consensus, and Working Code Michael Sweet
• Re: Concerns about HTTP/2 Priority Poul-Henning Kamp
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Shigeki Ohtsu
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Shigeki Ohtsu
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Martin Thomson
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Jason Greene
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Patrick McManus
• Re: 9.2.2, Rough Consensus, and Working Code Patrick McManus
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Shigeki Ohtsu
• Re: 9.2.2, Rough Consensus, and Working Code Michael Sweet
• RE: WPD - Proxy Discovery William Chow
• Re: #612: 9.2.2 requirements Jason Greene
• Re: Concerns about HTTP/2 Priority Greg Wilkins
• Re: 9.2.2, Rough Consensus, and Working Code Martin Nilsson
• Re: 9.2.2, Rough Consensus, and Working Code Jain, Shakesh
• Re: 9.2.2, Rough Consensus, and Working Code Martin Nilsson
• Re: #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Martin Thomson
• Re: 9.2.2, Rough Consensus, and Working Code Nicholas Hurley
• Re: 9.2.2, Rough Consensus, and Working Code Roy T. Fielding
• #642: Allowing PRIORITY on streams in any any state. [was: Concerns about HTTP/2 Priority] Mark Nottingham
• Re: #612: 9.2.2 requirements Greg Wilkins
• Re: #612: 9.2.2 requirements Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Martin Thomson
• Re: 9.2.2, Rough Consensus, and Working Code Martin Thomson
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: #612: 9.2.2 requirements Poul-Henning Kamp

Wednesday, 5 November 2014

• Re: #612: 9.2.2 requirements Jason T. Greene
• RE: 9.2.2, Rough Consensus, and Working Code Mike Bishop
• Re: #612: 9.2.2 requirements Greg Wilkins
• RE: 9.2.2, Rough Consensus, and Working Code Mike Bishop
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: #612: 9.2.2 requirements Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• Re: 9.2.2, Rough Consensus, and Working Code Mark Nottingham
• Re: #632 - Tweaks for client certs Mark Nottingham
• Re: HNL agenda DIEGO LOPEZ GARCIA
• Re: Concerns about HTTP/2 Priority Roberto Peon
• Re: <DKIM> Re: WPD Discovery Options nicolas.mailhot@laposte.net
• Re: #612: 9.2.2 requirements Yoav Nir
• Re: #612: 9.2.2 requirements Greg Wilkins
• Re: #612: 9.2.2 requirements Yoav Nir
• Re: 9.2.2, Rough Consensus, and Working Code Michael Sweet
• Re: 9.2.2, Rough Consensus, and Working Code Greg Wilkins
• 9.2.2, Rough Consensus, and Working Code Mike Bishop
• Re: #612: 9.2.2 requirements Greg Wilkins
• Re: #612: 9.2.2 requirements Greg Wilkins
• Re: a question about TLS renegotiation on ID 15 Nicholas Hurley
• Re: Concerns about HTTP/2 Priority Ilya Grigorik
• a question about TLS renegotiation on ID 15 山本和彦
• Re: Concerns about HTTP/2 Priority Martin Thomson

Tuesday, 4 November 2014

• Re: Concerns about HTTP/2 Priority Mark Nottingham
• Re: Concerns about HTTP/2 Priority Chad Austin
• RE: WPD - Proxy Discovery Mishra, Sanjay
• RE: WPD Discovery Options Dave Dolson
• Re: WPD Discovery Options Martin Thomson
• Re: WPD Discovery Options Amos Jeffries
• RE: HNL agenda DRUTA, DAN
• Re: WPD Discovery Options Martin Nilsson
• Re: WPD - Proxy Discovery Roland Zink

Monday, 3 November 2014

• Re: Concerns about HTTP/2 Priority Martin Thomson
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: Concerns about HTTP/2 Priority Mark Nottingham
• Re: WPD - Proxy Discovery Mark Nottingham
• Re: #612: 9.2.2 requirements Michael Sweet
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Erik Nygren
• Re: WPD and Multiple Proxies Salvatore Loreto
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Martin Thomson
• Re: WPD and Multiple Proxies Roland Zink
• WPD - Proxy Discovery Mishra, Sanjay
• Re: #612: 9.2.2 requirements Jason Greene
• WPD Discovery Options DIEGO LOPEZ GARCIA
• WPD and Multiple Proxies Salvatore Loreto
• Re: #612: 9.2.2 requirements Michael Sweet
• Re: #612: 9.2.2 requirements Roland Zink
• Concerns about HTTP/2 Priority Chad Austin
• #632 - Tweaks for client certs Mark Nottingham
• Re: #612: 9.2.2 requirements Mark Nottingham

Sunday, 2 November 2014

• Re: #612: 9.2.2 requirements Eric Rescorla
• Re: #612: 9.2.2 requirements Martin Nilsson
• Re: #612: 9.2.2 requirements Michael Sweet
• Re: #612: 9.2.2 requirements Eric Rescorla
• Re: #612: 9.2.2 requirements Michael Sweet

Saturday, 1 November 2014

• Re: #612: 9.2.2 requirements Mark Nottingham
• Re: #612: 9.2.2 requirements Martin J. Dürst
• Re: #612: 9.2.2 requirements Martin Nilsson
• Re: #612: 9.2.2 requirements Nicholas Hurley
• Re: #612: 9.2.2 requirements Jason T. Greene
• Re: #612: 9.2.2 requirements Michael Sweet
• Re: #612: 9.2.2 requirements Roland Zink
• Re: #612: 9.2.2 requirements Roland Zink
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: #612: 9.2.2 requirements Michael Sweet

Friday, 31 October 2014

• Re: #612: 9.2.2 requirements Brian Smith
• Re: #612: 9.2.2 requirements Brian Smith
• Re: #612: 9.2.2 requirements Brian Smith
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Michael Sweet
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Patrick McManus
• Re: #612: 9.2.2 requirements Brian Smith
• Re: #612: 9.2.2 requirements Jason Greene
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Erik Nygren
• Re: #612: 9.2.2 requirements Mark Nottingham
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Nicholas Hurley
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Michaela LaVan
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Martin Thomson
• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Robert Collins

Thursday, 30 October 2014

• Re: impact of 9.2.2 changes and discussions on opportunistic encryption draft Martin Thomson
• impact of 9.2.2 changes and discussions on opportunistic encryption draft Erik Nygren
• Re: #612: 9.2.2 requirements Amos Jeffries

Wednesday, 29 October 2014

• Re: #612: 9.2.2 requirements Nicholas Hurley
• Re: #612: 9.2.2 requirements Greg Wilkins
• Re: Call for Consensus: #578 Mark Nottingham
• Re: #612: 9.2.2 requirements Roland Zink

Tuesday, 28 October 2014

• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Dave Garrett
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Brian Smith
• Re: h2 header field names Martin Thomson
• RE: #578: getting real-ish numbers for option 3 Mike Bishop
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Erik Nygren
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Jason Greene
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Jason Greene
• Re: #612: 9.2.2 requirements Ilari Liusvaara
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Erik Nygren
• Re: #578: getting real-ish numbers for option 3 Kulkarni, Saurabh
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Albert Lunde
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Mark Nottingham
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Michael Sweet
• Re: Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Yoav Nir

Thursday, 23 October 2014

• Re: h2 header field names Louis Ryan

Tuesday, 28 October 2014

• Requiring TLS 1.3 as alternative to HTTP/2 section 9.2.2 Dave Garrett
• Re: #612: 9.2.2 requirements Yoav Nir
• Re: Origin cookies Yoav Nir
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: #578: getting real-ish numbers for option 3 Martin Thomson
• Re: #578: getting real-ish numbers for option 3 Amos Jeffries
• Re: #578: getting real-ish numbers for option 3 Nicholas Hurley
• Re: #578: getting real-ish numbers for option 3 Amos Jeffries
• Re: #612: 9.2.2 requirements Patrick McManus
• -15 Martin Thomson
• Re: #578: getting real-ish numbers for option 3 Nicholas Hurley

Monday, 27 October 2014

• I-D Action: draft-ietf-httpbis-http2-15.txt internet-drafts@ietf.org
• Re: #612: 9.2.2 requirements Martin Thomson
• Re: #612: 9.2.2 requirements Jason Greene
• Re: #612: 9.2.2 requirements Mike Sweet
• RE: #612: 9.2.2 requirements Mike Bishop
• Re: sending WINDOW_UPDATE when in reserved (remote) Mark Nottingham
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
• #612: 9.2.2 requirements Mark Nottingham
• Re: #578: getting real-ish numbers for option 3 Mark Nottingham
• Re: Origin cookies Zhong Yu
• I-D Action: draft-ietf-httpbis-alt-svc-04.txt internet-drafts@ietf.org
• Re: Origin cookies Mike West
• Re: Origin cookies Mike West

Sunday, 26 October 2014

• Re: Alt-Svc-Used indicator granularity (ext#34) Erik Nygren
• Re: Origin cookies Yoav Nir

Saturday, 25 October 2014

• Re: Origin cookies Martin Thomson
• Re: Origin cookies Zhong Yu
• Re: Origin cookies Martin Thomson
• Re: Origin cookies Mike West

Friday, 24 October 2014

• Re: Origin cookies Martin Thomson
• Re: Origin cookies Mike West
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: Origin cookies Martin Thomson
• Re: #578: getting real-ish numbers for option 3 Martin Thomson
• Re: Origin cookies Mike West
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: Origin cookies Martin Thomson
• Re: #578: getting real-ish numbers for option 3 Tatsuhiro Tsujikawa
• Re: #578: getting real-ish numbers for option 3 Mark Nottingham
• Re: Origin cookies Mike West
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Re: #578: getting real-ish numbers for option 3 Mark Nottingham
• Re: #578: getting real-ish numbers for option 3 Willy Tarreau
• Origin cookies Martin Thomson
• Re: #578: getting real-ish numbers for option 3 Mark Nottingham
• #578: getting real-ish numbers for option 3 Mark Nottingham
• Re: sending WINDOW_UPDATE when in reserved (remote) Martin Thomson
• #634: sending WINDOW_UPDATE when in reserved (remote) Mark Nottingham

Thursday, 23 October 2014

• Re: Implementer intent -- option 3 for #578 Michaela LaVan
• Re: sending WINDOW_UPDATE when in reserved (remote) Ryan Hamilton
• RE: sending WINDOW_UPDATE when in reserved (remote) Mike Bishop
• sending WINDOW_UPDATE when in reserved (remote) Patrick McManus
• RE: Implementer intent -- option 3 for #578 Mike Bishop
• Re: Implementer intent -- option 3 for #578 Kulkarni, Saurabh
• Re: Implementer intent -- option 3 for #578 Nicholas Hurley
• Re: Implementer intent -- option 3 for #578 Willy Tarreau
• Re: Implementer intent -- option 3 for #578 Tatsuhiro Tsujikawa
• Re: Implementer intent -- option 3 for #578 Simpson, Robby (GE Energy Management)
• Re: timestamps encoding Martin Nilsson
• Re: Implementer intent -- option 3 for #578 Michael Sweet
• Re: Implementer intent -- option 3 for #578 Cory Benfield
• Re: Implementer intent -- option 3 for #578 Willy Tarreau
• HNL agenda Mark Nottingham
• Re: Implementer intent -- option 3 for #578 Amos Jeffries
• Re: Implementer intent -- option 3 for #578 Mark Nottingham
• Small change to the renegotiation characteristics Martin Thomson
• Re: Implementer intent -- option 3 for #578 Shigeki Ohtsu
• Re: Implementer intent -- option 3 for #578 Adrian Cole
• Re: Implementer intent -- option 3 for #578 Greg Wilkins
• Implementer intent -- option 3 for #578 Mark Nottingham
• Re: Call for Consensus: #578 Tatsuhiro Tsujikawa

Wednesday, 22 October 2014

• Re: Call for Consensus: #578 Matthew Kerwin
• Re: Call for Consensus: #578 Craig Tiller
• Re: Call for Consensus: #578 Daniel Stenberg
• Re: Call for Consensus: #578 Ryan Hamilton
• Re: Call for Consensus: #578 K.Morgan@iaea.org
• RE: Call for Consensus: #578 Mike Bishop
• Re: draft-thomson-httpbis-cant Martin Thomson
• Re: h2 priority Chad Austin
• Re: Call for Consensus: #578 Kinkie
• Re: Call for Consensus: #578 Poul-Henning Kamp
• Re: Call for Consensus: #578 Kulkarni, Saurabh
• Re: Call for Consensus: #578 Shigeki Ohtsu
• Re: Call for Consensus: #578 Nicholas Hurley
• Re: draft-thomson-httpbis-cant Stephen Farrell
• Re: draft-thomson-httpbis-cant Stephen Farrell
• Re: Call for Consensus: #578 Adrian Cole
• Re: Call for Consensus: #578 Simpson, Robby (GE Energy Management)
• Re: draft-thomson-httpbis-cant Martin Thomson
• Re: draft-thomson-httpbis-cant Ilari Liusvaara
• draft-thomson-httpbis-cant Stephen Farrell
• Re: Call for Consensus: #578 Amos Jeffries
• Re: Call for Consensus: #578 Tatsuhiro Tsujikawa
• Re: Call for Consensus: #578 Michael Sweet
• Re: Call for Consensus: #578 Cory Benfield
• Re: Call for Consensus: #578 Willy Tarreau
• Re: Call for Consensus: #578 Mark Nottingham
• Re: Call for Consensus: #578 Greg Wilkins
• Re: Call for Consensus: #578 Jason Greene
• Call for Consensus: #578 Mark Nottingham
• Re: #578 [was: Straw Poll: Restore Header Table and Static Table Indices] Mark Nottingham
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
• Re: #578 [was: Straw Poll: Restore Header Table and Static Table Indices] Amos Jeffries
• Re: timestamps encoding Amos Jeffries
• Re: timestamps encoding (was: Re: Straw Poll: Restore Header Table and Static Table Indices) Martin Nilsson
• #578 [was: Straw Poll: Restore Header Table and Static Table Indices] Mark Nottingham

Tuesday, 21 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Jason Greene
• timestamps encoding (was: Re: Straw Poll: Restore Header Table and Static Table Indices) Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins
• Re: Removing SSL 3.0/Poodle Martin Thomson
• Re: [Editorial Errata Reported] RFC7230 (4136) Barry Leiba
• Re: Removing SSL 3.0/Poodle Walter H.
• Re: Removing SSL 3.0/Poodle Jim Manico
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Julian Reschke
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Removing SSL 3.0/Poodle Julian Reschke
• Re: Removing SSL 3.0/Poodle Jim Manico
• Re: Straw Poll: Restore Header Table and Static Table Indices Roberto Peon
• Re: Removing SSL 3.0/Poodle Matthew Kerwin
• Re: Removing SSL 3.0/Poodle Martin Thomson
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Removing SSL 3.0/Poodle Jim Manico
• Re: [Editorial Errata Reported] RFC7230 (4136) Julian Reschke
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: [Editorial Errata Reported] RFC7230 (4136) Barry Leiba

Monday, 20 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau

Saturday, 18 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau

Thursday, 16 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• RE: Straw Poll: Restore Header Table and Static Table Indices RUELLAN Herve

Wednesday, 15 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Jason Greene
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Simpson, Robby (GE Energy Management)
• Re: Straw Poll: Restore Header Table and Static Table Indices Simpson, Robby (GE Energy Management)
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• RE: Straw Poll: Restore Header Table and Static Table Indices RUELLAN Herve
• Re: No link to hpack-09 in some hpack draft pages Yi, EungJun
• Re: Extensions and error codes Ilari Liusvaara
• Re: No link to hpack-09 in some hpack draft pages Julian Reschke
• Re: Question about HTTP 2.0 priority Chad Austin
• No link to hpack-09 in some hpack draft pages Yi, EungJun
• Re: Extensions and error codes Adrian Cole
• Re: RST_STREAM(OK) after an HTTP response Daniel Stenberg
• Re: Concluding discussion on #612 (9.2.2) Adrian Cole
• Re: Concluding discussion on #612 (9.2.2) Mark Nottingham
• Extensions and error codes Adrian Cole
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: #603: Frame layout Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Amos Jeffries
• Re: RST_STREAM(OK) after an HTTP response Amos Jeffries
• Re: Straw Poll: Restore Header Table and Static Table Indices Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Adrian Cole
• Re: Restore Header Table and Static Table Indices Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Adrian Cole
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins

Tuesday, 14 October 2014

• Re: RST_STREAM(OK) after an HTTP response Robert Collins
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: Straw Poll: Restore Header Table and Static Table Indices Roberto Peon
• Re: RST_STREAM(OK) after an HTTP response Martin Thomson
• RE: RST_STREAM(OK) after an HTTP response Mike Bishop
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: HTTP/2 and Websockets Robert Collins
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham

Monday, 13 October 2014

• RE: RST_STREAM(OK) after an HTTP response Matthew Cox
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins

Sunday, 12 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Roberto Peon
• Re: #496: Feedback on Fallback Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham

Saturday, 11 October 2014

• Re: Concluding discussion on #612 (9.2.2) Jason Greene
• Re: Updated 9.2 Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Updated 9.2 Martin Nilsson
• Re: Updated 9.2 Yoav Nir
• Re: Updated 9.2 Ilari Liusvaara
• Re: Concluding discussion on #612 (9.2.2) Ilari Liusvaara
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Updated 9.2 Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Jason Greene

Friday, 10 October 2014

• Re: Concluding discussion on #612 (9.2.2) Ilari Liusvaara
• RE: Updated 9.2 Rob Trace
• Re: Concluding discussion on #612 (9.2.2) Eric Rescorla
• Re: Updated 9.2 Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Updated 9.2 Greg Wilkins
• Re: ECDHE security level Brian Smith
• Re: ECDHE security level Martin Thomson
• Re: ECDHE security level Brian Smith
• Re: Updated 9.2 Jason Greene
• Re: Updated 9.2 Julian Reschke
• Re: ECDHE security level Brian Smith
• Re: ECDHE security level Martin Thomson
• Re: ECDHE security level Brian Smith
• Re: ECDHE security level Ilari Liusvaara
• Re: Updated 9.2 Brian Smith
• Re: ECDHE security level Martin Thomson
• Re: ECDHE security level Brian Smith
• Updated 9.2 Martin Thomson
• ECDHE security level Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Jason Greene
• Re: Concluding discussion on #612 (9.2.2) Ilari Liusvaara
• Re: Question about HTTP 2.0 priority Tatsuhiro Tsujikawa
• Re: Question about HTTP 2.0 priority Greg Wilkins

Thursday, 9 October 2014

• Re: Question about HTTP 2.0 priority Martin Thomson
• Re: Question about HTTP 2.0 priority Chad Austin
• RE: Question about HTTP 2.0 priority Mike Bishop
• Re: Question about HTTP 2.0 priority Chad Austin
• Re: Concluding discussion on #612 (9.2.2) Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Eric Rescorla
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Ilari Liusvaara
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Eric Rescorla
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins

Wednesday, 8 October 2014

• Re: Concluding discussion on #612 (9.2.2) Jason Greene
• Re: RST_STREAM(OK) after an HTTP response Martin Thomson
• RE: RST_STREAM(OK) after an HTTP response Mike Bishop
• Re: Concluding discussion on #612 (9.2.2) Adam Langley
• Re: RST_STREAM(OK) after an HTTP response Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Brian Smith
• Re: Concluding discussion on #612 (9.2.2) Brian Smith
• RE: RST_STREAM(OK) after an HTTP response Matthew Cox
• Re: Concluding discussion on #612 (9.2.2) Patrick McManus
• Re: Concluding discussion on #612 (9.2.2) Ilari Liusvaara
• RE: Concluding discussion on #612 (9.2.2) Albert Lunde
• Re: Concluding discussion on #612 (9.2.2) Roland Zink
• RE: #496: Feedback on Fallback K.Morgan@iaea.org
• Re: Concluding discussion on #612 (9.2.2) Martin Thomson
• Static Table Values (was Re: Straw Poll: Restore Header Table and Static Table Indices) Simpson, Robby (GE Energy Management)
• Re: Concluding discussion on #612 (9.2.2) Patrick McManus
• Re: Concluding discussion on #612 (9.2.2) Brian Smith
• Re: Concluding discussion on #612 (9.2.2) Jason Greene

Tuesday, 7 October 2014

• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins
• Re: About Padding in PUSH_PROMISE/HEADERS Raullen Chai
• Re: Concluding discussion on #612 (9.2.2) 陈智昌
• Re: null ciphers in 9.2.2 Greg Wilkins
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
• Re: Concluding discussion on #612 (9.2.2) Mark Nottingham
• Re: null ciphers in 9.2.2 Eric Rescorla
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: About Padding in PUSH_PROMISE/HEADERS Martin Thomson
• Re: null ciphers in 9.2.2 Martin Thomson
• Re: About Padding in PUSH_PROMISE/HEADERS Raullen Chai
• Re: About Padding in PUSH_PROMISE/HEADERS Martin Thomson
• Re: null ciphers in 9.2.2 Greg Wilkins
• Re: Concluding discussion on #612 (9.2.2) Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Greg Wilkins
• Re: RST_STREAM(OK) after an HTTP response Martin Thomson
• About Padding in PUSH_PROMISE/HEADERS Raullen Chai
• Re: Concluding discussion on #612 (9.2.2) 陈智昌
• Re: Question about HTTP 2.0 priority Martin Thomson
• RE: Concluding discussion on #612 (9.2.2) Rob Trace
• RE: Concluding discussion on #612 (9.2.2) Albert Lunde
• Re: Concluding discussion on #612 (9.2.2) Eric Rescorla
• Re: #496: Feedback on Fallback Jason Greene
• RE: #496: Feedback on Fallback Mike Bishop
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Concluding discussion on #612 (9.2.2) Jason Greene
• RE: Straw Poll: Restore Header Table and Static Table Indices RUELLAN Herve
• Re: Straw Poll: Restore Header Table and Static Table Indices Nicholas Hurley
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Concluding discussion on #612 (9.2.2) Martin Thomson
• Re: Concluding discussion on #612 (9.2.2) Nicholas Hurley
• Re: Straw Poll: Restore Header Table and Static Table Indices Nicholas Hurley
• RE: #496: Feedback on Fallback Mike Bishop
• Re: Concluding discussion on #612 (9.2.2) Michael Sweet
• RE: #496: Feedback on Fallback Lucas Pardue
• RE: Straw Poll: Restore Header Table and Static Table Indices K.Morgan@iaea.org
• Re: Concluding discussion on #612 (9.2.2) Eric Rescorla
• Re: Quick feedback on draft-nottingham-web-proxy-desc-00 Mark Nottingham
• Re: #496: Feedback on Fallback Eliot Lear
• Re: Straw Poll: Restore Header Table and Static Table Indices Amos Jeffries
• #496: Feedback on Fallback Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: RST_STREAM(OK) after an HTTP response Mark Nottingham
• Re: #603: Frame layout Nottingham, Mark
• Concluding discussion on #612 (9.2.2) Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Question about HTTP 2.0 priority Chad Austin
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• Re: Question about HTTP 2.0 priority Martin Thomson
• Re: Question about HTTP 2.0 priority Chad Austin
• Re: Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: null ciphers in 9.2.2 Eric Rescorla
• Re: Straw Poll: Restore Header Table and Static Table Indices Greg Wilkins
• Re: Straw Poll: Restore Header Table and Static Table Indices Shigeki Ohtsu
• Re: Question about HTTP 2.0 priority Martin Thomson

Monday, 6 October 2014

• Re: Question about HTTP 2.0 priority Greg Wilkins
• Re: Straw Poll: Restore Header Table and Static Table Indices Willy Tarreau
• RE: Restore Header Table and Static Table Indices Mike Bishop
• Re: Restore Header Table and Static Table Indices Roberto Peon
• Re: Restore Header Table and Static Table Indices Simpson, Robby (GE Energy Management)
• Re: null ciphers in 9.2.2 Greg Wilkins
• Re: Restore Header Table and Static Table Indices Daniel Stenberg
• Re: Restore Header Table and Static Table Indices Greg Wilkins
• Re: Restore Header Table and Static Table Indices Michael Sweet
• Re: Restore Header Table and Static Table Indices Ludin, Stephen
• Straw Poll: Restore Header Table and Static Table Indices Mark Nottingham
• Re: Restore Header Table and Static Table Indices Poul-Henning Kamp
• Re: Restore Header Table and Static Table Indices Kulkarni, Saurabh
• Re: Restore Header Table and Static Table Indices Nicholas Hurley
• Re: Question about HTTP 2.0 priority Martin Thomson
• Re: null ciphers in 9.2.2 Nicholas Hurley
• Re: Question about HTTP 2.0 priority Chad Austin
• Re: Authentication and TCP Connection State Michael B Allen
• Re: #578: Header Table and Static Table Indices Switched Jeff Pinner
• Restore Header Table and Static Table Indices Jeff Pinner
• Re: Authentication and TCP Connection State Amos Jeffries
• Re: Authentication and TCP Connection State Willy Tarreau
• Re: null ciphers in 9.2.2 Greg Wilkins

Sunday, 5 October 2014

• Re: null ciphers in 9.2.2 Mark Nottingham
• Re: null ciphers in 9.2.2 Greg Wilkins
• Re: #578: Header Table and Static Table Indices Switched Mark Nottingham
• Re: null ciphers in 9.2.2 Mark Nottingham
• Re: Authentication and TCP Connection State Robert Collins
• Re: Authentication and TCP Connection State Michael B Allen
• Re: Authentication and TCP Connection State Willy Tarreau
• Re: Authentication and TCP Connection State Amos Jeffries
• Re: Authentication and TCP Connection State Yutaka OIWA
• Re: Authentication and TCP Connection State Yutaka OIWA

Saturday, 4 October 2014

• Re: Authentication and TCP Connection State Michael B Allen
• Re: Authentication and TCP Connection State Julian Reschke

Friday, 3 October 2014

• Re: Authentication and TCP Connection State Michael B Allen
• Re: Authentication and TCP Connection State Michael B Allen
• Re: Authentication and TCP Connection State Martin Thomson
• RE: Authentication and TCP Connection State Mike Bishop
• Re: Authentication and TCP Connection State Michael B Allen
• Re: Authentication and TCP Connection State Ilari Liusvaara
• Re: Authentication and TCP Connection State Willy Tarreau
• Re: Authentication and TCP Connection State David Morris
• Re: Authentication and TCP Connection State Michael B Allen
• RE: Authentication and TCP Connection State Matthew Cox
• RE: Authentication and TCP Connection State paincompiler
• RE: Authentication and TCP Connection State Matthew Cox
• Authentication and TCP Connection State Michael B Allen
• Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem John Mattsson
• Re: Quick feedback on draft-nottingham-web-proxy-desc-00 Martin Nilsson

Thursday, 2 October 2014

• Re: Quick feedback on draft-nottingham-web-proxy-desc-00 Julian Reschke
• PSA: Chromium ramping up h2-14 support. Bence Béky
• Re: Quick feedback on draft-nottingham-web-proxy-desc-00 Roland Zink
• RE: Quick feedback on draft-nottingham-web-proxy-desc-00 Smith, Kevin, (R&D) Vodafone Group
• Re: Quick feedback on draft-nottingham-web-proxy-desc-00 Julian Reschke
• Re:Quick feedback on draft-nottingham-web-proxy-desc-00 Smith, Kevin, (R&D) Vodafone Group
• Re: Question about HTTP 2.0 priority Amos Jeffries
• Re: Question about HTTP 2.0 priority Chad Austin
• Re: Question about HTTP 2.0 priority Amos Jeffries
• Question about HTTP 2.0 priority Chad Austin

Wednesday, 1 October 2014

• RE: null ciphers in 9.2.2 Gabriel Montenegro
• Re: null ciphers in 9.2.2 Jason Greene
• Re: null ciphers in 9.2.2 FOSSATI, Thomas (Thomas)
• Re: null ciphers in 9.2.2 Eric Rescorla
• Re: HTTP/2 and Websockets Amos Jeffries
• Re: HTTP/2 and Websockets Yutaka Hirano
• Re: null ciphers in 9.2.2 Jason Greene
• Re: null ciphers in 9.2.2 Martin Thomson
• Re: null ciphers in 9.2.2 Jason Greene
• Re: null ciphers in 9.2.2 Jason Greene
• Re: null ciphers in 9.2.2 Martin Thomson
• Re: null ciphers in 9.2.2 Jason Greene
• Re: null ciphers in 9.2.2 Greg Wilkins
• Re: User-Agent header field and quoted-string Amos Jeffries
• Re: null ciphers in 9.2.2 Stephen Farrell
• Re: null ciphers in 9.2.2 Greg Wilkins

Last message date: Wednesday, 31 December 2014 18:33:48 UTC