ietf-http-wg@w3.org from January to March 2017 by date

Thursday, 30 March 2017

Reminder: HTTPbis WG meeting Friday, March 31, 14:00 UTC Julian Reschke
Re: Position of HPACK Dynamic Table Size Update Cory Benfield
Re: 103 (Early Hints) vs. response headers Stefan Eissing

Wednesday, 29 March 2017

Re: 103 (Early Hints) vs. response headers Kazuho Oku
I-D Action: draft-ietf-httpbis-early-hints-01.txt internet-drafts@ietf.org
RE: Position of HPACK Dynamic Table Size Update Mike Bishop
Re: Alt-Svc special value "clear" clarification Ryan Hamilton
Re: Alt-Svc special value "clear" clarification Patrick McManus
Re: Alt-Svc special value "clear" clarification Samuel Hurst
Position of HPACK Dynamic Table Size Update Tatsuhiro Tsujikawa
Re: Alt-Svc special value "clear" clarification Patrick McManus
Alt-Svc special value "clear" clarification Samuel Hurst
Re: draft-ietf-httpbis-encryption-encoding-08, Relaxing UTF-8 requirement for `keyid` Julian Reschke

Thursday, 23 March 2017

draft-ietf-httpbis-encryption-encoding-08, Relaxing UTF-8 requirement for `keyid` Kit Cambridge

Tuesday, 28 March 2017

Re: Is a payload always a representation? Yi, EungJun

Monday, 27 March 2017

Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: Is a payload always a representation? Roy T. Fielding
Is a payload always a representation? Yi, EungJun

Saturday, 25 March 2017

Re: draft-ietf-httpbis-encryption-encoding-08, Relaxing UTF-8 requirement for `keyid` Martin Thomson

Thursday, 23 March 2017

Last Call: <draft-ietf-httpbis-encryption-encoding-08.txt> (Encrypted Content-Encoding for HTTP) to Proposed Standard The IESG

Monday, 20 March 2017

Document Action: 'Opportunistic Security for HTTP/2' to Experimental RFC (draft-ietf-httpbis-http2-encryption-11.txt) The IESG
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Mark Nottingham

Sunday, 19 March 2017

Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Cyrus Daboo
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Werner Baumann
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: since we've met last time mike
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Michael Sweet
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Michael Douglass
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Amos Jeffries

Saturday, 18 March 2017

Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Cyrus Daboo
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Walter H.
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch

Friday, 17 March 2017

I-D Action: draft-ietf-httpbis-http2-encryption-11.txt internet-drafts@ietf.org
Re: 103 (Early Hints) vs. response headers Mark Nottingham

Thursday, 16 March 2017

Re: 103 (Early Hints) vs. response headers Stefan Eissing
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Re: 103 (Early Hints) vs. response headers Willy Tarreau
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Stephen Farrell's Yes on draft-ietf-httpbis-http2-encryption-10: (with COMMENT) Stephen Farrell
FYI: Browser caching tests Mark Nottingham
Re: Ben Campbell's Yes on draft-ietf-httpbis-http2-encryption-10: (with COMMENT) Ben Campbell
Re: Ben Campbell's Yes on draft-ietf-httpbis-http2-encryption-10: (with COMMENT) Martin Thomson
Ben Campbell's Yes on draft-ietf-httpbis-http2-encryption-10: (with COMMENT) Ben Campbell

Wednesday, 15 March 2017

RE: Comments on draft-montenegro-httpbis-h2ot-profile-00 Gabriel Montenegro
Re: draft-ietf-httpbis-encryption-encoding-08, "6.1. Normative References" Julian Reschke
Re: draft-ietf-httpbis-encryption-encoding-08, "6.1. Normative References" Martin Thomson
Re: New Version Notification for draft-vkrasnov-h2-compression-dictionaries-02.txt Vlad Krasnov
Re: draft-ietf-httpbis-encryption-encoding-08, "6.1. Normative References" Amos Jeffries
Re: I-D Action: draft-ietf-httpbis-immutable-01.txt Amos Jeffries
Re: on HTTP/QUIC and HTTPBis Willy Tarreau
Re: 103 (Early Hints) vs. response headers Willy Tarreau
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Re: HTTPBis Agenda for Chicago IETF 98 Patrick McManus

