Skip to content
Permalink
gh-pages
Switch branches/tags

wg-materials/interim-13-06/agenda.md

Go to file
 
 
Cannot retrieve contributors at this time
HTTPbis Interim Meeting Agenda San Francisco, USA 13-14 June 2013 Related Documents Schedule THURSDAY 13 June 2013 FRIDAY 14 June 2013 Agenda Administrivia HTTP/2 Draft Review HTTP/2 Issues Upgrade Frame Layout Frame Semantics Stream Life Cycle Header Compression Server Push Flow Control Prioritization HTTP Mapping Transport Mapping Other Issues and Deliverables Implementation and Testing Wrap-up
168 lines (113 sloc) 5.9 KB
Raw Blame

HTTPbis Interim Meeting Agenda

San Francisco, USA 13-14 June 2013

(Meeting Arrangements)

Related Documents

Schedule

THURSDAY 13 June 2013

0830-0900 Reception
0900-1200 Morning Session
1200-1300 Lunch
1300-1500 Afternoon Session I
1500-1530 Break
1530-1700 Afternoon Session II

FRIDAY 14 June 2013

0830-0900 Reception
0900-1200 Morning Session
1200-1300 Lunch
1300-1500 Afternoon Session I
1500-1530 Break
1530-1700 Afternoon Session II

Agenda

Administrivia

  • Blue sheets
  • Introductions
  • Scribe selection
  • Agenda bashing
  • NOTE WELL
  • Ground rules for the meeting

HTTP/2 Draft Review

Martin Thomson will preset a review of the current draft and seek guidance on any outstanding editors' questions.

HTTP/2 Issues

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

Frame Layout

Frame Semantics

Stream Life Cycle

Header Compression

Server Push

Flow Control

Prioritization

HTTP Mapping

Transport Mapping

Other Issues and Deliverables

Discussion of other potential issues (editorial or design), additional deliverables, etc.

Implementation and Testing

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?

Wrap-up

We'll review action items and plan next steps, including future meetings: