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

Thursday, 31 December 2015

• RE: ABNF related feedback to: Re: AD review of draft-ietf-httpbis-alt-svc-10 Mike Bishop
• Re: AD review of draft-ietf-httpbis-alt-svc-10 Barry Leiba
• RE: AD review of draft-ietf-httpbis-alt-svc-10 Mike Bishop
• Re: ABNF related feedback to: Re: AD review of draft-ietf-httpbis-alt-svc-10 Barry Leiba
• ABNF related feedback to: Re: AD review of draft-ietf-httpbis-alt-svc-10 Julian Reschke
• Re: AD review of draft-ietf-httpbis-alt-svc-10 Barry Leiba
• Re: AD review of draft-ietf-httpbis-alt-svc-10 Julian Reschke
• [Errata Held for Document Update] RFC7541 (4574) RFC Errata System
• AD review of draft-ietf-httpbis-alt-svc-10 Barry Leiba
• [Technical Errata Reported] RFC7541 (4574) RFC Errata System

Monday, 28 December 2015

• Re: Brief History of Web Sessions (95/96) Amos Jeffries

Sunday, 27 December 2015

• Re: State | Re: Calls for Adoption -- Cookie-Related Specifications Kari Hurtta

Friday, 25 December 2015

• Re: Brief History of Web Sessions (95/96) Ryan Hamilton

Thursday, 24 December 2015

• I-D Action: draft-ietf-httpbis-encryption-encoding-00.txt internet-drafts@ietf.org

Wednesday, 23 December 2015

• Re: State | Re: Calls for Adoption -- Cookie-Related Specifications Poul-Henning Kamp
• RE: Brief History of Web Sessions (95/96) Dave Wain
• State | Re: Calls for Adoption -- Cookie-Related Specifications Kari Hurtta
• Re: Calls for Adoption -- Cookie-Related Specifications Martin Thomson
• Re: Calls for Adoption -- Cookie-Related Specifications Mike West
• Re: Harmonizing draft-west-cookie-prefixes-05 with the web origin concept Willy Tarreau
• Harmonizing draft-west-cookie-prefixes-05 with the web origin concept Adam Barth
• considerations for draft-west-leave-secure-cookies-alone-04 Adam Barth
• Re: Calls for Adoption -- Cookie-Related Specifications Martin Thomson
• RE: Brief History of Web Sessions (95/96) Mike Bishop

Tuesday, 22 December 2015

• Brief History of Web Sessions (95/96) Dave Wain
• Re: Calls for Adoption -- Cookie-Related Specifications Remy Lebeau
• Re: Range requests (information only) Dave Wain
• Re: Protocol Action: 'An HTTP Status Code to Report Legal Obstacles' to Proposed Standard (draft-ietf-httpbis-legally-restricted-status-04.txt) Barry Leiba
• Re: Protocol Action: 'An HTTP Status Code to Report Legal Obstacles' to Proposed Standard (draft-ietf-httpbis-legally-restricted-status-04.txt) Virgil Griffith
• Re: Calls for Adoption -- Cookie-Related Specifications Mike West
• Re: Range requests (information only) Matthew Kerwin
• Range requests (information only) Dave Wain
• Re: Calls for Adoption -- Cookie-Related Specifications Poul-Henning Kamp
• Re: Calls for Adoption -- Cookie-Related Specifications Amos Jeffries
• Re: Calls for Adoption -- Cookie-Related Specifications Willy Tarreau
• Re: Calls for Adoption -- Cookie-Related Specifications Cory Benfield
• Re: Range requests and content encoding Julian Reschke
• Re: Calls for Adoption -- Cookie-Related Specifications Daniel Stenberg
• Calls for Adoption -- Cookie-Related Specifications Mark Nottingham
• Re: Call for Adoption: Encrypted Content Encoding Mark Nottingham
• Re: Range requests and content encoding Matthew Kerwin
• Re: Range requests and content encoding Mark Nottingham
• RE: Range requests and content encoding Mike Bishop
• Range requests and content encoding Martin Thomson

Monday, 21 December 2015

• Re: Using SRV records with a http Web Service Erik Nygren
• Protocol Action: 'An HTTP Status Code to Report Legal Obstacles' to Proposed Standard (draft-ietf-httpbis-legally-restricted-status-04.txt) The IESG

