ietf-http-wg@w3.org from April to June 2014 by subject

#304, was: If-Range and cache validation using Last-Modified

#421: Mixed Schemes

#423: Security Implications of GZIP

#429: HPACKing security/privacy related header fields

#436: Enable weight of 0

#444: Flushing Alt-Svc Cache

#445: Transfer-Codings

#445: Transfer-codings - Alternate proposal

#446: alt-svc header field syntax

#460 [was: Transfer-codings, mandatory content-coding support and intermediaries]

#462: Intermediaries and Alt-Svc [was: Alt-Svc related Chromium bug report (proxy related)]

#466 segment compression

#492: Alt-Svc header host restriction

#535: No 1xx Status Codes

#540 jumbo frame, was: Stuck in a train -- reading HTTP/2 draft.

#540: "jumbo" frames

#541: Stateless Multiplexable Continuations

*** GMX Spamverdacht *** Re: Including screen size to header messages (extending UserAgent)

401 ("unauthenticated" v.s. "unauthorized")

[Technical Errata Reported] RFC7231 (4031)

Addressing gzip focus

agenda/charter brainstorming

ALPN RFC

Alt-Svc header + ALTSVC frame

Alt-Svc related Chromium bug report (proxy related)

Alt-Svc with UPGRADE

Alternative Service Indication

Ambiguous case in WWW-Authenticate grammar?

Back to the drawing board? was: #540: "jumbo" frames

BLOCKED frame specification

C-E for clients, was: Support for gzip at the server #424 (Consensus Call)

Call for Consensus: HTTP/2 Priorities Proposal

Clarifications on flow control and padding

Client Behavior for SETTINGS_TIMEOUT

Coalescing #490

Coalescing and Connection Management

Confusing numbering of flags & bits

Connection fatal HTTP/2 stream errors

CONTINUATION proposal w/ minimum change

CONTINUATION was: #540: "jumbo" frames

CRLF requirement

Dealing with BLOCKED

