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

Friday, 30 September 2016

• WebSocket2 Van Catha
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Mark Nottingham

Thursday, 29 September 2016

• Re: #227: Encoding advice for new headers and parameters Julian Reschke
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Kari hurtta

Wednesday, 28 September 2016

• site-wide headers Martin Thomson
• Re: Encryption content coding simplification Martin Thomson
• Re: HTTP Content-Location header usage Mark Nottingham
• Re: #227: Encoding advice for new headers and parameters Poul-Henning Kamp
• Fwd: New Version Notification for draft-ietf-httpbis-origin-frame-01.txt Mark Nottingham
• I-D Action: draft-ietf-httpbis-origin-frame-01.txt internet-drafts@ietf.org
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Mark Nottingham
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Mark Nottingham
• #227: Encoding advice for new headers and parameters Mark Nottingham

Wednesday, 21 September 2016

• HTTP Content-Location header usage Никита Пискунов

Tuesday, 20 September 2016

• Re: http2: what is the purpose of the "reserved" states? Martin Thomson
• Re: HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Kazuho Oku
• http2: what is the purpose of the "reserved" states? Tom Bergan
• Re: HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Martin Thomson
• Re: HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Kazuho Oku
• Re: Distinguishing 0-byte request body in HTTP/2 Kazuho Oku

Friday, 16 September 2016

• Re: HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Tom Bergan
• Re: Distinguishing 0-byte request body in HTTP/2 Willy Tarreau
• Re: HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Martin Thomson

Thursday, 15 September 2016

• HTTP/2: Race between PUSH_PROMISE and exclusive PRIORITY Tom Bergan
• Re: Distinguishing 0-byte request body in HTTP/2 Roy T. Fielding
• Re: Distinguishing 0-byte request body in HTTP/2 Roy T. Fielding
• Re: Distinguishing 0-byte request body in HTTP/2 Willy Tarreau
• Re: Distinguishing 0-byte request body in HTTP/2 Roy T. Fielding
• Re: Distinguishing 0-byte request body in HTTP/2 Roy T. Fielding
• Re: Clarification of dynamic table size change Tatsuhiro Tsujikawa
• Re: Distinguishing 0-byte request body in HTTP/2 Willy Tarreau
• Re: Distinguishing 0-byte request body in HTTP/2 Mark Nottingham
• Re: Distinguishing 0-byte request body in HTTP/2 Willy Tarreau
• Re: Distinguishing 0-byte request body in HTTP/2 Kazuho Oku

Wednesday, 14 September 2016

• Re: Distinguishing 0-byte request body in HTTP/2 Mark Nottingham
• Distinguishing 0-byte request body in HTTP/2 Kazuho Oku
• Re: Clarification of dynamic table size change Bence Béky
• Re: Interpreting "+" in query component of https:// scheme URIs. Matthew Kerwin

Friday, 9 September 2016

• Interpreting "+" in query component of https:// scheme URIs. Matt Randall

Tuesday, 13 September 2016

• Bar BOF in Seoul and Mailing List - DNS over HTTP ideas Patrick McManus

Sunday, 11 September 2016

• Re: Server Push and Caching Roy T. Fielding

Thursday, 8 September 2016

• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Kari hurtta

Tuesday, 6 September 2016

• httpbis - New Meeting Session Request for IETF 97 \

Thursday, 8 September 2016

• Re: Server Push and Caching Mark Nottingham
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Mark Nottingham

Wednesday, 7 September 2016

• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Patrick McManus
• RE: last call Feedback for Opportunistic Security for HTTP (Experimental) Mike Bishop
• Re: last call Feedback for Opportunistic Security for HTTP (Experimental) Nick Sullivan
• Re: Server Push and Caching Roy T. Fielding
• last call Feedback for Opportunistic Security for HTTP (Experimental) Patrick McManus
• Re: Server Push and Content Negotiation Mark Nottingham
• Re: Server Push and Content Negotiation Mark Nottingham
• Re: Server Push and Caching Mark Nottingham

Monday, 5 September 2016

• Re: I-D Action: draft-ietf-httpbis-cookie-alone-01.txt Mike West
• I-D Action: draft-ietf-httpbis-cookie-alone-01.txt internet-drafts@ietf.org

Sunday, 4 September 2016

• Re: Cookie-Attribute request header proposal Daniel Stenberg

Friday, 19 August 2016

• Re: [tcpm] TCP Tuning for HTTP - update Jana Iyengar