Tuesday, 14 March 2017

Re: HTTPBis Agenda for Chicago IETF 98 Martin Thomson
HTTPBis Agenda for Chicago IETF 98 Patrick McManus
Re: on HTTP/QUIC and HTTPBis Patrick McManus
Re: on HTTP/QUIC and HTTPBis Stefan Eissing
Comments on draft-montenegro-httpbis-h2ot-profile-00 Martin Thomson

Monday, 13 March 2017

RE: on HTTP/QUIC and HTTPBis Mike Bishop
RE: on HTTP/QUIC and HTTPBis Mike Bishop
I-D Action: draft-ietf-httpbis-immutable-01.txt internet-drafts@ietf.org
Re: draft-ietf-httpbis-encryption-encoding-08, "6.1. Normative References" Martin Thomson

Sunday, 12 March 2017

Re: on HTTP/QUIC and HTTPBis Adrien de Croy
Re: on HTTP/QUIC and HTTPBis Adrien de Croy

Saturday, 11 March 2017

draft-ietf-httpbis-encryption-encoding-08, "6.1. Normative References" Julian Reschke
Re: on HTTP/QUIC and HTTPBis Stefan Eissing
Re: on HTTP/QUIC and HTTPBis Poul-Henning Kamp
Re: on HTTP/QUIC and HTTPBis Poul-Henning Kamp
Re: on HTTP/QUIC and HTTPBis Patrick McManus
Re: on HTTP/QUIC and HTTPBis Patrick McManus
RE: on HTTP/QUIC and HTTPBis Mike Bishop
RE: on HTTP/QUIC and HTTPBis Mike Bishop

Friday, 10 March 2017

Re: on HTTP/QUIC and HTTPBis Alex Rousskov
Re: on HTTP/QUIC and HTTPBis Willy Tarreau
Re: on HTTP/QUIC and HTTPBis Poul-Henning Kamp
on HTTP/QUIC and HTTPBis Patrick McManus
RE: HTTP/QUIC Diverging from HTTP/2 Mike Bishop
RE: HTTP/QUIC Diverging from HTTP/2 Lucas Pardue
Re: HTTP/QUIC Diverging from HTTP/2 Cory Benfield
Re: HTTP/QUIC Diverging from HTTP/2 Daniel Stenberg
Re: HTTP/QUIC Diverging from HTTP/2 Poul-Henning Kamp
Re: HTTP/QUIC Diverging from HTTP/2 Ryan Hamilton
Re: HTTP/QUIC Diverging from HTTP/2 Andy Green
Re: HTTP/QUIC Diverging from HTTP/2 Adrien de Croy
Re: HTTP/QUIC Diverging from HTTP/2 Martin Thomson
Re: HTTP/QUIC Diverging from HTTP/2 Adrien de Croy
Re: HTTP/QUIC Diverging from HTTP/2 Eric Rescorla
RE: HTTP/QUIC Diverging from HTTP/2 Mike Bishop

Thursday, 9 March 2017

RE: HTTP/QUIC Diverging from HTTP/2 Mike Bishop
Re: HTTP/QUIC Diverging from HTTP/2 Alcides Viamontes E
HTTP/QUIC Diverging from HTTP/2 Mike Bishop

Wednesday, 8 March 2017

Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Cyrus Daboo
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Martin J. Dürst
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Martin J. Dürst
I-D Action: draft-ietf-httpbis-rand-access-live-00.txt internet-drafts@ietf.org

Tuesday, 7 March 2017

Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Mark Nottingham
RE: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Michael Thornburgh
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
RE: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Michael Thornburgh
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Wesley Oliver
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding nicolas.mailhot@laposte.net
Re: Fwd: New Version Notification - draft-ietf-httpbis-encryption-encoding-08.txt Julian Reschke
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Joe Touch
Re: 2017-03-06- UTC, TImeZone, DayLight Saving Shifts, Enconding Wesley Oliver
Re: [Editorial Errata Reported] RFC7232 (4957) Mark Nottingham

