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

[agenda] CT Call Tuesday 7 October 2008

From: Francois Daoust <fd@w3.org>
Date: Mon, 06 Oct 2008 10:02:14 +0200
Message-ID: <48E9C606.2080106@w3.org>
To: public-bpwg-ct <public-bpwg-ct@w3.org>

Thanks for joining the call on time. I noticed we tend to shift slowly 
from 1400Z-1500Z to 1415Z-1515Z...

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

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

1. Quick report on the internal project review

2. HTTPS links re-writing

Possible direction:
- make it clear we do not recommend HTTPS links rewriting
- make it clear it may break in several cases
- impose that proxies correctly handle/refuse invalid certificates
- make it clear that the user will see a confusing "secure" message in 
his browser and an "unsecure" one
- check with the IETF TLS Working Group about RFC 5056 on channel binding

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

3. LC-2078: claim of conformance in a Via HTTP header

4. LC-2019, LC-2034: Applicable HTTP methods (§4.1.1)

5. LC-1997, LC-2006, LC-2014, : Original HTTP headers in X-Device-foo

6. LC-2046: on HTTP headers deletion

7. LC-2041, LC-2080: Servers must return Cache-Control: no-transform 
when it is received, why?

8. LC-2083: Sniffing "rejected" responses (§4.3.3)

9. LC-2084: Receipt of Vary HTTP header (§4.3.4)

10. AOB
Received on Monday, 6 October 2008 07:59:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:30 UTC