Thursday, 1 September 2016

• Cookie-Attribute request header proposal David Eckel

Saturday, 3 September 2016

• Re: HTTP Hackathon at IETF Seoul -- Saturday and Sunday before Mark Nottingham

Thursday, 1 September 2016

• Re: Experiences with HTTP/2 server push Kazuho Oku
• Re: Experiences with HTTP/2 server push Tom Bergan
• Re: Experiences with HTTP/2 server push Tom Bergan
• Re: Experiences with HTTP/2 server push Kazuho Oku

Friday, 26 August 2016

• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Nick Sullivan
• Re: Server Push and Conditional Requests Kazuho Oku
• Re: Server Push and Conditional Requests Stefan Eissing
• Re: Server Push and Conditional Requests Kazuho Oku
• Re: Server Push and Conditional Requests Stefan Eissing
• Re: Server Push and Conditional Requests Kazuho Oku

Wednesday, 24 August 2016

• Re: Server Push and Caching Roy T. Fielding
• RE: Server Push Error Codes Mike Bishop
• RE: Server Push and Content Negotiation Mike Bishop
• RE: Server Push and Caching Mike Bishop
• Re: Server Push and Caching Tom Bergan
• Re: Experiences with HTTP/2 server push Tom Bergan
• Re: Server Push and Caching Roy T. Fielding
• Re: Server Push and Content Negotiation Tom Bergan
• Re: Scope of Server Push Tom Bergan
• Re: Server Push and Caching Tom Bergan
• Re: Server Push Error Codes Patrick McManus
• Re: Server Push and Content Negotiation Patrick McManus
• Re: Scope of Server Push Alcides Viamontes E
• Re: Server Push Error Codes Martin Thomson
• Re: Server Push Error Codes Emily Shepherd
• Re: draft-ietf-httpbis-cache-digest-00 comments Mark Nottingham
• Re: ORIGIN frame - Origin Sets Mark Nottingham
• Re: Server Push Error Codes Mark Nottingham
• Re: Server Push Error Codes Martin Thomson
• Scope of Server Push Mark Nottingham
• Server Push and Caching Mark Nottingham
• Server Push and Status Codes Mark Nottingham
• Server Push Error Codes Mark Nottingham
• Server Push and Content Negotiation Mark Nottingham
• Server Push and Conditional Requests Mark Nottingham

Saturday, 20 August 2016

• Re: Continuing discussion on Cache Digest Alcides Viamontes E
• Continuing discussion on Cache Digest Mark Nottingham

Friday, 19 August 2016

• Re: [Editorial Errata Reported] RFC7230 (4779) Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Eliot Lear
• Re: [Editorial Errata Reported] RFC7230 (4779) Roy T. Fielding
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Jeremy Harris
• Re: TCP Tuning for HTTP, the next step tjw ietf
• TCP Tuning for HTTP, the next step Daniel Stenberg
• Re: Client Hints to Experimental Ilya Grigorik
• Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
• Re: [Editorial Errata Reported] RFC7230 (4779) Mark Nottingham

Thursday, 18 August 2016

• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [Technical Errata Reported] RFC7230 (4667) Alex Rousskov
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: Clarification of dynamic table size change Patrick McManus
• Re: Clarification of dynamic table size change Tatsuhiro Tsujikawa
• Re: If not JSON, what then ? Sam Johnston
• Re: Clarification of dynamic table size change Bence Béky
• [Editorial Errata Reported] RFC7230 (4779) RFC Errata System
• Re: ORIGIN frame - Origin Sets Martin Thomson
• Re: [Technical Errata Reported] RFC7230 (4667) Alexey Melnikov
• ORIGIN frame - Origin Sets Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: Client Hints to Experimental Mark Nottingham

Wednesday, 17 August 2016

• Re: [Technical Errata Reported] RFC7230 (4667) Alex Rousskov
• Re: [tcpm] TCP Tuning for HTTP - update Matthew Kerwin
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Adrien de Croy
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Adrien de Croy
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Tim Wicinski
• Re: [tcpm] TCP Tuning for HTTP - update Eliot Lear
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Alexey Melnikov
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
• Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
• Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
• Fwd: Last Call: <draft-ietf-core-http-mapping-13.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC Mark Nottingham
• Re: Call for Adoption: draft-song-dns-wireformat-http Tim Wicinski
• Re: Call for Adoption: draft-song-dns-wireformat-http Mark Nottingham

Tuesday, 16 August 2016