Monday, 6 March 2017

Friday, 17 February 2017

Re: The future of forward proxy servers in an http/2 over TLS world Tom Bergan

Monday, 6 March 2017

Re: [Editorial Errata Reported] RFC7232 (4957) Mark Nottingham
[Editorial Errata Reported] RFC7232 (4957) RFC Errata System

Sunday, 5 March 2017

Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy

Saturday, 4 March 2017

Re: Why should caches and intermediaries ignore If-Match? Tom Bergan
Re: Why should caches and intermediaries ignore If-Match? Roy T. Fielding

Friday, 3 March 2017

Re: Why should caches and intermediaries ignore If-Match? Tom Bergan
Re: Why should caches and intermediaries ignore If-Match? Mark Nottingham
Re: Why should caches and intermediaries ignore If-Match? Roy T. Fielding
Re: forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Fwd: New Version Notification - draft-ietf-httpbis-encryption-encoding-08.txt Mark Nottingham
I-D Action: draft-ietf-httpbis-encryption-encoding-08.txt internet-drafts@ietf.org

Thursday, 2 March 2017

Re: forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: I-D ACTION:draft-ietf-httpbis-rfc5987bis-05.txt Julian Reschke
I-D ACTION:draft-ietf-httpbis-rfc5987bis-05.txt Internet-Drafts@ietf.org
Re: forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: Secdir review of draft-ietf-httpbis-http2-encryption-10 Martin Thomson
Re: Secdir review of draft-ietf-httpbis-http2-encryption-10 Mark Nottingham
Re: Why should caches and intermediaries ignore If-Match? Tom Bergan

Wednesday, 1 March 2017

Re: DRAFT agenda for Chicago Patrick McManus

Thursday, 2 March 2017

Re: forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov

Wednesday, 1 March 2017

RE: forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Mike Bishop
forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: The future of forward proxy servers in an http/2 over TLS world Poul-Henning Kamp
UI | Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
DRAFT agenda for Chicago Mark Nottingham

Tuesday, 28 February 2017

Re: The future of forward proxy servers in an http/2 over TLS world Roland Zink
Re: The future of forward proxy servers in an http/2 over TLS world Poul-Henning Kamp
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: The future of forward proxy servers in an http/2 over TLS world Willy Tarreau
Re: The future of forward proxy servers in an http/2 over TLS world Patrick McManus
Re: The future of forward proxy servers in an http/2 over TLS world Poul-Henning Kamp
Re: The future of forward proxy servers in an http/2 over TLS world Willy Tarreau
Re: Why should caches and intermediaries ignore If-Match? Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: Why should caches and intermediaries ignore If-Match? Roy T. Fielding

Monday, 27 February 2017

Re: The future of forward proxy servers in an http/2 over TLS world Mark Nottingham
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: Appropriate use of HTTP status codes for application health checks Willy Tarreau
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Ilya Grigorik
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Mark Nottingham
Re: Appropriate use of HTTP status codes for application health checks Amos Jeffries
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Re: The future of forward proxy servers in an http/2 over TLS world Mark Nottingham
Re: Review of draft-ietf-httpbis-http2-encryption-10 Mark Nottingham
Re: The future of forward proxy servers in an http/2 over TLS world Chris Bentzel

Sunday, 26 February 2017

Re: Why should caches and intermediaries ignore If-Match? Mark Nottingham
Re: Appropriate use of HTTP status codes for application health checks Mark Nottingham

Friday, 24 February 2017

Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Ilya Grigorik
Re: 103 (Early Hints) vs. response headers Vasiliy Faronov
Re: 103 (Early Hints) vs. response headers Kazuho Oku
Re: 103 (Early Hints) vs. response headers Mark Nottingham

Thursday, 23 February 2017