Saturday, 19 December 2015

• Re: Using SRV records with a http Web Service Glen Knowles

Friday, 18 December 2015

• HTTP using broadcast response Dave Wain
• Re: I-D Action: draft-ietf-httpbis-http2-encryption-03.txt Martin Thomson
• I-D Action: draft-ietf-httpbis-http2-encryption-03.txt internet-drafts@ietf.org
• Re: Using SRV records with a http Web Service Benjamin Carlyle

Thursday, 17 December 2015

• Re: HTTP/2.0 independent of TCP/IP Martin Thomson
• Re: Using SRV records with a http Web Service Phillip Hallam-Baker
• Re: HTTP/2.0 independent of TCP/IP Daniel Stenberg
• HTTP/2.0 independent of TCP/IP Dave Wain

Monday, 14 December 2015

• Re: [Moderator Action] Alissa Cooper's Yes on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Spencer Dawkins at IETF

Tuesday, 15 December 2015

• Joel Jaeggli's No Objection on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Joel Jaeggli

Wednesday, 16 December 2015

• Brian Haberman's No Objection on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Brian Haberman
• Benoit Claise's No Objection on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Benoit Claise
• Re: Benoit Claise's No Objection on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Barry Leiba
• Re: Alt-Svc WGLC Julian Reschke

Tuesday, 15 December 2015

• Re: Using SRV records with a http Web Service Patrick McManus
• Using SRV records with a http Web Service Phillip Hallam-Baker
• Re: Alt-Svc WGLC Hervé Ruellan
• Re: Alt-Svc WGLC Julian Reschke
• I-D Action: draft-ietf-httpbis-alt-svc-10.txt internet-drafts@ietf.org
• Re: Alt-Svc WGLC Mark Nottingham

Monday, 14 December 2015

• Re: Alissa Cooper's Yes on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Ted Hardie
• Alt-Svc WGLC Julian Reschke
• Re: alt svc issue #126 clarify invalidation rules wrt altsvc frame Julian Reschke

Sunday, 13 December 2015

• Re: alt svc issue #126 clarify invalidation rules wrt altsvc frame Martin Thomson
• Alissa Cooper's Yes on draft-ietf-httpbis-legally-restricted-status-04: (with COMMENT) Alissa Cooper
• Re: alt-svc WG Last Call comments Julian Reschke
• alt svc issue #126 clarify invalidation rules wrt altsvc frame Julian Reschke
• alt svc issue #125 alternative of alternatives vs invalidation Julian Reschke

Thursday, 10 December 2015

• Re: alt-svc WG Last Call comments Martin Thomson
• alt-svc WG Last Call comments Julian Reschke

Wednesday, 9 December 2015

• RE: Last Calls Lucas Pardue

Tuesday, 8 December 2015

• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson
• Re: Alt-Svc WG Last Call comment https://github.com/httpwg/http-extensions/issues/121 Julian Reschke
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear

Monday, 7 December 2015

• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: Browsers and .onion names Stuart Cheshire
• Finishing up the "SSL/TLS everywhere fail" Mark Nottingham
• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson
• RE: SSL/TLS everywhere fail Piotr Galecki
• Re: SSL/TLS everywhere fail Paul Wouters
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Martin Thomson
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Stefan Eissing
• Re: SSL/TLS everywhere fail Eliot Lear
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Maxthon Chan
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Maxthon Chan
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Phil Hunt
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Stephen Farrell

Sunday, 6 December 2015

• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Amos Jeffries
• Re: SSL/TLS everywhere fail Mark Nottingham

Saturday, 5 December 2015

• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Patrick McManus
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson
• Re: SSL/TLS everywhere fail Werner Baumann
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Zhong Yu
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Alex Rousskov
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Alex Rousskov
• Re: SSL/TLS everywhere fail Mark Nottingham
• Re: SSL/TLS everywhere fail Mark Nottingham
• Re: SSL/TLS everywhere fail Ted Hardie
• Re: SSL/TLS everywhere fail Mark Nottingham
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Mark Nottingham
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp

Friday, 4 December 2015

