ietf-http-wg@w3.org from April to June 2013 by author

Adrien W. de Croy

• Ranges (Thursday, 27 June)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 28 May)
• Re: Comments on Explicit/Trusted Proxy (Monday, 6 May)
• Re: Comments on Explicit/Trusted Proxy (Monday, 6 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: WGLC p1: Tear-down (Tuesday, 30 April)
• Re: WGLC p1: Tear-down (Tuesday, 30 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: Header Serialization Discussion (Monday, 15 April)
• Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Saturday, 13 April)

Albert Lunde

• Re: Design: Ignored Unknown Frame Types and Intermediaries (Tuesday, 14 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Resumable Uploads (Thursday, 18 April)

Alex Rousskov

• Re: #481, was: WGLC: p7 MUSTs (Sunday, 30 June)
• Re: #481, was: WGLC: p7 MUSTs (Sunday, 9 June)
• Re: #467: Expect: 100-continue and "final" status codes (Monday, 20 May)
• Re: #486: Requiring proxies to process warn-date (Monday, 20 May)
• Re: Requiring proxies to process warn-date (Wednesday, 15 May)
• Re: WGLC: p5 MUSTs (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• Re: WGLC p1: MUST fix Content-Length? (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• Re: WGLC p1: proxy handling of a really bad Content-Length (Wednesday, 1 May)
• Re: WGLC p1: MUST fix Content-Length? (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• WGLC p1: proxy handling of a really bad Content-Length (Wednesday, 1 May)
• WGLC p1: MUST fix Content-Length? (Wednesday, 1 May)
• WGLC: p7 MUSTs (Wednesday, 1 May)
• WGLC: p6 MUSTs (Wednesday, 1 May)
• WGLC: p5 MUSTs (Wednesday, 1 May)
• WGLC: p4 MUSTs (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Tuesday, 30 April)
• Re: WGLC: p1 MUSTs (Tuesday, 30 April)
• WGLC: p2 MUSTs (Tuesday, 30 April)
• WGLC: p1 MUSTs (Tuesday, 30 April)

Alexey Melnikov

• Re: p2: Considerations for new headers (Wednesday, 24 April)

Amos Jeffries

• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: Out-of-order Frames (Sunday, 23 June)
• Re: Out-of-order Frames (Sunday, 23 June)
• Re: Design: Adding ASSOCIATED_ONLY (Friday, 21 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Design: Adding ASSOCIATED_ONLY (Thursday, 20 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Sunday, 16 June)
• Re: Until HTTP header when the representation will disappear in the future (Wednesday, 12 June)
• Re: Until HTTP header when the representation will disappear in the future (Wednesday, 12 June)
• Re: #458: Requirements upon proxies for Expect (Wednesday, 5 June)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p1: Via and gateways (Tuesday, 23 April)
• Re: p2: Expectation extensions (Tuesday, 23 April)
• Re: p1: additional security considerations (Tuesday, 23 April)
• Re: p1: additional security considerations (Tuesday, 23 April)
• Re: p2: scope for status codes (Tuesday, 23 April)
• Re: p1: Via and gateways (Tuesday, 23 April)
• Re: Resumable Uploads (Sunday, 21 April)
• Re: p2: Purely editorial feedback (Sunday, 21 April)
• Re: p2: scope for status codes (Sunday, 21 April)
• Re: Resumable Uploads (Sunday, 21 April)
• Re: p1: Via and gateways (Sunday, 21 April)
• Re: p1: Receiving a higher minor HTTP version number (Sunday, 21 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: handling obs-fold (Saturday, 20 April)
• Re: p1: transfer coding registry (Saturday, 20 April)
• Re: p1: BWS (Friday, 19 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: p1: BWS (Thursday, 18 April)
• Re: p1: whitespace in request-target (Thursday, 18 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: p6: Returning the freshest response (Wednesday, 3 April)

Barry Leiba

• Re: HTTPBIS WG Interim Meeting, June 13-14, 2013 (Tuesday, 30 April)

Ben Niven-Jenkins

• Re: Caching 412 responses (Tuesday, 28 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• WGLC p1: Tear-down (Monday, 29 April)
• WGLC p1: Persistence & 1.1 proxies (Monday, 29 April)
• WGLC p7: Parsing auth challenges (Monday, 29 April)
• WGLC p1: Delimiting messages with multipart/byteranges (Monday, 29 April)

Benjamin Carlyle

• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: WGLC: p1 MUSTs (Tuesday, 30 April)

Bjoern Hoehrmann

• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: #440: max of max-age (Tuesday, 7 May)
• Re: p2: Accept-Language missing, empty or no match (Wednesday, 1 May)
• Re: p2: Accept-Language missing, empty or no match (Tuesday, 30 April)
• Re: p2: Expectation extensions (Friday, 26 April)
• Re: p2: Expectation extensions (Thursday, 25 April)

Brian Pane

• Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Monday, 15 April)

Brian Raymor (MS OPEN TECH)

• RE: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Wednesday, 17 April)
• 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Saturday, 13 April)
• Transitioning to TLS Application Layer Protocol Negotiation (ALPN) (Monday, 8 April)

Carsten Bormann

• Re: How to pronounce "charset"? (Wednesday, 15 May)
• Re: How to pronounce "charset"? (Monday, 13 May)
• Re: Resumable Uploads (Monday, 22 April)
• Re: Resumable Uploads (Monday, 22 April)
• Re: Resumable Uploads (Monday, 22 April)
• Re: Resumable Uploads (Sunday, 21 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Wednesday, 17 April)

D R

• Re: draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path (Thursday, 27 June)
• draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path (Thursday, 27 June)

Daniel Friesen

• Re: Web Keys and HTTP Signatures (Thursday, 18 April)

Daniel Stenberg

• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: Resumable Uploads (Saturday, 20 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Resumable Uploads (Thursday, 18 April)

David I. Lehn

• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Wednesday, 17 April)

David Kendal

• A modest proposal (Monday, 1 April)

David Morris

• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• RE: Multiple Headers (Monday, 17 June)
• Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Saturday, 15 June)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: #469: definition of "private" (Wednesday, 8 May)
• Re: #469: definition of "private" (Tuesday, 7 May)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)

Eggert, Lars

• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 17 April)

Eitan Adler

• Re: p6: Returning the freshest response (Monday, 1 April)

Eliot Lear

• Re: [#150] Making certain settings mandatory (Sunday, 30 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• DASH/XMPP workshop (Thursday, 20 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: [saag] Is the CA market broken? (Wednesday, 12 June)
• Is the CA market broken? (Wednesday, 12 June)
• Re: port #? (Monday, 10 June)
• Re: port #? (Friday, 7 June)
• port #? (Friday, 7 June)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: HTTP/2 and TCP CWND (Saturday, 27 April)
• Re: HTTP/2 and TCP CWND (Friday, 19 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)

Fabian Keil

• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)

Felix Geisendörfer

• Re: Resumable Uploads (Monday, 22 April)
• Re: Resumable Uploads (Monday, 22 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Resumable Uploads (Sunday, 21 April)
• Re: Resumable Uploads (Saturday, 20 April)
• Resumable Uploads (Thursday, 18 April)

Fred Akalin

• Re: Is the ability to disable flow control really needed? (Monday, 24 June)
• Re: Is the ability to disable flow control really needed? (Saturday, 22 June)
• Re: Is the ability to disable flow control really needed? (Friday, 21 June)
• Re: Is the ability to disable flow control really needed? (Friday, 21 June)
• Is the ability to disable flow control really needed? (Friday, 21 June)

Frédéric Kayser

• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: UTF-8 text (was: Header Serialization Discussion) (Wednesday, 17 April)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: Header Serialization Discussion (Tuesday, 16 April)

Gabriel Montenegro

• RE: Is the ability to disable flow control really needed? (Monday, 24 June)
• RE: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• RE: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" (Wednesday, 17 April)
• RE: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" (Wednesday, 17 April)
• RE: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• RE: HTTP/2 and TCP CWND (Monday, 15 April)
• RE: HTTP/2 and TCP CWND (Friday, 12 April)

Gábor Molnár

• Header compression question (Sunday, 30 June)
• Re: Summer of Code project (Monday, 24 June)
• Fwd: Summer of Code project (Monday, 24 June)

HAYASHI, Tatsuya

• Re: Planning for Future Meetings (Friday, 10 May)

Henry S. Thompson

• WGLC p1: Scope of https update (Wednesday, 29 May)

IESG Secretary

• HTTPBIS WG Interim Meeting, August 5-7, 2013 (Wednesday, 15 May)
• HTTPBIS WG Interim Meeting, June 13-14, 2013 (Friday, 19 April)

Ilari Liusvaara

• Re: Resumable Uploads (Saturday, 20 April)
• Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Sunday, 14 April)

Ilya Grigorik

• Re: Out-of-order Frames (Sunday, 23 June)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Sunday, 14 April)
• HTTP 2.0 "Upgrade" flow (Sunday, 14 April)

internet-drafts@ietf.org

• I-D Action: draft-ietf-httpbis-header-compression-00.txt (Wednesday, 26 June)
• I-D Action: draft-ietf-httpbis-http2-03.txt (Wednesday, 29 May)
• I-D Action: draft-ietf-httpbis-http2-02.txt (Wednesday, 3 April)

James Cloos

• Re: How to pronounce "charset"? (Tuesday, 14 May)
• Re: p2: Purely editorial feedback (Thursday, 25 April)
• Re: UTF-8 text (Thursday, 18 April)

James M Snell

• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Issue #154: Sending a response before the request is complete (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• Re: Rough Minutes from SF F2F (Wednesday, 26 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Design: Adding ASSOCIATED_ONLY (Thursday, 20 June)
• Re: Questions on Frame Size (Thursday, 20 June)
• Re: END_STREAM on PUSH_PROMISE (Wednesday, 19 June)
• END_STREAM on PUSH_PROMISE (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: Nit: Server-sent priority (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Multiple Headers (Sunday, 16 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Sunday, 16 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Sunday, 16 June)
• Re: Header Compression (Sunday, 9 June)
• Fwd: New Version Notification for draft-snell-httpbis-bohe-09.txt (Thursday, 6 June)
• Re: draft-snell-http-prefer: Preference-Applied (Thursday, 6 June)
• Re: Header Compression (Wednesday, 5 June)
• Re: HTTP in JSON Binary Encoding / Data Model (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Sunday, 26 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: notes on http2 draft (Tuesday, 21 May)
• Fwd: New Version Notification for draft-snell-httpbis-ext-frames-00.txt (Monday, 20 May)
• Fwd: New Version Notification for draft-snell-httpbis-bohe-08.txt (Monday, 20 May)
• Re: Preliminary agenda for the SF Interim (Monday, 20 May)
• Re: adding Header Continuation (Monday, 20 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Tuesday, 14 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: http/2 test framework (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Saturday, 11 May)
• Design: Frame type extensibility issues (Saturday, 11 May)
• Design: Ignored Unknown Frame Types and Intermediaries (Saturday, 11 May)
• Re: Associating URI-based identities with HTTP requests (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Thursday, 9 May)
• Re: 3.5.1 Connection Error Handling (Thursday, 9 May)
• Design Issue: Overlong Frames (Thursday, 9 May)
• Re: Git Issues: PING (Thursday, 9 May)
• Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Thursday, 9 May)
• Re: Design Issue: Frame Size Items (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Saturday, 4 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Saturday, 4 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Design Issue: Can we go ahead and remove persistent settings? (Thursday, 2 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 2 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 2 May)
• Re: Design Issue: Life-cycle of a Stream (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Design Issue: Life-cycle of a Stream (Wednesday, 1 May)
• Re: For review: editorial updates pull request (Tuesday, 30 April)
• Re: WGLC: SHOULD and conformance (Tuesday, 30 April)
• Re: p2: Accept-Language missing, empty or no match (Tuesday, 30 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Request: Have git commit messages for design changes include links to relevant discussion email threads (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: p2: deprecating 205 Reset Content? (Monday, 29 April)
• Re: p2: deprecating 205 Reset Content? (Monday, 29 April)
• Re: Editorial Issue: Persisted Settings... when does the client need to return them? (Sunday, 28 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Sunday, 28 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Sunday, 28 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Saturday, 27 April)
• Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? (Saturday, 27 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Saturday, 27 April)
• Re: Editorial Issue: Persisted Settings... when does the client need to return them? (Saturday, 27 April)
• For review: editorial updates pull request (Friday, 26 April)
• Editorial Issue: Persisted Settings... when does the client need to return them? (Friday, 26 April)
• Re: Editorial Issue: Unknown/Undefined Settings IDs (Friday, 26 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Friday, 26 April)
• Editorial Issue: Unknown/Undefined Settings IDs (Friday, 26 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Friday, 26 April)
• Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Friday, 26 April)
• Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Friday, 26 April)
• Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? (Friday, 26 April)
• Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Friday, 26 April)
• Re: RST_STREAM and FINAL flag (Friday, 26 April)
• Re: Design Issue: Frame Processing Model (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Re: Design Issue: Must Ignore Rule for Unknown Frame Types (Thursday, 25 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Design Issue: Must Ignore Rule for Unknown Frame Types (Thursday, 25 April)
• Design Issue: Frame Processing Model (Thursday, 25 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Re: RST_STREAM and FINAL flag (Thursday, 25 April)
• Design Issue: PUSH_PROMISE and Stream Priority (Thursday, 25 April)
• Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Re: p2: Considerations for new headers (Thursday, 25 April)
• FYI.. merged pull request.. (Thursday, 25 April)
• Editorial Issue: Uniteral Stream Creation (Wednesday, 24 April)
• Re: Editorial Issues: Section 4.2.2 (Wednesday, 24 April)
• Re: Push Promise Issues (Wednesday, 24 April)
• Re: Editorial Issues: Section 4.2.2 (Wednesday, 24 April)
• Re: HTTP Request+Response issues (Wednesday, 24 April)
• Editorial Issues: Section 4.2.2 (Wednesday, 24 April)
• HTTP Request+Response issues (Wednesday, 24 April)
• Push Promise Issues (Wednesday, 24 April)
• Re: what's up with commenting on http/2 github issues (Wednesday, 24 April)
• Re: Updated I-D.. (Tuesday, 23 April)
• Re: p2: Expect: 100-continue and "final" status codes (Tuesday, 23 April)
• Re: p2: Expectation extensions (Tuesday, 23 April)
• Updated Link I-D (Monday, 22 April)
• Re: Git Issues: PING (Saturday, 20 April)
• Git Issues: Reserved Stream-ID Bit (Saturday, 20 April)
• Git Issues: PING (Saturday, 20 April)
• Re: Updated I-D.. (Saturday, 20 April)
• Updated I-D.. (Saturday, 20 April)
• Re: UTF-8 text (was: Header Serialization Discussion) (Wednesday, 17 April)
• Re: UTF-8 text (was: Header Serialization Discussion) (Wednesday, 17 April)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: Header Serialization Discussion (Tuesday, 16 April)
• Re: Header Serialization Discussion (Tuesday, 16 April)
• Re: Header Serialization Discussion (Tuesday, 16 April)
• Re: Planning for Future Meetings (Monday, 15 April)
• Re: Header Serialization Discussion (Monday, 15 April)
• Re: FYI: Header Compression (Monday, 15 April)
• Header Serialization Discussion (Saturday, 13 April)
• Re: Updated Delta+BOHE Impl in Java (Thursday, 11 April)
• Re: Updated Delta+BOHE Impl in Java (Tuesday, 9 April)
• Updated Delta+BOHE Impl in Java (Tuesday, 9 April)

Jan Algermissen

• Question on Multiplicity of Authorization and WWW-Authenticate (Tuesday, 16 April)

Jeff Pinner

• Re: [#150] Making certain settings mandatory (Sunday, 30 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: Is the ability to disable flow control really needed? (Saturday, 22 June)
• Re: Is the ability to disable flow control really needed? (Saturday, 22 June)
• Re: Is the ability to disable flow control really needed? (Friday, 21 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Multiple Headers (Sunday, 16 June)
• Multiple Headers (Sunday, 16 June)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Wednesday, 29 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Sunday, 26 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Sunday, 26 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Sunday, 26 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: 3.5.1 Connection Error Handling (Thursday, 9 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: RST_STREAM and FINAL flag (Thursday, 25 April)
• Re: Git Issues: PING (Monday, 22 April)

Jitu Padhye

• HTTP/2 and TCP CWND (Monday, 1 April)

John Sullivan

• Re: WGLC p7: Parsing auth challenges (Tuesday, 30 April)

Julian Reschke

• Re: #481, was: WGLC: p7 MUSTs (Sunday, 30 June)
• Re: #481, was: WGLC: p7 MUSTs (Sunday, 30 June)
• Re: #487 Resubmission of 403 (Sunday, 30 June)
• Re: Ranges (Sunday, 30 June)
• Re: ADMIN: Discussion on Github issues (Thursday, 27 June)
• Re: #462, was: p5: editorial suggestions (Thursday, 20 June)
• #482l was: WGLC p1: proxy handling of a really bad Content-Length (Thursday, 20 June)
• #486, was: p2: Expectation extensions (Thursday, 20 June)
• Re: #462, was: p5: editorial suggestions (Thursday, 20 June)
• #487 Resubmission of 403 (Thursday, 20 June)
• #462, was: p5: editorial suggestions (Thursday, 20 June)
• Re: draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion (Saturday, 15 June)
• Re: PUT, If-Match, 412 - over-constrained? (Saturday, 15 June)
• Re: #448, was: p2: Accept-Language missing, empty or no match (Wednesday, 12 June)
• Re: duplicate parameters (Tuesday, 11 June)
• Re: #448, was: p2: Accept-Language missing, empty or no match (Monday, 10 June)
• #481, was: WGLC: p7 MUSTs (Sunday, 9 June)
• #474, was: WGLC p7: Parsing auth challenges (Sunday, 9 June)
• #448, was: p2: Accept-Language missing, empty or no match (Sunday, 9 June)
• Re: port #? (Friday, 7 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: How to pronounce "charset"? (Monday, 13 May)
• Re: #464, was: p7: editorial suggestions (Tuesday, 7 May)
• Re: #461, was: p4: editorial suggestions (Monday, 6 May)
• Re: #461, was: p4: editorial suggestions (Monday, 6 May)
• Re: #461, was: p4: editorial suggestions (Thursday, 2 May)
• Re: #461, was: p4: editorial suggestions (Tuesday, 30 April)
• Re: WGLC p7: Parsing auth challenges (Tuesday, 30 April)
• #461, was: p4: editorial suggestions (Tuesday, 30 April)
• #464, was: p7: editorial suggestions (Tuesday, 30 April)
• Re: WGLC p7: Parsing auth challenges (Tuesday, 30 April)
• Re: p2: deprecating 205 Reset Content? (Monday, 29 April)
• Re: p7: editorial suggestions (Sunday, 28 April)
• #463, was: p7: editorial suggestions (Sunday, 28 April)
• Re: p2: Considerations for new headers (Thursday, 25 April)
• Re: p2: Considerations for new headers (Wednesday, 24 April)
• Re: what's up with commenting on http/2 github issues (Wednesday, 24 April)
• Re: Resumable Uploads (Monday, 22 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)
• Re: p1: BWS (Friday, 19 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: p1: BWS (Friday, 19 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: p1: BWS (Thursday, 18 April)
• Re: Status code 451 adoption (Wednesday, 17 April)
• Re: Question on Multiplicity of Authorization and WWW-Authenticate (Tuesday, 16 April)
• Re: Question on Multiplicity of Authorization and WWW-Authenticate (Tuesday, 16 April)
• Re: Status code 451 adoption (Monday, 15 April)
• Re: WGLC: p5 multiple Range headers (Tuesday, 9 April)

Karl Dubost

• Re: Until HTTP header when the representation will disappear in the future (Wednesday, 12 June)
• Until HTTP header when the representation will disappear in the future (Wednesday, 12 June)
• Re: How to pronounce "charset"? (Wednesday, 15 May)

Ken Murchison

• draft-snell-http-prefer: Preference-Applied (Thursday, 6 June)
• Re: #467: Expect: 100-continue and "final" status codes (Friday, 17 May)
• Re: WGLC: p5 MUSTs (Wednesday, 1 May)
• Re: #461, was: p4: editorial suggestions (Tuesday, 30 April)
• Re: WGLC: p4, 304 Not Modified (Monday, 29 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Tuesday, 23 April)
• Re: Resumable Uploads (Monday, 22 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• WGLC: p4, 304 Not Modified (Tuesday, 16 April)
• Re: WGLC: p5 multiple Range headers (Tuesday, 9 April)
• WGLC: p5 multiple Range headers (Wednesday, 3 April)

Kevin Swiber

• Re: Resumable Uploads (Thursday, 18 April)

Larry Masinter

• RE: How to pronounce "charset"? (Wednesday, 15 May)

Leif Hedstrom

• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Wednesday, 29 May)

Manger, James H

• RE: Web Keys and HTTP Signatures (Wednesday, 17 April)

Manu Sporny

• Re: Associating URI-based identities with HTTP requests (Sunday, 12 May)
• Re: [http-auth] Associating URI-based identities with HTTP requests (Sunday, 12 May)
• Associating URI-based identities with HTTP requests (Friday, 10 May)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Web Keys and HTTP Signatures (Wednesday, 17 April)

Mark Nottingham

• Re: ADMIN: Discussion on Github issues (Thursday, 27 June)
• ADMIN: Discussion on Github issues (Thursday, 27 June)
• Re: Rough Minutes from SF F2F (Thursday, 27 June)
• Outcomes of the SF Interim Meeting (Wednesday, 26 June)
• Fwd: HTTPBIS WG Interim Meeting, August 5-7, 2013 (Wednesday, 26 June)
• Re: Rough Minutes from SF F2F (Wednesday, 26 June)
• Rough Minutes from SF F2F (Tuesday, 25 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: #462, was: p5: editorial suggestions (Thursday, 20 June)
• Re: #462, was: p5: editorial suggestions (Thursday, 20 June)
• Re: #448, was: p2: Accept-Language missing, empty or no match (Monday, 10 June)
• Re: port #? (Monday, 10 June)
• Re: #448, was: p2: Accept-Language missing, empty or no match (Monday, 10 June)
• Re: p6: Warning header field (Sunday, 9 June)
• Re: Header Compression (Thursday, 6 June)
• Re: #458: Requirements upon proxies for Expect (Tuesday, 4 June)
• Re: p2: Expectation extensions (Thursday, 30 May)
• #458: Requirements upon proxies for Expect (Thursday, 30 May)
• Agenda for June Interim meeting (Thursday, 30 May)
• Re: I-D Action: draft-ietf-httpbis-http2-03.txt (Wednesday, 29 May)
• Re: #486: Requiring proxies to process warn-date (Wednesday, 29 May)
• Re: #467: Expect: 100-continue and "final" status codes (Wednesday, 29 May)
• Re: HTTP/2.0 SETTINGS frame values (Tuesday, 28 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 28 May)
• Re: #467: Expect: 100-continue and "final" status codes (Tuesday, 28 May)
• Re: #467: Expect: 100-continue and "final" status codes (Tuesday, 28 May)
• Re: #486: Requiring proxies to process warn-date (Tuesday, 28 May)
• Re: adding Header Continuation (Tuesday, 28 May)
• Re: "Magic" string (Monday, 20 May)
• Preliminary agenda for the SF Interim (Monday, 20 May)
• adding Header Continuation (Monday, 20 May)
• "Magic" string (Monday, 20 May)
• Re: Caching 412 responses (Monday, 20 May)
• Re: #486: Requiring proxies to process warn-date (Monday, 20 May)
• Re: Upgrade ordering (possible HTTP/2 impact) (Friday, 17 May)
• Re: Caching 412 responses (Friday, 17 May)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Friday, 17 May)
• Re: #467: Expect: 100-continue and "final" status codes (Friday, 17 May)
• #467: Expect: 100-continue and "final" status codes (Friday, 17 May)
• #486: Requiring proxies to process warn-date (Friday, 17 May)
• Re: http/2 test framework (Monday, 13 May)
• Re: #453: Returning the freshest response (Sunday, 12 May)
• Re: p2: section 5.3.2 (Accept header) (Thursday, 9 May)
• Requiring proxies to process warn-date (Wednesday, 8 May)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Wednesday, 8 May)
• Re: HTTPBIS WG Interim Meeting, June 13-14, 2013 (Wednesday, 8 May)
• Re: p1: Via and gateways (Wednesday, 8 May)
• #443: whitespace in request-target (Wednesday, 8 May)
• Re: #469: definition of "private" (Wednesday, 8 May)
• Re: p6: Vary and effects on future requests (Tuesday, 7 May)
• #453: Returning the freshest response (Tuesday, 7 May)
• #469: definition of "private" (Tuesday, 7 May)
• Re: #440: max of max-age (Tuesday, 7 May)
• Re: p7: forwarding Proxy-* (Tuesday, 7 May)
• Re: WGLC: SHOULD and conformance (Tuesday, 7 May)
• Re: p2: Accept-Language missing, empty or no match (Tuesday, 7 May)
• #440: max of max-age (Tuesday, 7 May)
• Re: WGLC: p5 MUSTs (Tuesday, 7 May)
• Re: WGLC: p1 MUSTs (Tuesday, 7 May)
• Re: WGLC p1: MUST fix Content-Length? (Tuesday, 7 May)
• Re: WGLC p1: proxy handling of a really bad Content-Length (Tuesday, 7 May)
• Re: WGLC: p7 MUSTs (Tuesday, 7 May)
• Fwd: HTTPBIS WG Interim Meeting, June 13-14, 2013 (Tuesday, 7 May)
• Re: #461, was: p4: editorial suggestions (Monday, 6 May)
• Re: #461, was: p4: editorial suggestions (Monday, 6 May)
• Re: #461, was: p4: editorial suggestions (Monday, 6 May)
• Re: p2: Accept-Language missing, empty or no match (Wednesday, 1 May)
• Re: #464, was: p7: editorial suggestions (Tuesday, 30 April)
• Re: #461, was: p4: editorial suggestions (Tuesday, 30 April)
• Re: WGLC: SHOULD and conformance (Tuesday, 30 April)
• Re: p7: forwarding Proxy-* (Tuesday, 30 April)
• Re: p2: Accept-Language missing, empty or no match (Tuesday, 30 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 30 April)
• Re: p1: whitespace in request-target (Tuesday, 30 April)
• Re: WGLC p1: Tear-down (Tuesday, 30 April)
• Re: WGLC p1: Tear-down (Tuesday, 30 April)
• Re: WGLC p1: Delimiting messages with multipart/byteranges (Tuesday, 30 April)
• Re: WGLC p7: Parsing auth challenges (Tuesday, 30 April)
• WGLC: SHOULD and conformance (Tuesday, 30 April)
• WGLC: Strengthening SHOULDs (Tuesday, 30 April)
• Re: p2: deprecating 205 Reset Content? (Tuesday, 30 April)
• Re: p7: forwarding Proxy-* (Tuesday, 30 April)
• WGLC: misused SHOULDs (Tuesday, 30 April)
• p7: forwarding Proxy-* (Tuesday, 30 April)
• Re: Request: Have git commit messages for design changes include links to relevant discussion email threads (Tuesday, 30 April)
• Re: p6: Vary and effects on future requests (Monday, 29 April)
• Re: WGLC: p4, 304 Not Modified (Monday, 29 April)
• p2 / p6: What is "cacheable"? (Monday, 29 April)
• p2: deprecating 205 Reset Content? (Monday, 29 April)
• p6: Vary and effects on future requests (Monday, 29 April)
• Re: Editorial notes on p6 (Monday, 29 April)
• Re: p7: editorial suggestions (Monday, 29 April)
• Editorial notes on p6 (Monday, 29 April)
• Re: HTTP/2 and TCP CWND (Saturday, 27 April)
• p2: Considerations for new headers (Wednesday, 24 April)
• Re: what's up with commenting on http/2 github issues (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p1: Via and gateways (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: scope for status codes (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p2: Expectation extensions (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: BWS (Tuesday, 23 April)
• p2: Expect: 100-continue and "final" status codes (Tuesday, 23 April)
• p2: Expectation extensions (Tuesday, 23 April)
• p2: editorial for Expect and 1xx (Tuesday, 23 April)
• Re: p1: additional security considerations (Tuesday, 23 April)
• Re: WGLC: p6 editorial nits (Tuesday, 23 April)
• Re: p1: Via and gateways (Tuesday, 23 April)
• p1: additional security considerations (Tuesday, 23 April)
• p1/p2: 203 Non-Authoritative Information (Tuesday, 23 April)
• Re: p7: editorial suggestions (Tuesday, 23 April)
• p7: editorial suggestions (Tuesday, 23 April)
• p5: editorial suggestions (Tuesday, 23 April)
• p4: editorial suggestions (Tuesday, 23 April)
• Re: p2: scope for status codes (Tuesday, 23 April)
• Re: p1: generating "internal" errors (Monday, 22 April)
• Re: p2: Requirements upon proxies for Expect (Monday, 22 April)
• Re: p1: transfer coding registry (Monday, 22 April)
• Re: draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion (Monday, 22 April)
• Re: p6: Returning the freshest response (Monday, 22 April)
• Re: p2: Content-Length in HEAD responses (Monday, 22 April)
• Re: p1: Purely Editorial Feedback (Monday, 22 April)
• Re: p1: HTTP and TCP name delegation (Monday, 22 April)
• Re: p2: Accept-Language missing, empty or no match (Monday, 22 April)
• Re: p1: Receiving a higher minor HTTP version number (Monday, 22 April)
• Re: p2: Purely editorial feedback (Monday, 22 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Monday, 22 April)
• Re: p2: Purely editorial feedback (Sunday, 21 April)
• Re: Resumable Uploads (Sunday, 21 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• p2: scope for status codes (Saturday, 20 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• p2: Requirements upon proxies for Expect (Saturday, 20 April)
• Re: p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• p2: Accept-Language missing, empty or no match (Saturday, 20 April)
• p2: Content-Length in HEAD responses (Saturday, 20 April)
• Re: p2: Purely editorial feedback (Saturday, 20 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)
• Re: p2: Purely editorial feedback (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Saturday, 20 April)
• Re: p1: handling obs-fold (Saturday, 20 April)
• p2: Purely editorial feedback (Saturday, 20 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Saturday, 20 April)
• Re: p1: generating "internal" errors (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• Re: Resumable Uploads (Saturday, 20 April)
• p1: transfer coding registry (Saturday, 20 April)
• p1: Upgrade ordering (possible HTTP/2 impact) (Saturday, 20 April)
• p1: generating "internal" errors (Saturday, 20 April)
• p1: HTTP and TCP name delegation (Saturday, 20 April)
• p1: handling obs-fold (Saturday, 20 April)
• p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)
• p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• p1: Via and gateways (Saturday, 20 April)
• p1: Purely Editorial Feedback (Saturday, 20 April)
• #443: p1: whitespace in request-target (Friday, 19 April)
• #442: p1: BWS (Friday, 19 April)
• Re: p1: BWS (Friday, 19 April)
• Re: p1: BWS (Thursday, 18 April)
• Re: p1: BWS (Thursday, 18 April)
• p1: BWS (Thursday, 18 April)
• p1: whitespace in request-target (Thursday, 18 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: Status code 451 adoption (Wednesday, 17 April)
• Re: Status code 451 adoption (Tuesday, 16 April)
• Re: Planning for Future Meetings (Monday, 15 April)
• Re: FYI: Header Compression (Monday, 15 April)
• Re: Planning for Future Meetings (Monday, 15 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• FYI: Header Compression (Monday, 15 April)
• Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Saturday, 13 April)
• Re: Compression analysis of perfect atom-based compressor (Saturday, 6 April)
• Re: Compression analysis of perfect atom-based compressor (Friday, 5 April)
• Re: p6: Returning the freshest response (Wednesday, 3 April)
• Re: p6: Returning the freshest response (Wednesday, 3 April)

Martin J. Dürst

• Re: Proposal: New Frame Size Text (Saturday, 11 May)
• Re: p1: HTTP(S) URIs and fragment identifiers (Monday, 22 April)

Martin Nilsson

• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: Compression analysis of perfect atom-based compressor (Friday, 5 April)

Martin Thomson

• Re: HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• [#153] PUSH_PROMISE headers (Saturday, 29 June)
• HTTP Mapping editorial changes (Friday, 28 June)
• Header compression, editorial (Thursday, 27 June)
• [#150] Making certain settings mandatory (Thursday, 27 June)
• Brief header compression comments (Wednesday, 26 June)
• Re: Outcomes of the SF Interim Meeting (Wednesday, 26 June)
• Re: Is the ability to disable flow control really needed? (Monday, 24 June)
• Re: Is the ability to disable flow control really needed? (Friday, 21 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: END_STREAM on PUSH_PROMISE (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Wednesday, 19 June)
• Nit: Server-sent priority (Tuesday, 18 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• Re: port #? (Friday, 7 June)
• Re: Header Compression (Thursday, 6 June)
• Re: Header Compression (Wednesday, 5 June)
• Re: Questions on Server Push (Tuesday, 4 June)
• Re: Questions on Server Push (Monday, 3 June)
• Re: I-D Action: draft-ietf-httpbis-http2-03.txt (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 28 May)
• Re: notes on http2 draft (Tuesday, 21 May)
• Re: notes on http2 draft (Tuesday, 21 May)
• Re: "Magic" string (Monday, 20 May)
• Re: adding Header Continuation (Monday, 20 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Tuesday, 14 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Saturday, 11 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS (Wednesday, 8 May)
• Re: redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: #469: definition of "private" (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: #469: definition of "private" (Tuesday, 7 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Saturday, 4 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 2 May)
• Re: Design Issue: Life-cycle of a Stream (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Editorial Issue: Persisted Settings... when does the client need to return them? (Saturday, 27 April)
• Re: Editorial Issue: Unknown/Undefined Settings IDs (Friday, 26 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Friday, 26 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Friday, 26 April)
• Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? (Friday, 26 April)
• Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Thursday, 25 April)
• Re: Design Issue: Frame Processing Model (Thursday, 25 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Re: Design Issue: Must Ignore Rule for Unknown Frame Types (Thursday, 25 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• Re: RST_STREAM and FINAL flag (Thursday, 25 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Thursday, 25 April)
• RST_STREAM and FINAL flag (Thursday, 25 April)
• Re: Push Promise Issues (Thursday, 25 April)
• Re: Editorial Issues: Section 4.2.2 (Wednesday, 24 April)
• Re: Editorial Issues: Section 4.2.2 (Wednesday, 24 April)
• Re: HTTP Request+Response issues (Wednesday, 24 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Resumable Uploads (Friday, 19 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" (Wednesday, 17 April)
• Re: Header Serialization Discussion (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" (Wednesday, 17 April)
• Quoting email (was: HTTP/2 and TCP CWND) (Tuesday, 16 April)
• Re: Updated Delta+BOHE Impl in Java (Tuesday, 9 April)
• Fwd: I-D Action: draft-ietf-httpbis-http2-02.txt (Wednesday, 3 April)
• Re: p6: Returning the freshest response (Monday, 1 April)

Matthew Kerwin

• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)

Michael Sweet

• Re: Out-of-order Frames (Monday, 24 June)
• Re: #467: Expect: 100-continue and "final" status codes (Tuesday, 28 May)

Michael Welzl

• Re: HTTP/2.0 SETTINGS frame values (Tuesday, 28 May)
• HTTP/2.0 SETTINGS frame values (Tuesday, 28 May)

Mike Belshe

• Re: HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Thursday, 27 June)
• Re: Out-of-order Frames (Sunday, 23 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Nit: Server-sent priority (Wednesday, 19 June)
• Fwd: Nit: Server-sent priority (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Saturday, 15 June)

Mike Bishop

• RE: HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• HTTP Layer rework and PUSH_PROMISE contents (Saturday, 29 June)
• RE: GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• RE: Questions on Server Push (Tuesday, 4 June)
• RE: Design Issue: Frame Size Items (Tuesday, 7 May)
• RE: Design Issue: Life-cycle of a Stream (Wednesday, 1 May)
• RE: For review: editorial updates pull request (Monday, 29 April)
• RE: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Friday, 26 April)

Nandita Dukkipati

• Re: HTTP/2 and TCP CWND (Thursday, 18 April)

Nico Williams

• Re: Resumable Uploads (Saturday, 20 April)
• Re: Resumable Uploads (Saturday, 20 April)

Osama Mazahir

• p2: section 5.3.2 (Accept header) (Thursday, 9 May)

Patrick McManus

• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Nit: Server-sent priority (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• http2 draft feedback on flow control (Wednesday, 22 May)
• Re: notes on http2 draft (Wednesday, 22 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• notes on http2 draft (Tuesday, 21 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Implementation Notes on Server Push (Tuesday, 14 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 17 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Monday, 1 April)

Paul Hoffman

• Re: How to pronounce "charset"? (Wednesday, 15 May)

Peter Lepeska

• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 26 April)
• Re: HTTP/2 and TCP CWND (Friday, 26 April)
• Comments on Explicit/Trusted Proxy (Thursday, 25 April)
• Re: HTTP/2 and TCP CWND (Thursday, 25 April)
• Re: HTTP/2 and TCP CWND (Thursday, 25 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 24 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 24 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Wednesday, 24 April)

Peter Occil

• Re: Expect: 100-continue and "final" status codes (Wednesday, 29 May)
• Re: obs-text character encoding and error handling; duplicate parameter names in Content-Type (Saturday, 25 May)
• Re: obs-text character encoding and error handling; duplicate parameter names in Content-Type (Saturday, 25 May)
• obs-text character encoding and error handling; duplicate parameter names in Content-Type (Saturday, 25 May)
• Re: Upgrade ordering (possible HTTP/2 impact) (Friday, 17 May)
• Re: Upgrade ordering (possible HTTP/2 impact) (Friday, 17 May)
• Part 2: Editorial changes involving "instance of time" (Wednesday, 15 May)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Wednesday, 15 May)

Phillip Hallam-Baker

• Re: HTTP in JSON Binary Encoding / Data Model (Wednesday, 29 May)
• HTTP in JSON Binary Encoding / Data Model (Wednesday, 29 May)

Poul-Henning Kamp

• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Proposal: New Frame Size Text (Saturday, 11 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Design Issue: Frame Size Items (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 26 April)

R S

• duplicate parameters (Monday, 10 June)

Robert Collins

• Re: HTTP/2 and TCP CWND (Monday, 1 April)

Roberto Peon

• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#150] Making certain settings mandatory (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: Issue #154: Sending a response before the request is complete (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: Out-of-order Frames (Monday, 24 June)
• Re: Is the ability to disable flow control really needed? (Friday, 21 June)
• Re: Header Compression (Friday, 21 June)
• Re: Questions on Frame Size (Thursday, 20 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: Nit: Server-sent priority (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Wednesday, 19 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• Re: Nit: Server-sent priority (Tuesday, 18 June)
• Re: GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• GOAWAY(AND_DONT_COME_BACK) (Tuesday, 18 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Tuesday, 18 June)
• RE: Multiple Headers (Monday, 17 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Sunday, 16 June)
• Re: port #? (Friday, 7 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Wednesday, 29 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Sunday, 26 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Saturday, 25 May)
• Re: Design Issue: GZIP flag on DATA Frames (Wednesday, 22 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: adding Header Continuation (Monday, 20 May)
• Re: "Magic" string (Monday, 20 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Tuesday, 14 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Tuesday, 14 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: How to pronounce "charset"? (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Sunday, 12 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Saturday, 11 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Saturday, 11 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: 3.5.1 Connection Error Handling (Thursday, 9 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Comments on Explicit/Trusted Proxy (Saturday, 4 May)
• Re: Comments on Explicit/Trusted Proxy (Saturday, 4 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Saturday, 4 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Saturday, 4 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Saturday, 27 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Saturday, 27 April)
• Re: Editorial Issue: Persisted Settings... when does the client need to return them? (Saturday, 27 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Saturday, 27 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: BWS (Friday, 19 April)
• Re: p1: BWS (Thursday, 18 April)
• Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Thursday, 18 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)
• Re: Header Serialization Discussion (Tuesday, 16 April)
• Re: Quoting email (was: HTTP/2 and TCP CWND) (Tuesday, 16 April)
• Re: Quoting email (was: HTTP/2 and TCP CWND) (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)
• Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? (Saturday, 13 April)
• Re: Updated Delta+BOHE Impl in Java (Tuesday, 9 April)
• Re: Compression analysis of perfect atom-based compressor (Friday, 5 April)
• Compression analysis of perfect atom-based compressor (Thursday, 4 April)
• Re: HTTP/2 and TCP CWND (Monday, 1 April)
• Re: HTTP/2 and TCP CWND (Monday, 1 April)

Roland Zink

• Re: Design Issue: GZIP flag on DATA Frames (Tuesday, 21 May)

Roy T. Fielding

• p6: Warning header field (Sunday, 9 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: Lingering Close (Sunday, 19 May)
• Re: p1: handling obs-fold (Sunday, 19 May)
• Re: WGLC: SHOULD and conformance (Sunday, 19 May)
• Re: p1: whitespace in request-target (Sunday, 19 May)
• Re: WGLC p1: Tear-down (Sunday, 19 May)
• Re: WGLC: SHOULD and conformance (Tuesday, 30 April)
• Re: p7: forwarding Proxy-* (Tuesday, 30 April)
• Re: p7: forwarding Proxy-* (Tuesday, 30 April)
• Re: p2: deprecating 205 Reset Content? (Monday, 29 April)

RUELLAN Herve

• RE: Multiple Headers (Monday, 17 June)
• RE: Header Compression (Monday, 17 June)
• RE: Header Compression (Monday, 17 June)
• RE: Multiple Headers (Monday, 17 June)
• RE: Multiple Headers (Monday, 17 June)
• RE: Header Compression (Tuesday, 11 June)
• RE: Header Compression (Thursday, 6 June)
• Header Compression (Wednesday, 5 June)
• RE: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• RE: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 26 April)
• RE: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• RE: Header Serialization Discussion (Tuesday, 16 April)
• RE: Header Serialization Discussion (Tuesday, 16 April)
• RE: Header Serialization Discussion (Monday, 15 April)
• RE: HeaderDiff specification (Monday, 8 April)
• RE: Compression analysis of perfect atom-based compressor (Friday, 5 April)

Ryan Hamilton

• Re: Header Compression (Wednesday, 5 June)

Salvatore Loreto

• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Wednesday, 8 May)

Sam Pullara

• Re: Out-of-order Frames (Sunday, 23 June)
• Re: Out-of-order Frames (Sunday, 23 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Out-of-order Frames (Saturday, 22 June)

Shigeki Ohtsu

• Re: Questions on Frame Size (Saturday, 22 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Questions on Frame Size (Thursday, 20 June)
• Re: Questions on Frame Size (Thursday, 20 June)
• Questions on Frame Size (Thursday, 20 June)
• Re: Questions on Server Push (Tuesday, 4 June)
• Re: Questions on Server Push (Tuesday, 4 June)
• Re: Questions on Server Push (Tuesday, 4 June)
• Questions on Server Push (Friday, 31 May)

Simpson, Robby (GE Energy Management)

• Re: Quoting email (was: HTTP/2 and TCP CWND) (Tuesday, 16 April)
• Re: Quoting email (was: HTTP/2 and TCP CWND) (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Tuesday, 16 April)
• Re: HTTP/2 and TCP CWND (Monday, 15 April)

Stephane Bortzmeyer

• Re: Status code 451 adoption (Tuesday, 16 April)

Stephen Farrell

• Re: Comments on Explicit/Trusted Proxy (Sunday, 5 May)
• Re: Comments on Explicit/Trusted Proxy (Saturday, 4 May)
• Re: Comments on Explicit/Trusted Proxy (Saturday, 4 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 3 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Thursday, 2 May)
• Re: Comments on Explicit/Trusted Proxy (Friday, 26 April)
• Re: Web Keys and HTTP Signatures (Thursday, 18 April)

Tatsuhiro Tsujikawa

• Re: Header Compression (Friday, 7 June)

Ted Hardie

• Re: Header Compression (Thursday, 20 June)
• Re: Header Compression (Tuesday, 11 June)
• Re: port #? (Friday, 7 June)

Tim Bray

• Re: How to pronounce "charset"? (Monday, 13 May)
• Re: Status code 451 adoption (Tuesday, 16 April)
• Re: Status code 451 adoption (Tuesday, 16 April)
• Status code 451 adoption (Monday, 15 April)

Werner Baumann

• Re: Comments on Explicit/Trusted Proxy (Sunday, 5 May)

Wesley Eddy

• Re: HTTP/2 and TCP CWND (Friday, 19 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 17 April)

Willy Tarreau

• Re: HTTP URI in the form of "http://example.com?query" (Wednesday, 5 June)
• Re: #458: Requirements upon proxies for Expect (Tuesday, 4 June)
• Re: #458: Requirements upon proxies for Expect (Friday, 31 May)
• Re: #467: Expect: 100-continue and "final" status codes (Wednesday, 29 May)
• Re: #467: Expect: 100-continue and "final" status codes (Tuesday, 28 May)
• Re: p1: whitespace in request-target (Sunday, 19 May)
• Re: #467: Expect: 100-continue and "final" status codes (Friday, 17 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• Re: WGLC p1: MUST fix Content-Length? (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• Re: WGLC p1: proxy handling of a really bad Content-Length (Wednesday, 1 May)
• Re: WGLC p1: MUST fix Content-Length? (Wednesday, 1 May)
• Re: p2: Accept-Language missing, empty or no match (Wednesday, 1 May)
• Re: WGLC: p1 MUST NOT pipeline until connection is persistent (Wednesday, 1 May)
• Re: WGLC: p1 MUSTs (Tuesday, 30 April)
• Re: WGLC: p1 MUSTs (Tuesday, 30 April)
• Re: p7: forwarding Proxy-* (Tuesday, 30 April)
• Re: WGLC p1: Tear-down (Tuesday, 30 April)
• Re: WGLC: SHOULD and conformance (Tuesday, 30 April)
• Re: p1: whitespace in request-target (Tuesday, 30 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 30 April)
• Re: WGLC p1: Tear-down (Monday, 29 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p1: Via and gateways (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: p1: additional security considerations (Tuesday, 23 April)
• Re: p1: Via and gateways (Tuesday, 23 April)
• Re: p1: additional security considerations (Tuesday, 23 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• Re: p2: Requirements upon proxies for Expect (Saturday, 20 April)
• Re: p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p2: Purely editorial feedback (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Saturday, 20 April)
• Re: p1: generating "internal" errors (Saturday, 20 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Saturday, 20 April)
• Re: p1: generating "internal" errors (Saturday, 20 April)
• Re: p1: handling obs-fold (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• Re: p1: Receiving a higher minor HTTP version number (Saturday, 20 April)
• Re: p1: Via and gateways (Saturday, 20 April)
• Re: p1: BWS (Friday, 19 April)
• Re: p1: BWS (Thursday, 18 April)
• Re: p1: whitespace in request-target (Thursday, 18 April)
• Re: HTTP 2.0 "Upgrade" flow (Wednesday, 17 April)

Yi, EungJun

• How to pronounce "charset"? (Monday, 13 May)

Yoav Nir

• Re: [#153] PUSH_PROMISE headers (Saturday, 29 June)
• Re: Header Compression (Thursday, 6 June)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Tuesday, 14 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Tuesday, 14 May)
• Re: How to pronounce "charset"? (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Monday, 13 May)
• Re: Design: Ignored Unknown Frame Types and Intermediaries (Sunday, 12 May)
• Re: http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset (Wednesday, 8 May)
• Re: Comments on Explicit/Trusted Proxy (Monday, 6 May)
• Re: Comments on Explicit/Trusted Proxy (Sunday, 5 May)
• Re: Comments on Explicit/Trusted Proxy (Saturday, 27 April)
• Re: Resumable Uploads (Saturday, 20 April)

Yuchung Cheng

• Re: HTTP/2 and TCP CWND (Monday, 29 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 17 April)

Zhong Yu

• Re: Out-of-order Frames (Sunday, 23 June)
• Re: HTTP URI in the form of "http://example.com?query" (Wednesday, 5 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• Re: HTTP URI in the form of "http://example.com?query" (Tuesday, 4 June)
• HTTP URI in the form of "http://example.com?query" (Monday, 3 June)
• Re: #467: Expect: 100-continue and "final" status codes (Tuesday, 28 May)
• Re: #467: Expect: 100-continue and "final" status codes (Friday, 17 May)
• Re: WGLC p1: Delimiting messages with multipart/byteranges (Monday, 29 April)
• Re: WGLC p1: Tear-down (Monday, 29 April)
• Re: WGLC p1: Delimiting messages with multipart/byteranges (Monday, 29 April)
• Re: p2: Expectation extensions (Thursday, 25 April)
• Re: p2: Expect: 100-continue and "final" status codes (Wednesday, 24 April)
• Re: p2: Expect: 100-continue and "final" status codes (Tuesday, 23 April)
• Re: p2: Content-Length in HEAD responses (Saturday, 20 April)
• Re: p1: HTTP(S) URIs and fragment identifiers (Saturday, 20 April)

イアンフェッティ

• Re: How to pronounce "charset"? (Monday, 13 May)

陈智昌

• Re: Summer of Code project (Monday, 24 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Out-of-order Frames (Saturday, 22 June)
• Re: Is the ability to disable flow control really needed? (Saturday, 22 June)
• Re: Is the ability to disable flow control really needed? (Saturday, 22 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Questions on Frame Size (Friday, 21 June)
• Re: Design: Adding ASSOCIATED_ONLY (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR (Wednesday, 19 June)
• Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity (Sunday, 16 June)
• Re: Preliminary agenda for the SF Interim (Tuesday, 4 June)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 4 June)
• Re: Preliminary agenda for the SF Interim (Tuesday, 4 June)
• Re: HTTP/2.0 SETTINGS frame values (Monday, 3 June)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits (Tuesday, 28 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: notes on http2 draft (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY (Tuesday, 21 May)
• Re: Implementation Notes on Server Push (Thursday, 16 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Wednesday, 15 May)
• Re: Implementation Notes on Server Push (Tuesday, 14 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Monday, 13 May)
• http/2 test framework (Sunday, 12 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Design Issue: Overlong Frames (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Friday, 10 May)
• Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) (Thursday, 9 May)
• Re: 3.5.1 Connection Error Handling (Thursday, 9 May)
• 3.5.1 Connection Error Handling (Thursday, 9 May)
• Re: http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset (Wednesday, 8 May)
• redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS (Wednesday, 8 May)
• http://http2.github.io/http2-spec/#rfc.section.3.1 connections (Wednesday, 8 May)
• http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset (Wednesday, 8 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: Design Issue: Frame Size Items (Tuesday, 7 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Saturday, 4 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Saturday, 4 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• http/2 initial limits - i see flow control initial limits specified, but not stream limits (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Friday, 3 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Wednesday, 1 May)
• Re: Design Issue: Life-cycle of a Stream (Wednesday, 1 May)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Request: Have git commit messages for design changes include links to relevant discussion email threads (Monday, 29 April)
• Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams (Monday, 29 April)
• Re: p2: deprecating 205 Reset Content? (Monday, 29 April)
• Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks (Sunday, 28 April)
• Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? (Sunday, 28 April)
• Re: Editorial Issue: Persisted Settings... when does the client need to return them? (Sunday, 28 April)
• Re: Design Issue: PUSH_PROMISE and Stream Priority (Friday, 26 April)
• Re: Design Issue: Must Ignore Rule for Unknown Frame Types (Friday, 26 April)
• Re: Push Promise Issues (Friday, 26 April)
• Re: HTTP/2 and TCP CWND (Friday, 26 April)
• Re: HTTP/2 and TCP CWND (Thursday, 25 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 24 April)
• Re: Push Promise Issues (Wednesday, 24 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Wednesday, 24 April)
• Re: HTTP/2 and TCP CWND (Wednesday, 24 April)
• Re: what's up with commenting on http/2 github issues (Wednesday, 24 April)
• what's up with commenting on http/2 github issues (Wednesday, 24 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Wednesday, 24 April)
• Re: p1: Upgrade ordering (possible HTTP/2 impact) (Tuesday, 23 April)
• Re: Git Issues: Reserved Stream-ID Bit (Saturday, 20 April)
• Re: Git Issues: PING (Saturday, 20 April)

Last message date: Sunday, 30 June 2013 20:13:58 UTC