103 (Early Hints) vs. response headers Vasiliy Faronov
[Errata Held for Document Update] RFC7540 (4925) RFC Errata System
[Errata Rejected] RFC7233 (4665) RFC Errata System
[Errata Verified] RFC7233 (4664) RFC Errata System
[Errata Rejected] RFC7540 (4663) RFC Errata System
[Errata Rejected] RFC7234 (4616) RFC Errata System
[Errata Rejected] RFC7233 (4682) RFC Errata System
[Errata Held for Document Update] RFC7230 (4891) RFC Errata System
[Errata Rejected] RFC7540 (4871) RFC Errata System
[Errata Held for Document Update] RFC7540 (4666) RFC Errata System
[Errata Held for Document Update] RFC7231 (4689) RFC Errata System

Tuesday, 21 February 2017

Re: [OPS-DIR] Partial review of draft-ietf-httpbis-rfc5987bis-04 jouni.nospam

Thursday, 23 February 2017

Re: Review of draft-ietf-httpbis-rfc5987bis-04 Julian Reschke
Re: Appropriate use of HTTP status codes for application health checks Willy Tarreau
Re: Appropriate use of HTTP status codes for application health checks Amos Jeffries
Re: Appropriate use of HTTP status codes for application health checks Matthew Kerwin
Appropriate use of HTTP status codes for application health checks matt

Tuesday, 21 February 2017

Re: Call For Adoption Live Byte Ranges Craig Pratt
Re: Partial review of draft-ietf-httpbis-rfc5987bis-04 Julian Reschke

Monday, 20 February 2017

Re: draft-ietf-httpbis-encryption-encoding-07, "2. The “aes128gcm” HTTP Content Coding" Martin Thomson
Re: Call For Adoption Live Byte Ranges Patrick McManus
Last Call: <draft-ietf-httpbis-http2-encryption-10.txt> (Opportunistic Security for HTTP) to Experimental RFC The IESG
draft-ietf-httpbis-encryption-encoding-07, "2. The “aes128gcm” HTTP Content Coding" Julian Reschke

Saturday, 18 February 2017

Re: H2: Should there be a limit to tolerance ? Poul-Henning Kamp
Re: H2: Should there be a limit to tolerance ? Martin Thomson

Friday, 17 February 2017

Re: H2: Should there be a limit to tolerance ? Poul-Henning Kamp
Re: Why should caches and intermediaries ignore If-Match? Tom Bergan
Re: Why should caches and intermediaries ignore If-Match? Alex Rousskov
Re: Why should caches and intermediaries ignore If-Match? Tom Bergan
Re: H2: Should there be a limit to tolerance ? Martin Thomson
Re: The future of forward proxy servers in an http/2 over TLS world Francesco Chemolli
Re: The future of forward proxy servers in an http/2 over TLS world nicolas.mailhot@laposte.net
Re: H2: Should there be a limit to tolerance ? Poul-Henning Kamp
Re: H2: Should there be a limit to tolerance ? Stefan Eissing
Re: H2: Should there be a limit to tolerance ? Poul-Henning Kamp
Re: H2: Should there be a limit to tolerance ? Stefan Eissing
H2: Should there be a limit to tolerance ? Poul-Henning Kamp
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Tom Bergan
Re: The future of forward proxy servers in an http/2 over TLS world Willy Tarreau
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Amos Jeffries
Re: Why should caches and intermediaries ignore If-Match? Alex Rousskov

Thursday, 16 February 2017

Re: The future of forward proxy servers in an http/2 over TLS world Ryan Hamilton
Re: The future of forward proxy servers in an http/2 over TLS world Roland Zink
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Tom Bergan
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: The future of forward proxy servers in an http/2 over TLS world Poul-Henning Kamp
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Tom Bergan
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
[Errata Rejected] RFC7230 (4838) RFC Errata System
[Errata Verified] RFC7230 (4839) RFC Errata System
Re: aes128gcm: is the 1st example wrong? Daurnimator
RE: aes128gcm: is the 1st example wrong? Manger, James
Re: aes128gcm: is the 1st example wrong? Daurnimator
Third Working Group Last Call for draft-ietf-httpbis-encryption-encoding Mark Nottingham

Wednesday, 15 February 2017

Why should caches and intermediaries ignore If-Match? Tom Bergan
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
RE: The future of forward proxy servers in an http/2 over TLS world Mike Bishop
Re: The future of forward proxy servers in an http/2 over TLS world Patrick McManus
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Alex Rousskov
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Ryan Hamilton
Re: The future of forward proxy servers in an http/2 over TLS world Patrick McManus
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Patrick McManus
Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Kari Hurtta
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Patrick McManus
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Cory Benfield
Re: The future of forward proxy servers in an http/2 over TLS world Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Willy Tarreau
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Mark Nottingham
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Alex Rousskov
Re: ORIGIN - suggested changes Frederik Deweerdt
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Matthew Kerwin
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Alex Rousskov

Tuesday, 14 February 2017

Re: The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: The future of forward proxy servers in an http/2 over TLS world Dave Dolson
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Alex Rousskov
The future of forward proxy servers in an http/2 over TLS world Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Daniel Stenberg
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Willy Tarreau
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Jason T. Greene
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Matthew Kerwin
RE: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Mike Bishop
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Loïc Hoguin
Sections 3.3.2 and 3.3.3 allow bogus Content-Length? Adrien de Croy
Re: I-D Action: draft-ietf-httpbis-encryption-encoding-07.txt Martin Thomson
I-D Action: draft-ietf-httpbis-encryption-encoding-07.txt internet-drafts@ietf.org
Re: status of rfc6265bis? Mark Nottingham

Monday, 13 February 2017

Re: status of rfc6265bis? Adam Barth
Re: status of rfc6265bis? Julian Reschke
Re: status of rfc6265bis? Daniel Veditz
status of rfc6265bis? Julian Reschke
Re: aes128gcm: is the 1st example wrong? Martin Thomson
Re: aes128gcm: is the 1st example wrong? Julian Reschke
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Mark Nottingham
I-D Action: draft-ietf-httpbis-origin-frame-02.txt internet-drafts@ietf.org
Re: ORIGIN - suggested changes Mark Nottingham

Sunday, 12 February 2017

RE: aes128gcm: is the 1st example wrong? Manger, James
Re: aes128gcm: is the 1st example wrong? Martin Thomson
Re: aes128gcm: is the 1st example wrong? Julian Reschke

Saturday, 11 February 2017

Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Ilya Grigorik
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Willy Tarreau
RE: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mike Bishop
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Wenbo Zhu

Friday, 10 February 2017

Re: T-E chunked trailers Willy Tarreau
Re: T-E chunked trailers Mark Nottingham
T-E chunked trailers Ashok Kumar

Thursday, 9 February 2017

Re: I-D Action: draft-ietf-httpbis-expect-ct-00.txt Emily Stark
Re: I-D Action: draft-ietf-httpbis-early-hints-00.txt Kazuho Oku

Wednesday, 8 February 2017

Re: Second Working Group Last Call: draft-ietf-httpbis-http2-encryption-10 Patrick McManus
Re: I-D Action: draft-ietf-httpbis-expect-ct-00.txt Ilari Liusvaara
I-D Action: draft-ietf-httpbis-expect-ct-00.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-early-hints-00.txt internet-drafts@ietf.org

Tuesday, 7 February 2017

Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Willy Tarreau
Re: [Editorial Errata Reported] RFC7540 (4925) Martin Thomson
Re: [Editorial Errata Reported] RFC7540 (4925) Mark Nottingham
Re: Proposed text for erratum on PRIORITY in RFC 7540 Martin Thomson
[Editorial Errata Reported] RFC7540 (4925) RFC Errata System
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mark Nottingham
Re: Call for Adoption: Early Hints (103) Kazuho Oku
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Nick Doty
Re: Call for Adoption: Early Hints (103) Mark Nottingham

Monday, 6 February 2017