• Re: draft-west-cookie-prefixes-05 comments Eitan Adler
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Martin Thomson
• Re: SSL/TLS everywhere fail Alex Rousskov
• RE: Call for Adoption: Encrypted Content Encoding Martin Thomson
• Re: SSL/TLS everywhere fail Ted Hardie
• RE: Call for Adoption: Encrypted Content Encoding Mike Bishop
• Re: Last Calls Hervé Ruellan
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: SSL/TLS everywhere fail Constantine A. Murenin
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Werner Baumann
• Re: draft-west-cookie-prefixes-05 comments Mike West
• Re: draft-west-cookie-prefixes-05 comments Martin Thomson
• Re: Call for Adoption: Encrypted Content Encoding Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: draft-west-cookie-prefixes-05 comments Matthew Kerwin
• Re: SSL/TLS everywhere fail Martin Thomson
• Re: SSL/TLS everywhere fail Martin Thomson
• Re: draft-west-cookie-prefixes-05 comments Martin Thomson
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Mike Belshe
• Re: Call for Adoption: Encrypted Content Encoding Grahame Grieve
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Alex Rousskov
• Re: SSL/TLS everywhere fail Ted Hardie
• Re: SSL/TLS everywhere fail Jacob Appelbaum

Thursday, 3 December 2015

• RE: SSL/TLS everywhere fail Piotr Galecki
• RE: Call for Adoption: Encrypted Content Encoding Mike Bishop
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Alex Rousskov
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Matthew Kerwin
• Re: SSL/TLS everywhere fail Adrien de Croy
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Alex Rousskov
• Re: SSL/TLS everywhere fail Robert Collins
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Roland Zink
• Re: SSL/TLS everywhere fail Cory Benfield
• Re: SSL/TLS everywhere fail Jacob Appelbaum
• Re: SSL/TLS everywhere fail Mike Belshe
• Re: SSL/TLS everywhere fail Stephen Farrell
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Mike Belshe
• Re: draft-west-cookie-prefixes-05 comments Eitan Adler
• Re: draft-west-cookie-prefixes-05 comments Mike West
• Re: SSL/TLS everywhere fail Poul-Henning Kamp
• Re: SSL/TLS everywhere fail Constantine A. Murenin
• Re: SSL/TLS everywhere fail Amos Jeffries
• Re: SSL/TLS everywhere fail Walter H.
• Re: SSL/TLS everywhere fail Willy Tarreau
• Re: SSL/TLS everywhere fail Matthew Kerwin
• Re: SSL/TLS everywhere fail Martin J. Dürst
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• draft-west-cookie-prefixes-05 comments Eitan Adler

Wednesday, 2 December 2015

• Re: SSL/TLS everywhere fail Willy Tarreau
• SSL/TLS everywhere fail Poul-Henning Kamp
• Re: Call for Adoption: Encrypted Content Encoding Mark Nottingham
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding John Mattsson
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• RE: Alt-Svc WG Last Call comment https://github.com/httpwg/http-extensions/issues/121 Lucas Pardue

Tuesday, 1 December 2015

• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Kyle Rose
• Re: Call for Adoption: Encrypted Content Encoding Kyle Rose
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Kyle Rose
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Julian Reschke
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Julian Reschke
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Last Calls Martin Thomson
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink

Monday, 30 November 2015

• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Browsers and .onion names Adrien de Croy
• Re: Browsers and .onion names Alex Rousskov
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: Call for Adoption: Encrypted Content Encoding Roland Zink
• Re: Call for Adoption: Encrypted Content Encoding Eliot Lear
• Re: Call for Adoption: Encrypted Content Encoding John Mattsson
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Browsers and .onion names Matthew Kerwin

Sunday, 29 November 2015

• Applications and special use domain names | Re: Browsers and .onion names Kari Hurtta

Monday, 30 November 2015

• Re: Browsers and .onion names Cory Benfield
• Re: Browsers and .onion names Eliot Lear
• Re: Call for Adoption: Encrypted Content Encoding John Mattsson
• Re: Browsers and .onion names Alex Rousskov
• Re: Browsers and .onion names Amos Jeffries
• Re: Browsers and .onion names Adrien de Croy

Sunday, 29 November 2015

• Re: Browsers and .onion names Eliot Lear
• Re: Browsers and .onion names Eliot Lear
• Re: Browsers and .onion names Richard Hartmann
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Browsers and .onion names Mark Nottingham
• Re: Browsers and .onion names Cory Benfield
• Re: Browsers and .onion names Amos Jeffries
• Re: Browsers and .onion names Amos Jeffries
• Re: Browsers and .onion names Alex Rousskov

Saturday, 28 November 2015

• Re: Browsers and .onion names Mark Nottingham
• Re: Browsers and .onion names Adrien de Croy
• Re: Browsers and .onion names Willy Tarreau
• Re: Browsers and .onion names Willy Tarreau
• Re: Last Calls Mark Nottingham
• Alt-Svc WG Last Call comment https://github.com/httpwg/http-extensions/issues/121 Julian Reschke
• Re: Browsers and .onion names Cory Benfield
• Re: Browsers and .onion names Jacob Appelbaum
• Re: Browsers and .onion names Willy Tarreau
• Re: Browsers and .onion names Jacob Appelbaum
• Last Calls Julian Reschke
• Re: Browsers and .onion names Willy Tarreau
• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson

Friday, 27 November 2015

• Re: Browsers and .onion names Mark Nottingham
• Re: Revising RFC6265 ("Cookies") Mike West
• Re: Browsers and .onion names Cory Benfield
• Re: Browsers and .onion names Willy Tarreau
• Re: Call for Adoption: Encrypted Content Encoding Walter H.
• Re: Browsers and .onion names Walter H.
• Re: Browsers and .onion names Mark Nottingham
• Re: Browsers and .onion names Mark Baker
• Re: Browsers and .onion names Mark Nottingham

Thursday, 26 November 2015

• Re: Browsers and .onion names Mark Nottingham
• Re: Browsers and .onion names Mark Baker
• Re: Browsers and .onion names Jacob Appelbaum
• Re: Browsers and .onion names Willy Tarreau
• Browsers and .onion names Mark Nottingham

Wednesday, 25 November 2015

• Re: Call for Adoption: Encrypted Content Encoding Martin Thomson
• Re: Call for Adoption: Encrypted Content Encoding Cory Benfield
• Re: Call for Adoption: Encrypted Content Encoding Amos Jeffries
• Re: Call for Adoption: Encrypted Content Encoding John Mattsson
• Re: Call for Adoption: Encrypted Content Encoding Willy Tarreau
• Call for Adoption: Encrypted Content Encoding Mark Nottingham
• I-D Action: draft-ietf-httpbis-client-hints-00.txt internet-drafts@ietf.org

Tuesday, 24 November 2015

• Re: Call for Adoption: draft-grigorik-http-client-hints Ilya Grigorik
• Re: Call for Adoption: draft-grigorik-http-client-hints Mark Nottingham

Friday, 20 November 2015

• Last Call: <draft-ietf-httpbis-legally-restricted-status-04.txt> (An HTTP Status Code to Report Legal Obstacles) to Proposed Standard The IESG
• AD review of draft-ietf-httpbis-legally-restricted-status-04 Barry Leiba
• Re: Proposed 5xx status code for WebPush Mark Nottingham
• Re: Proposed 5xx status code for WebPush Amos Jeffries

Thursday, 19 November 2015

• [Errata Held for Document Update] RFC7540 (4535) RFC Errata System
• HTTP response includes request Dave Wain
• Re: Proposed 5xx status code for WebPush Martin Thomson
• Re: Proposed 5xx status code for WebPush Cyrus Daboo
• Re: Proposed 5xx status code for WebPush c^
• Proposed 5xx status code for WebPush Brian Raymor
• Working Group Last Call: HTTP Alternative Services Mark Nottingham

Wednesday, 18 November 2015

• Re: [Technical Errata Reported] RFC7540 (4535) Martin Thomson
• Re: [Technical Errata Reported] RFC7540 (4535) Barry Leiba

Tuesday, 17 November 2015

• Re: [Technical Errata Reported] RFC7540 (4535) Yoav Nir
• RE: [Technical Errata Reported] RFC7540 (4535) Mike Bishop
• Re: [Technical Errata Reported] RFC7540 (4535) Martin Thomson
• [Technical Errata Reported] RFC7540 (4535) RFC Errata System
• Re: Getting draft-ietf-httpbis-alt-svc to Working Group Last Call Julian Reschke
• I-D Action: draft-ietf-httpbis-alt-svc-09.txt internet-drafts@ietf.org