• Re: 304 on Non-Conditional Request? Adrien de Croy
• Re: #225: JFV Revisited Ilya Grigorik

Monday, 15 August 2016

• Re: 304 on Non-Conditional Request? Willy Tarreau
• Re: Experiences with HTTP/2 server push Matthew Kerwin
• Re: Experiences with HTTP/2 server push Kazuho Oku
• Re: Experiences with HTTP/2 server push Martin Thomson

Sunday, 14 August 2016

• Re: Experiences with HTTP/2 server push Kazuho Oku

Friday, 12 August 2016

• Re: #225: JFV Revisited Amos Jeffries
• Re: #225: JFV Revisited Julian Reschke
• Re: #225: JFV Revisited Amos Jeffries
• Re: #225: JFV Revisited Martin Thomson
• Re: 304 on Non-Conditional Request? Adrien de Croy
• Re: New Version Notification for draft-nottingham-httpbis-retry-00.txt Mark Nottingham
• Re: 304 on Non-Conditional Request? Mark Nottingham

Thursday, 11 August 2016

• 304 on Non-Conditional Request? Mike Bishop
• [Errata Held for Document Update] RFC7540 (4720) RFC Errata System
• Re: H2 Implementation Debug State URI Cory Benfield
• Re: #225: JFV Revisited Poul-Henning Kamp
• Re: #225: JFV Revisited Mark Nottingham
• Re: #225: JFV Revisited Poul-Henning Kamp
• Re: Fwd: New Version Notification for draft-nottingham-httpbis-retry-00.txt Daniel Stenberg
• #225: JFV Revisited Mark Nottingham
• Fwd: New Version Notification for draft-nottingham-httpbis-retry-00.txt Mark Nottingham

Wednesday, 10 August 2016

• Re: H2 Implementation Debug State URI Alex Rousskov
• Re: H2 Implementation Debug State URI Poul-Henning Kamp
• RE: H2 Implementation Debug State URI Mike Bishop
• Re: H2 Implementation Debug State URI Alex Rousskov
• Fwd: New Version Notification for draft-benfield-http2-debug-state-01.txt Cory Benfield
• Re: H2 Implementation Debug State URI Cory Benfield
• Client Hints to Experimental Mark Nottingham

Tuesday, 9 August 2016

• Re: H2 Implementation Debug State URI Alex Rousskov
• Re: H2 Implementation Debug State URI Cory Benfield
• Re: h2specd 山本和彦
• Re: h2specd Matthew Kerwin
• HTTP Hackathon at IETF Seoul -- Saturday and Sunday before Mark Nottingham
• Re: [Editorial Errata Reported] RFC7540 (4720) Mark Nottingham

Monday, 8 August 2016

• RE: h2specd Mike Bishop
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Patrick McManus
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Adrien de Croy
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Martin Thomson
• Re: h2specd Tom Bergan
• Re: Experiences with HTTP/2 server push Martin Thomson
• RE: Fwd: Call for Adoption: draft-song-dns-wireformat-http Mike Bishop
• Re: Experiences with HTTP/2 server push Alcides Viamontes E
• RE: Informal meeting on blind caching Mike Bishop
• Re: H2 Implementation Debug State URI Alex Rousskov
• Re: Experiences with HTTP/2 server push Tom Bergan
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Amos Jeffries
• RE: [Editorial Errata Reported] RFC7540 (4720) Mike Bishop
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Walter H.
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Amos Jeffries
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Poul-Henning Kamp
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] nicolas.mailhot@laposte.net
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] nicolas.mailhot@laposte.net
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Martin Thomson
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Martin Thomson
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Adrien de Croy
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Martin Thomson
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Adrien de Croy

Sunday, 7 August 2016

• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Kari hurtta
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Walter H.
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Kari hurtta
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Walter H.
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Walter H.
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Ilari Liusvaara
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Kari hurtta
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Amos Jeffries
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Walter H.
• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] nicolas.mailhot@laposte.net

Saturday, 6 August 2016

• Re: MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Adrien de Croy
• Re: H2 Implementation Debug State URI Cory Benfield

Friday, 5 August 2016

• Re: h2specd Ilya Grigorik

Saturday, 6 August 2016

• MITM and proxy messages [was: Call for Adoption: draft-song-dns-wireformat-http] Mark Nottingham

Friday, 5 August 2016