Re: draft-ietf-httpbis-http2-encryption-10 Martin Thomson
Re: Fwd: New Version Notification for draft-nottingham-httpbis-retry-01.txt Alex Rousskov
draft-ietf-httpbis-http2-encryption-10 Kari Hurtta
Last Call: <draft-ietf-httpbis-rfc5987bis-04.txt> (Indicating Character Encoding and Language for HTTP Header Field Parameters) to Proposed Standard The IESG
Re: ORIGIN - suggested changes Stefan Eissing

Sunday, 5 February 2017

Re: ORIGIN - suggested changes Patrick McManus
Re: draft-ietf-httpbis-http2-encryption-10: 2.3. The "http-opportunistic" well-known URI / cache-control Kari Hurtta

Saturday, 4 February 2017

Re: draft-ietf-httpbis-http2-encryption-10: 2.3. The "http-opportunistic" well-known URI / cache-control Martin Thomson
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Tom Bergan
draft-ietf-httpbis-http2-encryption-10: 2.3. The "http-opportunistic" well-known URI / cache-control Kari Hurtta
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Roy T. Fielding
Re: Call for Adoption: Expect-CT Emily Stark
Re: ORIGIN - suggested changes Mark Nottingham

Friday, 3 February 2017

Re: ORIGIN - suggested changes Patrick McManus
Re: ORIGIN - suggested changes Stefan Eissing
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mark Nottingham
Re: Call for Adoption: Expect-CT Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Mark Nottingham
Second Working Group Last Call: draft-ietf-httpbis-http2-encryption-10 Mark Nottingham
Re: draft-ietf-httpbis-http2-encryption-10: Example 2.1. Alternative Server Opt-In Martin Thomson
Re: ORIGIN - suggested changes Mark Nottingham

Thursday, 2 February 2017

Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Nick Doty
Re: ORIGIN - suggested changes Stefan Eissing
RE: ORIGIN - suggested changes Mike Bishop
draft-ietf-httpbis-http2-encryption-10: Example 2.1. Alternative Server Opt-In Kari Hurtta
Re: ORIGIN - suggested changes Stefan Eissing
Re: Fwd: New Version Notification for draft-nottingham-httpbis-retry-01.txt Willy Tarreau
Re: ORIGIN - suggested changes Mark Nottingham
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mark Nottingham
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Tom Bergan
Re: ORIGIN - suggested changes Martin Thomson
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mark Nottingham
Re: ORIGIN - suggested changes Mark Nottingham
Re: ORIGIN - suggested changes Nick Sullivan

Wednesday, 1 February 2017

Re: ORIGIN - suggested changes Martin Thomson
Re: ORIGIN - suggested changes Martin Thomson
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Matt Menke
Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt Tom Bergan
RE: draft-ietf-httpbis-http2-encryption-10 Mike Bishop
RE: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mike Bishop
Re: ORIGIN - suggested changes Frederik Deweerdt
Re: ORIGIN - suggested changes Ilari Liusvaara
back on draft-ietf-httpbis-header-structure-00 Poul-Henning Kamp
Re: ORIGIN - suggested changes Martin Thomson
Fwd: New Version Notification for draft-nottingham-httpbis-retry-01.txt Mark Nottingham
ORIGIN - suggested changes Mark Nottingham
Re: draft-ietf-httpbis-http2-encryption-10 Mark Nottingham
draft-ietf-httpbis-http2-encryption-10 Martin Thomson
I-D Action: draft-ietf-httpbis-http2-encryption-10.txt internet-drafts@ietf.org

Tuesday, 31 January 2017

Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Julian Reschke
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Patrick McManus
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-client-hints-03.txt Mark Nottingham
Re: Change to padding in encryption -- examples look ok Martin Thomson
RE: Change to padding in encryption -- examples look ok Manger, James

Monday, 30 January 2017