Dealing with BLOCKED [#362]

decompression at 2 -> 1.1 gateway breaks ranges

Design FAQs, Was: Our Schedule

Diminishing priorities in proposal

Done

draft-hutton-httpbis-connect-protocol-00.txt

Enable weight of 0

Encoding Context Update

END_SEGMENT and END_STREAM redundant

END_SEGMENT and headers

END_SEGMENT and headers, #2

END_SEGMENT?

END_SEGMENT? (#397)

END_SEGMENT? (#537)

END_STREAM flag and trailing headers

explicitly authenticated proxy: new draft

ezflate: proposal to reinstitute deflate header compression

fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression

Fourth Implementation Draft [was: I-D Action: draft-ietf-httpbis-http2-12.txt]

Frame Length Restrictions

Framing the proxy discussion

Framing the proxy discussion: does HTTP2 come with new proxy mechanism ?

Fwd: HPACK

Fwd: httpbis - Requested sessions have been scheduled for IETF 90

Fwd: I-D Action: draft-prudhommeaux-http-status-2nn-00.txt

Fwd: New Version Notification for draft-ietf-httpbis-http2-encryption-00.txt

Fwd: New Version Notification for draft-nottingham-http-over-version-00.txt

Fwd: New Version Notification for draft-nottingham-http2-encryption-03.txt

Fwd: New Version Notification for draft-nottingham-http2-ops-00.txt

Fwd: New Version Notification for draft-snell-link-method-09.txt

Fwd: Stuck in a train -- reading HTTP/2 draft.

GOAWAY and proxies

GOAWAY and proxies (#458)

GOOGLE SAVES THE WORLD - Range request utility: Chrome vs FF vs IE vs Safari

Graceful shutdown #458

GZip Content-Encoding / Reopen #404

h2#404 requiring gzip and/or deflate

Hard fail on self-dependency

Header fair share, Was: Our Schedule

Header Field definition is too broad

Header Size? Was: Our Schedule

HEADERS and flow control

heads in the _security_ sand was: fixing TLS vulnerabilities with h2 was: ezflate: proposal to reinstitute deflate header compression

HPACK

hpack huffman codes

HPACK problems (was http/2 & hpack protocol review)

HPACK security considerations

hpack static table question?

hpack table size 0

HTTP status code for transaction incomplete???

HTTP/1.1 and HTTP/2 investigation document

HTTP/1.1: They're done.

http/2 & hpack protocol review

HTTP/2 Implementation Draft 5 (and getting to Working Group Last Call)

HTTP/2 in examples

HTTP/2 Priorities Proposal

HTTP/2 vs 1.1 semantics: intermediate codes

HTTP/2 vs. proxies ?

http2 Working Code

I-D Action: draft-hutton-httpbis-connect-protocol-00.txt

I-D Action: draft-ietf-httpbis-alt-svc-01.txt

I-D Action: draft-ietf-httpbis-header-compression-07.txt

I-D Action: draft-ietf-httpbis-header-compression-08.txt

I-D Action: draft-ietf-httpbis-http2-11.txt

I-D Action: draft-ietf-httpbis-http2-12.txt

I-D Action: draft-ietf-httpbis-http2-13.txt

I-D Action: draft-ietf-httpbis-http2-encryption-00.txt

I-D Action: draft-lnageleisen-http-chunked-progress-00.txt

improved caching in HTTP: new draft

Including screen size to header messages (extending UserAgent)

Indicating Chosen Service #443

Initial agenda for Toronto

Interleaving #481 (was Re: Limiting header block size)

intermediaries, implicit gzip, etags, no-transform

Internet draft making SSL/TLS more transparent to the user

Issues for discussion in NYC

jumbo frame, was: Stuck in a train -- reading HTTP/2 draft.

large file transfers, was: Please admit defeat

Limiting allowable pre-SETTINGS requests

Limiting header block size

Maintenance frame contention vs CONTINUATION

Major decisions at the NYC Interim

Making extensibility cheap

Making Implicit C-E work.

Minor points in draft 12

Minutes Etherpad

Minutes from the New York Interim

Moving 421

Negotiating compression

Negotiating extensions

New HTTP/2 draft

New Version Notification for draft-bishop-http2-extension-frames-01.txt

New Version Notification for draft-nottingham-http2-encryption-03.txt

New Version Notification for draft-nottingham-http2-ops-00.txt

OAuth 2.0 - Proxy-Authenticate Bearer

Ops advice

Optimizing Huffman inputs

Other work items

Our Schedule

Padding should be specified for PUSH_PROMISE frames too?

PING frame behavior

Please admit defeat

Please admit defeat (was: Our Schedule)

PONG (was Re: Why do DATA frames have padding?)

Porting T-E to HTTP/2: Reasons Against

Priority inside PUSH_PROMISE frames

proposed clarifications regarding the state machine (editorial)

Proxies (includes call for adopting new work item, call for input)

Proxies (includes call for adopting new work item, call for input), ## HTTP Proxy Problems

push vs safe methods with payload, Re: END_STREAM flag and trailing headers

Question on HTTP 408

Range Requests vs Content Codings

REFUSED_STREAM and HPACK

Remove reserved bits from ALTSVC #467

Reservation and validity of colon-prefixed header keys

Reserved extension ids

review: http2-10

SETTINGS frames as header blocks?

Shipping, was: BLOCKED frame specification

Should we discuss "split UAs" in the context of proxies, was: Proxies (includes call for adopting new work item, call for input)

State of the Protocol (2014-03-31)

Stateless Multiplexable Continuations #541

Stricter TLS Usage in HTTP/2

strong server authentication

Stuck in a train -- reading HTTP/2 draft.

Support for gzip at the server #424 (Consensus Call)

TLS Renegotiation and HTTP/2 (#363)

Toronto

Transfer-codings, mandatory content-coding support and intermediaries

Trusted proxy UI redux

Trusted proxy UI strawman

unclaimed push streams using up the connection window

Values for Accept-Encoding

what about Proxies in Toronto?

Who to trust?

Why do DATA frames have padding?

why not multiple, short-lived HTTP/2 connections?

Will HTTP/2.0 be green ?

Zero weight for 100 CONTINUE, instead of flow control

Last message date: Monday, 30 June 2014 23:48:15 UTC