[agenda] CT Teleconference Tuesday 18 March 2008

Hi guys,

I'm enjoying a few days off, and must confess I preferred skiing to
CT-ing during that time... I suggest we move forward with the parts of
the drafts not resolved/reviewed yet.

Note to US residents: the call is still one hour later than it was
before.


-----
Chair: François
Staff Contact: François
Known regrets: Jo

Date: 2008-03-18T1500Z for 60mn
Phone: +1.617.761.6200, +33.4.89.06.34.99, +44.117.370.6152
Conference code: 2283 ("BCTF") followed by # key
IRC channel: #bpwg on irc.w3.org, port 6665.

Latest draft:
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080313
(Thanks for this new draft, Jo!)

Agenda:

1. Reminder: actions
--------------------
http://www.w3.org/2005/MWI/BPWG/Group/track/products/12


2. HTTPS rewrite (in §3.4)
--------------------------
- Review of Andrew's contribution (ACTION-633), adapted by Jo in latest
draft:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Feb/0026.html


3. Cache-control: no-transform and WAP gateways (in §1.2 and §3.2)
------------------------------------------------------------------
- Review of fd contribution (ACTION-634)
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Feb/0011.html
(and replies)


4. Server Response to Proxy (§3.2)
----------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#sec-ServerResponse
- recommend the use of the HTTP Vary header
- references to POWDER
- recommend the use of <link> elements?
- HTTP-300 and/or give the user a choice of representations


5. Proxy Receipt and Forwarding of Response from Server (§3.3)
--------------------------------------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#d0e508
- how does that fit with the content tasting approach?


6. Proxy Response to Client (§3.4)
----------------------------------
http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#d0e521
- how to advertise transformations done? Suggestions:
     + using the VIA header
     + using the PRAGMA header
     + don't advertise
- heuristics: anything else? (detection of mobile-friendly patterns in 
the URI? More on link elements?)
- resolution on dangerous content.


7. Further discussions / open questions if time allows
------------------------------------------------------
- Impact on sites that use redirections from the home page rather than 
adaptation?
- CT and redirections: use cases
- Requirements: things we can't address with existing technologies.

Received on Sunday, 16 March 2008 22:10:02 UTC