Re: Change to padding in encryption -- enabling random access Martin Thomson
RE: Change to padding in encryption -- enabling random access Manger, James
Re: Change to padding in encryption -- enabling random access Martin Thomson
RE: Change to padding in encryption -- enabling random access Manger, James
RE: aes128gcm: why verify padding? Manger, James
Change to padding in encryption Martin Thomson
Re: aes128gcm: why verify padding? Martin Thomson
RE: aes128gcm: why verify padding? Manger, James

Friday, 27 January 2017

Re: aes128gcm: why verify padding? Ilari Liusvaara
Re: HTTP/2 plaintext upgrade Kazuho Oku
RE: aes128gcm: why verify padding? Manger, James

Thursday, 26 January 2017

Re: HTTP/2 plaintext upgrade Daniel Stenberg
Re: HTTP/2 plaintext upgrade Loïc Hoguin
HTTP/2 plaintext upgrade Cory Benfield
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Amos Jeffries
[ietf-http-wg] <none> geronimotita@gmail.com

Wednesday, 25 January 2017

Re: aes128gcm: why verify padding? Martin Thomson
[Errata Rejected] RFC7231 (4734) RFC Errata System
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Stefan Eissing
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Cory Benfield
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? 山本和彦
Re: Proposed text for erratum on PRIORITY in RFC 7540 Scott Mitchell
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Tatsuhiro Tsujikawa
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Kazuho Oku
Re: Proposed text for erratum on PRIORITY in RFC 7540 Patrick McManus

Tuesday, 24 January 2017

Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Patrick McManus
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Tom Bergan
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? 山本和彦
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Tom Bergan
[ietf-http-wg] <none> geronimotita@gmail.com
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Stefan Eissing
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? 山本和彦
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Kazuho Oku
Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case? Tom Bergan
RE: aes128gcm: why verify padding? Manger, James

Monday, 23 January 2017

Re: aes128gcm: why verify padding? Martin Thomson
Re: aes128gcm: vulnerable to truncation attacks Martin Thomson
Re: Proposed text for erratum on PRIORITY in RFC 7540 Martin Thomson
RE: aes128gcm: why verify padding? Manger, James
Re: aes128gcm: why verify padding? Ilari Liusvaara
RE: aes128gcm: why verify padding? Manger, James
aes128gcm: vulnerable to truncation attacks Manger, James

Sunday, 22 January 2017

Re: Clarify some handling about extension frame and unknown frame on HTTP/2 蕭雋涵

Saturday, 21 January 2017

Re: Clarify some handling about extension frame and unknown frame on HTTP/2 Cory Benfield
Re: Clarify some handling about extension frame and unknown frame on HTTP/2 Tatsuhiro Tsujikawa
Clarify some handling about extension frame and unknown frame on HTTP/2 蕭雋涵

Friday, 20 January 2017

Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Tom Bergan
Re: Proposed text for erratum on PRIORITY in RFC 7540 Scott Mitchell
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Proposed text for erratum on PRIORITY in RFC 7540 laike9m
Re: Proposed text for erratum on PRIORITY in RFC 7540 Cory Benfield
Re: Stream State and PRIORITY Frames laike9m
Re: Shared Dictionaries (SDCH and friends) Martin Thomson
Proposed text for erratum on PRIORITY in RFC 7540 Martin Thomson
Shared Dictionaries (SDCH and friends) chaals@yandex-team.ru
Re: [Technical Errata Reported] RFC7233 (4664) Mark Nottingham
Re: [Technical Errata Reported] RFC7230 (4838) Mark Nottingham
Re: [Technical Errata Reported] RFC7540 (4663) Mark Nottingham
Re: [Editorial Errata Reported] RFC7234 (4616) Mark Nottingham
Re: [Technical Errata Reported] RFC7233 (4682) Mark Nottingham

Thursday, 19 January 2017

Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Multiple Alt-Svc parameters of the same type Martin Thomson
Re: Stream State and PRIORITY Frames Cory Benfield
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Patrick McManus
Re: Stream State and PRIORITY Frames Cory Benfield
RE: Multiple Alt-Svc parameters of the same type Lucas Pardue
Re: Stream State and PRIORITY Frames Amos Jeffries
Re: Stream State and PRIORITY Frames Kazuho Oku
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Scott Mitchell