• Re: Experiences with HTTP/2 server push Amos Jeffries
• Re: Experiences with HTTP/2 server push Alcides Viamontes E
• Re: Experiences with HTTP/2 server push Tom Bergan
• Re: H2 Implementation Debug State URI Alex Rousskov
• Re: H2 Implementation Debug State URI Stefan Eissing
• Re: H2 Implementation Debug State URI Martin Thomson
• Re: Experiences with HTTP/2 server push Martin Thomson
• Re: H2 Implementation Debug State URI Cory Benfield
• Re: H2 Implementation Debug State URI Poul-Henning Kamp
• Re: H2 Implementation Debug State URI Cory Benfield

Thursday, 4 August 2016

• Experiences with HTTP/2 server push Tom Bergan

Friday, 5 August 2016

• Re: H2 Implementation Debug State URI Poul-Henning Kamp
• h2specd 山本和彦

Thursday, 4 August 2016

• Re: Fwd: Call for Adoption: draft-song-dns-wireformat-http Nicolas Mailhot
• Re: Encryption content coding simplification Poul-Henning Kamp

Wednesday, 3 August 2016

• Re: If not JSON, what then ? Martin J. Dürst

Thursday, 4 August 2016

• Encryption content coding simplification Martin Thomson

Wednesday, 3 August 2016

• Re: Fwd: Call for Adoption: draft-song-dns-wireformat-http Adrien de Croy
• Re: Call for Adoption: draft-song-dns-wireformat-http Patrick McManus
• Re: Fwd: Call for Adoption: draft-song-dns-wireformat-http Poul-Henning Kamp
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: Fwd: Call for Adoption: draft-song-dns-wireformat-http Patrick McManus
• Re: If not JSON, what then ? Martin Thomson
• New Version Notification for draft-stenberg-httpbis-tcp-02.txt (fwd) Daniel Stenberg
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: New Version Notification for draft-nottingham-site-wide-headers-00.txt Mark Nottingham
• Re: New Version Notification for draft-nottingham-site-wide-headers-00.txt Martin Thomson
• Re: If not JSON, what then ? Martin Thomson
• Re: Call for Adoption: draft-song-dns-wireformat-http Tim Wicinski
• Re: Fwd: Call for Adoption: draft-song-dns-wireformat-http Poul-Henning Kamp
• Re: Call for Adoption: draft-song-dns-wireformat-http Mark Nottingham
• Fwd: New Version Notification for draft-nottingham-site-wide-headers-00.txt Mark Nottingham
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Kari hurtta
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Kari hurtta
• Re: Call for Adoption: draft-song-dns-wireformat-http Martin Thomson
• Re: Call for Adoption: draft-song-dns-wireformat-http tjw ietf
• Re: Call for Adoption: draft-song-dns-wireformat-http Martin Thomson
• Fwd: Call for Adoption: draft-song-dns-wireformat-http tjw ietf
• Re: If not JSON, what then ? Martin Thomson

Tuesday, 2 August 2016

• Re: If not JSON, what then ? Carsten Bormann
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Carsten Bormann
• Re: Call for Adoption: Two More Cookie Drafts / RFC6265bis status Patrick McManus
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: New co-chair for HTTPBIS WG Nicholas Hurley
• Re: If not JSON, what then ? Carsten Bormann
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? nicolas.mailhot@laposte.net
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? nicolas.mailhot@laposte.net
• Re: If not JSON, what then ? Stefan Eissing
• Re: If not JSON, what then ? Mark Nottingham
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Stefan Eissing
• Re: New co-chair for HTTPBIS WG Eliot Lear
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Mark Nottingham

Monday, 1 August 2016

• Re: New co-chair for HTTPBIS WG Daniel Stenberg
• Re: New co-chair for HTTPBIS WG Jason Greene
• Re: New co-chair for HTTPBIS WG Francesco Chemolli
• Re: New co-chair for HTTPBIS WG Stefan Eissing
• Re: New co-chair for HTTPBIS WG Willy Tarreau
• Re: Informal meeting on blind caching Kevin Marks
• Re: New co-chair for HTTPBIS WG Ilya Grigorik
• Re: New co-chair for HTTPBIS WG Mark Nottingham
• Re: If not JSON, what then ? Alcides Viamontes E
• Re: New co-chair for HTTPBIS WG Cory Benfield
• New co-chair for HTTPBIS WG Alexey Melnikov
• Re: If not JSON, what then ? James M Snell
• Re: If not JSON, what then ? Cory Benfield
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Nicolas Mailhot
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Poul-Henning Kamp
• Re: If not JSON, what then ? Willy Tarreau
• Re: If not JSON, what then ? Carsten Bormann
• If not JSON, what then ? Poul-Henning Kamp
• Re: Concepts to improve Http2.0 Wesley Oliver

