W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > September 2008

RE: [agenda] CT Call Tuesday 30 September 2008

From: Sullivan, Bryan <BS3131@att.com>
Date: Mon, 29 Sep 2008 23:09:44 -0700
Message-ID: <8080D5B5C113E940BA8A461A91BFFFCD0B9EA6BE@BD01MSXMB015.US.Cingular.Net>
To: "public-bpwg-ct" <public-bpwg-ct@w3.org>
Regrets, I have a conflict for tomorrow's call.

Best regards,
Bryan Sullivan | AT&T


-----Original Message-----
From: public-bpwg-ct-request@w3.org [mailto:public-bpwg-ct-request@w3.org] On Behalf Of Francois Daoust
Sent: Monday, September 29, 2008 4:02 AM
To: public-bpwg-ct
Subject: [agenda] CT Call Tuesday 30 September 2008


Hi guys,

Here is the agenda for tomorrow.
The rumor has it that Jo may not be on the call tomorrow, so the points 
below that specifically address Jo's comments may have to be postponed 
by a week.


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

Date: 2008-09-23T1400Z 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.


1. LC-2090, LC-2091 on headers/footers
-----
- continue with the discussion started last week.
- headers/footers are out of scope.
- clarify the Scope section re. headers/footers/ads?


2. LC-2012: clarification of the introduction
-----
Following Jo's comment on the text resolved last week:
PROPOSED RESOLUTION: re. LC-2012, replace the sentence deemed obscure by 
"Within this document content transformation refers to the manipulation 
  of requests to, and responses from, an origin server. This 
manipulation is carried out by proxies in order to provide a better user 
experience of content that would otherwise result in an unsatisfactory 
experience on the device making the request."


3. LC-2068: on requests that contain Cache-Control: no-transform directives
-----
Following Jo's comment on the text resolved last week:
PROPOSED RESOLUTION: re. LC-2068, amend the text in section 4.1.2 with 
references to RFC HTTP sections. Final text: "If the request contains a 
Cache-Control: no-transform directive, proxies must not alter the 
request other than to comply with transparent HTTP behavior defined in 
HTTP RFC 2616 sections 14.9.5 and 13.5.2. and to add headers as 
described in 4.1.6 Additional HTTP Headers below."


4. LC-2009, LC-2010, LC-2011: the Link element strikes back
-----
See Jo and fd's ping-pong starting at:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0027.html



5. LC-2023: transformation across character sets
-----
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0014.html and 
replies
- pending a response from Eduardo
- include "encoding" in the list of examples in 4.3.6.1?
- add some more normative statements to emphasize the "don't break 
content" point?


6. LC-2065: opting-out of CT
-----
http://lists.w3.org/Archives/Public/public-bpwg-comments/2008JulSep/0155.html



7. HTTPS links re-writing
-----
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Sep/0013.html


The list of comments:
LC-2026
LC-2027
LC-2085
LC-2028
LC-2029
LC-2030
LC-2015
LC-2031
LC-2016
LC-2032
LC-2001
LC-2033
LC-2004
LC-2024


8. Point on remaining comments
------


9. AOB
------



Received on Tuesday, 30 September 2008 06:10:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 September 2008 06:10:28 GMT