Wednesday, 18 January 2017

Re: Stream State and PRIORITY Frames Cory Benfield
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Cory Benfield
Re: Stream State and PRIORITY Frames Tom Bergan
Re: Stream State and PRIORITY Frames Daurnimator

Tuesday, 17 January 2017

Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Martin Thomson
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Matthew Kerwin
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Cory Benfield
Re: Stream State and PRIORITY Frames Scott Mitchell
Re: Stream State and PRIORITY Frames Cory Benfield
Re: Stream State and PRIORITY Frames Tatsuhiro Tsujikawa
Re: Stream State and PRIORITY Frames Benedikt Christoph Wolters
Stream State and PRIORITY Frames Scott Mitchell
Re: aes128gcm: is the 1st example wrong? Martin Thomson
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Barry Leiba
aes128gcm: is the 1st example wrong? Manger, James
Re: Multiple Alt-Svc parameters of the same type Martin Thomson

Monday, 16 January 2017

RE: Multiple Alt-Svc parameters of the same type Mike Bishop
Re: Multiple Alt-Svc parameters of the same type Martin Thomson
Re: Multiple Alt-Svc parameters of the same type Martin Thomson
RE: Multiple Alt-Svc parameters of the same type Lucas Pardue
Re: Multiple Alt-Svc parameters of the same type Kari Hurtta
Multiple Alt-Svc parameters of the same type Lucas Pardue
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Martin J. Dürst
Re: aes128gcm: why verify padding? Martin Thomson
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Julian Reschke
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Martin J. Dürst
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Mark Nottingham
RE: aes128gcm: why verify padding? Manger, James
Re: aes128gcm: why verify padding? Martin Thomson

Sunday, 15 January 2017

aes128gcm: why verify padding? Manger, James

Friday, 13 January 2017

Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Julian Reschke
Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard? Martin Thomson

Thursday, 12 January 2017

Issue 271 of 5987bis - Proposed Standard or Internet Standard? Patrick McManus
I-D Action: draft-ietf-httpbis-immutable-00.txt internet-drafts@ietf.org
Re: NEW PREFERENCE - depth-noroot (request for expert review) Julian Reschke
Re: NEW PREFERENCE - depth-noroot (request for expert review) Amos Jeffries
UPDATE TO PREFERENCE - return=representation (request for expert review) Julian Reschke
NEW PREFERENCE - depth-noroot (request for expert review) Julian Reschke
Re: draft-ietf-httpbis-http2-encryption (was wrong draft) | Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Kari Hurtta

Wednesday, 11 January 2017

Tuesday, 10 January 2017

Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Martin Thomson
Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Kari Hurtta

Monday, 9 January 2017

I-D ACTION:draft-ietf-httpbis-rfc5987bis-04.txt Internet-Drafts@ietf.org
Re: Question regarding RFC 7230 James M Snell

Sunday, 8 January 2017

Re: Question regarding RFC 7230 Julian Reschke

Saturday, 7 January 2017

Re: Question regarding RFC 7230 Julian Reschke

Friday, 6 January 2017

Question regarding RFC 7230 Hartford, Eric
Re: draft-ietf-httpbis-encryption-encoding Kari Hurtta

Wednesday, 4 January 2017

Re: Unicode escape sequence | Re: draft-ietf-httpbis-header-structure-00, unicode range Martin J. Dürst

Tuesday, 3 January 2017

Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Martin Thomson
Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Kari Hurtta
Re: Very large values (Re: Call For Adoption Live Byte Ranges) Craig Pratt
Re: draft-ietf-httpbis-encryption-encoding Martin Thomson
Very large values (Re: Call For Adoption Live Byte Ranges) Martin Thomson

Monday, 2 January 2017

Re: (rephrasing, sorry for duplicate) | Re: draft-ietf-httpbis-encryption-encoding Martin Thomson
Re: Call For Adoption Live Byte Ranges Craig Pratt

Last message date: Thursday, 30 March 2017 12:29:02 UTC