- Hypertext Transfer Protocol version 2.0
- Header Diff: A compact HTTP header representation for HTTP/2.0
- Header Delta-Compression for HTTP/2.0
- A DNS Resource Record for Service Descriptions
0830-0900 Reception
0900-1200 Morning Session
1200-1300 Lunch
1300-1500 Afternoon Session I
1500-1530 Break
1530-1700 Afternoon Session II
0830-0900 Reception
0900-1200 Morning Session
1200-1300 Lunch
1300-1500 Afternoon Session I
1500-1530 Break
1530-1700 Afternoon Session II
- Blue sheets
- Introductions
- Scribe selection
- Agenda bashing
- NOTE WELL
- Ground rules for the meeting
Martin Thomson will preset a review of the current draft and seek guidance on any outstanding editors' questions.
The primary focus of the issues discussion is to converge on what we need to do to publish a First Implementation Draft. As such, we can decide to skip any issue that isn't relevant to that goal in this meeting.
See also the Issues List.
- Upgrade Mechanism - general review
- Advertising Settings During Negotiation
- Pre-Upgrade Requests
- Magic Syntax
- Registry of Opaque Strings
- Cross-Protocol Attacks
- Opaque Data in RST_STREAM and GOAWAY
- Stream ID in GOAWAY
- Ping Payload
- The FINAL Flag
- Frame Extensibility
- SETTINGS persistence
- Discovering Maximum Frame Size
- Unilateral Stream Creation
- Concurrent Streams Limits and Unidirectional Streams
- Separate HEADERS+PRIORITY
- Frame Size limits
- SETTINGS_MAX_CONCURRENT_STREAMS
- Header Compression - selecting a candidate
- Routing Data in Headers
- Header Block Field Name Length
- Prioritisation - general review
- Priority
- Trailers
- Negotiation of trailers
- Handling Expect/continue
- Indicating the end of a header block
- Rejecting non-idempotent requests
- SETTINGS_CURRENT_CWND
- SETTINGS_UPLOAD_BANDWIDTH
- SETTINGS_DOWNLOAD_BANDWIDTH
- SETTINGS_ROUND_TRIP_TIME
- SETTINGS_DOWNLOAD_RETRANS_RATE
- TCP Exclusivity
Discussion of other potential issues (editorial or design), additional deliverables, etc.
We should have a first implementation draft shortly after the meeting, if all goes well. As such, our next phase of work should be implementing and testing the draft.
We'll discuss the schedule involved, in light of the upcoming Hamburg interim meeting. In addition to implementation planning, we'll need to start documenting how we'll perform testing.
In particular, we should discuss what aspects of the following will be tested in the first instance:
- Upgrade mechanisms: APLN? Dedicated port? Upgrade?
- Flow control?
- Prioritization?
- Server push?
We'll review action items and plan next steps, including future meetings:
- Berlin IETF
- Hamburg Interim
- 2013 Q4 Interim?
- Vancouver IETF
- 2014 Q1 Interim?