Monday, 16 November 2015

• Re: Request header in response Florian Best
• RE: Streams after receiving GOAWAY Mike Bishop
• Re: Streams after receiving GOAWAY Stefan Eissing
• Re: Streams after receiving GOAWAY Amos Jeffries
• Re: Streams after receiving GOAWAY Willy Tarreau
• Re: Streams after receiving GOAWAY Eitan Adler

Sunday, 15 November 2015

• Re: Streams after receiving GOAWAY Matthew Kerwin
• Re: Streams after receiving GOAWAY Glen Knowles
• Re: Streams after receiving GOAWAY Cory Benfield
• Re: Request header in response Florian Best
• Re: Streams after receiving GOAWAY Glen Knowles
• Re: Request header in response Florian Best
• Re: Streams after receiving GOAWAY Patrick McManus
• Request header in response Dave Wain
• Re: Streams after receiving GOAWAY Cory Benfield
• Streams after receiving GOAWAY Glen Knowles

Saturday, 14 November 2015

• Re: Revising RFC6265 ("Cookies") Willy Tarreau

Friday, 13 November 2015

• Re: Revising RFC6265 ("Cookies") Mark Nottingham
• Re: Revising RFC6265 ("Cookies") Martin Thomson
• Re: Revising RFC6265 ("Cookies") Hodges, Jeff
• Re: Revising RFC6265 ("Cookies") Cory Benfield
• Re: Revising RFC6265 ("Cookies") Daniel Stenberg
• Re: Revising RFC6265 ("Cookies") Amos Jeffries
• Revising RFC6265 ("Cookies") Mark Nottingham

Thursday, 12 November 2015

• Getting draft-ietf-httpbis-alt-svc to Working Group Last Call Julian Reschke
• #106: Policy for Key parameter registry Mark Nottingham

Tuesday, 10 November 2015

• I-D Action: draft-ietf-httpbis-legally-restricted-status-04.txt internet-drafts@ietf.org

Monday, 9 November 2015

• Re: Feedback about stale-while-revalidate Mark Nottingham

Sunday, 8 November 2015

• Re: TCP Tuning for HTTP c^

Saturday, 7 November 2015

• Re: TCP Tuning for HTTP Daniel Stenberg

Friday, 6 November 2015

• RE: TCP Tuning for HTTP Scharf, Michael (Michael)
• Re: TCP Tuning for HTTP Cory Benfield
• TCP Tuning for HTTP Daniel Stenberg
• I-D Action: draft-ietf-httpbis-legally-restricted-status-03.txt internet-drafts@ietf.org

Thursday, 5 November 2015

• Re: DRAFT minutes for Yokohama Cory Benfield
• Re: DRAFT minutes for Yokohama Mark Nottingham
• Re: DRAFT minutes for Yokohama Cory Benfield
• Re: DRAFT minutes for Yokohama Stefan Eissing
• Re: DRAFT minutes for Yokohama Willy Tarreau
• Re: DRAFT minutes for Yokohama Barry Leiba
• DRAFT minutes for Yokohama Mark Nottingham
• Re: http/2 and TLS security Martin Thomson
• Re: http/2 and TLS security Patrick McManus

Wednesday, 4 November 2015

• Re: http/2 and TLS security Francisco Moraes
• Re: http/2 and non-safe http methods Willy Tarreau
• RFC 7694 on Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding rfc-editor@rfc-editor.org
• Re: http/2 and non-safe http methods James M Snell
• Re: http/2 and TLS security Patrick McManus
• Re: http/2 and non-safe http methods Patrick McManus
• Re: http/2 and non-safe http methods Martin Thomson

Tuesday, 3 November 2015

• RE: http/2 and TLS security Mike Bishop
• http/2 and non-safe http methods James M Snell
• Re: http/2 and TLS security Cory Benfield
• http/2 and TLS security Francisco Moraes
• Re: can h2 extension frames carry data? Willy Tarreau
• Re: can h2 extension frames carry data? Cory Benfield
• Re: can h2 extension frames carry data? Willy Tarreau
• RE: can h2 extension frames carry data? Mike Bishop
• Re: can h2 extension frames carry data? Matthew Kerwin
• Re: can h2 extension frames carry data? Amos Jeffries

Monday, 2 November 2015

