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

"Magic" string

#440: max of max-age

#442: p1: BWS

#443: p1: whitespace in request-target

#443: whitespace in request-target

#448, was: p2: Accept-Language missing, empty or no match

#453: Returning the freshest response

#458: Requirements upon proxies for Expect

#461, was: p4: editorial suggestions

#462, was: p5: editorial suggestions

#463, was: p7: editorial suggestions

#464, was: p7: editorial suggestions

#467: Expect: 100-continue and "final" status codes

#469: definition of "private"

#474, was: WGLC p7: Parsing auth challenges

#481, was: WGLC: p7 MUSTs

#482l was: WGLC p1: proxy handling of a really bad Content-Length

#486, was: p2: Expectation extensions

#486: Requiring proxies to process warn-date

#487 Resubmission of 403

3.3.1 Frame Header: Purpose of 1-bit reserved field?

3.5.1 Connection Error Handling

[#150] Making certain settings mandatory

[#153] PUSH_PROMISE headers

[http-auth] Associating URI-based identities with HTTP requests

[saag] Is the CA market broken?

A modest proposal

adding Header Continuation

ADMIN: Discussion on Github issues

Agenda for June Interim meeting

Associating URI-based identities with HTTP requests

Brief header compression comments

Caching 412 responses

Comments on Explicit/Trusted Proxy

Compression analysis of perfect atom-based compressor

DASH/XMPP workshop

Design Issue: Can we go ahead and remove persistent settings?

Design Issue: Frame Processing Model

Design Issue: Frame Size Items

Design Issue: GZIP flag on DATA Frames

Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created??

Design Issue: Life-cycle of a Stream

Design Issue: Max Concurrent Streams Limit and Unidirectional Streams

Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type

Design Issue: Must Ignore Rule for Unknown Frame Types

Design Issue: Overlong Frames

Design Issue: PUSH_PROMISE and Stream Priority

Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY

Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks

Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?

Design: Adding ASSOCIATED_ONLY

Design: Frame type extensibility issues

Design: Ignored Unknown Frame Types and Intermediaries

Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR

draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion

draft-snell-http-prefer: Preference-Applied

draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path

duplicate parameters

Editorial Issue: Persisted Settings... when does the client need to return them?

Editorial Issue: Uniteral Stream Creation

Editorial Issue: Unknown/Undefined Settings IDs

Editorial Issues: Section 4.2.2

Editorial notes on p6

END_STREAM on PUSH_PROMISE

Expect: 100-continue and "final" status codes

For review: editorial updates pull request

Fwd: HTTPBIS WG Interim Meeting, August 5-7, 2013

Fwd: HTTPBIS WG Interim Meeting, June 13-14, 2013

Fwd: I-D Action: draft-ietf-httpbis-http2-02.txt

Fwd: New Version Notification for draft-snell-httpbis-bohe-08.txt

Fwd: New Version Notification for draft-snell-httpbis-bohe-09.txt

Fwd: New Version Notification for draft-snell-httpbis-ext-frames-00.txt

Fwd: Nit: Server-sent priority

Fwd: Summer of Code project

FYI.. merged pull request..

FYI: Header Compression

Git Issues: PING

Git Issues: Reserved Stream-ID Bit

GOAWAY(AND_DONT_COME_BACK)

Header Compression

Header compression question

Header compression, editorial

Header Serialization Discussion

HeaderDiff specification

How to pronounce "charset"?

HTTP 2.0 "Upgrade" flow

HTTP in JSON Binary Encoding / Data Model

HTTP Layer rework and PUSH_PROMISE contents

HTTP Mapping editorial changes

HTTP Request+Response issues

HTTP URI in the form of "http://example.com?query"

HTTP/2 and TCP CWND

http/2 initial limits - i see flow control initial limits specified, but not stream limits

http/2 test framework

HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge"

HTTP/2.0 SETTINGS frame values

http2 draft feedback on flow control

http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset

http://http2.github.io/http2-spec/#rfc.section.3.1 connections

HTTPBIS WG Interim Meeting, August 5-7, 2013

HTTPBIS WG Interim Meeting, June 13-14, 2013

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

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

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

Implementation Notes on Server Push

Is the ability to disable flow control really needed?

Is the CA market broken?

Issue #154: Sending a response before the request is complete

Issue re. HTTP2 STREAM and HEADER block use same end bit polarity

Lingering Close

Multiple Headers

Nit: Server-sent priority

notes on http2 draft

obs-text character encoding and error handling; duplicate parameter names in Content-Type

Out-of-order Frames

Outcomes of the SF Interim Meeting

p1/p2: 203 Non-Authoritative Information

p1: additional security considerations

p1: BWS

p1: generating "internal" errors

p1: handling obs-fold

p1: HTTP and TCP name delegation

p1: HTTP(S) URIs and fragment identifiers

p1: Purely Editorial Feedback

p1: Receiving a higher minor HTTP version number

p1: transfer coding registry

p1: Upgrade ordering (possible HTTP/2 impact)

p1: Via and gateways

p1: whitespace in request-target

p2 / p6: What is "cacheable"?

p2: Accept-Language missing, empty or no match

p2: Considerations for new headers

p2: Content-Length in HEAD responses

p2: deprecating 205 Reset Content?

p2: editorial for Expect and 1xx

p2: Expect: 100-continue and "final" status codes

p2: Expectation extensions

p2: Purely editorial feedback

p2: Requirements upon proxies for Expect

p2: scope for status codes

p2: section 5.3.2 (Accept header)

p4: editorial suggestions

p5: editorial suggestions

p6: Returning the freshest response

p6: Vary and effects on future requests

p6: Warning header field

p7: editorial suggestions

p7: forwarding Proxy-*

Part 2: Editorial changes involving "instance of time"

Planning for Future Meetings

port #?

Preliminary agenda for the SF Interim

Proposal - Reduce HTTP2 frame length from 16 to 12 bits

Proposal: New Frame Size Text

Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)

Push Promise Issues

PUT, If-Match, 412 - over-constrained?

Question on Multiplicity of Authorization and WWW-Authenticate

Questions on Frame Size

Questions on Server Push

Quoting email (was: HTTP/2 and TCP CWND)

Ranges

redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS

Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication

Request: Have git commit messages for design changes include links to relevant discussion email threads

Requiring proxies to process warn-date

Resumable Uploads

Rough Minutes from SF F2F

RST_STREAM and FINAL flag

Status code 451 adoption

Summer of Code project

Transitioning to TLS Application Layer Protocol Negotiation (ALPN)

Until HTTP header when the representation will disappear in the future

Updated Delta+BOHE Impl in Java

Updated I-D..

Updated Link I-D

Upgrade ordering (possible HTTP/2 impact)

UTF-8 text

UTF-8 text (was: Header Serialization Discussion)

Web Keys and HTTP Signatures

WGLC p1: Delimiting messages with multipart/byteranges

WGLC p1: MUST fix Content-Length?

WGLC p1: Persistence & 1.1 proxies

WGLC p1: proxy handling of a really bad Content-Length

WGLC p1: Scope of https update

WGLC p1: Tear-down

WGLC p7: Parsing auth challenges

WGLC: misused SHOULDs

WGLC: p1 MUST NOT pipeline until connection is persistent

WGLC: p1 MUSTs

WGLC: p2 MUSTs

WGLC: p4 MUSTs

WGLC: p4, 304 Not Modified

WGLC: p5 multiple Range headers

WGLC: p5 MUSTs

WGLC: p6 editorial nits

WGLC: p6 MUSTs

WGLC: p7 MUSTs

WGLC: SHOULD and conformance

WGLC: Strengthening SHOULDs

what's up with commenting on http/2 github issues

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

AltStyle によって変換されたページ (->オリジナル) /