1 | HTTPbis WG |
---|
2 | ---------- |
---|
3 | |
---|
4 | Mark discussed the status of the Working Group; there is still an intent to |
---|
5 | get to LC by the end of the year. |
---|
6 | |
---|
7 | Yves covered the changes in the -14 and -15 drafts; see the presentation for |
---|
8 | details. |
---|
9 | |
---|
10 | We worked through the issues identified in the agenda; there was general |
---|
11 | agreement with the approaches outlined in list discussion. |
---|
12 | |
---|
13 | Larry asked about IRIs and whether we needed to account for the charset of |
---|
14 | the context in query parameters; Roy pointed out that this is indeed |
---|
15 | context-specific, and so can't be defined by HTTP generically. |
---|
16 | |
---|
17 | Julian gave an overview of the more difficult aspects of HTTP header parsing |
---|
18 | (see presentation), primarily as input to the issue regarding header |
---|
19 | microsyntax, but also as a prelude to potential alignment in existing headers. |
---|
20 | |
---|
21 | We then had a look at tools, such as Julian's test cases |
---|
22 | <http://greenbytes.de/tech/tc/> and REDbot <http://redbot.org/>. We also |
---|
23 | highlighted the effort to socialise RFC6266 with server-side frameworks |
---|
24 | <http://trac.tools.ietf.org/wg/httpbis/trac/wiki/ContentDispositionProducerAdvice>. |
---|
25 | |
---|
26 | Larry posited that we should be thinking about / starting / finding people |
---|
27 | to to interoperability testing. |
---|
28 | |
---|
29 | Jim Gettys highlighted bufferbloat problems, and asked people to start |
---|
30 | thinking about the implications in future work (see |
---|
31 | <http://gettys.wordpress.com/bufferbloat-faq/>). |
---|
32 | |
---|
33 | We don't intend to meet in Taipei. |
---|
34 | |
---|
35 | Jabber logs at: <http://www.ietf.org/jabber/logs/httpbis/2011-07-26.html> |
---|