Sunday, 31 July 2016

• Re: [Editorial Errata Reported] RFC7540 (4720) Martin Thomson

Saturday, 30 July 2016

• Re: Concepts to improve Http2.0 Martin J. Dürst

Friday, 29 July 2016

• Re: Concepts to improve Http2.0 Matthew Kerwin
• Re: Concepts to improve Http2.0 Patrick McManus
• Re: Concepts to improve Http2.0 Patrick McManus
• Re: Concepts to improve Http2.0 Wesley Oliver
• Re: Concepts to improve Http2.0 Wesley Oliver
• Re: Concepts to improve Http2.0 Amos Jeffries
• Re: Concepts to improve Http2.0 Amos Jeffries
• Re: Concepts to improve Http2.0 Wesley Oliver
• Re: Concepts to improve Http2.0 Mark Nottingham
• Re: Concepts to improve Http2.0 Cory Benfield
• Re: Concepts to improve Http2.0 Wesley Oliver
• Re: Concepts to improve Http2.0 Amos Jeffries
• Re: RFC7234: Can a request body form part of a "cache key"? Amos Jeffries
• Re: Concepts to improve Http2.0 Cory Benfield
• Re: Concepts to improve Http2.0 Wesley Oliver
• Re: RFC7234: Can a request body form part of a "cache key"? Julian Reschke
• Re: RFC7234: Can a request body form part of a "cache key"? Willy Tarreau

Thursday, 28 July 2016

• Re: RFC7234: Can a request body form part of a "cache key"? Adrien de Croy
• Re: Informal meeting on blind caching Göran Eriksson AP
• Re: RFC7234: Can a request body form part of a "cache key"? Willy Tarreau
• Re: RFC7234: Can a request body form part of a "cache key"? Julian Reschke
• Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: RFC7234: Can a request body form part of a "cache key"? Roy T. Fielding
• Re: RFC7234: Can a request body form part of a "cache key"? David Morris
• Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: Bodies on GET (again) - was Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: RFC7234: Can a request body form part of a "cache key"? Graham Leggett
• Re: RFC7234: Can a request body form part of a "cache key"? Julian Reschke
• Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: H2 Implementation Debug State URI Alcides Viamontes E
• Rough minutes from IETF96 Berlin Mark Nottingham
• Re: Informal meeting on blind caching Erik Nygren
• Re: [Editorial Errata Reported] RFC7540 (4720) Mark Nottingham
• Re: [Editorial Errata Reported] RFC7540 (4720) Ben Campbell
• Re: H2 Implementation Debug State URI Stefan Eissing
• Re: [Editorial Errata Reported] RFC7540 (4720) Mark Nottingham
• Re: Bodies on GET (again) - was Re: RFC7234: Can a request body form part of a "cache key"? Mark Nottingham
• H2 Implementation Debug State URI Cory Benfield
• Re: Informal meeting on blind caching Richard Bradbury
• Re: Informal meeting on blind caching Richard Bradbury
• Re: RFC7234: Can a request body form part of a "cache key"? Julian Reschke
• Re: Bodies on GET (again) - was Re: RFC7234: Can a request body form part of a "cache key"? Willy Tarreau
• Re: Bodies on GET (again) - was Re: RFC7234: Can a request body form part of a "cache key"? Willy Tarreau
• Re: Concepts to improve Http2.0 Poul-Henning Kamp
• Bodies on GET (again) - was Re: RFC7234: Can a request body form part of a "cache key"? Adrien de Croy
• Re: RFC7234: Can a request body form part of a "cache key"? Adrien de Croy

Wednesday, 27 July 2016

• Re: RFC7234: Can a request body form part of a "cache key"? Alex Rousskov
• Re: RFC7234: Can a request body form part of a "cache key"? Julian Reschke
• Re: Concepts to improve Http2.0 Adrien de Croy
• Re: RFC7234: Can a request body form part of a "cache key"? Adrien de Croy
• Re: RFC7234: Can a request body form part of a "cache key"? Roy T. Fielding
• RFC7234: Can a request body form part of a "cache key"? Graham Leggett
• Re: Concepts to improve Http2.0 Dennis Olvany
• Re: Informal meeting on blind caching Amos Jeffries
• Re: Informal meeting on blind caching Martin Thomson
• Re: Informal meeting on blind caching Richard Bradbury
• RE: Concepts to improve Http2.0 Lucas Pardue
• Concepts to improve Http2.0 Wesley Oliver