• Re: can h2 extension frames carry data? Matthew Kerwin
• Re: can h2 extension frames carry data? Cory Benfield
• RE: can h2 extension frames carry data? Mike Bishop
• draft-ietf-httpbis-cice-03 in AUTH48, was: Protocol Action: 'Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding' to Proposed Standard (draft-ietf-httpbis-cice-03.txt) Julian Reschke
• can h2 extension frames carry data? Matthew Kerwin

Sunday, 1 November 2015

• Virtual Queue for httpbis Remote Attendees Alexa Morris

Thursday, 29 October 2015

• Re: Feedback about stale-while-revalidate Kenji Baheux

Wednesday, 28 October 2015

• Re: Http/2 Traffic generator Vimala Tadepalli
• Re: Report on preliminary decision on TLS 1.3 and client auth Yoav Nir
• Re: Feedback about stale-while-revalidate Amos Jeffries
• RE: Http/2 Traffic generator Lucas Pardue
• Feedback about stale-while-revalidate Kenji Baheux
• Re: Http/2 Traffic generator Cory Benfield

Tuesday, 27 October 2015

• Http/2 Traffic generator Vimala Tadepalli
• Re: Accept Push Policy draft Hervé Ruellan
• Re: Accept Push Policy draft Cory Benfield

Monday, 26 October 2015

• RE: Report on preliminary decision on TLS 1.3 and client auth Mike Bishop
• Accept Push Policy draft Hervé Ruellan
• Re: Report on preliminary decision on TLS 1.3 and client auth Yoav Nir
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Tim Bray

Friday, 23 October 2015

• Re: Clarification of dynamic table size change Ilari Liusvaara
• Re: Clarification of dynamic table size change Tatsuhiro Tsujikawa

Thursday, 22 October 2015

• Re: Report on preliminary decision on TLS 1.3 and client auth Kyle Rose
• Re: Report on preliminary decision on TLS 1.3 and client auth Martin Thomson
• Re: Report on preliminary decision on TLS 1.3 and client auth Kyle Rose
• Re: draft-west-leave-secure-cookies-alone Martin Thomson
• Re: Clarification of dynamic table size change Hervé Ruellan
• Re: draft-west-leave-secure-cookies-alone Willy Tarreau
• Re: draft-west-leave-secure-cookies-alone Mike West
• Re: draft-west-leave-secure-cookies-alone Willy Tarreau

Wednesday, 21 October 2015

• draft-west-leave-secure-cookies-alone Martin Thomson

Tuesday, 20 October 2015

• Re: Report on preliminary decision on TLS 1.3 and client auth Martin Thomson
• Re: Report on preliminary decision on TLS 1.3 and client auth Martin Thomson
• Re: Report on preliminary decision on TLS 1.3 and client auth Jason T. Greene
• Yokohama drafts Mark Nottingham
• Re: Report on preliminary decision on TLS 1.3 and client auth Ilari Liusvaara

Monday, 19 October 2015

• Re: Report on preliminary decision on TLS 1.3 and client auth Martin Thomson
• Re: Clarification of dynamic table size change Cory Benfield
• Re: Clarification of dynamic table size change Tatsuhiro Tsujikawa
• Re: Clarification of dynamic table size change Cory Benfield
• Clarification of dynamic table size change Tatsuhiro Tsujikawa
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham
• I-D Action: draft-ietf-httpbis-key-00.txt internet-drafts@ietf.org
• Re: Call for Adoption: draft-fielding-http-key Mark Nottingham

Saturday, 17 October 2015

• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Krzysztof Jurewicz

Friday, 16 October 2015

• Re: alpn + ciphers Martin Thomson
• Re: h2 ciphers Amos Jeffries
• Re: h2 ciphers Stefan Eissing
• Re: h2 ciphers Stefan Eissing
• Re: h2 ciphers Julien Vehent
• Re: alpn + ciphers Stefan Eissing
• Re: h2 ciphers Amos Jeffries
• Re: alpn + ciphers Ilari Liusvaara
• Re: h2 ciphers Ilari Liusvaara
• alpn + ciphers Stefan Eissing
• h2 ciphers Stefan Eissing

Wednesday, 14 October 2015

• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham

Tuesday, 13 October 2015

• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Matthew Kerwin
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov
• Re: [Moderator Action] Range Responses of Indeterminate Length: Draft Amos Jeffries
• RE: Range Responses of Indeterminate Length: Draft K.Morgan@iaea.org
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Amos Jeffries
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Matthew Kerwin
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham

Friday, 9 October 2015

• New Version Notification for draft-benfield-http2-p2p-02.txt Cory Benfield

Thursday, 8 October 2015

• RE: Alt-svc and CORS Christer Holmberg
• Re: Alt-svc and CORS Martin J. Dürst

Wednesday, 7 October 2015

• Re: Alt-svc and CORS Patrick McManus
• RE: Alt-svc and CORS Christer Holmberg
• Re: Alt-svc and CORS Julian Reschke
• Re: Alt-svc and CORS Martin Thomson
• Re: Alt-svc and CORS Julian Reschke
• Alt-svc and CORS Christer Holmberg
• Re: Adjustments to our work mode - please read Mark Nottingham
• Re: Adjustments to our work mode - please read Eliot Lear (elear)
• Re: Adjustments to our work mode - please read Eliot Lear (elear)

Tuesday, 6 October 2015

• Re: Adjustments to our work mode - please read Eliot Lear (elear)

Wednesday, 7 October 2015

• Re: Adjustments to our work mode - please read Barry Leiba
• Re: Adjustments to our work mode - please read Mark Nottingham
• Re: Adjustments to our work mode - please read Mark Nottingham

Tuesday, 6 October 2015

• RE: Adjustments to our work mode - please read Mike Bishop
• Process experiements (was Adjustments to our work mode - please read) Ted Hardie
• Re: Adjustments to our work mode - please read Ted Hardie
• Re: Call for Adoption: draft-fielding-http-key Ilya Grigorik
• Re: Adjustments to our work mode - please read Eliot Lear (elear)
• Re: Call for Adoption: draft-fielding-http-key Willy Tarreau
• Re: Adjustments to our work mode - please read Eliot Lear (elear)
• Re: Call for Adoption: draft-fielding-http-key Leif Hedstrom
• Re: Call for Adoption: draft-fielding-http-key Yoav Weiss
• Re: Call for Adoption: draft-fielding-http-key Julian Reschke
• Re: Adjustments to our work mode - please read Willy Tarreau
• Re: Adjustments to our work mode - please read Mark Nottingham

Monday, 5 October 2015

• Re: Adjustments to our work mode - please read Brian Smith
• Re: Adjustments to our work mode - please read Mark Nottingham
• Re: Adjustments to our work mode - please read Jason Greene
• Re: Adjustments to our work mode - please read Eliot Lear (elear)
• Adjustments to our work mode - please read Mark Nottingham

Saturday, 3 October 2015

• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Julian Reschke

Friday, 2 October 2015

• Re: NEW PREFERENCE - return=query-result Ning Dong
• Re: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons Kari Hurtta
• I-D Action: draft-ietf-httpbis-rfc5987bis-00.txt internet-drafts@ietf.org
• Re: Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: Range Responses of Indeterminate Length: Draft Plex
• Re: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons Tim Bray
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham

Thursday, 1 October 2015

• Re: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons Ted Hardie
• Re: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons Kari Hurtta
• Re: Yokohama Martin Thomson
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov
• Re: Call for Adoption: draft-fielding-http-key Amos Jeffries
• Re: Call for Adoption: draft-reschke-rfc54987bis Amos Jeffries
• Difffent ways to authenticate (Was: Re: Report on preliminary decision on TLS 1.3 and client auth) Ilari Liusvaara
• RFC 2617 ("HTTP Authentication: Basic and Digest Access Authentication") is obsolete Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc5987bis, was: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc5987bis, was: Call for Adoption: draft-reschke-rfc54987bis Poul-Henning Kamp
• Call for Adoption: draft-reschke-rfc5987bis, was: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Yokohama Mark Nottingham
• Re: Call for Adoption: draft-reschke-rfc54987bis Poul-Henning Kamp
• Re: Call for Adoption: draft-reschke-rfc54987bis Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham
• Call for Adoption: draft-fielding-http-key Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Mark Nottingham
• Re: Working Group Last Call for draft-ietf-httpbis-legally-restricted-status Alex Rousskov

Last message date: Thursday, 31 December 2015 17:55:03 UTC