16:15:39 RRSAgent has joined #webperf 16:15:39 logging to http://www.w3.org/2010/10/20-webperf-irc 16:15:46 list the agenda 16:18:44 agenda+ Feedback on Privacy Issue w/ Navigation Timing. 16:18:52 agenda+ Next steps to getting Navigation Timing to draft. 16:18:58 agenda+ Getting started with Resource Timing and User Timing. 16:19:04 agenda+ Any other business. 16:21:36 Zhiheng has joined #webperf 16:22:53 biesi has joined #webperf 16:27:40 meeting: Web Performance Working Group Teleconference 16:27:47 present: Sigbjorn 16:27:51 present: Zhiheng 16:27:54 present: NicJansma 16:27:59 present: AndersonQuach 16:28:22 Regrets: JasonWeber 16:28:33 regrets: plh 16:29:14 next agenda 16:30:03 Zhiheng: TonyG has gone thru security review with the Chrome team, suggestions include zero'ing out redirectCount in different origin navigations in the timeline, and to provide a means to disable the interface completely 16:30:26 AndersonQuach: Sounds good, as long as the disable via UI is a non-normative requirement. 16:31:06 Sigborn: We must be safe by default. The timings that reveal off-domain must not be available programmatically. 16:31:22 scribe: AndersonQuach 16:32:11 AndersonQuach: It can be feasible to attack with the same origin and a redirect service. We could remove redirectCount altogether. 16:32:29 AndersonQuach: And disable redirect and unloading timings for different origin. 16:33:07 Zhiheng: We need to hear more feedback from user-agent and security experts about the removal of redirectCount 16:33:23 Zhiheng: where is navigationStart? 16:34:59 Sigborn: What is same domain, same cookie domain? 16:35:02 Zhiheng: Same host 16:35:06 Sigborn: Cookie domain, sub domains of yahoo.com 16:35:17 AndersonQuach: where did we land with navigationStart 16:37:04 NicJansma: A->B->A->A, navigationStart should begin immediately prior the second A 16:37:35 NicJansma: for same domain with different origin redirections 16:37:59 Zhiheng: need to look to clarify navigationStart and redirectStart 16:42:47 AndersonQuach: Zhiheng, can you capture your thoughts and we'll get feedback from Jonas and TonyG? 16:43:30 NicJansma: Anderson and I will follow-up with additional feedback from our security review via mail and for the next meeting. 16:44:02 Sigborn: Should make the same domain be the same as the cookie domain, I will write it up. 16:45:17 Present: Biesi 16:46:51 Next Agenda 16:47:12 AndersonQuach: Let's move the spec to a working draft as all the latest feedback has been incorporated. 16:48:48 AndersonQuach: Let's be explicit that this is not a user-agent benchmark. 16:49:09 Sigborn: Let's say due to the non-normative phases, the individual phases should not be used as a benchmark. 16:49:15 AndersonQuach: Agreed. 16:49:40 Next Agenda 16:52:18 AndersonQuach: Let's simplify the accessing of the ResourceTiming 16:52:53 AndersonQuach: Let's say have a fixed buffer of 1000, have the ability to clear the buffer, and to expand the buffer to cater to WebApps. 16:53:14 Zhiheng: We don't want developers to crawl the page. 16:54:27 AndersonQuach: Agreed, we should have the timing centralized. 16:54:38 Zhiheng: Yup, the object should be easily serialized into a JSON object. 16:54:59 Zhiheng: How can a developer get the timing about a specific image? 16:55:20 NicJansma: Timing of a specific image? 16:55:23 Zhiheng: Yes. 16:56:00 NicJansma: ResourceTiming can have the URL and potentially the id and provide a means to filter based on type and/or id. 16:56:48 NicJansma: Goal for ResourceTiming to get timing that is inaccessible to JS. 16:57:14 NicJansma: We should keep in mind to be able to get the timing for individual elements and the collection. 16:57:36 Zhiheng: Come up with a short summary proposal and review the proposals. 16:58:12 AndersonQuach: I can write that out. 17:00:21 Zhiheng: ResourceTiming has privacy concern as well. To have an HTML header to turn this on. 17:02:08 Zhiheng: implement the allow policy in the http header. 17:02:24 Sigborn: This is possible but difficult to implement as seen in other W3C discussions. 17:03:12 NicJansma: For different origin we can reduce the amount of details, just having fetchStart -> loadEventEnd, not providing additional info via JS. Provide total time to load the content. 17:03:41 Sigborn: Expand definition of Same Origin to include Same Cookie Domain + Sub Domain. 17:06:34 AndersonQuach: 1. We agree to move spec to working draft. 17:06:38 Martijnc has joined #webperf 17:06:48 AndersonQuach: 2. Discuss privacy offline, feedback from Tony and Jonas. 17:06:59 AndersonQuach: 3. Zhiheng will provide a proposal for navigationStart. 17:07:05 AndersonQuach: 4. Anderson will respond with the simplified resource timing proposal. 17:07:14 AndersonQuach: Thanks everyone for meeting! 17:08:00 rrsagent, set logs world-visible 17:08:31 Chair: ArvindJain 17:08:38 rrsagent, draft minutes 17:08:38 I have made the request to generate http://www.w3.org/2010/10/20-webperf-minutes.html AndersonQuach_ 17:09:08 Present+ AndersonQuach 17:09:12 Present+ Zhiheng 17:09:19 Present+ NicJansma 17:09:25 Present+ Sigbjorn 17:09:30 rrsagent, draft minutes 17:09:30 I have made the request to generate http://www.w3.org/2010/10/20-webperf-minutes.html AndersonQuach_ 17:10:00 Present+ ArvindJain 18:22:52 AndersonQuach has joined #webperf 18:22:59 list the agenda 18:27:39 AndersonQuach_ has joined #webperf 18:32:12 rrsagent publish minutes 18:32:24 rrsagent, publish minutes 18:32:24 I have made the request to generate http://www.w3.org/2010/10/20-webperf-minutes.html AndersonQuach 18:33:02 dismiss Zakim 18:33:07 dismiss rrsagent 18:33:13 zakim, please part 18:33:13 Zakim has left #webperf 18:33:18 rrsagent, please part 18:33:18 I see no action items