Sunday, 24 July 2016

• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Ilari Liusvaara
• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Martin Thomson
• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Ilari Liusvaara

Saturday, 23 July 2016

• rfc5987bis, jfv, parameters Julian Reschke

Friday, 22 July 2016

• Re: Defining First and Third Party Cookies Anne van Kesteren
• Re: Defining First and Third Party Cookies Julian Reschke

Wednesday, 20 July 2016

• Re: Frames that manipulate set-based peer state Mark Nottingham
• Re: Frames that manipulate set-based peer state Mark Nottingham
• Re: Defining First and Third Party Cookies Anne van Kesteren
• Re: obsoleting RFC6454? (was: Defining First and Third Party Cookies) jeff.hodges@kingsmountain.com
• Very brief notes from BC info meeting Göran Eriksson AP
• Re: Defining First and Third Party Cookies Julian Reschke

Tuesday, 19 July 2016

• RE: draft-montenegro-httpbis-h2ot-00 Gabriel Montenegro
• RE: Frames that manipulate set-based peer state Lucas Pardue
• Re: Frames that manipulate set-based peer state Kazuho Oku
• Re: Informal meeting on blind caching Göran Eriksson AP
• Re: Frames that manipulate set-based peer state Mark Nottingham
• Re: Frames that manipulate set-based peer state Martin Thomson
• Re: Frames that manipulate set-based peer state Martin Thomson
• Re: Frames that manipulate set-based peer state Patrick McManus
• Re: Frames that manipulate set-based peer state Mark Nottingham
• Re: Frames that manipulate set-based peer state Martin Thomson
• Re: Frames that manipulate set-based peer state Mark Nottingham
• Re: Frames that manipulate set-based peer state Martin Thomson
• Frames that manipulate set-based peer state Mark Nottingham

Monday, 18 July 2016

• Re: Precision of numbers using JSON Header Field Values Matthew Kerwin
• Re: Precision of numbers using JSON Header Field Values Matthew Kerwin
• Re: Informal meeting on blind caching Göran Eriksson AP
• Re: Informal meeting on blind caching Kevin Marks
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Calculation of the hash width in cache-digests Martin Thomson
• Re: Calculation of the hash width in cache-digests Kazuho Oku
• RE: Precision of numbers using JSON Header Field Values Mike Bishop
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Patrick McManus
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Calculation of the hash width in cache-digests Martin Thomson
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Willy Tarreau
• Re: Informal meeting on blind caching Göran Eriksson AP
• Re: Clearing cache digests Martin Thomson
• Re: Clearing cache digests Kazuho Oku
• Re: Clearing cache digests Mike West
• Re: Clearing cache digests Mark Nottingham
• Re: Clearing cache digests Martin Thomson
• RE: Clearing cache digests Mike Bishop
• Re: Clearing cache digests Eric Rescorla
• Re: Clearing cache digests Martin Thomson
• Clearing cache digests Eric Rescorla
• Comments on draft-ietf-httpbis-encryption-encoding-02 Eric Rescorla

Sunday, 17 July 2016

• Informal meeting on blind caching Martin Thomson
• draft-montenegro-httpbis-h2ot-00 emile.stephan@orange.com
• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Amos Jeffries
• Re: JSON headers in Vary ? Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• JSON headers in Vary ? Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Willy Tarreau

Saturday, 16 July 2016

• RE: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Mike Bishop
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Willy Tarreau
• Re: Precision of numbers using JSON Header Field Values Willy Tarreau

Friday, 15 July 2016

• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Patrick McManus
• Re: Precision of numbers using JSON Header Field Values Kazuho Oku
• Re: Precision of numbers using JSON Header Field Values Kazuho Oku
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Julian Reschke
• Re: Precision of numbers using JSON Header Field Values Poul-Henning Kamp
• Re: Precision of numbers using JSON Header Field Values Kazuho Oku
• Re: Precision of numbers using JSON Header Field Values Willy Tarreau
• Precision of numbers using JSON Header Field Values Kazuho Oku

Thursday, 14 July 2016

• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Roy T. Fielding
• Re: JSON headers Roy T. Fielding
• RE: draft-montenegro-httpbis-h2ot-00 question Gabriel Montenegro
• Re: draft-ietf-httpbis-cache-digest-00 comments Kazuho Oku
• Re: what constitutes an "invalid" content-length Willy Tarreau
• Re: draft-asilvas-http-push-assets-00 comments Martin Thomson

Wednesday, 13 July 2016

• Re: draft-montenegro-httpbis-h2ot-00 question Carsten Bormann
• Re: EXT: RE: draft-montenegro-httpbis-h2ot-00 question Simpson, Robby (GE Energy Connections)
• RE: draft-ruellan-http-accept-push-policy-02 comments RUELLAN Herve
• RE: draft-ruellan-http-accept-push-policy-02 comments RUELLAN Herve
• Re: draft-asilvas-http-push-assets-00 comments Aaron L. Silvas
• Re: draft-asilvas-http-push-assets-00 comments Aaron L. Silvas
• RE: draft-montenegro-httpbis-h2ot-00 question Gabriel Montenegro
• RE: draft-bishop-httpbis-extended-settings-00 comments Mike Bishop
• RE: draft-asilvas-http-push-assets-00 comments Mike Bishop
• Re: draft-asilvas-http-push-assets-00 comments Alcides Viamontes E
• Re: draft-asilvas-http-push-assets-00 comments Aaron L. Silvas
• Re: what constitutes an "invalid" content-length Patrick McManus
• Re: draft-bishop-httpbis-extended-settings-00 comments Cory Benfield
• Re: JSON headers - No: CBOR headers Poul-Henning Kamp
• Re: draft-ruellan-http-accept-push-policy-02 comments Stefan Eissing
• Re: draft-bishop-httpbis-extended-settings-00 comments Matthew Kerwin
• Re: draft-bishop-httpbis-extended-settings-00 comments Martin Thomson
• draft-ruellan-http-accept-push-policy-02 comments Martin Thomson
• Re: draft-bishop-httpbis-extended-settings-00 comments Matthew Kerwin
• draft-bishop-httpbis-extended-settings-00 comments Martin Thomson
• Re: JSON headers - No: CBOR headers Martin Thomson
• draft-ietf-httpbis-cache-digest-00 comments Martin Thomson
• Re: JSON headers - No: CBOR headers Carsten Bormann
• draft-asilvas-http-push-assets-00 comments Martin Thomson
• Re: what constitutes an "invalid" content-length Mark Nottingham
• draft-montenegro-httpbis-h2ot-00 question Martin Thomson

Tuesday, 12 July 2016

• Re: JSON headers - No: CBOR headers Martin Thomson
• Re: what constitutes an "invalid" content-length Adrien de Croy
• Re: what constitutes an "invalid" content-length Tim Bray
• Re: what constitutes an "invalid" content-length Willy Tarreau
• Re: what constitutes an "invalid" content-length Alex Rousskov
• Re: what constitutes an "invalid" content-length Adrien de Croy
• Re: what constitutes an "invalid" content-length Patrick McManus
• Re: JSON headers Willy Tarreau
• Re: JSON headers nicolas.mailhot@laposte.net
• what constitutes an "invalid" content-length Adrien de Croy
• Re: JSON headers Yanick Rochon
• Re: Call for Adoption: Cache Digests for HTTP/2 Alcides Viamontes E
• Re: JSON headers - No: CBOR headers Poul-Henning Kamp
• Re: Call for Adoption: Cache Digests for HTTP/2 Amos Jeffries
• Re: JSON headers Carsten Bormann
• Re: JSON headers Julian Reschke
• Re: JSON headers Amos Jeffries
• Re: JSON headers Martin J. Dürst
• Re: JSON headers Julian Reschke
• Re: JSON headers Carsten Bormann
• Re: JSON headers Julian Reschke
• Re: JSON headers Willy Tarreau
• Re: JSON headers Yanick Rochon
• Re: JSON headers Willy Tarreau

Monday, 11 July 2016

