See also: IRC log
<Bryan> here
<jo> Scribe: Jo
<scribe> Scribe: AndrewSwainston
<jo> ACTION-575
<jo> Sean: Aaron had comments on this this
<jo> ... clarify no 5 - this is the idea where the original header gets sent and then replaced depending ont he content?
<jo> jo: yes
<jo> sean: ok, think I need to get back by email with comments
<jo> jo: sure, that's what I was expecting, we need to discuss on email first
<jo> ... some of them are worth trying to see
<jo> ... if they work in a significant
<jo> no of cases
Bryan: Good list. Use of HEAD does work in practice
... particularly used for WAP1
Jo: We need a survey of how many of these options are supported
... Possible issue with only changing the User-Agent
... hence idea of sending original headers in body of a GET
... indicated in #7
Sean: Would be problems with POST
Bryan: Have experience of using a body inside a GET - does work
<jo> Andrew: changing user agent is seen as being important, do we have any evidence to support that?
<jo> ... raised on earlier call
<jo> sean: we do have data I am trying to get it, will chase
Jo: Have interesting statistics but cannot currently share
<jo> andrew: CT PRoxy should augment but not remove content types from accept header?
<jo> Sean: I guess ... depends if the proxy can handle it
Jo: Need to raise as an issue in the guide lines
AndrewSwainston: Good list as focus of discussion
Jo: Missing - addition of Warn header
Bryan: Question: What exactly is a CT's proxy in view of BPWG?
... if to improve usability OK but policy may be outside BPWG
... Example of policy is parental control, or to reduce cost of network use
... can not assume all policy control is at ends of communication, some is in the middle
<jo> thread with Bryan's comments
Jo: Idealy need a framework for all types of proxies but this would be outside of the BPWG domain
... we probable have sufficient to work on if we limit ourselves to CT
Bryan: A mechanism to exchange end point requirements would cover other cases
... Example - user goes to portal with links to a competitor's site - may want to remove links because these would not work via own network
... Example - may need to change domain names in links to make them work
Jo: Some of these examples could fit our remit
Bryan: Happy to accept existing scope of problem statement
Jo: Suggestion that name of problem statement changes
<jo> -- Title: Proxy Transformation of Web Content
<jo> -- Sub-Title: Statement of Current Issues
Jo: No one on call minds change in name
Jo: Will send a note reminding about weekly calls