• Re: JSON headers Carsten Bormann
• Re: JSON headers Yanick Rochon
• Re: JSON headers Willy Tarreau
• Re: JSON headers Julian Reschke
• Re: JSON headers Willy Tarreau
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Yanick Rochon
• Re: JSON headers Poul-Henning Kamp
• Re: Remaining lifetime | Re: draft-ietf-httpbis-http2-encryption-06.txt Kari Hurtta
• Re: Call for Adoption: Cache Digests for HTTP/2 Kazuho Oku
• Re: Abbreviation form for HTTP JSON Header Field Values? Kazuho Oku
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Carsten Bormann
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Martin J. Dürst
• Re: JSON headers Cory Benfield
• Re: JSON headers Cory Benfield
• Re: JSON headers Julian Reschke
• Re: Abbreviation form for HTTP JSON Header Field Values? Poul-Henning Kamp
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Andy Green
• Re: Abbreviation form for HTTP JSON Header Field Values? Carsten Bormann
• Re: JSON headers Julian Reschke
• Re: JSON headers Mark Nottingham
• Re: JSON headers Andy Green
• Re: JSON headers Julian Reschke
• Re: JSON headers Julian Reschke
• Re: JSON headers Julian Reschke
• Re: Abbreviation form for HTTP JSON Header Field Values? Julian Reschke
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Poul-Henning Kamp
• Re: Remaining lifetime | Re: draft-ietf-httpbis-http2-encryption-06.txt Martin Thomson
• Re: Draft agenda for Berlin Mark Nottingham
• Re: JSON headers Andy Green
• Re: Abbreviation form for HTTP JSON Header Field Values? Martin Thomson
• Re: JSON headers Martin J. Dürst
• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Martin Thomson
• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Eric Rescorla

Sunday, 10 July 2016

• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Willy Tarreau
• Re: JSON headers Julian Reschke
• Re: JSON headers Yanick Rochon
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Julian Reschke

Saturday, 9 July 2016

• Re: JSON headers Phil Hunt (IDM)
• Re: JSON headers Kevin Marks
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Poul-Henning Kamp
• Re: JSON headers Tim Bray
• Re: JSON headers Cory Benfield

Friday, 8 July 2016

• Fwd: New Version Notification for draft-ietf-httpbis-cache-digest-00.txt Mark Nottingham
• I-D Action: draft-ietf-httpbis-cache-digest-00.txt internet-drafts@ietf.org
• Re: JSON headers Poul-Henning Kamp
• RE: Draft agenda for Berlin Gabriel Montenegro
• RE: JSON headers Mike Bishop
• I-D ACTION:draft-ietf-httpbis-rfc5987bis-02.txt Internet-Drafts@ietf.org
• Re: JSON headers Phil Hunt
• JSON headers Poul-Henning Kamp
• Re: Abbreviation form for HTTP JSON Header Field Values? Julian Reschke
• I-D Action: draft-ietf-httpbis-jfv-01.txt internet-drafts@ietf.org
• Call for Adoption: Cache Digests for HTTP/2 Natasha Rooney

Thursday, 7 July 2016

• RE: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Mike Bishop
• Re: http-push-assets | draft-asilvas-http-push-assets-00.txt Aaron L. Silvas
• RE: http-push-assets | draft-asilvas-http-push-assets-00.txt Lucas Pardue
• Re: Call for Adoption: Cache Digests for HTTP/2 Alcides Viamontes E
• Re: [Editorial Errata Reported] RFC7231 (4734) Mark Nottingham
• Re: I-D Action: draft-ietf-httpbis-cookie-prefixes-00.txt Matthew Kerwin
• Re: I-D Action: draft-ietf-httpbis-cookie-prefixes-00.txt Constantine A. Murenin

Wednesday, 6 July 2016

• http-push-assets | draft-asilvas-http-push-assets-00.txt Aaron L. Silvas
• Re: [Editorial Errata Reported] RFC7231 (4734) Martin J. Dürst
• Re: [Editorial Errata Reported] RFC7231 (4734) Julian Reschke
• [Editorial Errata Reported] RFC7231 (4734) RFC Errata System

Monday, 4 July 2016

• Re: Call for Adoption: Secondary Certificate Authentication in HTTP/2 Eric Rescorla
• http-opportunistic | draft-ietf-httpbis-http2-encryption-06 Kari hurtta
• Remaining lifetime | Re: draft-ietf-httpbis-http2-encryption-06.txt Kari Hurtta

Friday, 1 July 2016

• Re: TE request header deployment Poul-Henning Kamp
• Re: TE request header deployment Adrien de Croy
• Re: TE request header deployment Cory Benfield
• Re: TE request header deployment Roland Zink
• Re: TE request header deployment Daniel Stenberg
• Re: TE request header deployment Amos Jeffries
• Re: The "http-opportunistic" well-known URI | draft-ietf-httpbis-http2-encryption-06 Kari hurtta
• TE request header deployment Adrien de Croy

Last message date: Friday, 30 September 2016 21:17:14 UTC